The brief from a busy labour practice
The firm in Kempton Park handled day to day employment work for small and medium employers, with a steady mix of contracts, letters of demand, policy letters and related correspondence. Their team wanted a document process that kept the wording consistent, reduced manual editing and made it easier to move from a new instruction to a ready draft without retyping the same material every time.
The brief was practical. They needed a structured system for approved templates, clause choices and matter data capture, with enough control for a lawyer to review each document before it left the office. They also wanted the setup to suit a small team, where one person may be collecting information while another is checking the final wording.
- Client type: labour and employment law practice
- Town: Kempton Park, Gauteng
- Main document sets: employment agreements and standard correspondence
- Working style: guided drafting with review and sign-off
Where the old process slowed the room down
Before the setup, the firm relied on manual copying from old files, desktop folders and a handful of trusted precedents. That worked for a while, but it made version control awkward and left too much room for small changes to be missed when a matter moved from draft to final form. A quick update in one place did not always reach every saved copy.
They also wanted cleaner intake. Labour matters often start with a few core details that drive the whole document, such as employer details, employee details, role title, start date, notice period and signature parties. If those fields sit in different places each time, the drafting process becomes slower and the risk of an odd omission goes up. In a firm that handles several files at once, that sort of drift is hard to manage.
- Manual drafting created version drift
- Key matter details were being retyped across files
- Approved clauses were reused in different ways
- The team wanted a cleaner sign-off path before issue
Template mapping for employment and correspondence
We mapped the firm’s core employment agreement set into guided templates with merge fields, conditional sections and linked clause banks. That let the team choose the right options for a matter while keeping the base wording controlled. Standard correspondence followed the same pattern, so letters could be assembled from approved text blocks.
We also set up document fields for the matter data that the firm used most often, then matched those fields to the wording inside each template. Where a clause needed to appear only in certain cases, the conditional logic handled that without exposing extra clutter to the drafting user. The result was a neater working file with less backtracking between notes, drafts and final copy.
- Employment agreement templates were mapped to matter data
- Clause banks were grouped by use case
- Conditional sections only appeared when needed
- Standard correspondence used the same drafting rules
Review steps, version control and secure storage
The practice wanted a proper check before any file moved out of draft. We set up review and sign-off steps so a senior user could check the wording, confirm the correct template version and release the final document only when the file was ready. That kept the process steady and light for each matter.
Secure cloud storage was arranged for template files, working drafts and approved versions, with POPIA-aware handling and clear permission grouping for the team. We kept the file structure simple enough for daily use, but organised enough that older versions could be traced if needed. That mattered for a labour firm where one letter may be revised several times before issue.
- Review steps were built into the workflow
- Version control kept approved templates separate from working drafts
- Secure cloud storage was used for controlled access
- POPIA-aware handling guided the setup of stored matter data
The four week build and handover
The project ran over four weeks. The first week was spent on template mapping and the main data fields. The second week covered clause bank setup and the first round of questionnaire design. In week three, we tested the draft paths with sample labour matters and refined the wording flow where the team wanted a cleaner sequence. The final week focused on user training, admin training and go-live support.
Training covered both the people drafting files and the people managing the templates. That split mattered, because a document system can only stay usable when the admin side knows how to update clauses, adjust versions and keep the library tidy. We also showed the team how to handle document migration from older precedents into the new structure without losing useful wording.
- Week 1: template mapping and data fields
- Week 2: clause bank setup and questionnaire design
- Week 3: testing with sample matters and workflow tuning
- Week 4: training, migration and go-live support
What changed once the templates were in use
The firm now had a cleaner route from instruction to draft. Employment agreements could be prepared from a guided workflow, and standard correspondence followed a more consistent format across the team. That reduced the amount of rework caused by copy and paste errors, and it gave the practice a steadier way to manage recurring labour documents.
They also gained better control over how documents moved through the office. The same approved wording could be reused more carefully, while the review step made it easier to keep a final check before issue. For a small labour firm, that combination of structured drafting and practical oversight makes the workday less fragmented.
- Drafting was more consistent across users
- Routine letters followed standard wording
- Approved clauses were reused with less manual editing
- The final check sat inside the workflow
Lessons this labour firm rollout taught us
We would use the same sequence again for another small labour practice, starting with the documents that are used most often and building out from there. Employment agreements, letters of demand and standard correspondence are usually the best place to begin because they show the value of clause banks and matter data quickly. Once those pieces are settled, the rest of the library becomes easier to organise.
We would also keep the training split between drafting users and administrators, because that separation helps the system stay tidy after go-live. A neat template library, clear review steps and a sensible migration plan go a long way when a firm works across several labour files at once.
- Start with the highest use document set
- Keep the questionnaire short and matter led
- Separate drafting training from admin training
- Leave the library structure easy to maintain
Key facts
| Project | Kempton Park labour firm |
|---|---|
| Town | Kempton Park, Gauteng |
| Project scope | Employment agreement templates and standard correspondence workflows |
| Delivery window | 4 weeks |
| Core setup | Template mapping, clause banks, questionnaires and matter data |
| Support focus | Review steps, version control, training and go-live support |
