ChatGPT, Claude & Gemini Prompts for Healthcare Administration

Patient Letters, Reminders, No-Shows & Telehealth

Patients read admin messages closely and often anxiously. These prompts draft appointment letters, reminder sequences, referral-process explanations, missed-appointment follow-ups, leaflets, delay notices, accessibility guidance and telehealth joining instructions. One prompt analyses aggregate no-show counts. They leave clinical wording to a qualified professional, marked [CLINICIAN REVIEW].

You are a patient communications officer at {{PRACTICE_TYPE}}. Write an appointment confirmation letter that a patient can understand on first read.

Appointment details: {{APPOINTMENT_DETAILS}}
How to find us and park or use transport: {{DIRECTIONS}}
What the patient must bring or do beforehand (admin only, such as ID, forms, arrival time): {{BEFORE_YOU_COME}}
Reading level: plain English, about US grade 7 (UK reading age 12).

Include: a clear first line with date, time and place; what to bring; how to cancel or change, with the notice we ask for; what happens if they are late; accessibility and interpreter requests; our phone number as {{CONTACT_DETAILS}}. Keep it under 250 words, warm and neutral, with short paragraphs and a bulleted list for the bring-list.

Then give a 160-character text-message version of the same reminder.

Put the date and time in the first line, in bold, and write the date out in words so it cannot be misread. Do not mention the reason for the visit. Add [PATIENT NAME] and [DATE] placeholders. If I left out a fact you need, write [ADD] rather than guessing. Anything clinical gets [CLINICIAN REVIEW].

You are a front-office manager designing reminders for {{PRACTICE_TYPE}}. Create a three-step reminder sequence for {{APPOINTMENT_TYPE}} appointments.

Channels we can use: {{CHANNELS}}
Notice we need for cancellations: {{CANCELLATION_NOTICE}}
Tone of the practice: {{TONE}}

Write: (1) a reminder to send one week before, (2) a reminder to send two days before with a simple reply or link action to confirm, (3) a same-day message with arrival and entry details. For each, give the SMS version (max 160 characters) and, where the channel allows, an email version with a subject line. Never include diagnosis, test names or treatment details in any message; messages may be seen by someone else. Include an opt-out line and a way to reach a person.

Finish with a short table listing each message, when to send it, and the one action we want from the patient.

Use placeholders such as [PATIENT NAME]. Anything about symptoms, results or preparation for a procedure is clinical: leave it out and mark it [CLINICIAN REVIEW]. If a channel cannot carry a confirm-by-reply action, say so and offer an alternative.

You are a health literacy editor. Rewrite the following administrative process explanation so a patient with no healthcare background can follow it.

Process: {{PROCESS_NAME}}
Current wording (admin text only): {{CURRENT_TEXT}}
Audience: {{AUDIENCE}}

Produce: (1) a rewrite in plain English at about US grade 6 to 8 (UK reading age 11 to 13), with short sentences, everyday words, and any unavoidable term explained in brackets the first time; (2) a numbered "what happens next" list with who does each step and a rough timeframe only if I supplied one; (3) a "what we need from you" checklist; (4) a list of the jargon words you replaced and what you replaced them with.

If the current wording describes anything clinical, leave that sentence unchanged and mark it [CLINICIAN REVIEW]. Do not invent timelines, fees or legal rights; mark any gap as [CONFIRM WITH OFFICE MANAGER].

Keep every sentence under 20 words where possible. Use bullet points for steps. Do not name individuals. Do not add documents, steps, contacts or requirements that are not in the text; write [CONFIRM] where the text is silent.

You are a referral coordinator at {{ORGANISATION}}. Write a letter explaining to a patient how the referral process works, without discussing why they were referred.

Referral type (admin label only): {{REFERRAL_TYPE}}
Steps in our process and who does each: {{PROCESS_STEPS}}
Usual waiting-time information we can legitimately share: {{WAIT_INFO}}
Who they should contact for updates: {{CONTACT_DETAILS}}

Write the letter in plain English under 300 words. Include: what a referral is, what we do, what the other service does, what the patient should do if they hear nothing, and how to check their contact details are right. Add a short note on how to ask us to repeat or put this in another format.

Do not predict outcomes, say how urgent anything is, or reassure about a condition; mark those [CLINICIAN REVIEW]. If wait information was not provided, write [CONFIRM] rather than guess.

Use [PATIENT NAME] and [DATE] placeholders. Give the letter a clear subject line and finish with a single sentence on what the patient should do next.

You are a practice manager. Draft a supportive follow-up to a patient who missed an appointment, written to bring them back rather than to blame them.

Appointment type (admin label only): {{APPOINTMENT_TYPE}}
Our missed-appointment policy in brief: {{POLICY_SUMMARY}}
How to rebook: {{REBOOKING_OPTIONS}}
Tone: {{TONE}}

Write three versions: a phone script of about 90 words for a receptionist leaving a voicemail, an SMS of up to 160 characters, and a short letter. Each must say we noticed the missed visit, ask them to contact us, explain how to rebook, and mention any support with transport, childcare or access only if listed in my policy summary. No clinical detail, no mention of why they might need care, and no threats or fee warnings unless my policy lists them.

Add three tips for the voicemail on identity-safe wording, so nothing private is said to someone who is not the patient.

Use [PATIENT NAME] placeholders. Anything about the patient's health or why they were due is clinical: leave it out and mark it [CLINICIAN REVIEW]. Present the three versions under clear headings.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are a document designer for health services. Turn the text below into the structure of a one-page patient leaflet about {{LEAFLET_TOPIC}}. The text is administrative (opening hours, how to book, what to bring); do not add clinical content.

Source text: {{SOURCE_TEXT}}
Audience: {{AUDIENCE}}
Languages needed later: {{LANGUAGES}}

Deliver: (1) a headline and a 20-word summary; (2) five or six short headed sections with 2 to 4 lines each; (3) a boxed "Contact us" panel; (4) suggestions for icons or simple images and alt text for each; (5) a readability note: longest sentences to shorten and any term to define; (6) translation notes: phrases that may translate badly and should be reviewed by a professional translator.

Do not add statistics, opening hours or phone numbers I did not provide; use [ADD] as a placeholder.

Present the result as a numbered list matching the six items. Write headings as questions a patient would ask.

You are the communications lead at {{ORGANISATION}}. Write a short, honest notice for patients about a delay: {{DELAY_SITUATION}}.

What we know for sure: {{CONFIRMED_FACTS}}
What we do not yet know: {{UNKNOWNS}}
What patients can do or where to get updates: {{PATIENT_OPTIONS}}

Write three versions: (1) a waiting-room poster of under 60 words, (2) a website or app banner of under 40 words, (3) a script for reception staff of about 100 words that they can say aloud. Apologise once without over-apologising, state facts plainly, and do not speculate about causes or promise a time. Do not include anything about individual patients.

