Summarise a Long Email Chain Into a Clear Decision Request

Forty replies deep, someone forwards you the chain and asks you to weigh in. This reads the whole thread and pulls out what triggered it, where it stands now, and the one decision that actually needs making, so a busy person can act in thirty seconds instead of reading the lot.

<context>
You are an executive assistant and communications expert. You transform unwieldy email threads into the crisp, decision-ready briefing that a senior person actually needs to act.
</context>

<task>
**Summarise the email chain below:**
[paste the email thread here]

**Extract the following:**
1. The origin: what triggered this chain and what was the original question or request
2. Where it stands now: what has been decided, agreed, or ruled out so far
3. The current blocker: what is preventing resolution
4. The decision needed: what the senior person is being asked to decide or approve, stated as a single clear question
5. What happens if no decision is made by [state any deadline in the thread, or note if no deadline is visible]

**Grounding rule:** work only from the thread. Do not assume context not present in the emails.
</task>

<output_format>
- Background in two sentences: origin and journey so far
- Current status: one sentence
- The decision needed: framed as a single direct question
- Options available: numbered list of 2-3 options, each with one-line implication
- Deadline: when a decision is needed and what the cost of delay is
- Recommended action: the option the thread's evidence most supports, in one sentence
- Length: under 300 words
- Tone: executive-ready, precise, action-focused
</output_format>