A Soweto practice with a steady stream of repeat work
The client was a family-law-focused firm in Soweto that handled a lot of similar matters each month, from parenting arrangements and separation letters to settlement agreements, consent papers and related correspondence. The team had strong legal judgment, but document production was spread across old files, shared folders and individual staff habits, which made version control harder than it needed to be.
The brief was practical. They wanted recurring document packs that felt consistent from one matter to the next, while still allowing the attorney and support team to tailor key details for each file. They also wanted the setup to suit a busy office, with clear review steps and enough structure for new staff to see where each clause or field goes.
- Practice type: family law
- Town: Soweto, Gauteng
- Main need: repeat document packs with controlled variation
- Users: attorneys, support staff and admin team members
What was blocking clear drafting
Several pain points kept showing up. Matter details were being retyped into letters and agreements, which created avoidable errors when names, dates or address lines changed. Some documents had too many versions saved under similar file names, so staff had to stop and check which draft was current before sending anything for review. Approved wording for the common clauses was collected into one bank.
There was another constraint too. The firm wanted a system that supported family-law work with room for each matter's details. A custody-related letter, for instance, needs different wording from a general instruction letter, and a parenting plan needs more choice points than a standard client update. We kept that in mind while structuring the templates and questionnaires.
- Reduce retyping across repeat matters
- Keep approved wording centralised
- Allow conditional fields where the facts differ
- Make review and sign-off easier to follow
The document packs we mapped and built
We mapped the firm’s common document types and grouped them into recurring packs. That included client intake letters, instruction letters, settlement-related correspondence, affidavit support material, consent wording, agreement templates and standard follow-up letters. We kept the number of screens small. It was to make each document start from a trusted structure, with matter data flowing into the right places.
Clause banks were built for the sections that changed often but still needed consistency. Merge fields handled names, addresses, dates, file references and other matter data. Conditional questionnaire paths were used where the answer changed the document path, so the team only saw the fields that were relevant to the matter in hand.
- Template libraries for common family-law documents
- Clause banks for approved wording
- Merge fields for matter data
- Conditional questionnaires for changing facts
How the review process was kept practical
The review stage needed the same care as the drafting stage. We set the workflow so staff could draft, check and sign off in a set order. Version control made it easier to see which file was current, while the approved templates helped reduce stray wording that had crept in from older precedent files. Secure cloud storage and POPIA-aware handling were part of the working setup, with access kept to the right team members only.
We also designed the structure so the firm could manage updates without rebuilding everything from scratch. When a clause changed or a heading needed to be reworded, the team had a controlled way to update the source template and keep the pack aligned. That mattered for a family practice, where consistency counts but the wording still has to match the matter type.
- Review and sign-off steps built into the flow
- Version control across the template set
- Secure cloud storage for working files
- Access control for sensitive matter data
Onboarding and training for a busy office
The rollout took four weeks from mapping to go-live support. Week one focused on planning, document inventory and the first mapping sessions with the practice team. Week two covered template mapping, clause bank setup and questionnaire design. Week three moved into matter data design, document migration and testing with a few live-style scenarios. Week four was used for user training, admin training and go-live support, so the firm could settle into the new process with real files moving through the system.
Training was split by role because the work was different for each person. Attorneys needed to understand review points and clause choices. Admin staff needed to know where the matter data lived and how the packs were assembled. The onboarding sessions were paced around actual documents the firm used every week, which made the learning more grounded and easier to keep.
- Week 1: planning and mapping
- Week 2: template and clause setup
- Week 3: migration and testing
- Week 4: training and go-live support
What changed for the team after rollout
Once the packs were in use, the firm had a clearer path for repeat documents and a more orderly way to handle edits. Staff no longer had to rebuild routine letters from loose precedents, and the review stage became easier to manage because the same template structure kept reappearing in the same places. That cut down on file searching and helped the team spend less time cleaning up format drift.
The practice also found it easier to hand work between people. A matter could start with one team member, move through the questionnaire and template flow, then reach review with the relevant data already in place. For a family-law practice, that kind of continuity matters because the work often moves between reception, admin, support and attorney review several times before a document goes out.
- Cleaner repeat drafting across common matter types
- Less retyping of names, dates and references
- More consistent layout and clause use
- Easier handover between staff members
We would repeat that setup for another matter like it
On a similar brief, we would keep the first pass focused on the actual documents the firm uses most often. That keeps the build grounded in the work on the floor and gives the team a faster route to everyday value. We would also keep the questionnaire logic tight, because family-law documents can become clumsy if every field is treated as mandatory.
The other point is training. A good system still needs clear handover notes and role-based guidance, especially where several people touch the same file. For a small firm, the best outcome usually comes from a compact setup with disciplined review.
- Start with high-use documents first
- Keep questionnaire paths lean
- Train by role
- Protect the review step from drift
Key facts
| Client type | Family-law-focused small law firm |
|---|---|
| Town | Soweto, Gauteng |
| Project length | 4 weeks |
| Core build | Template libraries, clause banks and conditional questionnaires |
| Data handling | Matter data, version control and secure cloud storage |
| Training | User training and admin training for the team |
