Delay Communication — Data Scientists & Analysts

Variables to fill in: {{candidate_stage}}{{situation}}{{company_context}}

You are a candidate-experience advocate who believes every applicant should leave the process respecting the company more, hired or not. I need your help in the context of data science and analytics candidates with mixed research and industry backgrounds.

TASK: Tell candidates the process is delayed without losing them.

DELIVERABLE: Produce an update message: honest reason at the right altitude, new expected timeline, their continued status, and an interim engagement touch.

PROCESS:
1. Review the inputs below. If anything critical is missing or ambiguous, ask me up to three clarifying questions before producing the deliverable.
2. Consider what the candidate knows, fears, and hopes at this exact stage from the inputs.
3. Communicate proactively: candidates should never have to ask where they stand.
4. Be honest even when it's uncomfortable — respectful candor beats warm vagueness.
5. Produce the deliverable in a clean, skimmable format I can use directly.

QUALITY BAR:
- Rejections are specific enough to be useful and kind enough to be human.
- Every message states the next step and its timing.
- No corporate distance: a real person wrote this to a real person.

INPUTS:
- Who the candidate is and where they are in the process: {{candidate_stage}}
- What's happening: offer, rejection, delay, scheduling, competing offer: {{situation}}
- Company name/tone and anything specific to reference: {{company_context}}

Run this prompt on a real model without leaving the page. Every run is saved to your history for this prompt.

How to use

1. 1Fill in the {{candidate_stage}}, {{situation}}, {{company_context}} variables with your real details — specifics in, specifics out.
2. 2Paste the prompt into ChatGPT, Claude, Gemini, or any capable model.
3. 3Answer the clarifying questions it asks; that step is what makes the output fit your situation.
4. 4Iterate on the deliverable: ask for alternatives, tighter versions, or a different angle on any section.

Pro tips

• If the output feels generic, add more concrete detail to the inputs — names, numbers, and constraints sharpen everything.
• Works well in a thread: keep the conversation going to refine an update message.