What it means
The phrase comes from workplace culture rather than from accounting textbooks. It describes the instinct that when something might go wrong, the safest move is to make sure there is a record showing you followed the rules, flagged the concern or obeyed an instruction.
Many employees do it, and most managers have seen it. There is a legitimate side.
Clear records, sign-offs and written approvals are core parts of internal control, the system of checks that stops errors and fraud. A finance manager who emails the CFO about a risky accounting treatment and keeps the reply is doing good practice, not just self-protection.
The problem starts when documentation replaces judgment. People copy in ten colleagues so no one can say they were not told, reports are filled with caveats until they say nothing and decisions wait for approvals that add no value.
The business bears the cost in slower processes, higher overhead and lost opportunities. It also changes behaviour around risk.
If staff fear being blamed for any error, they may avoid raising bad news or admit uncertainty, because they expect to be punished rather than thanked. Over time, the organisation hears about problems later, when they are bigger and more expensive.
Leaders can reduce harmful defensiveness by making it safe to report problems, setting clear decision rights and distinguishing between records that add control and records that merely add cover. Finance teams can test this by asking, for any approval step, what error it would catch and how often it has caught one.
Ultimately the useful question is not whether to keep records, but who the record is for. If the answer is the auditor, regulator or future decision maker, it is probably good practice.
If the answer is only the author's protection, it may be worth redesigning the process.
In practice
Real-world examples.
Example
A junior analyst sends a 40-page forecast pack to eight people with the subject line "FYI, as discussed". The actual recommendation is buried on page 31, and none of the recipients feels responsible for acting on it. Nothing in the pack is false, but nothing in it helps the reader decide.
Example
A finance manager emails the CFO that a customer's $120,000 invoice may not be collectable, and asks whether to create a provision. The reply is saved with the working papers, giving a clear record and a decision. This kind of note protects the writer and the company at the same time, because the decision maker has the facts.
Example
A purchasing team requires five approvals for every order above $500. A review finds that approvals take an average of six days and have stopped only two errors in a year. The finance team recommends a single approval for orders under $5,000, with a monthly review of exceptions.
Case study
Seen in the real world.
Ashgrove Industrial is an illustrative, fictional manufacturer where staff had learned to protect themselves with long email chains and multiple sign-offs. Expense claims of $200 needed three approvals, and the monthly management report grew to 60 pages. Several managers admitted that they copied the finance team into messages simply so they could say it had been told.
The new finance director ran a simple exercise. She listed every approval step in the purchase-to-pay process, asked what risk each one addressed and measured how many errors each had actually caught over twelve months. She also interviewed a sample of staff to understand which approvals they believed were useful.
In this illustrative case, four of the nine steps had caught nothing and were removed, while the report was cut to eight pages with a clear page-one summary. Cycle times fell by a third, and staff reported feeling more trusted. Critical controls such as segregation of duties stayed in place. The finance director presented the results to the board as proof that removing pointless steps can make control stronger rather than weaker.
Watch out
Common mistakes.
- Assuming that more copies, more approvals and more caveats always mean better control.
- Hiding real concerns in dense wording so that you cannot be blamed, but nobody can act either.
- Punishing people who raise problems, which teaches everyone to protect themselves instead of the business.
Questions
People also ask.
Is keeping a paper trail always a bad thing?
No, good records are an essential internal control; the issue is when records are made only to shift blame. Auditors will usually ask to see evidence of approval for significant transactions.
How can a manager tell the difference?
Ask whether the record helps someone make a better decision or check the work, or whether it only protects the person who wrote it.
What is a healthy alternative?
Clear decision rights, short factual updates and a culture where raising a problem early is rewarded. Regular review of the approval process keeps it from growing back.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%