Made for Administrators
Resolve a Request That Keeps Bouncing Between Offices
Also useful for: people in Government
You trace a request's full route, separate confirmed facts from office assumptions, identify the decision or service still needed, and secure a documented ownership agreement.
Create a free account to save your progress and use this Playbook.
Use this when
Use this when two or more offices have redirected the same request, no office accepts responsibility, the requester is receiving conflicting instructions, or a deadline is approaching without a clear owner.
You'll need
- Request and desired result
- Travel history
- Office responses
- Rules and procedures
- Contacts and authority
- Deadline and impact
- Constraints
You'll get
- The request's route reconstructed
- The unresolved service or decision defined
- Evidence from assumptions separated
- Each office's responsibility mapped
- Or escalated the accountable owner named
- The agreement documented
By the end of this playbook
You will have:
- The request's route reconstructed
- The unresolved service or decision defined
- Evidence from assumptions separated
- Each office's responsibility mapped
- Or escalated the accountable owner named
- The agreement documented
Sample
This is sample data, not your prompt. Pro unlocks this higher-stakes Playbook. On Free Playbooks you can still copy the assembled prompt into any AI.
Sample input
You need a vendor address corrected before an invoice can be paid. Procurement says Finance owns changes to existing records. Finance says Procurement owns all vendor records. The request moved between both offices three times over eight business days. A service guide says Procurement maintains vendor profiles, while Finance validates payment-impacting changes. The invoice will miss the monthly payment run if the correction isn't completed by May 15.
Sample assembled prompt
You identify Procurement as the strongest... You prepare an ownership conversation that... You also set May 14 at...