Include a one-line internal checklist of who must approve the notice before it goes live, and a reminder to update or remove it by a set time. If urgent or clinical questions might arise, add a line telling reception how to escalate; mark clinical wording [CLINICIAN REVIEW].

Do not add emergency advice that I did not give. Present each version under its own heading, with a word count after each. Put the most important fact in the first sentence.

You are an access and inclusion lead for {{ORGANISATION}}. Draft guidance for non-clinical staff on how to handle requests for interpreters, translated documents and accessibility support.

Services we actually offer: {{SERVICES_OFFERED}}
Who approves or books them: {{APPROVAL_PROCESS}}
Local legal or policy duties as we understand them: {{LOCAL_RULES}}

Produce: (1) a one-page staff guide with what to ask, how to record the request (without recording unnecessary personal detail), and how to book; (2) a phrase card of five plain sentences staff can say; (3) a note to patients explaining that they may ask for support, in under 120 words; (4) a list of mistakes to avoid, such as using a family member or child as an interpreter for sensitive matters.

I am not asking for legal advice. Tell me which duties above I should confirm with our compliance lead or a lawyer, and mark anything uncertain [VERIFY].

Use headings for each of the four deliverables and keep staff-facing wording to short sentences. Mark any medical-consent wording [CLINICIAN REVIEW], because consent conversations are clinical.

You are an operations analyst at {{ORGANISATION}}. Analyse our missed-appointment (no-show or DNA) data and suggest admin changes.

Aggregate counts by clinic type, weekday, time slot and booking lead time (counts only, no patient rows): {{AGGREGATE_COUNTS}}
Reminder and cancellation process today: {{CURRENT_PROCESS}}
Constraints such as staffing, booking system limits and policy: {{CONSTRAINTS}}

Do this: (1) calculate the missed-appointment rate for every group, showing the working and the totals, and flag groups with fewer than 20 appointments as too small to rely on; (2) rank groups by rate and by number of lost slots; (3) list patterns the counts support and patterns they do not; (4) give five admin changes (reminder timing, easier cancelling, waiting-list fill, booking lead-time limits, confirmation by reply), each with effort, risk and how to measure it; (5) suggest a four-week trial design; (6) draft a one-page summary for the practice meeting.

Do not guess reasons for non-attendance or infer anything about individuals. Overbooking and slot lengths are clinical-governance decisions: do not recommend them; list them only as questions for the clinical lead. Do not use benchmarks I did not supply.

You are a telehealth coordinator at {{ORGANISATION}}. Write patient-facing admin instructions for a remote appointment.

Platform and how patients join: {{PLATFORM_AND_JOIN_STEPS}}
What we ask patients to prepare (device, space, ID, forms): {{PREPARATION}}
What we do if the connection fails or the patient cannot join: {{FALLBACK_PROCESS}}
Privacy and recording rules as stated by our policy: {{PRIVACY_RULES}}

Produce: (1) a step-by-step guide at a US grade 7 or UK reading age 12 level; (2) a two-minute test checklist to do the day before; (3) a reminder text of up to 160 characters; (4) a short script for reception to guide someone by phone; (5) a staff checklist for starting a session on time; (6) a note on accessibility, such as captions, an interpreter and help from a carer, listing only what we offer.

Use only the platform steps I supplied; do not invent menus or buttons. Do not describe what the clinician will do or say. Do not add emergency or self-care advice that I did not give. Mark anything about consent to remote care, prescribing or clinical suitability [CLINICIAN REVIEW]. Remote-care rules vary by place, so list what to verify with compliance as [VERIFY].

Front Desk & Reception

Reception staff handle the hardest conversations with the least preparation. These prompts build phone scripts, a role-play partner for difficult calls, check-in instructions, shift handovers, phone menu text, records-request explanations and a waiting-room audit. Where a caller mentions symptoms, the scripts escalate and never interpret them.

You are a front-desk trainer at {{PRACTICE_TYPE}}. Write phone scripts for receptionists for these common calls: {{CALL_TYPES}}.

Our opening hours and booking rules: {{BOOKING_RULES}}
What reception may and may not discuss: {{SCOPE_LIMITS}}
Tone: warm, calm and professional.

For each call type give: an opening line, the questions to ask in order (administrative only), the information to give, a closing line, and a "handover" line for when the caller needs someone else. Add a general script for callers who are upset, and one for verifying a caller's identity before discussing anything, using these steps: {{ID_CHECK_STEPS}}.

Rules: receptionists never give medical advice, interpret symptoms or decide urgency. Where a caller describes symptoms, the script must follow our escalation route: {{ESCALATION_ROUTE}}. Mark anything clinical or uncertain [CLINICIAN REVIEW]. Put each call type under its own heading.

Include a note for each call type listing what the receptionist must never say. Keep each script under 120 words.

You are a customer-service coach for healthcare reception teams. Run a role-play to practise a difficult administrative conversation: {{SCENARIO}}.

I will play: {{MY_ROLE}}
You will play: a fictional patient or relative, unnamed, who is {{EMOTIONAL_STATE}}
Policies in play: {{POLICY_SUMMARY}}

Rules: stay in character and respond in two to four sentences at a time. Do not use real patient details. Do not make clinical claims; if the scenario drifts into symptoms or treatment, break character and say [CLINICIAN REVIEW: escalate per policy]. After six exchanges, stop and give feedback: what I did well, three phrases that worked, three that could escalate things, and a better rewrite of my weakest reply.

Finish with a three-line summary I can use as a huddle note, covering acknowledging feelings, explaining the policy in plain words, and offering a next step.

Begin by asking me one question: confirm the scenario and my role. Then start the role-play only when I say 'go'. To stop at any time I will type 'stop', and you will give feedback immediately.

You are an operations lead at {{ORGANISATION}}. Write step-by-step instructions that tell patients how to check in and register for {{VISIT_TYPE}}.

Check-in options we offer (desk, kiosk, app, online): {{CHECKIN_OPTIONS}}
Documents and forms needed (admin only): {{DOCUMENTS_NEEDED}}
What staff will do at each step: {{STAFF_STEPS}}

Write: (1) a patient guide with numbered steps and a "if something goes wrong" section; (2) a poster version with five lines and a QR-code instruction placeholder [QR LINK]; (3) a one-paragraph script for staff to say to a first-time visitor; (4) a checklist for staff to confirm the desk is ready at opening.

Keep sentences short. Do not request medical history details in the instructions; if a form asks about health, say only that staff will explain it and mark the wording [CLINICIAN REVIEW]. Tell me what privacy notice or consent wording I should confirm with my compliance lead.

Present items 1 to 4 under separate headings and keep the patient guide to about 250 words. Use [ADD] for any step I did not describe.

You are a front-office supervisor. Create a shift handover template and an example filled with fictional, non-identifiable entries for {{FRONT_DESK_TYPE}}.

Things that matter in our handover: {{HANDOVER_ITEMS}}
Systems and tools used: {{SYSTEMS}}
Shifts: {{SHIFT_PATTERN}}

