What belongs in a template update request
A good request names the document, the matter type and the exact part that needs attention. That might be a contract clause, a will paragraph, a lease condition, a letter of demand section or a piece of conveyancing wording that no longer matches your internal approval line.
Include the current wording, the preferred wording and any trigger that controls when the text appears. If the change affects merge fields, conditional sections, signature blocks or clause bank references, mention that too so the update follows the structure already sitting in the template library.
How the update moves through our side
We look at the approved version, the linked clause bank items and any questionnaire path tied to that document. Small wording changes often sit in one place, while logic changes can touch several fields, conditions or version notes.
- Check the document name and version in use
- Review the clause, field or rule that needs revision
- Adjust the template, questionnaire or matter data link
- Keep a clear version trail for review and sign-off
Where a change affects more than one template, we treat each linked document carefully so the same wording does not drift across different matter types.
Details that make the update easier to process
Send the source text, the new text and the reason for the change. If your practice uses internal style notes, a precedent mark-up or a specific approval route, add that as well. For teams in Johannesburg, Pretoria, Cape Town, Durban or Bloemfontein, it helps to note whether the change should apply across all offices or only to one working group.
- Document name and version number
- Clause bank reference, if there is one
- Whether the change is wording only or logic based
- Any related templates that should be checked too
That level of detail keeps the update close to the approved precedent and reduces back-and-forth inside the drafting team.
When the request touches questionnaire logic
Some changes also affect fields, logic or the approval path. A new conditional question, a different answer path or an updated merge field can change what appears in the final document. Those requests need the question text, the answer options and the point where the logic should branch.
If the change affects client-facing forms, internal matter data or document assembly rules, we work through the sequence step by step. We update the questionnaire with the template, so the output matches the version your team reviews.
Secure handling and version control around the change
Template work often involves matter details, names, dates and other confidential content. We keep the file handling tied to secure cloud storage and POPIA-aware practices, with version control that shows what changed and where.
That matters when several people review the same precedent. One person may be checking the clause bank, another the merge fields and another the sign-off copy, so the history of the edit needs to stay clear and readable.
What to send for a clean handover
Use our contact form and attach the files or text you want updated. If you have a marked-up precedent, a screenshot of the current questionnaire or a note on the workflow step that needs changing, include that with the request.
- Current template or clause wording
- Requested wording or logic change
- Any linked documents that use the same clause
- Notes on approval, review or sign-off
Once the request is logged, the update can be handled alongside the rest of the document set, whether it sits in onboarding, ongoing support or a broader workflow tuning task.
