Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. Our Generated Documents Break the Firm's Numbering and Styles in Word. How Do We Fix It?
Problems We Solve

Our Generated Documents Break the Firm's Numbering and Styles in Word. How Do We Fix It?

Legal tech products that generate Word documents break firm numbering, styles and clause references. We build output on the firm's own templates.

Updated 3 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Generated Word documents break house style because your product writes text with direct formatting instead of the firm's styles and numbering, so clause numbers restart, cross-references fail and secretaries spend an hour fixing each document. We build output on the firm's own templates, using their named styles, multilevel numbering and fields, and check every document before it reaches the fee earner.

A draft that needs an hour of fixing

Your product drafts a facility agreement from a term sheet. The words are good. When the associate opens the Word document, the clause numbering is typed as plain text, so inserting a clause means renumbering by hand. Schedules restart at 1 in the wrong places. Cross-references say see clause 14.2 as fixed text, which is wrong as soon as anything moves. The font is close to the firm's house style but not quite, and the defined terms are bold in some places and not others.

The associate sends it to their secretary, who rebuilds it in the firm's template. The time your product saved on drafting goes into formatting.

Why generated documents fight Word

Law firm documents rely on Word features that are easy to lose when generating documents in code: styles, multilevel list numbering, fields for cross-references, and templates with the firm's settings.

  • Text is written with direct formatting such as font and size, not the firm's named styles.
  • Numbering is written as text rather than using Word's numbering linked to heading styles.
  • Cross-references are typed as numbers, not as fields that update.
  • Documents start from a blank file, not the firm's template with its styles and settings.
  • Each firm's house style differs, and your product has one output format.

What broken formatting costs

Fee earners judge a drafting product by the document they open. If it needs rebuilding, they stop using the product for anything important, however good the text. Secretaries and document production teams resent the extra work, and they are often the people who decide whether a tool gets used in practice. Formatting errors that survive, such as a wrong cross-reference, can also make it into documents sent to the other side.

The problem compounds on long documents and later rounds. A facility agreement or a share purchase agreement goes through many turns of drafts, and each turn adds manual fixes on top of broken structure. By the third draft, nobody can trust the numbering, and the document production team rebuilds it from scratch, which is the work your product was supposed to remove.

How we build output that fits the firm's templates

What we build generates documents inside the firm's own Word setup, rather than imitating it.

  1. Firm templates loaded into your product: the firm's .dotx files with their styles, numbering definitions and settings, for each document type.
  2. A style mapping per firm: your product's structure (clause heading, sub-clause, definition, schedule heading) mapped to the firm's named styles.
  3. Numbering applied through the template's multilevel lists linked to heading styles, so inserting a clause renumbers everything automatically.
  4. Cross-references written as Word fields pointing to bookmarked clauses, so they update when clauses move.
  5. Defined terms formatted by style, consistently, with an optional check that every defined term is defined.
  6. A validation step on every generated file: numbering continuity, broken references, direct formatting outside allowed places, and style use, with problems flagged before the fee earner sees the document.
ProblemHow the output handles it
Clause numbers typed as textWord numbering linked to heading styles
Fixed cross-referencesFields to bookmarks that update
Font close to house styleFirm's own named styles from its template
Schedules restart wronglyNumbering definitions from the template
Inconsistent defined termsStyle-based formatting and a definition check

We build this with the firm's document production or knowledge team where possible, because they know which styles matter and which are legacy.

The facility agreement, second time

The associate generates the draft again. It opens in the firm's template with its styles. Clause numbers are live, schedules are numbered correctly, and cross-references are fields. They insert a new clause 9, and everything after it renumbers, including the references. The secretary opens the document, checks the styles pane, finds nothing unusual, and moves on to other work. The validation report attached to the draft shows no problems.

Is formatting undoing your drafting product?

  • Fee earners send your drafts to secretaries to rebuild.
  • Clause numbers in generated documents are plain text.
  • Cross-references do not update when clauses move.
  • Every firm gets the same formatting from your product.
  • You do not check generated files before users open them.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Can you work with firms' existing Word templates?

Yes. We load them as they are and map your product's structure to their styles, rather than asking the firm to change.

What about firms with messy templates?

Some templates have legacy styles or broken numbering. We tell you what we find and work with the firm on which styles to use.

Does this work with document assembly tools the firm already has?

It can sit alongside them. Where a firm uses a document assembly product, we look at whether output should go through it instead.

What do you need from us?

Your document generation code, sample outputs, and templates from a few target firms.

Keep reading

More on Problems We Solve

Start here

Tell us what is slowing your legal tech product inside law firms

Describe what your product does for law firms, which systems it has to work with and where deals or rollouts get stuck: security reviews, integrations, adoption or support. We will tell you what we would build and what we would not, and if the answer is a document or a process rather than software, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →