Capture Decisions and Commitments
Create a decision ledger from authorized fictional notes without inventing owners, deadlines, or agreement.
Why this decision matters
The pre-call brief is not evidence of the meeting. Post-call input must come from notes supplied by a participant or an authorized transcript. Each item receives a type: decision, commitment, action, open question, concern, or suggestion. The actor and exact wording matter. If no owner or date was agreed, those fields remain unknown or proposed. A human reviewer corrects the ledger before it becomes relationship history.
This lesson advances the same capstone used throughout the course: the Meeting Preparation and Follow-Up Agent Pack. The learner is not collecting ideas for later. The workbook record created here becomes an input to the next module and must be specific enough that another operator could review it. Where evidence is incomplete, the artifact should show the gap instead of smoothing it over.
Source evidence and limits
C7-S3 specifies after-call continuity, separate commitments, proposed owners and dates, transcript consent, and shared meeting IDs. C7-S4 emphasizes workflow, ownership, baseline, human judgment, and fit.
The sources support the operating method stated above. They do not prove universal performance, guaranteed savings, complete market coverage, causal impact, or a client result. Any date-sensitive product, platform, competitor, legal, pricing, or policy fact must be checked against a current primary source before publication or operational use.
Continuing fictional example
Example: Northstar Operations, Cedar Workshop, and operations lead Jordan Lee are fictional. The meeting concerns inconsistent enquiry handling.
Fictional notes say Jordan will provide three anonymized enquiry examples, while Northstar will send a one-page process-review scope. No deadline was recorded. The agent marks both as stated actions and leaves dates unknown; it does not claim a purchase.
Example boundary: The fixture contains no live person, address, email, profile, company, meeting, or customer result. Its source excerpts exist only to test the course method.
Workbook application
Use Workbook Section 6: Capture Decisions and Commitments. Complete Workbook Section 6. Convert the fixture notes into the decision ledger, cite the note line, distinguish actual and proposed items, and mark unknown owners or dates.
- Write the current evidence or input before adding interpretation.
- Apply the lesson's decision rule and state the reason for the classification.
- Mark uncertainty, missing information, and the human owner for the next decision.
- Check that the result stays inside the course boundaries and can be tested.
Failure modes to inspect
Treating the pre-call recommendation as an outcome; converting discussion into commitment; inventing dates; assigning every task to the prospect; and retaining raw sensitive notes unnecessarily.
A polished output can still fail if its evidence, permissions, identity, denominator, source date, or action boundary is wrong. Review the underlying record rather than grading tone alone. The correct repair may be to narrow the scope, gather a permitted source, label an unknown, or stop the proposed action.
Decision rules
Meeting evidence starts after the meeting. Preserve the original authorized note locator. Human review precedes use as history. Unknown remains unknown.
Record the rule in the workbook in language two reviewers can apply consistently. A rule that depends on intuition alone cannot support a deterministic fixture. If reviewers disagree, preserve both readings, identify the missing evidence, and revise the rule before automation.
Three application checks
1. Authorized notes say, 'We should probably review three examples next week,' but name no owner. How should the ledger classify it?
2. The pre-meeting brief recommended a process review, but the meeting notes never mention it. Should it appear as an agreed next step?
3. A commitment is clear, but no deadline was agreed. What should the decision ledger record?