Made for Federal Contractors
Scope Change Warning Check
Also useful for: people in Government
Catch possible scope changes before work begins and document the next action.
We'll use them to write your prompt.
Make Your Play
Give us the situation. We’ll build the prompt.
Prevent informal requests from quietly changing deliverables, deadlines, staffing, cost, or contract assumptions without proper direction.
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.
Make Your Play
Scope Change Warning Check
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
Paste the request exactly as received, including requested actions and deadlines.
0/10000
Paste or upload the contract sections that define the current work, schedule, resources, reporting, and authority.
0/10000
Select how the request was received.
Describe who sent the request, the stated authority, when it arrived, and when action is expected.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Paste the request exactly as received. Add only the contract sections, task order language, statement of work excerpts, or prior written directions that relate to it. Review every citation before using the result. Don’t treat the AI’s recommendation as a contract interpretation or authorization to stop work.
Advanced instructions
Add the applicable CLIN, work breakdown reference, period of performance, deliverable identifier, funding constraint, and prior direction history. Route the result through the contract manager, program manager, or counsel required by internal policy before sending it.
Use this when
A government contact asks for work that seems new, larger, faster, differently staffed, or outside the written contract.
You'll need
- Government request
- Contract baseline
- Request source
- Sender and timing context
You'll get
- Every requested action matched to the supplied contract baseline
- Each possible change tied to a specific fact or missing detail
- A proceed, pause, or escalate status recorded
- Clarification questions ready for internal review
- Supporting messages and contract references identified for retention
By the end of this playbook
You will have:
- Every requested action matched to the supplied contract baseline
- Each possible change tied to a specific fact or missing detail
- A proceed, pause, or escalate status recorded
- Clarification questions ready for internal review
- Supporting messages and contract references identified for retention