Midrand Litigation Team

A litigation floor that needed fewer loose versions

The brief came from a small litigation team in Midrand that handled a steady mix of motion work, correspondence and urgent filings. The partners wanted tighter control over affidavits, notices, practice letters and briefing documents, because drafts were moving through email threads and shared folders with too many copy-paste changes. That created avoidable rework, and it made sign-off harder when different people were touching the same matter pack.

We mapped the way the team actually worked, from first instructions to final internal approval. The pattern was not unusual for a busy litigation office in Gauteng: several lawyers on one file, short deadlines, and a need to keep names, case details and annexure references aligned. The brief was to close the gaps where a typo or outdated clause could slip through.

• Practice type: small litigation firm
• Town: Midrand, Johannesburg
• Core documents: affidavits, briefs, letters and internal review packs
• Main control need: version tracking and sign-off discipline

What the team asked us to tighten up

The firm wanted document automation that fit the way litigation work actually moves. Affidavit templates had to carry the right opening structure, matter fields and paragraph options. Briefs needed cleaner matter data, more consistent formatting and a quicker route from draft to review. They also asked for a controlled way to manage internal approvals before anything left the office.

There was a second constraint too. The office needed a setup that could be used by different staff members without each person building their own style of document from scratch. That meant conditional questions, locked clauses where needed and clear rules for who could review, edit or release a document. Secure cloud storage and POPIA-aware handling were part of the conversation as well, because litigation files often carry sensitive personal and matter data.

• Guided questionnaires for matter capture
• Clause bank options for recurring litigation text
• Merge fields for names, dates and matter references
• Review and sign-off controls before release

Templates, clause banks and matter data in one flow

We built the setup around approved templates for affidavits, briefs and internal correspondence. The team could open a matter, answer a guided set of questions and let the system populate the relevant fields. That included party names, file numbers, dates, court references where relevant and the standard wording that the firm reused across similar instructions. When a clause needed to vary, the questionnaire steered the user to the correct option.

Clause banks handled the parts that changed less often, while the template library kept the firm’s preferred structure in place. We also added version control so the office could see which draft was current and which one had already been checked. That mattered when more than one practitioner was working on a file and the team needed a clean way to separate draft text from approved text.

For sensitive litigation material, we kept the storage model disciplined and the access rules practical. Staff only saw the documents they needed for their role. Review notes sat inside the process, which made the handover between drafting and sign-off less messy.

• Affidavit structure with conditional paragraph choices
• Briefing documents tied to matter data
• Internal comment and approval steps
• Central storage for current versions and archived drafts

Six weeks from mapping to live use

The project ran in three stages over six weeks. The first stage focused on mapping the existing documents and finding where the repeated errors lived. The second stage covered template rebuilding, clause bank structure and questionnaire design. The third stage dealt with training, testing and the final move into live use. Each stage built on the last one, so the office could see the shape of the process before the whole team switched over.

Week one was mostly document review and workflow mapping. By week two, the core affidavit and brief templates were rebuilt. Week three covered matter data design and review steps. Week four and five were used for testing with real file types and internal edits. Week six was the handover into daily use, with training for both admin staff and practitioners who needed to create or check documents. A small missing field or a wrong clause flag showed up quickly during testing, which saved later clean-up.

• Week 1: document review and process mapping
• Weeks 2 to 3: template build and matter data setup
• Weeks 4 to 5: testing, corrections and workflow tuning
• Week 6: go-live support and team training

What shifted once the office stopped rebuilding the same paper trail

Once the system was in use, routine drafting came from approved templates and every version was tracked. The main gain was consistency. Affidavits followed the same structure, briefs pulled in the right matter details, and internal sign-off became visible to the whole team. The partners also had a better sense of which version was current, which matters still needed review and where the draft had been paused.

The office reported less duplicated effort on recurring matters and fewer corrections caused by mismatched names or stale wording. Staff who handled administration could prepare the base document with confidence, while the lawyers focused on checking content. For a Midrand litigation team serving clients across Johannesburg, that kind of control matters because the work moves quickly and the file trail has to stay neat.

The setup also gave the firm a cleaner way to train new staff. They could work from the approved template set and follow the same review route every time. That is what keeps a busy litigation office orderly.