Healthcare English for Performance Reviews

Describing a strength — Use behaviour plus example plus effect, and pick strengths a healthcare manager values: reliability, calm under pressure, clear handovers, careful documentation, patience with residents and families. 'I stay calm when the unit gets busy — last month during the flu surge I reprioritized my tasks and checked in with the charge nurse instead of rushing.' Practise the pushback: when the manager asks 'Can you give me another example?', your evidence list means you have one ready.

Responding to feedback — The first move is always the pause: 'Thank you — could you give me a recent example so I know exactly what to change?' If you disagree with part of it, acknowledge first and then offer your side as information, not defence: 'I understand how it looked. Can I share what was happening from my side that day?' Rehearse this aloud with feedback that stings — documentation gaps, communication with a particular colleague — because composure on easy topics does not transfer by itself.

Setting a goal — Build it as verb, measure, date: 'By the end of March, I will use the checklist format in every handover.' Then prepare for the follow-up that always comes — 'How will you measure that?' — with the answer built in: 'I'll keep the checklist in my pocket notes, and you'd see it in the shift log.' Vague goals ('communicate better') get written down and forgotten; measurable ones get supported.

Requesting support — Name the task and the type of help, with a timeframe: 'Could someone review my documentation once a week for the next month? I want to be sure my notes meet the standard.' Practise the busy-manager version too — one sentence, no apology: 'The one thing that would help me most is feedback on my handover notes.' A support request framed this way reads as ownership, not weakness.

Vague strength — Weak: I am good with people. Improved: I communicate calmly with residents and families. For example, I repeat key information and check that the person understands before I leave. The improved version survives the question every reviewer silently asks: 'How would I know that's true?' It names a behaviour someone could watch you do tomorrow.

Defensive response — Weak: That is not my fault. Improved: Thank you for explaining that. Could you give me one example so I can understand what to improve? Notice the improved version concedes nothing — it neither accepts nor rejects the feedback. It buys information first, which is the strongest position to respond from. Weak goal — Weak: I will do better. Improved: My goal is to make shift updates more concise by using status, concern, and next step in every handover this month. The difference is checkability: in four weeks, one of these sentences can be verified and one cannot.

Support request — Weak: I need more help. Improved: Could I get feedback on my documentation for the next two weeks so I can make sure my notes are clear and complete? Naming the task, the help, and the timeframe converts a complaint into a plan the manager can say yes to on the spot. Across all four pairs the upgrade is the same move — replace a general claim with something observable and dated — so practise that move on your own sentences, not just these.

These phrases map onto the four moments of a review — strengths, feedback, goals, support — so prepare them in that order, matching the meeting's actual flow. Fill each frame with real material from your evidence list before the review: 'A recent example is...' should already have its example attached when you walk in.

Practise the feedback-response group hardest and aloud, because those are the only phrases you must produce under emotional pressure, without notes, while someone watches your reaction. The strengths and goals language can live on paper; 'Thank you — could you give me a specific example?' has to live in your mouth.

1. Write three strength statements with the behaviour-example-effect structure, drawing each example from a different month so your evidence covers the year. 2. Have a partner deliver one piece of genuinely uncomfortable feedback — pick your real sore spot — and respond with the pause formula without breaking it. 3. Take the vaguest goal you have ever written ('improve communication') and rebuild it as verb, measure, date. 4. Write one support request and then cut it to a single sentence for a manager with ninety seconds. 5. Role-play the evidence challenge: state a strength, and have your partner ask 'Can you give me another example?' twice in a row. 6. Record your 90-second self-review and listen once only for tone — confident and factual, or apologetic and hedged?

Repeat the recording task at the end of your practice week with fresh examples. Comparing the two recordings shows you what a listening manager would hear — which is the only measure that matters here.

Being too modest: Name real contributions with evidence instead of saying “nothing special.” - Becoming defensive: Ask for examples and next steps before explaining your side. - Using vague goals: Add action, timeline, and measurement. - Forgetting support requests: Prepare what help would make improvement possible. - Sharing too many private details: Keep examples focused on work behaviours and anonymized situations. - Only preparing complaints: Prepare strengths, goals, and questions as well as concerns.

