Verified against ChatGPT · 2026-08-09
Write a delegation handoff brief that survives you being unreachable for two weeks
Produces a delegation brief with explicit decision authority, escalation triggers, and check-in cadence — built so the task doesn't stall or get re-decided the moment you're offline.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are writing a delegation handoff brief for a task I'm handing off, written so the person taking it over doesn't need to reach me to keep moving. TASK BEING DELEGATED Finalizing and sending the Q3 vendor renewal contracts to our three top-tier suppliers. WHO IT'S GOING TO Priya, a mid-level ops analyst who has read the contracts but has never negotiated one solo. DECISION AUTHORITY I'M GRANTING She can accept standard terms and up to a 5% price increase without checking with me; anything beyond that needs me. CHECK-IN CADENCE A short Slack update every Friday, even if there's nothing to report. ESCALATION TRIGGER If a vendor threatens to walk away from the deal entirely, or asks for a term we've never granted before. Most delegation fails not because the task wasn't explained but because the authority boundary was never stated, so the delegate either stalls on things they were actually allowed to decide, or decides things they weren't. Write the brief so that boundary is unmistakable. Open with the task itself and what 'done' looks like — specific enough that the delegate can self-check without asking me. Then write the decision-authority section as a list of concrete decision types with a yes/no next to each: what they can decide alone, what they should decide and just inform me after, and what requires waiting for me. A decision-rights section that just says 'use your judgment' is not a boundary — replace any vague authority language from what I gave you with the sharpest concrete version you can construct from context, and flag anywhere the input was genuinely ambiguous rather than guessing silently. Write the escalation trigger as a specific, observable condition — not 'if something goes wrong' but the exact signal that should make them stop and escalate instead of proceeding on their own judgment. State the check-in cadence as a concrete rhythm with a default channel, and specify what happens if I don't respond within that cadence given I'm unreachable — the delegate needs a documented default action, not a dependency on my responsiveness. Close with a short list of the two or three most likely places this task goes sideways, based on the task description, and what the delegate should do in each case without waiting for me. Do not write this as a generic delegation template with placeholders like 'insert responsibilities here' — every line should be usable as-is, referencing the actual task. Do not soften the authority boundary to be diplomatic; an ambiguous boundary is the exact failure mode this brief exists to prevent. OUTPUT FORMAT 1. Task and definition of done, two to three sentences. 2. Decision-authority table: decision type, decide-alone / inform-after / wait-for-me. 3. Escalation trigger, stated as an observable condition, with the default action if I'm unreachable. 4. Two or three likely failure points and the delegate's default response to each.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
The single most common delegation failure is not unclear task description but an unclear authority boundary, and GPT-5.1 defaults toward diplomatic hedging language ('use your best judgment', 'feel free to decide') when asked to write delegation instructions in a neutral tone — which is precisely the failure mode this prompt targets by forcing every decision type into an explicit decide-alone / inform-after / wait-for-me bucket instead of a soft suggestion. Stating the escalation trigger as an observable, checkable condition rather than an open-ended 'if something goes wrong' matters because an unobservable trigger leaves the delegate guessing whether the current situation qualifies, which recreates the exact dependency on the delegator the brief is supposed to eliminate — a concrete signal like a vendor threatening to walk removes that guesswork entirely. Requiring a documented default action for what happens if the delegator is unreachable within the check-in cadence addresses a specific structural gap in most handoff documents: they describe the ideal case where the delegator responds promptly, but say nothing about the realistic case of a two-week absence, so the delegate stalls exactly when autonomy matters most. Asking the model to flag ambiguity in the authority input rather than silently resolving it in either direction is important because an AI-generated brief that guesses wrong on scope either grants too much authority (creating real risk) or too little (recreating the bottleneck) — surfacing the ambiguity lets the actual delegator make that call instead of an assumption baked silently into the document.
What you get back
Decide-alone: accepting standard terms, price changes up to 5%. Inform-after: any change to payment terms or delivery timelines. Wait-for-me: anything involving exclusivity clauses or contract termination language. Escalation trigger: a vendor refuses the 5% cap outright — stop, do not counter-offer, message me directly rather than waiting for Friday's check-in.
Verified against
ChatGPT GPT-5.1 · 2026-08-09
Changelog
- 2026-08-09 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — custom software, built and maintained for you — that's Scult's day job.
EXPLORE CUSTOM SOFTWARE