Produce: (1) a one-page template with sections for open tasks, callbacks owed, equipment or system issues, staffing changes, notices for the next shift, and "things I'm unsure about"; (2) a five-line rule set for what must never appear in a handover note, such as full patient names or clinical details, and what to write instead; (3) a spoken 60-second version; (4) a Friday review checklist for the supervisor.

Use placeholders like [PATIENT A] for any example. Mark anything that sounds clinical [CLINICIAN REVIEW] and instruct staff to hand it to a clinician directly rather than writing it down. Present as a table plus short notes.

Keep the template to one printed page. Include a column for 'done / still open / escalated' and a row for equipment faults.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are a communications officer for {{ORGANISATION}}. Write the spoken text for our phone menu and voicemail greetings.

Our options: {{MENU_OPTIONS}}
Opening hours: {{OPENING_HOURS}}
Emergency and urgent-advice instruction we are required or choose to give: {{URGENT_INSTRUCTION}}

Write: (1) a main greeting under 25 seconds when read aloud, (2) text for each menu option, (3) after-hours message, (4) voicemail greeting for a named team, (5) holiday closure template with {{DATES}} placeholder.

Put the urgent instruction first where appropriate, in my wording exactly. Write for the ear: short sentences, numbers spoken clearly, no more than four menu options at a time. Add notes on pace, pauses and translation for other languages, and flag any line a clinician or compliance lead should review before recording. Use [CLINICIAN REVIEW] for urgent-care wording.

Give an approximate spoken duration for each message and mark each line the clinical lead should approve. Give a spoken-length estimate for each message.

You are an information governance assistant. Help front-desk staff explain how patients can request their own records, based on our policy only.

Our policy and process: {{POLICY_TEXT}}
Jurisdiction: {{JURISDICTION}}
Identity checks we require: {{ID_CHECKS}}

Produce: (1) a plain-English explanation for patients under 200 words; (2) a staff flowchart in text form (step, owner, decision point); (3) a template acknowledgement letter with [PATIENT NAME] and [DATE RECEIVED] placeholders; (4) a template for explaining a delay or partial refusal, but only using reasons I supply; (5) a list of questions to ask the information governance lead.

Do not state legal deadlines, fees or exemptions unless they appear in my policy text; instead write [VERIFY LOCAL LAW] and say what to check. Do not summarise or discuss any actual record. Mark clinical questions [CLINICIAN REVIEW].

Write the patient explanation at about US grade 7 (UK reading age 12) and keep sentences short. Use [ADD] for any step my policy does not describe.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are an operations consultant. Create a walkthrough audit of a waiting area at {{ORGANISATION}} that I will do myself.

Features of the space: {{SPACE_DESCRIPTION}}
Patient groups we serve: {{PATIENT_GROUPS}}
Current complaints or comments (summarised, no names): {{COMMENT_SUMMARY}}

Produce: (1) a checklist of 25 observations grouped by arrival, signage, seating and access, noise and privacy, information on display, children and carers, and toilets; (2) three questions to ask five patients, framed neutrally; (3) a scoring table I can use to prioritise fixes by impact and effort; (4) a short template for reporting the results to management.

Include privacy checks such as whether screens, desk conversations or call-outs reveal personal details. Do not invent legal standards; say which requirements I should verify locally.

Frame observations as yes/no or 1-to-5 items so that different observers record the same things. Add a column for evidence, such as a photograph of a sign with no person in it.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

Policies, SOPs & Governance

Procedures only help when people can follow them. Draft SOPs, turn policies into briefings, write privacy reminders, a continuity outline, a policy gap review, neutral incident summaries, a first-hour privacy incident checklist and an inspection readiness tracker. Rules that depend on HIPAA, UK GDPR or local law are marked for your privacy or compliance lead to verify.

You are a quality and operations lead at {{ORGANISATION}}. Draft a standard operating procedure for the following non-clinical process: {{PROCESS_NAME}}.

Who does it and who owns it: {{ROLES}}
How it works today, as notes: {{CURRENT_STEPS}}
Systems and forms used: {{SYSTEMS}}

Use this structure: purpose, scope, definitions, roles and responsibilities, step-by-step procedure (numbered, one action per step), exceptions and escalation, records to keep, related documents, review date and version table. Add a RACI table.

Rules: write steps in the active voice with a named role per step. List every assumption as [ASSUMPTION] and every missing detail as [ADD]. Do not invent regulations or standards; list which ones I should check, such as HIPAA, UK GDPR or accreditation rules, as [VERIFY].

Keep each step to one sentence. End with a short checklist the user can print and tick, and list the three questions an auditor might ask about this SOP. Keep the whole SOP to two pages and note which steps a new starter is most likely to get wrong.

You are a compliance communications specialist. Convert the following policy into a staff briefing.

Policy text (non-clinical, no patient data): {{POLICY_TEXT}}
Audience: {{AUDIENCE}}
Why it is changing: {{REASON_FOR_CHANGE}}

Produce: (1) a one-paragraph summary at US grade 8 (UK reading age 13); (2) "what changes for me" bullets by role; (3) five do's and five don'ts with an example for each, using fictional scenarios; (4) a 5-question quiz with answers; (5) an FAQ of five likely questions based only on the policy text; (6) a list of ambiguities or contradictions you noticed, so the policy owner can resolve them.

Do not add rules that are not in the policy. If the policy raises a legal or clinical point, mark it [VERIFY] and do not interpret it. Keep each example realistic but free of real names or patient details.

Quote the policy's own section numbers where you refer to a rule so staff can find the original. Do not change the meaning of any rule.

You are a privacy awareness trainer for {{ORGANISATION}} in {{JURISDICTION}}. Create a staff reminder pack about handling patient information responsibly in everyday admin work.

Systems and tools our staff use: {{TOOLS_USED}}
Our AI-use rule, if any: {{AI_RULE}}
Recent incident types (anonymised): {{INCIDENT_TYPES}}

Produce: (1) a one-page poster text with six rules; (2) five short "what would you do" scenarios with fictional details and model answers; (3) a short note explaining why patient information must not be pasted into public AI tools; (4) a checklist for sending emails or letters; (5) three lines for managers to say in a team huddle.

I am not asking for legal advice. Describe obligations only in general terms and tell me what to confirm under HIPAA, UK GDPR or local policy with the privacy officer; mark [VERIFY] wherever you rely on a rule. No real patient examples.

Keep each model answer to three sentences. Make the poster readable from two metres, with each rule under ten words.

You are an operations resilience planner for {{ORGANISATION}}. Outline a non-clinical business continuity plan for {{DISRUPTION_TYPES}}.

Critical admin functions: {{CRITICAL_FUNCTIONS}}
Systems we rely on: {{SYSTEMS}}
Staff roles available: {{ROLES}}

Produce: (1) a table of each function, the impact of an outage, the manual workaround, who is in charge, and how long we can cope (leave blank as [ADD] if unknown); (2) a communications tree with sample messages for staff and patients; (3) a downtime paper-process checklist for registration, appointments and messages; (4) a recovery checklist; (5) a test exercise outline.

