What the Boksburg team required from the project
The office handled leases, related letters and supporting property documents for clients in and around Boksburg, with work often moving between attorneys, secretaries and admin staff. Their main concern was consistency: the same matter could be opened by different people, and each handover created a new chance for a missing clause, an old version or the wrong party details.
The brief was to build a practical document setup for lease drafting and approval paths, without forcing the team into a heavy process. They wanted guided inputs for the details that change from matter to matter, while keeping approved wording in a central template library and clause bank. They also wanted a cleaner review step before any document went out.
- Lease templates with fixed clauses and editable matter fields
- Approval paths for internal review before release
- Structured clause banks for common property wording
- Version control for drafts, edits and final copies
How we mapped the property documents
We started by breaking the property work into the document types used most often in the office. That included lease agreements, letters linked to lease matters, notices, and supporting paperwork that needed the same names, dates and property references repeated with care. The mapping stage showed where the team wanted standard wording and where they needed room for matter-specific changes.
From there, we set out the data fields that would feed each document. Party names, erf details, lease dates, payment terms and signature blocks were separated into clear inputs, so the drafting screen would ask for the right information in the right order. That cut down on free typing and made it easier for staff to check whether the file was complete before it moved forward.
- Conditional questionnaires for lease type and matter details
- Merge fields for names, dates and property references
- Standardised sections for recurring lease wording
- Drafting paths that followed the office review process
What we supplied for the lease drafting workflow
The setup covered template libraries, clause bank structure and review steps that suited a small property practice. We also added a clear sign-off sequence, so drafts could be checked before final issue. Where the team needed more control, we built conditions that opened only the sections relevant to that matter, which kept the form shorter and easier to work through.
We also arranged matter data fields for the information the office reused across a file. That meant the same client details and property details could flow into several documents without retyping. Secure cloud storage was set up for the approved files and working drafts, with general POPIA-aware handling built into the workflow and access rules.
- Template library for leases and supporting letters
- Clause bank setup for common property wording
- Review and sign-off steps for draft control
- Secure storage for working and approved documents
Onboarding inside the office in Rosebank and Boksburg
The implementation was run over several weeks, starting with planning and template mapping, then moving into questionnaire design and document migration. Once the first templates were ready, we trained the staff who would prepare drafts, and then trained the people responsible for admin checks and updates. The property office wanted a setup that people could learn without long interruptions to the workday.
We also adjusted the workflow as the team tested it with live matters. In practice, the office found that some fields were being asked too early, while other details needed to be collected before the lease could move to review. Those changes were folded into the questionnaire design and the approval path, so the final process matched the way the office already handled property files.
- Week 1 and 2: planning, template mapping and clause review
- Week 3: questionnaire design and matter data structure
- Week 4: template migration, staff training and go-live support
- Follow-up tuning: workflow adjustments and template updates
What changed for the property practice
After the rollout, the team had a clearer lease drafting path and fewer opportunities for version confusion. Staff could start from a guided template, fill the required fields and move the file through the agreed review path before issuing it. That made the drafting side less dependent on whoever happened to be free at the time.
The office also had a neater way to handle repeat property wording. Common clauses stayed in the bank, but the wording could still be controlled by the approved template and the review step. For a busy property practice, that meant less rework on routine matters and a cleaner record of what had been drafted, checked and signed off.
- More consistent lease drafts across the team
- Cleaner handovers between drafting and review
- Better control over clause reuse and document versions
- Less time spent fixing avoidable formatting and wording errors
What we would use on a similar property file
On a similar brief, we would keep the core approach the same: map the documents first, then build the questions around the matter data that actually drives the lease. That gives the office a drafting flow that stays practical when several people touch the file and the details need to remain exact.
We would also keep approvals brief and clear. Property work needs careful checking, so we kept the review step to a short, set order. A tight workflow, controlled clause bank and clear version history are usually enough to keep the office moving without adding noise.
- Start with the most common lease and letter types
- Keep matter fields narrow and specific
- Use approval steps only where they are needed
- Update templates in one place
Key facts
| Client type | Property law office |
|---|---|
| Town | Boksburg |
| Project focus | Lease drafting templates and approval paths |
| Core setup | Template libraries, clause banks, questionnaires and version control |
| Timeline | Several weeks from planning to go-live support |
| Base | Rosebank, Johannesburg |
