The meeting happened. The decision was made. Now nobody can find it.
This is one of the most common and quietly expensive problems in organizational life. A decision is made in a meeting. Someone might have taken notes. Those notes live somewhere. Six months later, a new team member asks why something was done a certain way, a funder asks for the rationale, or the team is about to relitigate the same question again. Nobody can find the record.
This is not a filing problem. It is a memory architecture problem. And it has a structural fix.
Meeting notes are not organizational memory.
There is a category difference between a meeting note and a decision record. Most organizations only have the first one and wonder why they cannot find the second.
Meeting notes capture what was said, not what was decided
A meeting summary is a transcript with formatting. It records who spoke and what they said in what order. It does not extract the discrete decision, name the decision-maker, record the rationale, or flag the follow-up. To find the decision later, someone has to re-read the whole thing and interpret it correctly.
Notes are organized by date, not by decision
Meeting notes live in folders organized by when they happened: 'October 12 team meeting,' 'Q3 retrospective.' That works for filing. It fails for retrieval. If you need to know what was decided about the vendor contract, you have to know which meeting it was discussed in, find the notes, and read through them hoping the relevant passage is clearly marked.
Nobody owns the record
Meeting notes are often created by whoever volunteered, whoever remembered, or whoever's turn it was. The quality varies. The storage location varies. The format varies. When a decision needs to be traced six months later, there is no clear source of truth, and often no one who knows where to look.
Decisions are rarely marked as decisions
In a real meeting, the actual moment of decision is often ambiguous. Someone says 'I think we should go with option B.' Someone else says 'yeah that makes sense.' The group moves on. Was that a decision? In what meeting notes would it appear as such? With what level of clarity?
Undocumented decisions compound over time.
The cost of a missing decision record is not usually visible at the moment the record fails to be created. It surfaces later, when the information is needed and not there.
Decisions get relitigated
The team discusses the same question three times over six months because nobody can find or verify what was decided before. Time and goodwill spent on territory already covered.
Commitments get missed
Someone agreed to something in a meeting. Nobody logged it as a commitment. Nobody followed up. The other party is still waiting. The organization finds out when the relationship is already damaged.
Context gets lost in transitions
A new team member, board member, or funder asks why something was done a certain way. Nobody can find the decision record. The reasoning is gone. The organization either cannot explain itself or reconstructs an explanation that may not be accurate.
Authority becomes ambiguous
When a decision is undocumented, who made it is also undocumented. Disagreements about what was decided become disagreements about who had the authority to decide it. Organizations with no decision record spend disproportionate energy on these disputes.
A decision record is not a formatted meeting note.
A decision record names the decision. It names who made it. It captures the rationale, the options that were considered, the constraints that shaped the choice, and any dissent or objection. It links to the source: the meeting where it happened, the email where it was confirmed. It is queryable, not just findable.
What a decision record contains
- The decision itself, stated clearly as a discrete item
- Who made it and who was involved
- The rationale and the options that were considered
- Any objections or dissent captured at the time
- The source: the specific meeting or email where the decision was made
- Whether the decision is still active, revised, or superseded
How Saberra creates them
Saberra reads meeting transcripts and emails, extracts decision candidates, and routes them to a human reviewer for approval before they enter the organizational record. Sera can then answer questions about what was decided, when, by whom, and why, with a source citation for every answer.
Why meeting notes are not memory
The structural difference between notes and organizational records.
What Saberra captures
The full set of organizational memory objects Saberra extracts from meetings and emails.
The real cost of key-person knowledge loss
What organizations actually lose when a key person leaves.
Your organization has been making decisions. Do you have the records?
The Memory Audit takes 10 minutes and tells you exactly where your organization's decision record is leaking. Most teams are surprised by the score.