Copying last month’s document: the riskiest template

Copying last month’s finished document and overtyping the values is the most common way small offices reuse a template, and the riskiest. Every field you fail to overtype keeps the previous client’s data, and the result looks exactly as finished as a correct document. The fix is not more care. It is a different order of work.

Why offices reuse documents this way

The habit is rational. The finished document from last month is already right: the wording, the clause order, the fonts, the layout that took an afternoon to settle. Copying it costs nothing and requires no tool, no setup and no learning. Open, save as, overtype the name, done. For a busy office it is the path of least resistance, which is why almost everyone does it. The problem is not laziness. The problem is that the method has a failure mode that behaves differently from every other typing error.

The leftover: an error class of its own

A normal typo produces a wrong value: a misspelled name, a swapped digit. A leftover produces a valid value that belongs to someone else. The previous client’s name is spelled correctly. Their identity number has the right number of digits. Their address is a real address. Nothing about a leftover looks wrong, because nothing about it is wrong in form. It is only wrong in fact, and only someone comparing the document against today’s case can see that. Spellcheck passes it. Grammar check passes it. A quick skim passes it.

• The second and third mention: you overtype the name on page one and miss the same name in a clause on page four.
• Headers and footers: Word edits them in a separate view, so a party name or case number sitting there survives every pass through the body text.
• The amount in words: the figure gets updated, the spelled-out amount two lines later does not, and the document now contradicts itself.
• Dates in the signature block, far from the dates you were thinking about.
• The file itself: last month’s client in the file name or the document properties, visible to anyone the file is sent to.

Why proofreading does not catch leftovers

Proofreading hunts for things that look wrong, and a leftover does not look wrong. Worse, the person proofreading has read this document dozens of times, so the eye slides over the settled text at speed. A familiar name in a familiar position reads as correct precisely because it is familiar. Some offices catch leftovers with a second reader who knows the current case, which works but spends a second professional’s time on every document. Most offices catch them later, and later is the expensive place: at signing, in front of the client whose document carries a stranger’s name.

A safer order of work

The leftover exists because the starting point is full of old data. Change the starting point and the error class disappears. The safer order of work costs a little discipline up front and nothing after.

• Keep one clean master per document type. Never produce a document by editing a finished one.
• In the master, make every changing value visibly empty: a blank, an underscore run, or a bracketed label. Empty is the point; empty cannot be mistaken for filled.
• Fill from the source materials in front of you, never from memory.
• Review the filled values as a list against the sources, instead of re-reading prose you know by heart.
• Save the result under the new matter’s name immediately, before the first edit, so the file never masquerades as the old one.

Notice what changed. In copy-and-overtype, a missed field silently keeps wrong data. In fill-from-clean-master, a missed field stays visibly empty. Same lapse of attention, opposite outcome: one failure hides, the other announces itself.

The short version

Copying a finished document seeds the new one with old data, and every field you miss keeps it: correctly spelled, plausibly formatted, invisible to proofreading. Work in the other direction. Start from a clean master with visibly empty fields, fill from today’s sources, review the values as a list, and rename the file before you touch it. Then a missed field is an empty one you can see, not another client’s data you cannot.