The week mirrors the review itself. Days 1 and 2 build your material: the lists of strengths, growth areas, and questions, then one example attached to every strength. Days 3 to 5 build the three hard sentences: the calm feedback responses, one measurable goal, one support request. Day 6 is the performance: the 90-second self-review, spoken aloud, ideally recorded. Day 7 is selection: review everything and choose the single most important question to ask your manager — because a review is also your meeting, not only theirs.

If your review is sooner than a week away, compress to three days: evidence list, feedback responses, spoken run-through. And keep each block to ten minutes; the aim is sentences you can retrieve in the room, which short frequent practice builds far better than one anxious evening.

Audit one practice answer against four labels: strength, evidence, tone, next step. A review-ready answer names a strength, backs it with something checkable, keeps a tone that is neither boastful nor apologetic, and points forward. The label most learners fail is evidence — reread your answer and ask the reviewer's question: 'How would I know this is true?'

Run the tone check on your recorded 90-second self-review specifically. Count the hedges — 'just', 'a little bit', 'I try to', 'maybe' — and cut half of them. Hedging is the accent of underselling, and in a review it costs real money. One phrase that worked, one hedge removed, one place to reuse the improved sentence: that is a complete progress check.

Run the whole review once, in order, out loud: your 90-second self-summary, then a partner (or you, changing chairs) delivers one positive comment and one criticism, you respond with the pause formula, and you close by proposing your goal and your support request. Fifteen minutes, start to finish.

Then make exactly three improvements: add the strongest example you forgot, shorten your goal sentence until it fits on the form in one line, and replace your weakest feedback response with a calmer one. Save your three core sentences — the strength with its evidence, the goal, the support request — somewhere you can reread the morning of the real review. Walking in with three prepared sentences changes the meeting more than any amount of general fluency.

Take the review question that scares you most — for most people it is 'What could you improve?' — and give it one ten-minute block. Two minutes: write the honest answer in plain notes. Three minutes: shape it into growth-area language: 'One area I'm working on is documentation speed. I've started using templates, and I'd like feedback on whether my notes are at the right level of detail.' Two minutes: strip the weakest sentence, usually the one that over-apologizes. Three minutes: answer it again with a different growth area, without notes.

The second run matters because a real manager may not pick the weakness you prepared. If you can shape any honest weakness into the improvement-plus-plan structure on the spot, the scariest question in the review has lost its power.

In a review, the follow-up questions are where prepared answers go to die. Drill the big four. 'Can you give me an example?' — your evidence list answers this; the drill is retrieving it in five seconds. 'How will you measure that?' — attach a measure to your goal before the meeting: 'You'd see it in the shift log.' 'Why did that happen?' — about a mistake, answer with the incident-report discipline: facts, what you changed, no blame of colleagues. 'Anything else?' — this is the invitation for your support request; do not let it close with 'no, all good.'

Practise them as rapid pairs: your prepared statement, then the follow-up fired straight after, then your answer. The review meeting is a chain of second turns; the first turn is the only one you can fully script.

Run one complete invented case. The setup: a care aide's manager says her patient interactions are excellent, but her shift documentation is often late and sometimes thin. She has been covering extra shifts all quarter, which is the real reason — and also a contribution nobody has mentioned.

