Reviewed and updated: 21 July 2026.
Teams often remember that a decision was made but cannot recover the approved wording, authority, rationale, assumptions or review trigger. Meeting minutes describe individual meetings; a decision register creates a searchable cross-meeting record of significant choices and how they changed over time.
Quick verdict: Record one row per significant decision, verify the final wording against the source, identify the authorised decision maker, preserve rationale and assumptions and mark later changes as superseding—not deleting—the original history.
What belongs in a decision register?
Include decisions that affect:
- Project scope
- Budget or pricing
- Product or design direction
- Supplier selection
- Risk acceptance
- Policy or process
- Launch timing
- Customer commitments
- Technical architecture
- Legal, safety or compliance controls
Do not fill the register with every routine task or conversational preference.
Decision register versus meeting minutes
| Meeting minutes | Decision register |
|---|---|
| Chronological record of one meeting | Cross-meeting record of significant decisions |
| Includes discussion, actions and updates | Focuses on approved decision and context |
| Often read shortly after the meeting | Used throughout the project lifecycle |
| May contain several decisions | One controlled entry per decision |
The twelve fields of a strong decision entry
- Decision ID
- Title
- Approved wording
- Date and effective date
- Decision maker or authority
- Context and problem
- Options considered
- Rationale and evidence
- Assumptions and constraints
- Impact and related actions
- Review trigger or expiry
- Source meeting and status
Use exact approved wording
Weak entry:
“Website changes approved.”
Stronger entry:
“Approve moving the ‘Why not use a phone app?’ comparison section directly beneath the main product-benefit section on the unpublished Halo theme. No live-theme change is authorised.”
The stronger version preserves scope and limits.
Separate decision status from discussion
| Status | Meaning |
|---|---|
| Proposed | An option has been raised but not approved |
| Agreed in principle | Direction accepted, material conditions remain |
| Approved | Authorised wording and scope confirmed |
| Deferred | Decision postponed to a defined trigger or date |
| Rejected | Option deliberately not selected |
| Superseded | Replaced by a later linked decision |
Identify the authority
Record:
- Who made the decision
- The role or governance body
- Whether the authority was delegated
- Any required approval still outstanding
- Whether the decision was unanimous, majority or individual
A confident statement by a participant is not necessarily an authorised decision.
Preserve rationale without replaying the debate
Summarise:
- The problem being solved
- Evidence relied upon
- Important alternatives
- Why the selected option was preferred
- Material trade-offs
- Known uncertainty
Link detailed papers rather than copying them into the register.
Record assumptions and constraints
Examples:
- Stock will arrive before the launch date.
- Security approval will be completed.
- The budget remains within the approved limit.
- The pilot includes ten users.
- No live-theme change occurs before final review.
An assumption should trigger review if it later proves false.
Connect the decision to execution
| Impact area | What to record |
|---|---|
| Actions | Owner, deliverable and deadline |
| Budget | Approved amount and cost owner |
| Scope | Included and excluded work |
| Risk | Accepted risk and mitigation |
| Documents | Plans, contracts, designs or policies to update |
| Communication | People who need the approved outcome |
Use review triggers
A decision may need review when:
- Cost exceeds a threshold
- A deadline moves
- A supplier or system changes
- A pilot misses its success measure
- A legal or professional requirement changes
- An assumption proves false
- A risk materialises
- A set date arrives
Recording-to-register workflow
- Generate the transcript and meeting summary.
- Search for final decision language.
- Replay the relevant section.
- Check who had authority.
- Draft one entry per significant decision.
- Verify rationale, assumptions and conditions.
- Link actions and source documents.
- Obtain the required approval.
- Publish the entry in the controlled register.
- Notify affected owners.
Decision entry template
ID: DEC-[number]
Title: [short decision title]
Approved wording: [exact controlled wording]
Date/effective date: [dates]
Authority: [person or body]
Context: [problem]
Options: [main alternatives]
Rationale: [evidence and trade-off]
Assumptions: [conditions]
Impact/actions: [links and owners]
Review trigger: [date or event]
Source: [meeting and document links]
Status: [approved, superseded or other]
Do not delete superseded decisions
Mark the old decision as superseded and link the replacement. Preserving history explains why earlier actions and designs made sense at the time.
Control access and sensitivity
Some rationales contain personal, commercial, legal, security or privileged information. Use appropriate access and create a less sensitive summary where wider communication is necessary.
Measure register quality
- Percentage of significant decisions entered promptly
- Entries with identified authority
- Entries with review triggers
- Decisions repeatedly debated because context was missing
- Actions linked successfully
- Superseded decisions linked to replacements
Using NERALVO Halo
NERALVO Halo is an ultra-slim AI voice recorder with 64GB local storage, up to 35 hours of recording, NOTE mode, supported CALL mode, Bluetooth synchronisation with the DOWAY app, and AI transcription, summaries, templates, translation, mind maps and exports. One year of DOWAY Max access is included.
A practical Halo decision workflow
- Confirm recording is lawful, disclosed and permitted.
- Capture the meeting using the appropriate mode.
- Synchronise with DOWAY.
- Generate and verify the transcript.
- Locate decision language and replay the source.
- Create the controlled register entry.
- Obtain approval and link actions.
- Apply the retention policy to audio and temporary text.
Frequently asked questions
Is a decision register the same as minutes?
No. Minutes record one meeting; the register tracks significant decisions across meetings and time.
Should rejected options be included?
Include material alternatives and why they were rejected where that context may prevent repeated debate or explain risk.
Who owns the register?
A named project, product, programme or governance owner should maintain it.
Can AI decide which statements count as decisions?
It can highlight candidates, but a human must verify status, authority, wording and context.
Decision-register checklist
- One entry per significant decision
- Approved wording verified
- Authority identified
- Rationale and options recorded
- Assumptions visible
- Impact and actions linked
- Review trigger set
- Source meeting linked
- Sensitive access controlled
- Superseded history preserved
A good decision register preserves not only what changed, but why the authorised choice made sense.
Ready to capture meetings properly?
View the NERALVO Halo AI voice recorder with 64GB local storage, meeting capture, compatible phone-call recording workflows and one year of DOWAY Max included.
View NERALVO Halo