A Centurion office with too many repeat drafts
The project came from a general practice in Centurion that was spending too much time retyping the same legal paperwork. The team handled a steady mix of client instructions, short-form agreements, letters of demand and permission letters, with each file needing careful wording and a paper trail that made sense when a matter moved from first instruction to sign-off.
The brief was plain enough: reduce duplicate typing, keep document versions under control and make sure the office could work from approved wording. The practice also wanted a clearer way to capture matter details, so the right names, dates, identities and property details could flow into the document without constant rework.
- Client type: general legal practice
- Town: Centurion
- Document mix: letters, agreements and permissions
- Main aim: less retyping, cleaner drafts
The drafting rules we had to fit around
The office needed a system that would support routine legal work without getting in the way of the lawyers and support staff who already knew their files. That meant keeping the templates familiar, using clause banks for common wording and building questionnaires that asked only for the matter data needed for each document type. No one wanted a long form full of irrelevant fields that slowed the team down.
We also had to keep the review path clear. Drafts needed to pass through the right checks before a document was issued, and older versions had to stay traceable. Because the practice worked with sensitive client information, we planned secure cloud storage and POPIA-aware handling, with access controls that matched the office structure.
- Approved template libraries for routine files
- Clause bank setup for standard wording
- Conditional questionnaires tied to the document type
- Version control for edits and sign-off
- Secure storage with permission-based access
How we set up the document flow
We began by sorting the office’s document categories into a usable library. Standard letters sat in one group, agreements in another and permissions in a third, with each item broken down into the fields and clauses that changed from matter to matter. That let us build templates with merge fields for names, reference numbers, addresses, dates and other file-specific details.
After that, we worked through matter data design and template mapping. The same core information was used more than once, so it had to be captured in the right order and stored cleanly for reuse across the file. Review and sign-off steps were added where they mattered, especially for documents that moved from a draft state to an issued state. We then tied in document migration, so older working files could be brought into the new structure without leaving the team with half-finished records.
- Template mapping for recurring office documents
- Matter data design for repeated file information
- Document migration from old working files
- Review and sign-off steps before issue
- Merge fields for accurate populated drafts
Training the team without slowing the office
The rollout took place over six weeks. The first two weeks were spent on onboarding planning, template mapping and clause bank setup. Week three focused on questionnaire design and matter data design, with the office checking that the questions matched the way their files were opened and managed. Week four covered document migration and workflow tuning, while the last two weeks were used for user training, admin training and go-live support.
The training needed to be practical. Staff had to know where to enter details, how to choose the right clause and how to spot a draft that needed another review before it was issued. The admin side also needed attention, because even a good template setup becomes messy if access, naming and version habits are not handled properly.
- Week 1 to 2: onboarding planning and template mapping
- Week 3: questionnaire and matter data design
- Week 4: document migration and workflow tuning
- Week 5 to 6: user training, admin training and support
What changed once the templates were in use
Once the new structure was in place, the office could prepare standard letters and agreements with less repetitive typing and far fewer version mix-ups. The staff had one place to work from, which made it easier to keep the same wording across similar matters while still adjusting the parts that had to change from file to file. The change was especially useful for permissions and short agreements, where a missed detail can force extra corrections later.
It also helped the team keep control of file information. Matter data was entered once and carried through the document, which reduced copy errors and gave the office a tidier record of what had been issued. For a busy Centurion practice, that meant less manual sorting and a more settled way of handling routine drafting work.
- Less repeated typing across routine documents
- Cleaner file data carried into drafts
- More consistent wording across similar matters
- Better control over working versions
The follow-on work we would keep in the mix
If we were handling a similar general practice again, we would keep the same order of work: map the document set first, then build the questionnaire logic, then tighten the review steps before any wider rollout. That sequence keeps the team working from real office habits.
We would also keep the ongoing helpdesk and template updates in scope from the start, because legal offices do not stay still for long. New letter types appear, old wording gets revised and staff turnover means the system has to remain understandable to someone joining the file team later. We kept a steady support layer in place after the setup.
- Keep the template library short and usable
- Update clause banks as office wording changes
- Review permissions and access as staff roles shift
- Maintain support for new and revised documents
Key facts
| Project | Centurion General Practice |
|---|---|
| Town | Centurion |
| Client type | General legal office |
| Delivery scope | Template libraries, clause banks, questionnaires and matter data design |
| Rollout period | 6 weeks |
| Document types | Letters, agreements and permissions |