Prepare her side in both formats the review demands. Spoken: accept the documentation point with the pause formula, surface the extra shifts as fact rather than excuse ('I want to flag that I've covered eight extra shifts this quarter — I think the lateness tracks those weeks'), and propose the goal plus a support request. Written, for the self-review form: two strengths with examples, the growth area in her own measured words, the goal as verb-measure-date. Then check three things: did the spoken version name the extra shifts without sounding defensive, does the written growth-area line say what she is already doing about it, and do both versions end pointing forward? Swap in your own real situation and run it again — this case is a scaffold, and your review is the building.

This page is strongest when you use it as a narrow practice module, not as a replacement for every related resource. Use the general performance reviews guide when you need the complete overview. Use this page when you want repeated language for healthcare role-specific review language for strengths, goals, feedback, and support requests. That distinction matters because learners often study a large topic, understand it in theory, and still hesitate during the exact moment when they need a sentence. The goal here is to make that moment smaller, clearer, and easier to rehearse. The ideal practice cycle is simple: choose one realistic situation, prepare the details, say the sentence, repair one weak part, and confirm the next step. For healthcare workers preparing to discuss communication, teamwork, reliability, patient interaction, and professional growth in a review, this is more useful than collecting a long list of vocabulary without a speaking or writing task. Scenario lab — - Describe a strength: connect behaviour to workplace value. Try: “One strength I have developed is staying calm during busy periods and checking instructions when priorities change.” - Respond to feedback: acknowledge and ask for a concrete next step. Try: “Thank you for explaining that. I understand I need to document updates more consistently. Could we agree on the best format?” - Set a goal: make the goal observable. Try: “My goal is to improve shift handoff clarity by using a short checklist and asking one confirmation question.” After each scenario, add one confirmation line: “Let me repeat that back,” “So the next step is ___,” or “Could you send that in writing?” This final line turns language practice into real communication because it checks understanding instead of only sounding polite. Weak to improved language — - Weak: “I am good with patients.” Better: “I try to make patients feel respected by greeting them clearly and checking that they understand the next step.” - Weak: “That is not my fault.” Better: “I understand the concern. Here is what happened, and here is what I can change next time.” - Weak: “I need better English.” Better: “I would like to improve my handoff language and confidence when asking for clarification.” Notice the pattern. The improved version usually names the situation, gives one useful detail, and asks for a clear next step. It does not need advanced vocabulary. It needs order, tone, and enough information for the listener to help. Phrase bank for fast recall — - Strengths: I have improved in ___; A recent example is ___; I try to support the team by ___. - Feedback: I understand; I can work on ___; Could you give me an example?. - Goals: My next goal is ___; I will measure it by ___; I would appreciate support with ___. Build your own phrase bank with three columns: purpose, detail, and next step. For example: “I am calling about ___,” “The date is ___,” and “Could you please ___?” This structure works for speaking, email, forms, and exam-style role plays because it keeps the message complete. Role, level, exam, and country adjustments — A2 healthcare workers should prepare short examples and pronunciation of role vocabulary. B1 learners can explain situations and goals. B2 learners can handle feedback with nuance and professionalism. Country and workplace expectations vary, so this guide supports communication for reviews, not employment or clinical decisions. Role matters because a parent, employee, manager, test taker, student, or service customer needs different tone even when the grammar is similar. Level matters because beginners need short reliable sentences, while higher-level learners need flexibility and repair language. Exam and country context matter when the task has a specific format or local vocabulary, but the safest starting point is still clear communication: purpose, detail, confirmation. Practice tasks — - Write a one-sentence goal for healthcare role-specific review language for strengths, goals, feedback, and support requests and say it aloud twice. - Record a sixty-second version of one scenario, then rewrite only the unclear sentence. - Practise one weak example, pause, and replace it with the improved version without reading. - Ask a partner or teacher to correct only two things: clarity and tone. - After real use, write the exact phrase that worked and one phrase to improve next time. Common mistakes to avoid — - Trying to explain the whole background before the listener knows the purpose. - Using a memorized phrase without changing the name, time, document, role, or next step. - Forgetting to confirm what happens next. - Confusing confidence with speed; clear and slow is usually stronger than fast and vague. Ten-day practice plan — Days 1 and 2: learn the phrase bank and say each phrase with your own details. Days 3 and 4: practise the scenario lab with a timer, first slowly and then at natural speed. Days 5 and 6: record yourself and mark only two issues, such as missing details or unclear tone. Days 7 and 8: practise a second turn where the other person asks a question or gives unexpected information. Day 9: use the language in a low-pressure real task or realistic role-play. Day 10: write a short reflection: what sentence felt natural, what sentence failed, and what you will practise next. FAQ for this focused practice angle — How is this page different from the broader resource? The broader resource is better for the full topic. This page is narrower: it trains healthcare role-specific review language for strengths, goals, feedback, and support requests with scripts, repair language, and repeatable practice. What should I practise first if I have only ten minutes? Choose one scenario, say the model line aloud, change the names and times, and finish with a confirmation question. Should I memorize the scripts exactly? Use them as frames, not fixed speeches. Keep the structure, but change the details so the sentence sounds like your real situation. How do I know the practice is working? You should be able to state the purpose sooner, ask for clarification without panic, and name the next step at the end of the conversation or task.