Prompts that work, with the safety notes built in.

• Care records & notes

  Turn a spoken visit note into a record

  You are helping a care worker write up a visit. This goes into a care record that may be read later by a nurse, a social worker, a safeguarding review or a coroner, so an invented detail is far worse than a missing one, and a tidy summary that leaves something out is worse than a rough one that does not.
  
  Turn the notes below into a record under these headings, and no others:
  [your headings, e.g. Personal care / Nutrition / Mood / Health / Medication / Anything to report]
  
  Rules:
  1. Use only what is in the notes. If something is unclear, write [CHECK] rather than guessing.
  2. Keep anything unusual, even if it does not fit a heading. Put it under "Anything to report". The odd detail is usually the reason the record matters.
  3. Keep the care worker's own words where they describe what someone said or did. Do not make strong language more professional: "he shouted and threw the cup" must not become "he became agitated".
  4. List every medication name and time separately at the end, marked [CHECK NAMES], because mis-heard drug names are the most common serious error.
  5. Do not add any clinical judgement or conclusion that is not in the notes.
  
  Notes:
  [paste or dictate the notes]

  Safety note: Contains information about a person you support. Approved business tool only, never a personal account, and only with a DPIA in place. Read the draft against what actually happened before saving it.

  About this use

• Care records & notes

  Check a draft before you use it

  Check the draft you just produced against the source I gave you. I have to sign this off, so I need to know where to look rather than a reassurance.
  
  Give me four lists:
  1. **Facts to verify** — every name, date, time, number and medication, with what the source says.
  2. **Things you were unsure about** — where the source was ambiguous and you made a choice.
  3. **Things you left out** — anything in the source that did not make it into the draft, however minor it seemed.
  4. **Things you changed the wording of** — where you rephrased something, with the original alongside.
  
  If a list is empty, say so. Do not reassure me that the draft is accurate: you cannot know that.

  Safety note: Use after any summary or draft. It narrows where to look, but it is not a reliability score. A tool can be confidently wrong and will not list that error, because it does not know.

  About this use

• Care records & notes

  Find themes in anonymised incidents

  Below are anonymised incident records from [period]. I am preparing a quality review. I need counting and grouping, not judgement — I know the service and you do not.
  
  Produce:
  1. **Counts** — total, and by type, time of day and location.
  2. **Recurrences** — anything that appears more than once, stated as a count only.
  3. **Five questions** the review meeting should discuss.
  
  Rules:
  - Report each incident's severity exactly as recorded. Do not rank, rate or re-describe severity.
  - With small numbers almost any split looks meaningful. Where a pattern is based on fewer than five incidents, say so explicitly next to it.
  - Do not suggest causes. Ask a question instead.
  - If anything in the list still looks identifying, tell me before you continue.
  
  Incidents:
  [paste anonymised incident list]

  Safety note: Remove names, dates of birth, room numbers and identifying details first. In a small service, removing the name may not be enough. Never use this to write or edit the original incident record.

  About this use

• Care records & notes

  Tidy up team meeting notes

  Turn these rough notes into minutes. People will act on this, so an action invented to make the minutes look complete is worse than an obvious gap.
  
  Three sections:
  1. **Decisions** — what was actually decided.
  2. **Actions** — what, who, by when. If an owner or a date is missing, write [OWNER?] or [DATE?] rather than assigning one.
  3. **Carried forward** — raised but not resolved.
  
  Use only what is in the notes. Mark anything you could not follow with [CHECK]. Do not add a decision that was only discussed.
  
  Notes:
  [paste notes, removing details about people you support]

  Safety note: Remove details about the people you support, or use an approved tool. Check that every action has a real owner before circulating.

• Referrals & assessments

  Summarise a referral pack

  Summarise the referral pack below. Someone is deciding whether we can safely meet this person's needs, and they will read the full pack as well — so your job is to tell them what to expect and where to look, not to replace their reading.
  
  Use these headings and no others:
  1. Needs
  2. Risks
  3. Medication
  4. Who else is involved
  5. What is missing from this pack
  
  Rules:
  - Keep the source's uncertainty. If it says "query dementia", do not write "has dementia". If a family member reports something, say who reported it.
  - Give a page reference for each point.
  - Under "what is missing", list anything you would expect a referral to include that is not here.
  - If any page appears to be a scan or handwriting you could not read, say so at the top. Do not silently skip it.
  - Do not add anything that is not in the pack.
  
  Pack:
  [paste pack]

  Safety note: Health and social care information about an identified person, often including family members. Approved business tool only. Whoever decides still reads the full pack: summaries drop the detail mentioned once on page 30, and that is often the one that matters.

  About this use

• Referrals & assessments

  Find the gaps in a referral

  Read the referral below. Do not summarise what is there — I have read it. Tell me only what is missing or unclear, as questions I should ask before accepting this package.
  
  Group the questions under:
  1. **Must know before we accept** — anything affecting whether we can safely deliver this.
  2. **Should know before the first visit** — practical things that will cause problems on day one.
  3. **Unclear rather than absent** — where the pack says something but it could be read two ways.
  
  If the pack is unusually complete, say so rather than inventing questions.
  
  Referral:
  [paste referral]

  Safety note: Approved business tool only. The gaps it finds are a starting point, not a complete list. It can only see what is on the form, and the most important information in a referral is often not on the form.

  About this use

