01
Gather the controlling record
Collect the request, governing contract language, current delivery baseline, and known facts about funding and authority. Keep facts separate from assumptions.
Made for Federal Contractors
Test a Requirement Change Before Committing
Also useful for: people in Government
35 min
Intermediate
Government
Federal Contractor
Improve Operations
Career outcome:
Avoid Professional Risk
Assess whether a requested change is covered, feasible, funded, and authorized, then prepare a defensible response that avoids an accidental commitment.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Protect the contract and delivery plan by separating valid clarification from added scope before agreeing to cost, schedule, staffing, or performance changes.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Test scope and delivery impact
Break the request into distinct change elements, then compare each element with the contractual and operational baselines.
03
Check funding and authority
Determine whether the record supports action, clarification, impact estimation, or formal change control before commitment.
04
Prepare the response package
Turn the analysis into language suitable for a meeting and a written record without implying unsupported agreement.
Make Your Play
Test a Requirement Change Before Committing
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Describe the request, who made it, when it was made, the stated deadline, and any exact wording that could imply a commitment.
0/10000
Paste or upload the relevant statement of work, task order, deliverable, acceptance, period of performance, or change-control language.
0/10000
Summarize the approved schedule, staffing plan, deliverables, assumptions, and commitments that could be affected.
0/10000
State what is known about available funding, labor ceilings, funded hours, and whether anyone has approved additional work.
0/10000
List affected teams, systems, approvals, milestones, security reviews, data sources, and existing deliverables.
0/10000
Describe who issued the direction, what authority is documented, and which contracting or program officials have been consulted.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Gather the controlling record
Collect the request, governing contract language, current delivery baseline, and known facts about funding and authority. Keep facts separate from assumptions.
02
Test scope and delivery impact
Break the request into distinct change elements, then compare each element with the contractual and operational baselines.
03
Check funding and authority
Determine whether the record supports action, clarification, impact estimation, or formal change control before commitment.
04
Prepare the response package
Turn the analysis into language suitable for a meeting and a written record without implying unsupported agreement.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Start with the exact request and the strongest baseline language available. If funding or authority is unclear, say so plainly instead of guessing. Review the final position with the appropriate contracts or program lead before sending it.
Advanced instructions
Break mixed requests into separate change elements and test each one independently. Replace general impacts with dated milestones, labor assumptions, acceptance effects, and cited contract sections wherever the record supports them.
Use this when
A government stakeholder requests a change, expects a quick answer, or treats new work as if it were already included in the contract.
You'll need
- Requested change
- Contract baseline
- Delivery baseline
- Funding status
- Dependencies and impacts
- Authority context
You'll get
- The requested change separated into testable elements
- Each element compared with the current contractual and delivery baselines
- Funding, dependency, feasibility, and authority gaps identified
- A recommended position supported by supplied evidence
- Non-committal talking points and written follow-up prepared
- Questions requiring contracts, program, security, pricing, or legal review flagged.
By the end of this playbook
You will have:
- The requested change separated into testable elements
- Each element compared with the current contractual and delivery baselines
- Funding, dependency, feasibility, and authority gaps identified
- A recommended position supported by supplied evidence
- Non-committal talking points and written follow-up prepared
- Questions requiring contracts, program, security, pricing, or legal review flagged.
Examples
Progress 1 of 4