Document assembly without a six-figure system

What does "document assembly" actually mean for a small firm?

It means producing a standard document from a fixed structure plus the details of one job. Engagement letters, quotes, proposals, service agreements, onboarding packs, letters of offer for new staff, renewal notices. If you send the same kind of document more than a few times a month, it is a candidate.

There are three layers in almost every one of them:

• Fixed wording. Your terms, your scope boundaries, your payment conditions. Chosen once, deliberately, and ideally checked by an adviser.
• Merged details. Client name, address, ABN, dates, the job reference, the fee from your own price list. Facts that already exist somewhere.
• Variable drafting. The description of this particular job, a covering paragraph, notes specific to this client. The part that genuinely changes.

Copy-and-edit treats all three the same way, which is where the risk comes from. Assembly separates them.

Why does copying last month's document cause problems?

Because the old document carries more than its structure. It carries the last client's details in places you didn't think to look, wording you changed once for a special case and forgot about, and terms that were current when that version was written.

The failures are predictable:

1. A previous client's name or address survives in a clause, a footer or the file properties.
2. A one-off concession, such as a longer payment term, quietly becomes standard because it was in the file you copied.
3. Your terms change, but only in the version someone happened to update, so three versions are in circulation.
4. Every document takes twenty minutes of careful reading because nobody trusts it.

The fourth one is the cost most owners never count. Track it for a fortnight: how many of each document you produce, and roughly how long each takes from opening the old file to sending the new one. Multiply out to a year. That figure, and how many near-misses you caught along the way, tells you whether this is worth an afternoon.

How do you set this up with tools you already have?

Start with the document you produce most often, not the most complicated one.

1. Collect the last ten versions. Lay them side by side and mark what changed between them. That shows you which parts are really fixed and which are variable.
2. Build one master. Write the fixed wording once, clean, with the current terms. Where a detail changes, put a clearly marked field such as [CLIENT NAME] or a merge field from your word processor.
3. Keep the details in one place. A spreadsheet row, a form response or your practice management or job system. The rule is that a client's name is typed once, not once per document.
4. Handle options as switches, not copies. If some clients get an extra clause, mark it as optional in the master rather than keeping a second template.
5. Lock the master. Store it where only one or two people can edit it, and put a version date on it. Everyone else produces documents from it, never edits it.
6. Check the output against a list. Names, dates, amounts and the optional sections, every time, before it leaves.

Most word processors can merge from a spreadsheet, and most form and job tools can fill a template. I'd get one document working this way for a month before adding a second.

Where does AI genuinely help?

On the variable drafting, which is the slow part that templates can't fill. Given your notes from a call, AI can draft a scope summary, a covering email or a plain-English explanation of what happens next, in your firm's voice if you give it examples. That is real time back, and a person reads it before it goes anywhere.

It is also useful as a checker. Ask it to compare the finished document against the details you merged in and list anything that doesn't match. It won't catch everything, but it is a cheap second pass on the fields that matter.

Where does AI introduce risk?

Anywhere the exact words or the exact numbers matter. AI drafts a wrong figure in the same confident tone as a right one, which is the problem I covered in where AI mistakes cost a small firm.

Keep it away from:

• Your fixed terms. Asked to "tidy up" a contract, it will improve wording that was written that way for a reason.
• Prices and amounts. These come from your price list or job system by merge, never from a model.
• Dates and deadlines, including payment terms and notice periods.
• Anything with legal effect, such as limitation of liability, termination or privacy wording. Have an adviser approve those clauses once and keep them locked.

This is general information, not legal advice. What your engagement letters and contracts need to say depends on your industry, your clients and your obligations, so confirm the fixed wording with someone who advises your business.

The pattern is the one in what AI won't do: it drafts, a person approves, and the parts that carry risk come from a source you control.

When is it worth paying for a dedicated system?

When the template stops being simple. A few signs:

• Many conditional clauses that interact, so a master with switches becomes hard to follow.
• Several people producing documents who need the same controls.
• A requirement to show exactly which version went to whom, and when.
• Signing, storing and sending that you want in one flow rather than three tools.

Compare products on those needs, not on feature lists, and check current pricing and terms directly. If you can't yet name which of those problems you have, you probably don't have them.

What to do next

• Pick the one document you produce most and pull the last ten versions this week.
• Mark the fixed, merged and variable parts, and build a single master from them.
• Decide where client details will live so they are typed once.
• Write down which sections AI may draft and which it may not, and share that with whoever produces the documents.
• If you'd like help working out which documents are worth doing first, the AI Tools Assessment covers it.