Home / SOPs & Documentation
01 · SOPs & Documentation

Documentation Debt: Why Businesses Stop Writing Things Down

The Ops Manual · Updated 2026-07-18

Documentation debt is the gap between what your business knows and what your business has written down. Like financial debt, a bit of it is normal and even sensible — you shouldn't document a process that changes weekly. But left to compound, it gets expensive in ways that never show up on a single invoice.

How the debt accrues

Nobody decides to stop documenting. It happens the same way in almost every growing business:

  • Early on, the founder does everything, so nothing needs writing down — the business and the founder's head are the same place.
  • The first hires learn by sitting next to someone. It works, so it becomes the system.
  • Things change fast; any documents written in year one are now wrong, and wrong documents teach people not to trust documents.
  • Everyone is flat out doing the work, and writing about the work always loses to doing it.
Documentation debt is invisible right up until the person holding it hands in their notice.

What it actually costs

The interest payments are mundane and constant: every new starter takes weeks longer to become useful; experienced staff are interrupted daily to answer the same questions; the owner can't take four uninterrupted weeks off; jobs are quoted, invoiced or closed differently depending on who touches them; and when someone leaves, part of the business leaves with them. None of these arrive as a bill labelled "documentation", which is exactly why the debt survives.

Common failure: responding to this with a documentation blitz — a wiki, a mandate, forty half-written pages in a fortnight, then nothing. Big-bang documentation projects almost always stall and leave behind a graveyard that makes the next attempt harder.

Paying it down without boiling the ocean

  • Start from risk, not completeness. List the five tasks that would hurt most if their person was hit by the proverbial bus — usually money in, money out, access to systems, and whatever the business's core delivery is. Document those first.
  • Use the interruptions as the queue. Every time someone answers the same question a second time, the answer becomes a document that day. You're already spending the explanation time; spend it once more with a record.
  • Attach writing to events. New hire? They document what they learn as they learn it — fresh eyes catch the steps veterans skip. Process changed? Updating the doc is the final step of the change.
  • Timebox it. One process per week, properly, beats ten stubs. A steady drumbeat clears a startling amount of debt in a quarter.
  • Make findable non-negotiable. One agreed home for documents, boring consistent names. A perfect SOP nobody can find is still debt.
In practice: the businesses that get on top of this treat documentation as an exhaust of normal work, not a project. The question shifts from "who will write all this?" to "we just did the thing — where's the note?"

FAQ

How much documentation is enough?

Enough that any critical task can survive its usual person being away for a month, and a competent new starter can reach useful output in weeks rather than months. Most small businesses reach that with a couple of dozen current documents — not hundreds.

Who should own it?

Each document needs a named owner, and one person — often whoever runs operations or admin — owns the system: the home, the naming, the review cycle. Records that carry legal weight, such as employment and safety records, have their own retention rules; check the Fair Work Ombudsman and your state regulator rather than treating internal docs as a substitute.

Official sources