# Meeting — Decisions & Actions

![Meeting — Decisions & Actions](/docs-content/789b54fb74-04-decisions-and-actions.png.webp)

**Navigation:** Home → Meetings → select a meeting → Decisions & Actions  
**Primary audience:** meeting participants and users responsible for resulting work or records

## Purpose

This screen turns one meeting's decisions, proposals, acceptances, commitments, tasks, and open questions into executable follow-through. It identifies incomplete ownership, deadlines, conditional customer acceptance, contradictions, and records that still need formalization.

## Summary indicators

- **Decisions** separates accepted, conditional, and proposed decisions.
- **Actions** shows newly created and carried-over actions.
- **Urgent actions** counts items due within the configured urgent window.
- **Overdue** identifies prior commitments still unresolved.
- **Pending acceptance** counts records awaiting customer or authorized confirmation.

## Decision register

Each row shows the decision and business impact, owner, lifecycle state, and timestamped evidence. States include Proposed, Conditional, Accepted, Superseded, Rejected, or Needs formalization. A proposed statement does not become an accepted decision merely because it appears in a transcript.

## Action execution board

The board lists task, owner, deadline, urgency, state, linked decision or finding, dependencies, and required evidence of completion. It distinguishes Open, Draft, Waiting, Blocked, Completed, and Escalated work.

## Completeness and acceptance

**Record completeness** checks owner, date, acceptance state, action text, and evidence link. **Acceptance checkpoints** displays exactly what the customer or another authority accepted, conditioned, or has not yet confirmed. **Dependencies & required follow-through** shows the chain preventing an accepted outcome from being completed.

## Actions

- **Create action** opens an editable task with suggested context.
- **Request acceptance** prepares a confirmation request containing the precise statement and evidence.
- Assign or change an owner and due date.
- Confirm completion and attach evidence.
- Escalate an urgent dependency.
- Formalize a decision, risk, scope change, acceptance, or baseline update in its owning record.
- Resolve a contradiction between meeting sources.

## Recommended procedure

Review conditional and proposed decisions first. Verify literal evidence, assign missing owners and dates, and request formal acceptance where authority matters. Then work through critical-path actions and check that completion evidence is sufficient before closing them.

## Related screens

[Meeting Findings](/documentation/packages/bnd-findings/screens/home-meetings-findings), [Actions](/documentation/packages/bnd-work/screens/work-actions), [Decisions & Commitments](/documentation/packages/bnd-work/screens/work-decisions-and-commitments), and [Acceptances](/documentation/packages/bnd-scope/screens/intelligence-project-acceptances).