Skip to content

Decision logs: the one page that captures why your business does what it does

A frosted-glass single-page document card showing five decision-log field rows — header, decision, owner, reasoning, and revisit trigger — beside a smaller panel with an open book representing commentary on the why, with a green check on the owner row.

Series: Building an AI-Ready Business — Part 3 of 3 Part 1: Process problem · Part 2: Writing SOPs · Part 3: Decision logs · Series hub

SOPs tell you what to do. They never tell you why you do it that way. That gap is where onboarding stalls, handoffs leak, and AI agents misfire when conditions change. The fix is a decision log.

The gap your SOPs leave behind

A good SOP is a closed loop. Trigger, steps, decision rules, output. That structure is what makes the work repeatable.

What it does not contain is the reasoning. Why this approval threshold and not a higher one. Why this vendor over the cheaper one. Why this client gets priority routing. The SOP records the conclusion. The thinking that produced it lives in someone's head.

When that person leaves, gets promoted, or is on holiday, the SOP keeps running. Right up until the conditions shift and nobody knows whether the original logic still applies.

What a decision log actually is

A decision log is a one-page running document that records the reasoning behind your standing decisions. Not every email. Not every meeting. The decisions that shape how the business operates.

One entry per decision. A handful of fields. Plain language. The point is that a new hire, a new partner, or a new AI agent can read it and understand not just what you do, but why.

Think of it as the commentary track for your SOPs. The SOP says "route invoices over $10,000 to the partner for approval." The decision log says "we set the threshold at $10,000 in 2024 after a wrong-vendor payment of $9,200. Below that, the AP lead approves. We will revisit if monthly invoice volume crosses 200."

Why small teams feel this gap first

Enterprises absorb lost context through sheer headcount. Someone always remembers. In a twelve-person firm, when the operations lead leaves, the reasoning leaves with them.

I have sat with owners trying to onboard a replacement and watched them realize the SOPs do not explain anything. The new hire does the work, but every edge case ends up back on the owner's desk. The handoff never completes.

Take a 14-person legal services firm I worked with. Their case intake SOP ran cleanly for two years. When the senior paralegal left, the replacement followed every step and still picked the wrong fee schedule three times in a month. The SOP did not mention that one schedule applied only to referrals from a specific partner firm. Nobody had written it down because everyone who needed to know already knew. The fix was not a new SOP. It was a decision log entry explaining the carve-out and the reason behind it.

Five fields every decision log entry needs

Keep the structure tight. If an entry takes more than ten minutes to write, it will not get written.

  1. Decision. What was decided, in one sentence.
  2. Date and owner. When it was made and who is accountable for revisiting it.
  3. Reasoning. Why this choice, not the obvious alternatives.
  4. Trade-offs. What you accepted by choosing this path.
  5. Revisit trigger. The condition that should prompt a review.

That last field is the one most teams skip. Without it, the log becomes a graveyard. With it, the log stays alive.

How to start your decision log this week

Do not try to backfill ten years of decisions. Start forward.

Pick three standing decisions you made in the last quarter. Write one entry for each, using the five fields. Put the file in the same shared folder as your SOPs. Add a line to your weekly leadership meeting: "any new decisions to log?"

Within a quarter you will have twelve to fifteen entries. That is enough to onboard a new hire, brief an AI agent, or justify a review to a board. More usefully, the next time someone asks "why do we do it this way?", the answer will not depend on you being in the room.

Keep exploring

Return to the series hub or revisit Part 1: Process problem for where this all started. When you are ready to surface the reasoning behind your standing workflows alongside the workflows themselves, start the AI Readiness Audit or contact FIT.