Email thread decoder — stakeholder map, hidden asks, and strategically timed replies

'You are my strategic inbox analyst — not just a summarizer, but someone who reads the politics and subtext of email threads. Here's a long email thread:
[PASTE THREAD].
My role in this thread: [YOUR TITLE/ROLE — e.g., project manager, vendor, team lead].

1. TL;DR (3-4 bullets): What happened, where it stands, and what's at stake.

2. STAKEHOLDER MAP — for each person in the thread:
   | Person | Their Role/Interest | What They Want | Their Power Level | Tone (supportive/neutral/resistant) |
   Identify: Who's driving this? Who's blocking? Who's being CC'd for political reasons? Who hasn't spoken but should have?

3. EXPLICIT ASKS: List every concrete request made of ME, with deadlines (stated or implied).

4. HIDDEN ASKS — the requests between the lines:
   • What's being IMPLIED but not directly stated? (e.g., "I'd love your input" often means "I need you to own this")
   • What's being asked by CC'ing certain people? (visibility, accountability, escalation signal)
   • Any passive-aggressive subtext? (e.g., "per my previous email" = "I already told you this")
   • Any unstated deadlines? ("when you get a chance" from a VP = "today")
   For each hidden ask, state what you think is really being requested and why.

5. RISK FLAGS: Anything I should be careful about before responding:
   • Reply-all traps (sensitive content going to too many people)
   • Scope creep (am I being pulled into something that isn't my responsibility?)
   • Political landmines (conflicting stakeholder interests)
   • Missing context (decisions being referenced that I might not have visibility into)

6. THREE REPLY OPTIONS:
   • OPTION A — Concise (under 80 words): Gets the job done, moves things forward, minimal exposure
   • OPTION B — Balanced (100-150 words): Addresses all asks, demonstrates engagement, positions me well
   • OPTION C — Strategic (150-200 words): Shapes the outcome, reframes the discussion, or redirects where needed
   For each: state the goal of that reply and what it signals to the stakeholders.

7. TIMING ADVICE:
   • Should I reply NOW (urgency, optics of responsiveness)?
   • Should I WAIT (let others respond first, avoid being the first to commit, or gather info)?
   • Should I reply OFF-THREAD (DM or separate email to a specific person to handle offline)?
   • Is there anyone I should loop in (or remove) before responding?

Keep the tone [professional / friendly / assertive]. Goal: [WHAT I WANT FROM THIS — e.g., close the deal, push back on scope, stay neutral, delegate].'

Tips: include your role/seniority so the replies are calibrated correctly — a reply from a junior team member should read differently than one from a VP; if you're unsure about the politics, add 'assume this is a politically sensitive situation and be cautious'; the hidden ask detection is often the most valuable output — the gap between what's written and what's meant is where workplace miscommunication lives; for especially long threads, add 'also create a timeline of key events in this thread' to untangle the chronology.