A practical rollout map before any build work starts
Onboarding Planning gives the project a clear working order. We look at the firm’s document types, team roles, matter flow and the places where documents are still assembled by hand. That includes contracts, letters, wills, leases, letters of demand and conveyancing paperwork where relevant.
The plan puts the rollout in a set order. Some firms need a narrow first stage for one practice area, while others need a wider setup across several document sets and offices in Johannesburg, Pretoria, Cape Town, Durban or Bloemfontein. The plan sets what is included, what waits for a later phase, and which people need to review each step before anything goes live.
- Scope definition for the first release
- Document family sorting by practice area
- Priority list for high use templates
- Review points for legal and admin teams
What we map into the plan
We map the parts that shape the system behind the documents, including template libraries, clause banks, questionnaire paths, merge fields, matter data fields, version control, approval steps and secure storage requirements. Where a firm works with different drafting habits across branches, those differences are noted early so the build does not force one office into another office’s way of working.
We also note how matter information is captured, who checks the output before issue, and which items need sign-off by a principal or senior practitioner. If migration is part of the rollout, the planning stage identifies which existing files, templates or clause sets need cleaning before import.
- Template structure and naming rules
- Clause library structure and ownership
- Questionnaire logic and branch specific fields
- Approval, tracking and archive steps
How the planning stage moves through the office
The process usually starts with a working session around the current drafting process. We look at the forms, letters and agreements that appear most often, then track how instructions move from attorney to administrator and back again. From there, the rollout plan is written as a practical sequence: what gets mapped, what gets reviewed, what gets tested and what gets signed off.
Once the shape is agreed, the team can move into template mapping, questionnaire design or clause bank setup with less rework. Onboarding gives the firm the features it will use and lines up the document flow so the software supports the way the practice already operates, while making room for cleaner control and better version history.
- Current process review
- Gap notes for manual drafting steps
- Rollout staging by team or document type
- Sign-off list for decision makers
What the planning deliverable covers
The planning output is a working brief for the rollout. It sets scope, priorities and technical notes in everyday terms, so the build team and the law firm are looking at the same instruction set. It is also where practical limits are set. Some document groups need immediate attention, while others are better handled in a later phase after the first live set is stable.
For firms with multiple attorneys or several branches, the plan can separate admin tasks from legal review tasks, and separate the core document set from the longer tail of specialised material. That helps keep the first release manageable without losing the wider picture.
- Document list for phase one and later phases
- Field list for matter data capture
- Review matrix for who approves what
- Notes on storage, access and confidentiality handling
Timing, pricing and project shape
Planning work is usually priced as a defined project stage, based on the size of the document set, the number of people involved and how much existing material needs sorting before the build. A small firm with a tight set of core templates will need a different scope from a practice that wants several branches, several users and a broader document library in play. The fee approach reflects that difference, with each firm quoted on its own shape.
The delivery timeline depends on how much material is being reviewed and how many decisions must be signed off during planning. The work is best treated as a structured setup phase. Where there are legacy templates or older clause sets, more time may go into sorting structure and removing duplication before any configuration begins.
- Project priced against scope and complexity
- Planning is separate from build and migration work
- Legacy material can be reviewed during scoping
- More document families mean more planning depth
Aftercare once the rollout plan is signed off
After the plan is approved, the firm does not get left with a loose brief. The next step is usually template mapping, clause bank setup or questionnaire design, depending on the agreed sequence. If questions surface while the work is being built, the original planning notes keep the project tied to the same scope and reduce drift.
Aftercare also matters when the firm starts using the system for live matters. Early use often shows where labels need tightening, where a field should move, or where a review step needs one more checkpoint. That is why the plan is written to support the whole rollout.
- Hand-off notes for the build phase
- Reference point for later template updates
- Support for early live use issues
- Revision notes where process changes are needed
Key facts
| Service area | Onboarding Planning for legal document automation |
|---|---|
| Typical users | Small law firms and multi-office practices |
| Core output | Scope, priority and rollout plan |
| Documents covered | Contracts, wills, leases, letters of demand, conveyancing paperwork |
| Key build inputs | Template libraries, clause banks, questionnaires, merge fields, matter data |
| Location | Rosebank, Johannesburg, with work for firms across South Africa |
