A decision record is a system that answers who decided something, when, and why, with a named source the person stood behind. It is not a folder of documents and it is not a meeting note. It is the thing you ask when you need to know how a call was made and who made it, and it gives you back a specific answer with a name attached. The defining feature is accountability: every decision in the record traces to a real person who vouched for it.
Most teams think they have a decision record because they have places where decisions get written: a wiki, a chat channel, meeting notes. But a record is defined by what you can get out of it, not what you put in. If you cannot ask "who decided to skip the second region, and why?" and get a sourced answer, you have storage, not a record.
What is a decision record, exactly?
A decision record answers three questions about any choice a team made: who decided it, when, and why. To count as a record rather than a pile of notes, each answer has to be retrievable on demand and attached to a named person who stood behind it.
Those four elements, the who, the when, the why, and the named source, are what separate a real decision record from the things people mistake for one. A meeting note has the when but loses the who and the why within a month. A chat thread has all four scattered across a hundred messages, which means it has none of them in any usable form. A decision record keeps them together and answerable.
| Element | What it captures | Why it matters |
|---|---|---|
| Who | The person who made the call | You know who to ask, and who is accountable |
| When | The date it was decided | You can tell current decisions from stale ones |
| Why | The reasoning and the options weighed | New people understand it without re-litigating |
| Named source | The person who stood behind the answer | The answer carries weight; it is not a guess |
Why does a team need a decision record?
Because decisions are the questions people ask most, and the answers decay the fastest. A spec sits still. A decision is a moment in time that someone has to remember, and memory fades, people leave, and context gets lost. Six months after a choice, the only person who knows why often cannot be reached, so the team either guesses or re-decides, and re-deciding is slow and demoralizing.
A decision record stops that decay. It holds the reasoning at the moment it was clearest, attached to the person who made the call, so the answer survives the meeting, the quarter, and the person's departure. Our piece on why teams lose decisions in Slack walks through the failure this prevents.
The cost of not having one is quiet but constant. People interrupt each other to ask what was decided, new hires take months to understand choices nobody documented, and audits stall because nobody can show who approved what. None of these feel like a crisis on any given day, which is exactly why teams tolerate them for years.
How is a decision record different from a decision log or a wiki?
A decision log is usually a chronological list of decisions, which is a good start but stops at storage. You can read the log, but you still have to find the right entry and interpret it. A wiki holds pages, including some about decisions, but it is built to store documents, not to answer questions. A decision record is defined by the answering: you ask, and it returns the specific decision, sourced.
The difference is the same one between knowledge you read and knowledge you ask. A log and a wiki are knowledge you read. A decision record is knowledge you query, a distinction we go deeper on in what queryable knowledge means.
So the upgrade path is clear. A log is better than nothing. A queryable record, where you ask a plain question and get the who, when, and why back with a name attached, is what saves the team time and protects it from lost context.
How does StandIn act as a decision record?
StandIn gives each person a Representative, your StandIn, that can answer questions as them, but only from records they explicitly stood behind. That constraint is what makes it a trustworthy decision record rather than a chatbot that guesses. The flow has two parts. First, a person's work gets indexed automatically, so it is findable and pointable. Second, the person declares a decision: they vouch for it as their own, on the record, which is the human step that puts a name behind the answer.
Once a decision is declared, the record works the way you want. Anyone can ask "who decided this, and why?" in plain language and get the answer back, with the named person and the source attached, even when that person is offline or has left. The who, the when, and the why are all there because someone chose to stand behind them.
The restraint is the whole point. Your StandIn never invents a decision someone did not make. It does not infer what a person "probably decided" or summarize a thread into a position nobody took. If no one has declared a decision on a question, it points to where the discussion lives, routes the question to someone closer, or says it has no declared answer. A refusal there is information, not a failure, because "no one stood behind a decision on this" is what you need to know before you act on a guess. You can see the indexing-and-declaring flow in how StandIn works.
What does a good decision record entry look like?
A good entry is short and complete. It names the decision in a sentence, states who made it and when, and gives the reasoning, including the main option that was rejected and why. It is attached to a person, so the answer carries their name.
The discipline is small but real. Before a decision is finished, write the one line that makes it a record: what was chosen, by whom, on what date, and the core reason. That single habit is the difference between a team that can answer its own past and one that keeps re-deciding what it already settled.
Frequently Asked Questions
What is a decision record?
A decision record is a system that answers who decided something, when, and why, with a named source the person stood behind. It is defined by what you can ask of it, not just what was written down.
How is a decision record different from a decision log?
A log is a chronological list you still have to read and interpret. A decision record answers plain questions directly and returns the specific decision with a name and source attached.
Why do teams need a decision record?
Because decisions are asked about constantly and their reasoning decays fast as people forget or leave. A record keeps the who, when, and why retrievable so the team does not re-decide settled things.
Does StandIn invent decisions?
No. StandIn answers only from decisions a person declared and stood behind. It never infers a decision someone did not make, and it points or refuses when no one has declared an answer.
What should a decision record entry include?
The decision in a sentence, who made it, the date, and the reasoning including the main rejected option. It should be attached to a named person so the answer carries weight.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to retire your daily standup?
Distributed teams use StandIn to start every shift with full context, no standup required. Engineers publish a 60-second brief. The next shift wakes up knowing exactly what to work on.