Do not invent legal requirements or standards; list those to verify. Never include real contact numbers or patient details; use [PHONE] placeholders.

Present the output under the five headings in order. Where I have not told you a recovery time, leave the cell as [ADD] and do not suggest one. Give each manual workaround as numbered steps a temporary staff member could follow without training, and list the supplies, such as paper forms and contact lists, that must be kept ready.

You are an internal auditor reviewing the policy library of {{ORGANISATION}}, a {{ORGANISATION_TYPE}}.

Policies we currently have: {{POLICY_LIST}}
Regulators or standards we answer to: {{REGULATORS}}
Last review dates and known problem areas: {{REVIEW_NOTES}}

Produce: (1) a table of common non-clinical policy areas for an organisation like ours, showing whether I appear to have each; (2) the ones that look missing or out of date, ranked by risk; (3) a suggested review calendar; (4) five questions to ask each policy owner; (5) a template for recording the review.

Be explicit that you cannot see our regulators' current requirements: for each regulator name, tell me to check their current published guidance and do not state specific rules or deadlines. Mark uncertain points [VERIFY].

List the areas as a table with columns for area, evidence of a current policy, risk if missing, and suggested owner. Do not state what any regulator requires. Limit the output to one page of tables.

You are a patient safety administrator preparing a non-identifiable summary of a non-clinical incident, such as a lost document, double booking, or system outage.

What happened (use labels, no names): {{INCIDENT_FACTS}}
When and where in the process: {{TIMING_AND_PLACE}}
Actions already taken: {{ACTIONS_TAKEN}}

Write: (1) a neutral, factual summary in under 200 words; (2) a timeline table; (3) contributing factors phrased as process issues, not blame; (4) three suggested corrective actions with owners marked [ASSIGN]; (5) questions for the people involved; (6) a check on whether it may need reporting externally, expressed as a question for the compliance lead.

Do not speculate beyond the facts. Do not say whether anyone was harmed or whether the incident meets a legal reporting threshold; mark those [CLINICIAN REVIEW] or [VERIFY]. Replace any names or numbers with placeholders.

Keep the summary free of names: write [STAFF MEMBER A] and [PATIENT A].

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are an information governance coordinator at {{ORGANISATION}} in {{JURISDICTION}}. Draft an internal first-response checklist for a suspected privacy incident, such as a letter sent to the wrong address, an email to the wrong recipient, or a lost paper file.

Our current incident and breach policy, if any: {{POLICY_SUMMARY}}
Who is our privacy or compliance lead, by role: {{PRIVACY_LEAD}}
Systems and paper records involved: {{RECORD_TYPES}}

Produce: (1) the first 60 minutes: what any staff member does and does not do (do not delete evidence, do not email the data again, tell the lead at once); (2) an information-gathering form using labels, with names removed and dates, places and rare roles generalised; (3) a decision table of who decides whether the incident must be reported, left blank where the answer depends on law; (4) a timeline template; (5) a calm template note to the affected person with [PATIENT NAME] and [WHAT HAPPENED] placeholders, for the lead to approve..

I am not asking for legal advice. Do not state reporting deadlines, thresholds or penalties from memory. For each, write [VERIFY: current rule under HIPAA, UK GDPR or local law] and tell me whom to ask. Keep to plain English and numbered steps.

You are a quality manager preparing {{ORGANISATION}} for {{INSPECTION_TYPE}}. Build an admin-side readiness tracker.

Standards document or inspector framework we use (paste headings only): {{STANDARD_HEADINGS}}
Evidence we normally keep (policies, logs, training records, meeting minutes): {{EVIDENCE_AVAILABLE}}
Weeks until the visit: {{WEEKS_TO_GO}}

Produce: (1) a table mapping each heading to the non-clinical evidence that could support it, who holds it and whether it is current; (2) a countdown plan by week; (3) a list of documents with no review date or owner; (4) ten questions staff may be asked, with the factual point each answer should cover, with no scripted answers; (5) a folder index and naming scheme; (6) a one-page briefing for staff about how to answer honestly.

Do not claim what the standard requires beyond the headings I pasted, and do not tell me we would pass. Mark [VERIFY WITH CURRENT STANDARD] where the wording matters. Leave clinical evidence rows blank and label them [CLINICIAN LEAD TO COMPLETE]. Output the tracker as a table.

Staff, Rotas & Training

Admin teams run on rotas, onboarding and clear expectations. These prompts write healthcare job descriptions with pre-employment checks flagged to verify, check a rota for coverage and fairness, plan inductions, build a cross-training matrix and set out reception competencies. Staff data is personal data, so the prompts ask for initials and no health reasons.

You are an HR business partner at {{ORGANISATION}}. Write a clear, inclusive job description for the role of {{ROLE_TITLE}}.

Main duties: {{MAIN_DUTIES}}
Essential skills and experience: {{ESSENTIALS}}
Working pattern, location and pay range if shareable: {{TERMS}}

Include: summary, key responsibilities (8 to 10 bullets starting with verbs), essential and desirable criteria separated, working conditions, equality statement, and a short "a day in this job" paragraph. Avoid biased or unnecessary requirements, jargon and age-coded words; list any you changed.

Do not invent salary figures, benefits or legal terms; mark gaps [ADD]. Tell me what I must check, such as local employment law or registration rules.

Limit the job description to two pages. Give the list of biased or unnecessary phrases you replaced at the end, with the replacement for each. Use plain English throughout. Include a line on confidentiality duties and, as items to verify rather than state, any pre-employment checks, registration or immunisation requirements that apply in our setting. Do not assume which apply: mark each [VERIFY WITH HR].

You are a workforce planner reviewing an administrative team's rota at {{ORGANISATION}} for fairness and coverage. Use the fictional or anonymised data below.

Roles and numbers: {{TEAM_STRUCTURE}}
Cover required by time: {{COVER_RULES}}
Rota data (initials only): {{ROTA_DATA}}
Rules and agreements we follow: {{WORKING_RULES}}

Do the following: (1) check coverage against the cover rules and list gaps; (2) compare weekends, late shifts and holidays by person using a table; (3) flag patterns that look unfair or likely to cause tiredness, without making assumptions about individuals; (4) suggest three adjustments; (5) draft a short, neutral message to the team explaining a change.

Show your counts so I can check them, and give me a spreadsheet formula or a manual method for recounting each column, because models miscount. You cannot verify employment law or union agreements: list the rules I should confirm with HR and mark them [VERIFY].

Present the counts in a table by person (initials) with columns for weekend, late and holiday shifts. Do not suggest changes that break the cover rules I gave.

Colleagues' data is personal data too: use initials or roles, never names, and leave out health or absence reasons and any date or rare role that identifies a person. If that is not possible, use only an approved tool covered by a data processing agreement.

You are a training coordinator. Create a four-week induction plan for a new {{ROLE_TITLE}} joining {{ORGANISATION}}.

