The brief from a one-lawyer practice handling mixed files
The practice dealt with a spread of matters, from client agreements and letters of demand to lease schedules, wills and transfer related paperwork. The owner wanted a setup that would keep drafting orderly with a short admin load per matter.
The main constraint was volume, or rather the lack of it. A sole practice does best with a light system and a short handover. It needs enough structure to stop retyping the same material, while leaving room for judgment where the facts change from file to file.
- One principal user drafting across several matter types
- A mixed document set
- Need for cleaner version control and review steps
- Preference for a compact setup that would not slow daily work
What we mapped before any templates were loaded
We first mapped the common matter data points that kept showing up across the practice. That included client names, property details, dates, party details, reference fields and a small set of variable clauses that could be inserted or withheld depending on the brief.
From there we designed conditional questionnaires so the right prompts appeared only when they were needed. If a file called for a lease, the workflow asked for lease terms and property details. If it was a demand letter, the flow focused on parties, background facts and relief sought in the draft. The form was kept short, with only the items that applied.
- Template mapping for the most used document families
- Clause bank setup with reusable wording blocks
- Questionnaire design that kept forms short and focused
- Merge field structure for names, dates and matter references
A lean build for daily drafting without clutter
We loaded a compact library of approved templates and linked them to the questionnaire flow. The setup used merge fields for recurring details and condition rules for sections that only belonged in certain matters. That way, the practitioner could move from intake to a draft without retyping the same information into every page.
Version control formed part of the routine from the start. Drafts could be updated, checked and signed off in a clearer sequence, which matters when a sole practitioner is also the person who reviews, edits and sends the final copy. Secure cloud storage kept the working files together and reduced the chance of a draft sitting in a loose folder or under an unclear file name.
- Approved template library for repeat use
- Clause bank entries grouped by document type
- Draft review and sign off steps built into the process
- Secure cloud storage with POPIA-aware handling
Training that fitted a small office rhythm
The onboarding was kept practical and direct. We covered how to pick the right template, where to update matter details and how to check the merged draft before release. The training also included admin handling, so supporting records and template changes could be kept in step with the main drafting work.
Because the practice was small, we kept the handover focused on habits the owner could sustain alone. There was no need for a large internal approval chain. The system was shaped around a simple drafting sequence that matched the pace of a solo file load and left less room for duplicate work.
- Onboarding planning for one decision maker
- User training on live drafting steps
- Admin training for template upkeep and file control
- Go-live support during the first active use period
Four weeks from mapping to live use
The work ran over four weeks in a steady sequence. Week one covered discovery and template mapping. Week two focused on clause bank setup and questionnaire design. Week three dealt with document migration and the first draft tests. Week four covered training, go-live support and the first round of workflow tuning.
That timeline suited a sole practice because the work could be fitted around the normal file load. The draft set was lean, but it still needed care. A small system can drift fast if no one cleans up field names, clause wording or document labels while it is being used.
- Week 1: mapping and intake structure
- Week 2: templates, clauses and question flow
- Week 3: migration and draft checking
- Week 4: training, go-live support and tuning
What changed in the day-to-day drafting flow
The immediate change was less repetition. The practitioner no longer had to rebuild standard text for every file, and common details were pulled into the draft through fields that matched the questionnaire. That cut down on small typing slips and made the first draft easier to review line by line.
It also improved control over the working documents. When the same templates and clause blocks are used in a single location, it becomes easier to track what was changed and why. The practice could keep its common work moving, with each matter starting from approved wording.
- Fewer repeated drafting steps across common files
- Cleaner first drafts with less manual re-entry
- More consistent use of approved wording
- Better visibility over version changes and final sign off
What we would use in a similar sole practice setup
We would keep the library small at the start and build only the documents that the practice uses often. A lean setup is easier to learn and easier to maintain, especially when one person handles both the legal work and the admin side. The moment the template set grows too fast, the system becomes harder to use and less reliable.
We would also keep the questionnaire design strict, so each field has a purpose and every draft pulls only the data it needs. That gives the practitioner a cleaner working rhythm and makes later updates more manageable. For a sole practice in Randburg, the value sits in less repetition, clearer drafts and a better grip on the files already on the go.
- Keep the first template set narrow and practical
- Build clause banks around real drafting patterns
- Use plain field names that are easy to scan
- Reserve admin steps for changes that matter
Key facts
| Project type | Lean template setup for a sole practitioner |
|---|---|
| Town | Randburg, Johannesburg |
| Practice size | Single principal user |
| Delivery window | 4 weeks |
| Core build | Template libraries, clause banks, conditional questionnaires |
| Document scope | Contracts, letters, wills, leases and conveyancing paperwork |
