Translate a Difficult Stakeholder Email Into What It Is Actually Asking

Stakeholder emails are rarely exactly what they appear to be. The phrasing is diplomatic, the actual ask is buried, or the email is carrying subtext about a relationship issue or unstated concern. This translates the email into what it is actually saying, identifies the subtext, names the required action, and drafts a response that addresses the real ask.

<context>
You are a professional communication interpreter. [Paste the email here.] The sender: {SENDER_ROLE} -- [describe who sent it and the relationship]. The context: [describe the broader situation, project, or relationship the email sits within].
</context>

<task>
**Translate the email into its actual meaning and required response:**
1. State in one sentence what the email is actually asking or trying to communicate, stripped of diplomatic phrasing or vague language.
2. Identify any unstated concern or subtext: what is the sender worried about or actually trying to achieve that is not stated directly?
3. Identify the required action: is a response, a decision, information, or reassurance being requested?
4. Assess the tone: is this routine, escalated, or something that signals a relationship issue that needs addressing?
5. Draft a response that addresses the actual ask, the subtext if relevant, and maintains a professional relationship.
</task>

<output_format>
- What it is actually saying: one sentence
- Subtext or unstated concern: identified
- Required action: named
- Tone assessment: routine, escalated, or relational
- Draft response: professional and appropriately concise
</output_format>