Document Generator Module — User Manual
Audience: Attorneys, candidate attorneys, legal secretaries, and knowledge-management staff
Version: 1.0 — October 2026
Module: Mod-Document-Generator
Jurisdiction: South Africa (court and matter document drafting)
Table of Contents
- Introduction
- Getting Started
- How Document Generation Works
- Core Workflow
- Template Suitability and Matter Data
- Practical Guidance for South African Legal Practice
- Troubleshooting
1. Introduction
The Document Generator helps the firm produce court and matter documents from structured templates instead of retyping the same information repeatedly.
Typical generated documents may include:
- summonses;
- notices of motion;
- letters built from matter data;
- standard pleadings;
- other firm templates appropriate to the matter.
The generator uses the matter’s stored information to merge details such as:
- matter number;
- court context;
- party information;
- procedural posture;
- pronouns and entity wording; and
- other template fields available from the matter context.
Generated documents are then filed into the matter document store rather than left floating outside the file.
2. Getting Started
The generator is surfaced through the matter workspace, especially the Pleadings or Court Documents area for litigation matters.
Before generating a document, check that the matter has been properly maintained. Template quality depends heavily on matter data quality.
At minimum, confirm:
- the correct matter is open;
- the court and procedural information are correct;
- the key parties have been captured properly;
- the document type you want has a suitable template.
3. How Document Generation Works
The process has four broad stages:
- Readiness — is the matter sufficiently complete for the chosen document?
- Template selection — which template best suits the court and procedure?
- Merge — the system fills what it can from the matter context.
- Filing — the generated Word document is filed into the matter’s document store as a draft output.
This means the generator is not a blind mail-merge tool. It is matter-aware and deliberately cautious.
4. Core Workflow
4.1 Open the Pleadings / Court Documents Area
On a litigation matter, open the Pleadings tab or equivalent document-generation entry point.
Typical actions available are:
- Generate Document…
- Document Readiness…
- Manage Templates…
If the tab does not appear, the matter may not yet qualify as litigation content or may lack the recorded litigation details required for the extension tab to show.
4.2 Check Document Readiness
Click Document Readiness… before generating if you are unsure whether the matter has enough information.
The readiness check helps identify blockers such as missing:
- party details;
- court details;
- role or procedural data;
- matter context needed by the chosen document.
Use readiness proactively. It is faster to fix the matter record first than to generate a broken document and repair every field manually later.
4.3 Choose a Template
When you open Generate Document…, the dialog loads templates and tries to present those that best suit the matter’s:
- court family; and
- procedure type.
The template list will often prefer relevant templates first. There is also an option to show templates for other courts or procedures if needed.
Each template has:
- a name;
- an origin;
- and a description.
Read the description before generating, especially where multiple templates have similar names.
4.4 Generate the Document
- Select the template.
- Choose the document type for filing.
- Click Generate.
The generator builds the document in the background and prepares it for filing to the matter document store.
If the matter is not ready, the system will stop and direct you back to readiness checking instead of filing an unsuitable document.
4.5 Review Unresolved Placeholders
If the matter has no value for certain template fields, the system can leave visible highlighted placeholders such as [[...]] in the output.
You will be warned before filing such a document.
This behaviour is helpful because it avoids silently inventing data. It tells the user exactly what still needs manual completion.
Typical examples:
- incomplete party descriptions;
- missing dates;
- incomplete court heading details;
- facts that must be drafted manually for this specific matter.
4.6 File the Generated Document
Once accepted, the generated document is filed into the matter document store as a draft-style output.
Benefits of this approach:
- the document is preserved inside the matter file;
- it can be opened from the document store later;
- provenance is recorded;
- staff do not need to hunt for separate local copies.
After filing, open the document, review it carefully, and make any necessary legal edits before issue or service.
4.7 Manage Templates
Use Manage Templates… when you need to:
- add templates;
- rename them;
- customise existing templates;
- remove obsolete templates.
Template management should normally be controlled by authorised users only. Poor template discipline affects the whole firm.
Good template governance includes:
- meaningful template names;
- clear descriptions;
- version control outside ad hoc personal copies;
- legal review of substantive precedent wording.
5. Template Suitability and Matter Data
A document template is only as good as the matter data it relies on.
Data that often matters most
- court selection / court family;
- procedure type;
- party roles;
- organisation form and formal citation details;
- matter number and description;
- dates and hearing information.
Why template filtering matters
A motion-court template may not suit an action matter. A magistrates’ court heading may not suit a High Court document. The system therefore tries to present the most suitable templates first.
Still, the user remains responsible for choosing the correct precedent.
6. Practical Guidance for South African Legal Practice
Treat generation as a drafting accelerator, not a legal substitute
The system can assemble structure and known facts. It does not replace professional legal review.
Keep matter roles and party descriptions current
Generated pleadings depend on party data being correct. A badly maintained matter record leads to bad pleadings faster.
Use readiness before urgent filing work
If a document must go out urgently, check readiness first so you do not discover a structural omission after generation.
Review unresolved placeholders carefully
A document with unresolved placeholders should never be issued without checking and completing those fields.
7. Troubleshooting
No suitable templates appear
The matter may not yet have enough court or procedure data, or there may genuinely be no template loaded for that combination.
The readiness check shows blockers
Open the matter record and complete the missing details before generating again.
The document generated but contains highlighted placeholders
The matter did not contain values for those fields. Complete them manually in the document and consider whether the matter record also needs updating.
The document did not file to the matter store
Check whether document types are configured and whether the matter document store is available.
The wrong template was used
Regenerate using the correct template and remove or clearly supersede the mistaken draft according to your document-control process.