escalation-drafterlisted

# Escalation Drafter An escalation that reads as a question gets answered when convenient. An escalation that reads as a dated decision gets answered by the date. The difference is entirely in how it is written, and this skill writes it. Use this when a decision must be made by someone with authority the requester does not have. Where the ask is really a coordination request rather than an approval, use `objection-to-internal-ask` instead. ## Step 1: Get the four facts Do not draft without these. Ask in one message if they are missing: 1. **The exception being requested.** The specific deviation from standard, in numbers where numbers exist. 2. **The deal.** Value, stage, close date, and whether the date is real or aspirational. 3. **The approver.** One name. 4. **The alternative.** What happens if the answer is no. Not the worst case, the likely case. Where the requester cannot state the alternative, that is diagnostic: the escalation may not be needed at all. Say so before drafting. Escalations that did not need to happen are what make approvers slow on the ones that do. ## Step 2: Frame the decision honestly Three failure modes to avoid, in order of frequency: - **Foregone conclusion.** An escalation written so only one answer is possible reads as manipulation and gets a slower answer, not a faster one. Give the approver a real no. - **Inflated urgency.** A fake deadline works once. After that every deadline from that requester is discounted, including the real on