Key systems and processes to learn: {{SYSTEMS_AND_PROCESSES}}
Mandatory training required before certain tasks: {{MANDATORY_TRAINING}}
Buddy or supervisor available: {{SUPPORT_AVAILABLE}}

Produce: (1) a week-by-week table of learning goals, activities and who supports; (2) a day-one checklist; (3) a "first questions" list the starter should feel free to ask; (4) sign-off points where the supervisor confirms competence; (5) a friendly welcome email under 150 words; (6) a short feedback form for week four.

Do not invent mandatory courses; use my list and mark gaps [ADD].

Number the weeks and use a table with columns for goal, activity, support and sign-off. Keep the welcome email warm and under 150 words. Include a confidentiality briefing before any system access, a plan for shadowing the front desk, and a checkpoint at the end of week two to ask what is unclear. Do not assume what systems the starter may access; use only my list and mark gaps [ADD].

You are an operations manager planning cross-training for the admin team at {{ORGANISATION}}.

Tasks the team must cover: {{TASK_LIST}}
Team skills today (initials, scores of 0 to 3 that I supply): {{SKILL_DATA}}
Constraints: {{CONSTRAINTS}}

Produce: (1) a skills matrix as a table; (2) the tasks where only one person can currently do the job, ranked by risk; (3) a 12-week training plan pairing trainers and learners, with sign-off criteria; (4) a script for talking to a team member about learning a new task; (5) a measure of success based on coverage, not output pressure.

Only use the data I provide; do not infer ability from anything else. Remind me to check job descriptions, pay and union agreements with HR before asking anyone to do new duties, and mark [VERIFY].

Show the matrix with initials down the side and tasks across the top. State clearly which tasks have only one person with a score of 2 or more.

You are a training lead. Build a competency checklist for a {{ROLE_TITLE}} at {{ORGANISATION}} that a supervisor can use to observe and sign off.

Core duties: {{CORE_DUTIES}}
Standards or policies the role must follow: {{POLICIES}}
Observation methods available: {{METHODS}}

Produce: (1) a table with competency, what good looks like in observable behaviours, how to assess, and sign-off date; (2) 10 competencies covering communication, privacy, systems, accessibility, escalation and teamwork; (3) a fair, non-judgmental observation form; (4) a template development plan for any gap.

Keep competencies to non-clinical admin tasks. Do not claim the checklist meets any accreditation standard; tell me what to verify with the quality team.

Present the checklist as a table. Use short, observable criteria and avoid vague words such as 'good' or 'professional'. Add a final column for the evidence the supervisor saw, and keep the whole checklist to two pages. Add a column for the date of each observation and a space for the staff member's own comments.

Meetings, Quality Improvement, Audit & Scheduling

Good minutes and tidy audits save hours every month. Turn rough notes into minutes, plan agendas, design a small improvement project, write up an audit with checked calculations, summarise admin dashboards and staff surveys, write a board narrative and draft a clinic session template for the clinical lead to approve. The prompts use only your numbers and show their workings.

You are the minute-taker for a clinic or practice governance meeting. Turn my rough notes into minutes for the {{MEETING_NAME}}.

Date, attendees (roles or initials), apologies: {{ATTENDANCE}}
Rough notes: {{ROUGH_NOTES}}
Format: {{FORMAT}}

Produce minutes with: standing headings where the notes cover them (matters arising, incidents and near misses, complaints, clinical-governance items, health and safety, operations); decisions kept separate from discussion; items deferred; risks raised; and a confidentiality line saying who may receive the minutes. Add an action log table with owner, due date and status, and a three-sentence summary for people who did not attend.

Rules: add no decisions or dates that are not in the notes; mark gaps [CONFIRM]. Replace patient names with [PATIENT A]; summarise clinical discussion only as "clinical item discussed" and mark it [CLINICIAN REVIEW] for the chair. If a note may describe a patient-safety event, complaint or near miss, add a line recommending the chair decide whether it needs an incident report.

Write in the past tense, about one page. For safeguarding or clinical-governance items, record only that they were reported to the named lead, not the detail.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are an experienced practice manager. Create an agenda and pre-read for a {{MEETING_TYPE}} meeting at {{ORGANISATION}}.

Topics to cover and time available: {{TOPICS_AND_TIME}}
Decisions needed: {{DECISIONS_NEEDED}}
Background documents: {{DOCUMENTS}}

Produce: (1) a timed agenda with lead names or roles, purpose for each item (information, discussion or decision) and papers needed; (2) a one-page pre-read summarising each decision with options and open questions; (3) the ground rules for the meeting; (4) a standing item for "learning from incidents and complaints, no names"; (5) a closing checklist so minutes go out within 48 hours.

Do not invent figures or recommendations. Keep patient-identifiable details out and use placeholders.

Give times in minutes and make sure they add up to the meeting length. State the purpose of each item as information, discussion or decision. Allow two minutes at the start for apologies and actions from last time, and end with a summary of decisions read aloud. Give the pre-read a title and a date.

You are a quality improvement facilitator. Help me plan a small non-clinical improvement project at {{ORGANISATION}}: {{PROBLEM_STATEMENT}}.

What we measure now (only numbers I supply): {{BASELINE_DATA}}
Team and time available: {{TEAM_AND_TIME}}
Constraints: {{CONSTRAINTS}}

Produce: (1) a refined problem statement and SMART aim with [ADD] where I need data; (2) a process map in text form; (3) a list of possible causes in a fishbone-style table; (4) three change ideas with effort and impact; (5) a PDSA cycle plan for the best idea; (6) measures: outcome, process and balancing; (7) a communication plan.

Do not invent baseline numbers or targets. Tell me which ethics, governance or audit approvals I should check before starting.

Number the seven outputs. For the SMART aim, give the wording as a template with blanks where I must add my own numbers. Keep each section to a few lines, state the assumptions you made, and include a stop rule: the conditions under which we would end or change the trial.

You are a clinical audit administrator writing up a non-clinical audit for {{ORGANISATION}}. Audit topic: {{AUDIT_TOPIC}}.

Standard or target we compared against: {{STANDARD}}
Method and sample (as described by me): {{METHOD}}
Results I counted (numbers only, no patient data): {{RESULTS}}

Write: (1) an executive summary of 150 words; (2) background and standard; (3) method; (4) results with a table and a sentence on what each shows; (5) discussion that mentions limits of the method; (6) recommendations with owners marked [ASSIGN] and dates [ADD]; (7) an action plan and re-audit plan.

Use only my numbers; recalculate any percentages and show the working so I can verify them. Do not overstate what the results prove. Check the standard's current wording with the source document and mark [VERIFY].

Keep percentages to one decimal place. If the sample is small, say that percentages can swing widely. Give recommendations as numbered actions, and state which are quick wins and which need more resource.

You are an operations analyst. Summarise the monthly admin figures below for the leadership team at {{ORGANISATION}}.

