01
Gather the decision facts
You collect the requests, authority sources, deadlines, commitments, capacity, and known consequences in one place. You separate confirmed facts from urgency claims and assumptions.
Made for Administrators
Decide What Gets Done When Every Request Is Urgent
Also useful for: people in Government
25 min
Intermediate
Boundaries
Improve Operations
Need to Make a Decision
Turn a crowded list of urgent government administration requests into a defensible work queue. You also get concise language for confirming priorities, exposing conflicts, and resetting deadlines you can't realistically meet.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Urgency alone is a weak basis for setting priorities.
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
Run the authority and consequence check
You use the primary prompt to place each request into an authority tier before comparing impact, risk, commitments, and effort.
03
Lock the queue and reset expectations
You choose the practical work sequence, confirm any escalation, and tailor the generated deadline-reset messages before sending them.
Make Your Play
Decide What Gets Done When Every Request Is Urgent
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
List each request with the requested outcome, requesting office, stated deadline, urgency reason, likely impact, estimated effort, dependencies, and owner when known.
0/10000
Add any laws, regulations, court orders, directives, service standards, formal commitments, or office rules that control timing.
0/10000
List work you've already promised, started, scheduled, or assigned, including dates and consequences of disruption.
0/10000
Enter the approximate number of work hours you can use for these requests before the nearest meaningful deadline.
Add staffing limits, approval paths, political sensitivity, public-facing consequences, known blockers, and any facts that should shape your decision.
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 decision facts
You collect the requests, authority sources, deadlines, commitments, capacity, and known consequences in one place. You separate confirmed facts from urgency claims and assumptions.
02
Run the authority and consequence check
You use the primary prompt to place each request into an authority tier before comparing impact, risk, commitments, and effort.
03
Lock the queue and reset expectations
You choose the practical work sequence, confirm any escalation, and tailor the generated deadline-reset messages before sending them.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
You can start with rough notes. Include every active request, even if some details are missing. For each request, give your best estimate of the deadline, consequence of delay, effort, and source of urgency. The result will show you what still needs clarification.
Advanced instructions
You can paste records from your request register and include service standards, formal directives, audit findings, public commitments, and workload limits. Replace the default scoring scale only if your office already uses an approved priority model, and preserve an audit trail for any manual override.
Use this when
Use this when several offices or leaders want immediate action, your available capacity can't cover every request, or a new priority would disrupt work you've already committed to deliver.
You'll need
- Incoming requests
- Deadline and authority rules
- Existing commitments
- Available capacity
- Decision context
You'll get
- One ranked queue, a short reason for every position, a visible list of unresolved authority or deadline conflicts, and usable messages for every deadline you need to reset
- You can explain why lower-ranked work is waiting without relying on vague claims about being busy.
By the end of this playbook
You will have:
- One ranked queue, a short reason for every position, a visible list of unresolved authority or deadline conflicts, and usable messages for every deadline you need to reset
- You can explain why lower-ranked work is waiting without relying on vague claims about being busy.
Examples
Progress 1 of 3