01
Gather the request and routing facts
You capture what was requested, how it arrived, where it should have gone, and whether the deadline reflects real urgency or simple convenience.
Made for Administrators
Push Back on Work That Arrived Through the Wrong Channel
Also useful for: people in Government
15 min
Intermediate
Government
Administrator
Communicate Better
Career outcome:
Avoid Professional Risk
Turn an informal or misrouted request into a clear decision: accept only through the proper intake route, redirect it, or escalate a real exception.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Protect request tracking, approvals, priorities, and ownership without giving the requester a cold procedural brush-off.
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 the risk of informal acceptance
You identify the operational cost of saying yes outside the process, including hidden priority changes, missing approvals, weak records, or unclear ownership.
03
Produce the redirect message
You turn the decision into a short response that stays helpful while making the proper route non-negotiable.
04
Record ownership and watch the handoff
You document the redirect so the request doesn't disappear or quietly remain assigned to you.
Make Your Play
Push Back on Work That Arrived Through the Wrong Channel
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
Provide what was requested, the requested outcome, and any deadline or reason given.
0/10000
Identify how the request reached you outside the normal process.
Name the exact form, mailbox, system, approval route, or office that should receive the request.
Note what could go wrong if you accept or start the work without proper intake.
0/10000
Rate how quickly the request appears to require action based on the facts provided.
Add relevant context about your working relationship, prior instructions, authority, or repeated bypasses.
0/10000
Name the approved route for urgent exceptions, or state that you don't know of one.
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Gather the request and routing facts
You capture what was requested, how it arrived, where it should have gone, and whether the deadline reflects real urgency or simple convenience.
02
Test the risk of informal acceptance
You identify the operational cost of saying yes outside the process, including hidden priority changes, missing approvals, weak records, or unclear ownership.
03
Produce the redirect message
You turn the decision into a short response that stays helpful while making the proper route non-negotiable.
04
Record ownership and watch the handoff
You document the redirect so the request doesn't disappear or quietly remain assigned to you.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
You can paste the request almost as received, but remove sensitive personal details that aren’t needed. Name the correct intake route as specifically as you can, including the form, mailbox, system, approval path, or office. Review the draft before sending it and replace every placeholder.
Advanced instructions
You can strengthen the result by naming the exact control at risk, such as approval authority, workload sequencing, records retention, service deadlines, or audit history. If you allow an exception, make it narrow, time-bound, documented, and clear that future requests must use the normal route.
Use this when
Use this when you receive work through a direct message, hallway conversation, personal email, meeting chat, or other channel that bypasses your normal intake process.
You'll need
- Request summary
- Channel used
- Correct intake route
- Risk of informal acceptance
- Time sensitivity
- Requester context
- Approved exception route
You'll get
- The real risk of informal acceptance identified
- A defensible response posture chosen
- A message with a specific routing instruction drafted
- A short record that makes the next owner visible prepared
By the end of this playbook
You will have:
- The real risk of informal acceptance identified
- A defensible response posture chosen
- A message with a specific routing instruction drafted
- A short record that makes the next owner visible prepared
Examples
Progress 1 of 4