Figures (aggregate only, no patient data): {{MONTHLY_FIGURES}}
Comparison periods: {{COMPARISON}}
Questions leadership asked: {{QUESTIONS}}

Produce: (1) a five-line headline summary; (2) a table with figure, comparison, change and a note on whether the change looks meaningful or could be normal variation (explain simply); (3) three questions to investigate; (4) caveats such as small numbers or changed definitions; (5) a suggested chart for each figure and why.

Show your calculations. If the data is too small or inconsistent, say so and do not manufacture a trend. Do not use any external benchmarks I did not give you.

Use a table for item 2, and keep the narrative in item 1 to five lines. Where a figure moved by only a small amount on a small base, say it may be normal variation. Write for a reader with two minutes.

You are an engagement analyst. Summarise the results of a staff survey for the {{TEAM_NAME}} at {{ORGANISATION}}.

Survey results (aggregate scores and anonymised comment themes): {{SURVEY_DATA}}
Response rate and groups too small to report: {{RESPONSE_NOTES}}
What management wants to understand: {{MANAGEMENT_QUESTIONS}}

Produce: (1) a plain-language summary; (2) strengths and concerns with supporting evidence from my data; (3) a table of comment themes with example paraphrases, not quotes that could identify people; (4) five questions to explore with staff; (5) a shortlist of actions with owners marked [ASSIGN]; (6) a draft message to staff thanking them and saying what happens next.

Do not identify individuals or guess who wrote a comment. Do not diagnose burnout or health issues; for any health or safety concern, mark [HR / OCCUPATIONAL HEALTH REVIEW]. Do not invent benchmarks. Say clearly when numbers are too small to interpret.

Put the summary in under 200 words. Present the theme table with columns for theme, how many comments mention it (if I supplied counts), and a paraphrase.

Colleagues' data is personal data too: use initials or roles, never names, and leave out health or absence reasons and any date or rare role that identifies a person. If that is not possible, use only an approved tool covered by a data processing agreement.

You are a practice manager writing the operations section of a report for {{AUDIENCE}} at {{ORGANISATION}}.

Reporting period: {{PERIOD}}
Figures and facts (aggregate only, no patient data): {{FIGURES_AND_FACTS}}
Decisions or support you need from the reader: {{ASKS}}

Write: (1) a headline paragraph of three sentences that states what changed and what is needed; (2) a short section on performance against each figure, with the comparison I supplied and a plain statement of whether it is up, down or flat; (3) risks and issues in a table with owner and next step; (4) a RAG status for each area, with the rule you used to assign it, which I can change; (5) the asks, in order of priority; (6) one paragraph of context a non-specialist director needs.

Use only my figures. Show any percentage or difference you calculate with the working. Do not explain causes unless I gave them: write [CAUSE UNKNOWN] and suggest what to check. Keep to 450 words, in plain business English, with no adjectives that the figures do not support.

You are a practice operations manager preparing a proposal for the clinical lead at {{ORGANISATION}}. Help me draft an appointment-session template for {{CLINIC_TYPE}}.

Staff available and their hours: {{STAFF_AND_HOURS}}
Appointment types and the lengths the clinicians have set (take these as given): {{APPOINTMENT_TYPES_AND_LENGTHS}}
Demand pattern, in aggregate: {{DEMAND_SUMMARY}}
Rules we must keep (breaks, room use, cover): {{RULES}}

Produce: (1) a weekly template as a table by day and time showing which appointment types go where; (2) the arithmetic: slots per session, total slots per week, and a check that no one is booked beyond their hours; (3) slots held back for same-day demand, with the reasoning, labelled as a proposal; (4) three scenarios for sickness or absence; (5) questions for the clinical lead to decide, such as appointment lengths and overbooking; (6) a communication note to staff.

Do not change appointment lengths or decide who may see which patients; these are clinical decisions. Show all totals so I can check them, and say plainly if the inputs do not add up.

Complaints & Patient Feedback

Complaint handling is where tone and accuracy matter most. These prompts draft acknowledgements and response letters, group complaint themes, write safe replies to online reviews, and design a patient survey and summarise its results. Free text can identify people, so each tells you to de-identify first.

You are a patient experience officer at {{ORGANISATION}}. Write an acknowledgement letter for a complaint we have received.

Complaint handling steps and timescales in our policy: {{PROCESS_AND_TIMESCALES}}
Contact person for the complainant: {{CONTACT_PERSON}}
Support or advocacy services available: {{SUPPORT_OPTIONS}}

Write a letter of about 250 words that: thanks them for raising the concern; confirms we have received it and what happens next; gives realistic timescales exactly as in my policy; explains how to add information or get support; and avoids defending, blaming or promising an outcome. Use a warm, respectful voice with [COMPLAINANT NAME] and [DATE] placeholders.

Do not state any facts about the complaint or any clinical matter; mark clinical content [CLINICIAN REVIEW]. If my policy timescales are missing, mark [CONFIRM]. Tell me which statutory complaint rules I should verify locally.

Give the letter a subject line with a reference placeholder [REFERENCE]. Offer to talk by phone and to send information in another format.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are a complaints manager preparing a draft response letter for review by a senior leader. Use the investigation summary below, which has had names removed.

Complaint themes: {{COMPLAINT_THEMES}}
What the investigation found (facts only): {{FINDINGS}}
Actions taken or planned: {{ACTIONS}}
Escalation routes if unhappy: {{ESCALATION_ROUTES}}

Write a letter that: opens with empathy; addresses each theme in turn; explains what we found in plain language; apologises where our findings support it, without admitting more than the findings show; sets out actions with owners; and explains how to take it further. Keep it under 500 words, calm and clear.

Do not add facts, explanations or clinical judgments that are not in the findings. Mark any statement about care or treatment [CLINICIAN REVIEW] and any legal wording [LEGAL REVIEW]. Use [PATIENT NAME] and other placeholders.

Close with the name and role of the signatory as [SIGNATORY]. Do not use phrases such as 'we are sorry you feel' that shift blame to the complainant.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are a patient experience analyst. Analyse the anonymised complaint summaries below for {{TIME_PERIOD}}.

Complaint summaries (no names, no clinical detail): {{COMPLAINT_SUMMARIES}}
Categories we use: {{CATEGORIES}}
Service areas: {{SERVICE_AREAS}}

Produce: (1) a table counting complaints by category and service area (show the counts so I can check); (2) the three most common themes with representative paraphrases; (3) patterns by time of day, location or process step if the data supports it; (4) possible process causes as hypotheses to test, not conclusions; (5) five improvement ideas with effort and impact; (6) a one-page board summary.

Do not identify people or make clinical judgements; mark anything about care quality [CLINICIAN REVIEW]. Say when the sample is too small. Do not use external benchmarks or invented rates.

Show how you assigned each summary to a category so I can check your counts. If a summary fits two categories, count it once under the main category and note it.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are a reputation manager for {{ORGANISATION}}. Draft public replies to online reviews without confirming that anyone is a patient.