• Recruitment & training

  Job advert for a care role

  Write a job advert for a [role] at a small [type of service] in [town].
  
  The facts, which are the only ones you may use:
  - Pay: [pay]. Hours: [hours]. [Driving licence needed / not needed].
  - Benefits we actually offer: [list them, or write "none beyond statutory"].
  - Experience needed: [none, we train / list it].
  - Two or three things that are genuinely true about the team: [e.g. four people have been here over ten years].
  
  Rules:
  1. Do not add any benefit, requirement or qualification I have not listed. Inventing "career progression opportunities" advertises something we do not offer, and adding "six months' experience" excludes the people we most want.
  2. Avoid the phrases that make every care advert identical: "rewarding role", "make a real difference", "supportive team environment", "person-centred care delivery", "passionate about care". A reader has seen them a hundred times and they carry no information.
  3. Write for someone who has never worked in care. No sector jargon, no "service user".
  4. Lead with the pay and the hours. That is what people actually want to know.
  5. Under 200 words.
  6. End with the specific true details about the team. They are the only part no other advert can copy.

  Safety note: No personal data needed, so a free account is fine for this. Check every factual claim in the advert before publishing: inventing a benefit is the most common failure.

  About this use

• Recruitment & training

  Values-based interview questions

  Our values are [values]. Suggest eight interview questions for a [role] that show whether someone shares them.
  
  For each question give:
  - The question, in plain spoken English.
  - One line on what a strong answer might include.
  - One line on what a weak answer might sound like.
  
  Rules:
  - Ask about what someone has actually done, not what they would do. "Tell me about a time" beats "how would you handle".
  - Avoid anything touching age, health, disability, family plans, pregnancy, religion or nationality, including indirectly. A question about "flexibility for early starts" can screen out carers of children without meaning to.
  - No trick questions and no hypotheticals that need care-sector knowledge a new starter would not have.
  - At the end, list any question you are unsure about on fairness grounds, and say why.

  Safety note: No personal data needed. Review the final set against your equality policy, and never paste a candidate’s CV or application into an unapproved tool.

  About this use

• Recruitment & training

  Turn a policy into a five-minute team briefing

  Turn the policy below into something I can deliver to the team in five minutes at a handover.
  
  Give me:
  1. **The three things they must remember** — the ones that change what someone does.
  2. **What is different from before** — if I have told you what changed: [what changed, or "this is new"].
  3. **Two questions someone will probably ask**, with the answer.
  4. **One sentence they could repeat to a colleague who missed it.**
  
  Rules:
  - Spoken English, not written English. I am saying this out loud.
  - Skip anything that does not change what someone does on a shift.
  - If the policy is unclear on something staff will ask about, tell me — do not smooth over it.
  
  Policy:
  [paste policy]

  Safety note: Most policies contain no personal data, so a general tool is fine. Remove any real case examples first. Check the briefing against the policy: a briefing that contradicts the policy is worse than no briefing.

  About this use

• Bids, reports & policies

  Structure a funding bid

  Here are a funder's questions and my notes. Organise my notes into an answer for each question, within the word limits.
  
  Rules:
  1. Use only my figures, outcomes and examples. Where my notes do not cover something, write [NEEDS EVIDENCE] and move on. Submitting an invented figure to a funder is fraud whether or not anyone meant it, so a visible gap is always the right answer.
  2. Do not upgrade my claims. If my notes say participants reported feeling less isolated, do not write that the project transformed lives. Funders who fund care can tell, and it costs credibility.
  3. Attribute every figure to its source: a survey, our records, a headcount.
  4. Avoid sector boilerplate. "Uniquely placed to deliver transformative outcomes" tells a reader nothing.
  5. At the end, list the three weakest answers and what evidence would strengthen each.
  
  Funder's questions and word limits:
  [paste]
  
  My notes and figures:
  [paste, with any case studies anonymised]

  Safety note: Use anonymised case studies only, and get consent for any story about a named person. Check every number in the output against your own records: if a figure is not in what you supplied, it is not real.

  About this use

• Bids, reports & policies

  Turn figures into an impact summary

  Write a [150]-word impact summary for [audience, e.g. trustees / a funder] using only the figures and facts below.
  
  Rules:
  - No number that is not in my list, including percentages you could calculate. If a calculation would help, tell me instead of doing it silently.
  - Say where each figure came from.
  - If something did not go well and it is in my notes, include it. A report where everything succeeded is less believable than one that is honest, and funders read a lot of both.
  - Plain English. No "transformative", "unprecedented" or "journey".
  
  Figures and facts:
  [paste]

  Safety note: Check every figure against your source before it goes out.

  About this use

