Inputs
- A consented meeting record or notes
- Project vocabulary
- Action-item schema
- Meeting owner
Control points
- Do not infer absent commitments
- Mark unresolved owners
- Link back to source notes
- Owner confirms assignment
Human approval gate
The meeting owner and each named assignee confirm the decision, owner, due date, and destination before task creation.
The workflow
Every step includes a check that can stop the process before risk moves downstream.
- 01
Confirm consent and source
Use notes or recordings under the organization's meeting and retention policy.
Gate: Participants and reviewers know what source is being processed. - 02
Separate decisions from discussion
Extract explicit decisions, proposals, questions, and actions into different fields.
Gate: A suggestion is not mislabeled as a decision. - 03
Preserve uncertainty
Use unassigned and no-date values when the meeting did not establish an owner or deadline.
Gate: The assistant never fabricates accountability. - 04
Ask owners to confirm
Send the draft to the meeting owner and named assignees before task creation.
Gate: Rejected or corrected items remain auditable. - 05
Publish the decision log
Link approved items to the original notes and the relevant project space.
Gate: Readers can reconstruct why the action exists.
Candidates to pilot
Inclusion means relevant product shape, not measured superiority.
Sources checked
Open the original pages before relying on a time-sensitive product decision.