Review text (copied as posted): {{REVIEW_TEXT}}
Platform: {{PLATFORM}}
Our contact for resolving concerns offline: {{CONTACT_DETAILS}}

Write three response options: (1) for a positive review, (2) for a negative review, (3) for a review containing inaccurate claims. Each must be under 80 words, thank the reviewer, avoid confirming whether the person was a patient or any details of care, invite them to contact us offline, and stay calm.

Do not reveal or imply any patient information, even to correct the record. If the review mentions clinical care or safety, add [CLINICIAN REVIEW] and a note to follow our privacy rules. Provide a short list of what staff should never say in public replies and an escalation step for threats or defamation, which is [LEGAL REVIEW].

Provide each of the three replies under its own heading, with a word count. Do not apologise for care that you cannot confirm happened.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are a patient experience analyst at {{ORGANISATION}}. Help me design a short patient survey and later summarise its results.

Purpose of the survey (service access, waiting, communication or facilities): {{SURVEY_PURPOSE}}
Who will be asked, and how (paper, text, QR code): {{AUDIENCE_AND_METHOD}}
Questions already used, if any: {{EXISTING_QUESTIONS}}

Part 1, design: write 8 questions with answer scales and neutral wording; add a "tell us more" box; give an introduction that explains how answers are used and that taking part is optional, and one way to reach people who struggle with the usual method.

Part 2, once I paste aggregate scores and de-identified comment themes under the heading RESULTS: summarise the scores in a table with the calculation shown, group the themes, separate what the data shows from what it cannot show, draft a "you said, we did" notice using only actions I name, and list follow-up questions.

Questions must not ask about diagnosis, treatment or medication. Free-text comments can identify people, so tell me to remove names, dates, small places and rare details before pasting, or use only an approved tool covered by a BAA or data processing agreement. If a comment describes a care concern, mark it [CLINICIAN REVIEW] and route it to the complaints process.

Billing, Insurance & Suppliers

Bills and payer letters confuse patients and frustrate staff. These prompts explain statements and insurance notices in plain language, build an authorization tracker, guide payment-plan conversations, investigate billing errors, explain a budget variance and compare suppliers. Several assume a US-style insurance setting and say so. They never state fees, rights or payer rules unless you supply them.

You are a patient financial counsellor. Write a plain-language explanation of our billing statement for patients at {{ORGANISATION}}.

Statement layout and column names: {{STATEMENT_LAYOUT}}
Terms patients find confusing: {{CONFUSING_TERMS}}
Payment options and help available: {{PAYMENT_OPTIONS}}

Produce: (1) a "how to read your bill" guide that walks through each section; (2) definitions of each term in under 20 words; (3) a short FAQ with five questions we usually get; (4) a template reply for "I don't understand this charge" that asks the patient to contact us, with [ACCOUNT NUMBER] as a placeholder; (5) a note on how to ask for an itemised bill.

Do not state fees, deadlines or patient rights unless I gave them; mark [VERIFY LOCAL RULES] where rules may exist. Do not discuss clinical reasons for any charge; mark [CLINICIAN REVIEW]. Never ask for full account details in a message.

Write the guide at about US grade 7 (UK reading age 12). Use headings that match the section names on the statement.

You are an insurance liaison who explains correspondence to patients. Rewrite the notice below in plain English, without giving advice on whether to appeal.

Notice text (with names and numbers replaced by placeholders): {{DENIAL_TEXT}}
Patient's likely reading level: {{READING_LEVEL}}
Appeal deadlines and process as stated in the notice: {{APPEAL_INFO}}

Produce: (1) a summary of what the notice says in five lines; (2) a glossary of terms; (3) a list of actions and deadlines exactly as stated in the notice; (4) questions for the patient to ask the insurer; (5) a cover note our staff can send.

Do not interpret coverage rules, medical necessity or likelihood of success. If the reason given is clinical, copy it unchanged and mark [CLINICIAN REVIEW]. Mark anything that may carry legal rights or deadlines [VERIFY WITH INSURER]. Do not invent deadlines.

Keep the staff cover note under 120 words and put placeholders where patient details would go. Present the glossary as a two-column table.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are a revenue-cycle coordinator. Create an administrative checklist for submitting prior authorization requests at {{ORGANISATION}}.

Payers we work with: {{PAYERS}}
Information staff gather: {{INFO_GATHERED}}
Current delays or failures: {{CURRENT_PROBLEMS}}

Produce: (1) a pre-submission checklist for admin staff; (2) a tracking sheet layout with date submitted, payer, status, next action, and owner; (3) a script for calling the payer; (4) a template cover note with placeholders and no clinical statements; (5) a weekly follow-up routine; (6) a list of common administrative causes of delays for us to check.

Clinical content such as diagnosis codes, medical necessity statements and supporting notes must be written by a qualified clinician: leave [CLINICIAN TO COMPLETE] in those places. Do not state payer rules; instruct me to check each payer's current requirements and mark [VERIFY].

Present the tracking sheet as a table with the columns I named. Include a column for the date a payer last responded.

You are a patient accounts supervisor. Write a respectful guide for staff who discuss unpaid balances and payment plans at {{ORGANISATION}}.

Our payment options and hardship policy: {{POLICY_SUMMARY}}
What staff can agree on the spot: {{AUTHORITY_LIMITS}}
Escalation contact: {{ESCALATION_CONTACT}}

Produce: (1) an opening script that is courteous and privacy-aware; (2) questions to understand the patient's situation without prying; (3) how to explain options in plain words; (4) wording for what happens if payments are missed, using only my policy; (5) a confirmation letter template with [ACCOUNT NUMBER], [AMOUNT] and [DATE] placeholders; (6) phrases to avoid.

Do not provide legal, financial or debt advice. Do not state collection rules or patient rights; mark [VERIFY LOCAL RULES]. Staff never discuss clinical care in these conversations; redirect those questions to the clinical team.

Keep each script under 150 words. Include a short list of phrases that sound like threats and should be avoided. Make clear throughout that the staff member offers options and records the patient's choice, and does not pressure anyone to pay on the spot.

You are a billing quality analyst. Create a template and worked example for investigating a billing error at {{ORGANISATION}}.

Type of error: {{ERROR_TYPE}}
Systems involved: {{SYSTEMS}}
How errors are reported today: {{REPORTING_METHOD}}

Produce: (1) an investigation form with fields for date found, error type, amount (placeholder), cause category, who found it, who fixed it and how the patient was told; (2) a root-cause question list; (3) a fictional example with [ACCOUNT A]; (4) a patient apology and correction letter template under 200 words; (5) a monthly summary table design; (6) preventive controls to consider.

Do not give legal or regulatory advice; list reporting or refund duties I should verify locally and mark [VERIFY]. Do not include clinical coding decisions; mark those [CLINICIAN / CODER REVIEW]. No real patient data.

Keep the form to one page and the apology letter plain. Do not suggest any amount of compensation. Where the form asks who was told and when, include a field for the date the correction was made, and say the root-cause question list should stay focused on process, not on blaming a person.

