The gap between a report and a reason

Every business generates reports constantly — sales reports, stock reports, cash flow reports, variance reports. Almost none of them generate reasons, and the difference between the two is where a surprising amount of operational risk quietly accumulates.

A report describes what happened

That's its whole job, and it does it well. Revenue was this. Stock moved that much. This customer's account is this many days overdue. A report is a snapshot of outcome, stated as fact, with no opinion attached.

A reason is different in kind, not just in detail. It describes a choice: why this customer got extended terms, why this product was discontinued, why this supplier relationship ended. A reason has a decision-maker, a set of circumstances, and a judgement call embedded in it. None of that fits naturally into a report, because a report is built to be objective and a reason is inherently a point of view at a moment in time.

Why businesses accumulate reports but not reasons

Reports are a byproduct of the system doing its job — every transaction generates one automatically. Reasons require someone to stop, think about why they did something, and write it down, which is an active choice that competes with everything else on their plate that day.

The asymmetry compounds. A year of operating a business produces thousands of reports and, realistically, a handful of documented reasons — the ones important enough, or contentious enough, that someone insisted on writing them down. Everything else lives in memory, in a WhatsApp thread, or nowhere at all.

Where the absence actually costs something

Three moments where a missing reason turns into a real problem.

Reviewing an old decision with new information. A supplier was dropped eighteen months ago. Prices have gone up elsewhere and someone wants to reconsider. Without the original reason, the business either repeats a mistake it already made once, or avoids a supplier for a problem that no longer applies.

Explaining a pattern to someone who wasn't there. A new manager inherits a set of pricing exceptions with no history attached — see explaining your numbers to someone who was not there. Every exception looks arbitrary until someone can explain the reasoning, and the person who can explain it may no longer be around.

Defending a decision under scrutiny. An auditor, a new investor, or a board member asks why something was done a certain way. "It seemed right at the time" is true and useless. A written reason, made at the time, is the only version of that answer that survives.

Why this is a harder problem than "just document things"

Telling a team to "document your reasoning" fails for a predictable reason: it has no natural home. A report has a system that generates it automatically. A reason has no equivalent, so it depends entirely on individual discipline, which degrades under deadline pressure — which is exactly when the most consequential decisions tend to get made.

The fix isn't more discipline. It's making the reason as easy to attach as the report is to generate — a field next to the decision, not a separate document nobody opens.

What to actually do

Pick the decisions in your business that would be expensive to get wrong twice: supplier terms, customer exceptions, pricing overrides, write-offs. For each category, agree one place the reason gets written — attached to the record, one or two sentences, at the moment the decision is made rather than reconstructed afterward.

That's a smaller commitment than a documentation project, and it only has to cover the decisions that would actually hurt to lose. Most of a business doesn't need this. The exceptions do.

Common questions

What's the difference between a report and a reason?

A report describes an outcome objectively — what happened, measured. A reason describes a choice — why someone decided something, given the circumstances at the time. Reports are generated automatically by transaction systems; reasons require a person to actively write down their thinking, which is why businesses accumulate far more of the former than the latter.

Why don't businesses document reasoning as a matter of course?

Because reasons have no natural system generating them the way reports do. Writing one down is an active choice competing with everything else on someone's plate, and it tends to lose that competition precisely when decisions are made under time pressure — which is when the reasoning is most worth keeping.

When does a missing reason actually cause a problem?

Three common moments: reconsidering an old decision with new information, explaining a pattern of exceptions to someone who inherited them, and defending a past decision to an auditor or investor. In each case, "it seemed right at the time" is true but useless without a record made at the time.

What's a realistic way to start capturing reasons?

Don't try to document everything. Identify the categories of decision that would be expensive to get wrong twice — supplier terms, customer exceptions, write-offs — and agree one place the reason gets written for those specifically, attached to the record itself, at the moment the decision is made.

Related: explaining your numbers to someone who was not there · what your ERP does not record · key-person risk in finance