Made for Federal Contractors
Turn a Review Meeting Into Clear Commitments
Also useful for: people in Government
35 min
Intermediate
Government
Federal Contractor
Communicate Better
Career outcome:
Avoid Professional Risk
Separate firm commitments from discussion, then produce a source-linked action register and precise meeting follow-up.
Create a free account to save your progress and use this Playbook.
Use this when
A government review meeting has ended, and the notes or transcript contain mixed signals about decisions, requirements, approvals, owners, or deadlines.
You'll need
- Meeting date
- Review context
- Meeting record
- Authority guardrails
- Attendees and roles
- Follow-up constraints
- Output depth
You'll get
- Every claimed decision tied to a source reference
- Every action assigned an owner or marked "Not stated"
- Every deadline preserved or flagged as unclear
- Every approval condition separated from final approval
- Every possible scope change flagged for review
- A follow-up message limited to supported commitments
By the end of this playbook
You will have:
- Every claimed decision tied to a source reference
- Every action assigned an owner or marked "Not stated"
- Every deadline preserved or flagged as unclear
- Every approval condition separated from final approval
- Every possible scope change flagged for review
- A follow-up message limited to supported commitments
Sample
This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.
Sample input
Meeting date: September 18, 2026 Context: Release 3 interface specification review Record: At 00:18:42, the program manager said, "Comments 12 and 14 are closed from our side." At 00:27:10, the COR asked for a revised schedule by next Friday. At 00:31:05, the cybersecurity lead said final approval depended on receiving the updated control mapping. At 00:39:22, the program manager suggested adding a new reporting field but said the group needed to assess the effect first. Guardrails: The contracting officer must authorize contract changes. The COR may provide technical direction within scope. Attendees: Program manager, COR, cybersecurity lead, contractor delivery lead. Constraint: Draft a concise email and don't describe the reporting field as approved. Output depth: Detailed audit trail
Sample assembled prompt
Executive readout Comments 12 and 14... Final approval remains conditional on the... A revised schedule was requested, but... The proposed reporting field isn't... Action register 1. Submit updated control mapping Owner: Not... Provide revised schedule Owner: Not stated... Possible scope change New reporting field...