The prompt
Score 10 of 10, Excellent
Use it when You need a short, respectful script and logistics checklist for letting someone go.
- {{employee_role}}
- {{attendees}}
- {{approved_reason}}
- {{approved_terms}}
- {{logistics}}
- {{hr_contact}}
Full prompt and why it works
Prompt
Prepare a plan for a meeting in which {{employee_role}} will be told that their employment is ending. The decision has been made and reviewed by HR or employment counsel; this plan only helps {{attendees}} deliver it clearly, respectfully and in line with the approved terms. HR or counsel should check the script before the meeting. Approved reason, as it may be stated in the meeting: """ {{approved_reason}} """ Approved terms (last day, final pay, any severance, benefits, equipment return, references and what may be said to the team): """ {{approved_terms}} """ Meeting details: {{logistics}} Produce, with a heading for each part: 1. Script for the person leading, under 200 words: the decision in the first two or three sentences, the approved reason in one sentence, then what happens next. For example, an opening with the right shape: "Thank you for meeting with me. I have difficult news: we have decided to end your employment, effective [date]." The example shows the form only. 2. Likely reactions: five, such as silence, anger, arguing with the reason, asking for another chance, or raising a complaint or legal concern. For each, a calm reply of one or two sentences that neither debates the decision nor adds reasons. For a complaint or legal concern, the reply acknowledges it, does not argue, and says it will be passed to {{hr_contact}}. 3. Checklist: before the meeting (HR has confirmed there is no recent complaint, protected leave or accommodation request that needs review first; the approved terms in writing; a private room; access timing agreed with IT), during, and after (equipment, personal items, a note of what was said, how and when the team is told). 4. What not to say: five to eight short lines. Plan for a short meeting, usually 10 to 15 minutes. The tone should be direct and kind: the person should leave knowing what happened and what comes next, with their dignity intact. Rules: - Use only the approved reason and terms. Do not add reasons, severance, pay dates, benefit end dates, legal rights or promises about references. - Do not comment on the person's character or personal life, in the script or in the replies. If a term the meeting needs is missing, do not guess: write [HR TO CONFIRM] in its place. If the reason does not read as approved, or the material mentions a recent complaint, leave, health condition or accommodation request, add a first line starting "FOR HR:" that says so, because the meeting should not go ahead until HR or counsel has reviewed it.
Variables
- {{employee_role}}
- The person's role and team.
- {{attendees}}
- Who will be in the meeting, for example "the manager, who leads, and an HR partner".
- {{approved_reason}}
- The reason HR or counsel has approved, in the words that may be used in the meeting.
- {{approved_terms}}
- The approved terms: last day, final pay timing, any severance, benefits, equipment return, references and what the team will be told.
- {{logistics}}
- Date, time, place or video link, and when system access will change.
- {{hr_contact}}
- Who handles questions and concerns afterward, for example "our HR business partner".
Why it works
- What to avoid. It sticks to the approved reason and terms and lists what not to say, because new reasons or promises made in the room are where these meetings go wrong.
- What good looks like. A short meeting with the decision in the first sentences gives the person clarity without a debate, and keeps their dignity intact.
- If unsure. Missing terms are marked for HR, and a FOR HR line stops the plan if the material suggests a recent complaint, leave or accommodation request.