01
Gather the Direction and Contract Basis
Collect the request, governing language, delivery context, and known authority before analyzing the work.
Made for Federal Contractors
Clarify an Ambiguous Task Order
Also useful for: people in Government
30 min
Intermediate
Government & Public Service
Improve Operations
Miscommunication
Pin down unclear scope, acceptance criteria, dependencies, inputs, and deadlines before assigning work or promising delivery.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Resolve task order gaps before they cause unauthorized work, missed deadlines, rejected deliverables, or disputes about what the government requested.
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
Map Gaps and Work Status
Use the AI to separate stated requirements from assumptions, conflicts, and missing decisions.
03
Send the Clarification Package for Review
Prepare the questions, email, commitment gate, and evidence list for internal approval before government submission.
Make Your Play
Clarify an Ambiguous Task Order
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 exact request, meeting notes, ticket, or follow-up message. Include who sent it and when.
0/10000
Paste or upload the relevant task order, scope, deliverable table, acceptance language, modifications, and prior written direction.
0/10000
Describe current deadlines, dependencies, government inputs, access needs, team limits, and work already underway.
0/10000
Select how the government request reached the team.
List the government and contractor contacts involved, including any known limits on who can direct or authorize the work.
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 Direction and Contract Basis
Collect the request, governing language, delivery context, and known authority before analyzing the work.
02
Map Gaps and Work Status
Use the AI to separate stated requirements from assumptions, conflicts, and missing decisions.
03
Send the Clarification Package for Review
Prepare the questions, email, commitment gate, and evidence list for internal approval before government submission.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Paste the exact request and the most relevant contract sections. If a document is long, include the sections covering scope, deliverables, acceptance, schedule, government inputs, and changes.
Advanced instructions
Include section numbers, modification history, prior written direction, dependency owners, review windows, and the known authority of each government contact. Replace the draft email’s generic references with exact contract citations before sending.
Use this when
You received a vague or incomplete government request and need to determine what the team can start, what must wait, and what needs written clarification.
You'll need
- Government Request
- Governing Requirements
- Delivery Context
- Request Channel
- Contacts and Authority
You'll get
- Every unclear requirement mapped to its source or marked as unsupported
- Scope, acceptance, dependencies, government inputs, and deadlines checked
- Clarification questions prioritized by delivery risk
- Work divided into start, conditional start, and hold categories
- Written clarification request ready for internal review
- Supporting evidence identified for retention.
By the end of this playbook
You will have:
- Every unclear requirement mapped to its source or marked as unsupported
- Scope, acceptance, dependencies, government inputs, and deadlines checked
- Clarification questions prioritized by delivery risk
- Work divided into start, conditional start, and hold categories
- Written clarification request ready for internal review
- Supporting evidence identified for retention.
Examples
Progress 1 of 3