• Bids, reports & policies

  Check a policy against a standard

  Compare the policy below against the standard I have pasted. Use only the standard I have given you — do not rely on what you know about regulations, because you may be describing superseded guidance or another country's rules, and I cannot tell the difference from the way you write.
  
  Give me:
  1. **Not covered** — requirements in the standard with nothing in the policy, quoting the requirement.
  2. **Partly covered** — where the policy touches it but does not meet it, quoting both.
  3. **Contradictions** — anywhere the policy contradicts itself.
  4. **Out of date references** — bodies, job titles or forms that look superseded.
  
  Do not rewrite the policy. Do not cite any regulation, clause or standard that is not in what I pasted.
  
  Standard:
  [paste the actual guidance you are checking against]
  
  Policy:
  [paste]

  Safety note: Remove names and real case examples first. Never ask the tool to recall a regulation from memory: supply the text. Someone who knows the rules signs off the result.

  About this use

• Bids, reports & policies

  Turn updates into a board paper

  Turn the material below into a one-page paper for [trustees / the board] meeting on [date].
  
  Structure:
  1. **What the board needs to decide** — at the top, in one or two sentences. If nothing needs deciding, say "for information only".
  2. **Position** — where things stand, in plain English.
  3. **Risks** — what could go wrong, and what we are doing about each.
  4. **What we are asking for** — a decision, a steer, or nothing.
  
  Rules:
  - Trustees are not in the day-to-day. Expand any abbreviation on first use and cut internal shorthand.
  - Do not smooth over bad news. A board that finds out late cannot help.
  - Where the material does not answer an obvious question, write [GAP] rather than filling it.
  - One page.
  
  Material:
  [paste your updates, notes or figures]

  Safety note: Remove names and identifying details of people you support. Board papers get circulated and stored more widely than you expect.

• Letters & updates

  Rewrite a letter in plain English

  Rewrite the letter below at about reading age nine, for [audience, e.g. families / people with a learning disability].
  
  Keep exactly as they are, word for word if you need to:
  - any deadline or date
  - any right the reader has, such as asking for a review
  - anything conditional: "may", "might", "if", "unless"
  
  Those three are where simplifying goes wrong. "Visits may be subject to alteration" becoming "your visits will change" is a different statement, and "within 28 days" disappearing removes the reader's right rather than simplifying it.
  
  Then:
  1. One idea per sentence. Everyday words. No sector jargon.
  2. After the rewrite, list anything you changed that might have altered the meaning, and anything you removed.
  
  Letter:
  [paste the letter, with names and personal details removed]

  Safety note: General letters and leaflets are fine on any tool. A letter about a named person needs an approved tool. Check every deadline and condition against the original, then read it aloud.

  About this use

• Letters & updates

  Warm update for a family member

  Write a short update for a family member about their relative's week, using only the notes below.
  
  Structure:
  1. How the week went, in three or four sentences.
  2. **Things we wanted to mention** — anything difficult, listed plainly.
  
  Rules:
  1. Do not soften anything difficult. A refusal of personal care, a fall or a low patch goes in section 2 in plain words. A warm tone that buries bad news is the main way this goes wrong: the family reads an account of a good week that was not one.
  2. Use only what is in the notes. Do not add reassurance, prognosis or interpretation.
  3. Do not name anyone else who appears in the notes — neighbours, other residents, visiting professionals.
  4. At the end, list separately anything in the notes that I should check before sending, because the person may not want it shared.
  
  Notes:
  [paste, using an approved tool, and only information the person has agreed to share]

  Safety note: Contains health information about a named person: approved business tools only. Check consent, check nothing private has been included, and check nothing difficult has been softened out.

  About this use

• Letters & updates

  Draft a response to a complaint

  Help me draft a response to the complaint below. This is a first draft for me to rewrite, not something to send.
  
  Structure:
  1. What they have told us, in their terms, so they can see we understood.
  2. What we found: [what you actually found, or leave blank if you have not finished looking].
  3. What we are doing about it.
  4. What they can do if they are not satisfied.
  
  Rules:
  - Do not admit or deny anything I have not told you. Where I have not given you a finding, write [FINDING?] rather than producing one.
  - No defensive language, and no "we are sorry you feel". Apologise for what happened if I have said it happened.
  - Plain English, short sentences, no legal tone.
  - Do not promise any action I have not listed.
  - At the end, list anything in the complaint I have not addressed.
  
  Complaint:
  [paste, with names removed or using an approved tool]
  
  What I know so far:
  [paste]

  Safety note: Complaints contain personal information and often safeguarding material. Approved tool only, or remove every identifying detail first. A person rewrites and signs this: a complaint response is a document that may be read by a regulator.

• Wellbeing & check-ins

  Questions for a wellbeing check-in

  Suggest six short questions for a wellbeing check-in with someone who lives alone and receives care [number] times a week.
  
  Rules:
  - Plain spoken English, the way a person would actually ask. Not assessment language.
  - One idea per question.
  - Include one that gives the person an easy way to say something is wrong without having to make a complaint of it.
  - Nothing that can only be answered yes or no, except where a yes or no is genuinely the useful answer.
  
  Then, separately, list:
  1. **What these questions will not tell us** — be specific.
  2. **What a person at the door would notice that a question cannot capture.**

  Safety note: No personal data needed to draft the questions. A person reads every answer. A script cannot ask the follow-up question that matters, and someone may not be able to speak freely.

  About this use

Suggest a prompt