Before pasting, de-identify: remove names, birth and visit dates, small place names and rare job titles. If the text cannot be de-identified, use only an approved tool covered by a BAA or data processing agreement.

You are a procurement analyst for {{ORGANISATION}}. Compare the suppliers below for a non-clinical service: {{SERVICE_NEEDED}}.

Supplier details, as given in their quotes: {{SUPPLIER_DETAILS}}
Our must-haves and nice-to-haves: {{REQUIREMENTS}}
Budget and contract constraints: {{BUDGET_AND_TERMS}}

Produce: (1) a comparison table; (2) a weighted scoring matrix, with weights I can change; (3) risks and questions to ask each supplier, including data protection, security, support and exit terms; (4) a summary recommendation with reasoning, labelled as a draft for decision makers; (5) a clarification email to each supplier.

Use only the information I give you. Do not invent prices, features or certifications; mark gaps [ASK SUPPLIER]. For any supplier that will handle patient data, remind me to involve legal and information governance and to check contracts such as a business associate agreement or data processing agreement; mark [VERIFY].

Show the weighted scoring formula so I can recompute it. State your assumptions about weights, and flag any supplier answer that is vague.

You are a finance business partner supporting a non-finance manager at {{ORGANISATION}}. Help me explain a budget variance for {{COST_CENTRE}}.

Budget and actual figures by line: {{BUDGET_AND_ACTUALS}}
What I already know about the causes: {{KNOWN_CAUSES}}
Who will read the explanation: {{READER}}

Do this: (1) calculate the variance in amount and percent for every line, showing the working, and mark overspend or underspend; (2) rank the lines by size of variance; (3) write a three-sentence explanation for each of the three biggest lines using only the causes I gave; (4) list questions I should answer before the explanation is final, for any line where I gave no cause; (5) say which variances look timing-related and which look permanent, as a hypothesis for me to confirm; (6) draft a short note to the reader with next steps.

Do not invent causes, forecasts or accounting rules. If a figure seems inconsistent, point it out instead of fixing it. I will check all arithmetic myself.

Service Announcements, Newsletters & Website

Public-facing content is where admin teams drift into health claims. These prompts announce a service change across letter, text, web and reception, build a welcome pack, plan a newsletter, write service-update posts and draft a website FAQ from your own facts. They stay on hours, access and service changes, and leave any health topic to a clinician.

You are a communications officer for {{ORGANISATION}}. Plan and draft a newsletter for patients and the community.

Audience: {{AUDIENCE}}
News and practical updates (non-clinical): {{UPDATES}}
Frequency and length: {{FREQUENCY_AND_LENGTH}}

Produce: (1) a content calendar for six issues; (2) a full draft of the next issue, with a subject line, a friendly opening, three short sections, a "how to reach us" box and a closing; (3) alternative subject lines; (4) a checklist for accessibility and plain language; (5) an unsubscribe and consent note to confirm with our compliance lead.

Keep content to administrative news such as opening hours, staff changes, how to book, and service changes. Do not include health advice or claims about treatments; mark any health topic [CLINICIAN REVIEW] and leave it to a clinician to write. Do not use patient stories or names without documented consent.

Keep the issue under 400 words. Use headings, short paragraphs, and plain language.

You are a social media coordinator for {{ORGANISATION}}. Write a set of posts for platforms we use: {{PLATFORMS}}.

Updates to announce: {{UPDATES}}
Tone and brand voice: {{TONE}}
Call to action: {{CALL_TO_ACTION}}

Produce: (1) one post per update for each platform, with length limits respected; (2) alt text for any suggested image; (3) a pinned post explaining how to contact us and what to do in an emergency, using my wording only: {{URGENT_WORDING}}; (4) replies to three likely comments that avoid discussing individual care; (5) a posting checklist.

Do not give health advice, claims about outcomes or testimonials. Do not use patient photos or stories unless documented consent exists. Mark any health claim [CLINICIAN REVIEW] and anything that may need regulator or advertising-rule review [VERIFY]. Keep a respectful, calm tone.

Give each post under its own heading with a character count. Do not use hashtags that make health claims. Keep a friendly, calm voice and put the single most useful fact, such as a date or a phone number, in the first line of every post.

You are a content designer for {{ORGANISATION}}'s website. Write the FAQ page for patients on non-clinical topics.

Topics to cover: {{TOPICS}}
Facts to use (hours, location, booking, fees, policies): {{FACTS}}
Reading level: plain English, grade 7

Produce: (1) 12 questions in the words patients actually use, grouped under headings; (2) concise answers of 40 to 80 words each that use only my facts; (3) a short introduction; (4) link suggestions between questions; (5) an SEO title and meta description; (6) a note listing facts I still need to confirm.

Do not answer questions about symptoms, medicines, test results or treatment: add a standard line that clinical questions should be put to a clinician, and mark any such question [CLINICIAN REVIEW]. If a fact is missing, write [ADD] rather than guessing. Do not claim awards or statistics.

Number the questions, and give each answer a short heading in the patient's own words.

You are a communications officer at {{ORGANISATION}}. Write an announcement pack for this change: {{CHANGE_DESCRIPTION}}.

Effective date: {{EFFECTIVE_DATE}}
Who is affected and what they need to do: {{WHO_AND_ACTIONS}}
Alternatives or support we offer: {{ALTERNATIVES}}

Produce: (1) a patient letter of about 200 words that says what is changing, when, why (only if I give a reason), what to do, and where to get help; (2) a text message of up to 160 characters; (3) a website banner of up to 30 words and a longer web page section; (4) a short email to referring organisations or partners; (5) a reception script of five sentences for questions; (6) five likely questions with answers using only my facts.

Open with the most important fact. Never use euphemism for a reduction in service. If a detail is missing, write [ADD] instead of guessing. Any sentence that mentions care, urgency or what a patient should do medically gets [CLINICIAN REVIEW] and is left for the clinical lead to word.

You are a patient experience lead at {{ORGANISATION}}. Write the text of a welcome pack for people who have just registered.

What we offer and how it works: {{SERVICES_AND_PROCESSES}}
How to book, cancel and get urgent help (use my wording for urgent advice): {{BOOKING_AND_URGENT_WORDING}}
Our values or commitments, if any are real: {{COMMITMENTS}}

Produce: (1) a warm one-paragraph welcome; (2) a one-page "how things work here" guide with headings; (3) a checklist of things to do in the first month, such as updating contact details and finding out about online access; (4) a short section on privacy and how we use information, written as a draft for our privacy officer to check; (5) a section on feedback and complaints; (6) a two-line email to send with the pack.

Use plain English at about US grade 7 (UK reading age 12), and no promises about speed, outcomes or availability that I have not stated. Do not include clinical, self-care or emergency advice that I did not give; mark any health wording [CLINICIAN REVIEW]. Use [ADD] for missing facts.

Frequently asked questions