Physiotherapy Assistant Operations Case Studies
Healthcare5 Case StudiesUpdated Sep 2026
The five cases in this set come from outpatient, community, and inpatient settings where physiotherapy assistants plan sessions within a supervised plan, keep detailed records, and pass patients between colleagues several times a day. None of them turns on a single mistake. Each shows a moment where routine work, a missing piece of information, or a protocol applied too loosely began to shape what happened next. The organizations and people are fictional, but the pressures are familiar. Check each recommendation against your own local protocol. Where a case calls for escalation, name who holds the decision.
Case Study 1
A slow-building pattern across six physiotherapy sessions
Larkfield Community Therapy, a group of six outpatient clinics serving about 4,200 active patients, with a supervised assistant model for most follow-up sessions.
The situation
Ruth, a retired bookkeeper, attended six sessions over five weeks after a fall at home. Her programme was set by the supervising physiotherapist, Dev, and most sessions were delivered by Priya, a physiotherapy assistant working within that plan. In the third week Ruth reported numbness in her left hand and said her discomfort no longer eased overnight. Priya recorded both points in the session note but read them as a slower recovery rather than a change in direction. Two sessions later Ruth mentioned headaches and unsteadiness on the stairs. Each note was thorough on its own. Nobody read the six together until the front desk noticed a reschedule request that mentioned the stairs.
The challenge
Priya was working within the scope of the plan and could not change it without Dev. The question was whether the combined pattern met the local escalation criteria, and who should decide that. Dev was away at a training commitment for two days, and the clinic's protocol named him as first contact for any change in presentation. Cover sent queries to a shared inbox checked once per shift. The protocol listed red flags requiring same-day contact with a medical provider, but each item was written for a single finding, and nothing in the list covered a gradual cluster across sessions.
Analysis
Ruth's needs had moved faster than her plan. The evidence was scattered across six notes, each a reasonable reading of one session. Taken together, they described a new neurological symptom, a shift in night pain, and a fall-related risk that had not been present at intake. A useful review starts by placing the notes side by side and marking which findings are new compared with the intake baseline. This is not a diagnostic exercise for an assistant. It is a recognition task: noticing that a set of observations has crossed a threshold the protocol was written to catch, and handing it to someone who can make the medical decision.
Teams grounded in Physiotherapy Assistant Operations usually treat escalation as a communication problem before it is a clinical one. Priya had the information but no reliable route to put it in front of someone with authority to act. The named contact was out of reach, and the cover route depended on a shared inbox that was read once per shift. Better routing would have included a duty clinician listed on the rota for any note containing a new neurological or safety finding, and a rule that the assistant phones rather than messages when a red flag appears. The protocol also needed a review trigger, so that a pattern across sessions prompted a look at the whole record and not only the latest entry.
- IntakeStable neck pain recorded, with no neurological symptoms noted.
- Third weekNumbness in left hand logged as a slower recovery.
- Fourth weekNight pain worsens and headaches appear in the session note.
- Fifth weekUnsteadiness on stairs noted, and a reschedule request follows.
- Same afternoonSix notes compared, duty clinician contacted, referral made.
Actions taken
- Add a cross-session comparison step to the assistant progress note template, asking the assistant to check each new entry against the intake findings at every third session and record any change in writing.
- Name a duty clinician on the rota for every shift, and route any new neurological or safety finding to that person by phone the same day, with the call logged in the record.
- Run a monthly case review with assistants and supervising therapists, using two anonymized records to practice writing escalation notes that state what has changed from baseline and what decision is needed.
- Audit escalation timeliness each quarter by sampling records where a red flag was noted, measuring the interval from first documentation to clinician contact, and reporting the median to the governance group.
Results
The clinic adopted the comparison step and the duty clinician route within the quarter. Ruth was reviewed by a physician on the afternoon her reschedule request was read, and her referral went through the local pathway without delay. The first audit found that the median interval from first documentation to clinician contact had fallen from more than two working days to under four hours across the sampled records. Dev now reviews the duty log at the start of each week, and Priya reports that the cross-session check has made her notes more useful to the team, not just more detailed.
Questions for discussion
- Which of Ruth's six notes would you have read first, and what made that note stand out or fail to stand out?
- How would your own service define the threshold for same-day clinician contact when findings appear gradually rather than in a single session?
- What information should an assistant be able to pass to a duty clinician by phone in under two minutes, and how would you check that the call was understood?
Case Study 2
A verbal handover that dropped a mobility change
Brightwater Inpatient Rehabilitation, a 42-bed unit attached to a regional hospital, where physiotherapy assistants run afternoon and evening sessions alongside nursing teams.
The situation
Walter, a patient on a rehabilitation ward, had been progressing well until his mobility status was revised in the afternoon. The care plan changed from independent with supervision to requiring two staff for transfers, following a session in which Owen, a physiotherapy assistant, noted reduced balance. Owen updated the electronic record and told the charge nurse in person. He then handed over verbally to Mei, the evening assistant, at the end of a long shift with two patients still waiting for discharge paperwork. The whiteboard at the bedside was not changed, and the verbal handover mentioned the session but not the new status.
The challenge
The change existed in the record and in one person's memory, but not in the place the evening team actually worked from. The ward used a verbal handover with a short written summary, and the summary template had no field for mobility status. Mei was covering a larger caseload than usual because a colleague had called in sick. Nobody was assigned to check that the bedside board matched the chart, and the ward's safety huddle did not include an equipment or status check at shift change.
Analysis
Walter's needs had changed in a way that mattered at transfer times, not during the session itself. The clinical evidence was a single note describing reduced balance, which was accurate and recent. What was missing was a clear statement of what the change meant for staffing and for who should be present when he moved. Any transfer decision depends on the current status, and a status that exists only in the chart is effectively invisible to a nursing aide who is working from the board. Evidence about risk is only useful when it reaches the people making the movement decisions in time to act on it.
The handover failure was a coordination failure rather than an individual lapse. Owen did what the ward asked: record in the chart and tell the nurse. The gap sat between the chart and the verbal summary, and the protocol did not say which source was authoritative at shift change. Applicable standards for handover in this setting call for a structured exchange that includes current mobility status, equipment needs, and any change within the past shift. Here, the structure existed on paper but had no field for mobility, so the most safety-relevant item was the one most likely to be left out when time ran short.
Actions taken
- Add a mobility status field to the shift handover summary, with a required entry for any change recorded in the past twelve hours, and make the field visible on the bedside board.
- Adopt a single source of truth for mobility status by naming the electronic record as authoritative, and require the bedside board to be checked against it at each shift change.
- Include a two-minute status check in the safety huddle at each shift change, with the charge nurse and incoming assistant confirming any changes read back aloud.
- Track handover quality with a monthly sample of ten transfers, recording whether the bedside status matched the chart, and report any mismatch to the ward quality group.
Results
The ward added the mobility field and the read-back check within the first month. In the following audit, the bedside board matched the chart in every sampled transfer, and two mismatches found in the first round were traced to handovers given during the same busy period. Walter's transfers were planned with the correct staffing from the afternoon of the change. Owen and Mei now run the status check together at the start of their shared shift, and the charge nurse reports fewer questions at the huddle about who is moving which patient. The ward has kept the audit running with a smaller sample.
Questions for discussion
- Where in your own handover does a change in mobility status get recorded, and which source would a nursing aide trust at the bedside?
- How would you decide which handover items must be read back aloud and which can be recorded only in writing?
- What would you need to see in a monthly audit to know a handover fix had worked, rather than only been introduced?
Case Study 3
Allocating scarce staff and bays during a seasonal peak
Tidewell Physiotherapy Hub, a shared outpatient clinic with nine treatment bays and an attached exercise gym, with a waiting list of 1,240 patients.
The situation
In the middle of a seasonal rise in referrals, Tidewell's waiting list grew from 860 to 1,240 patients over a few weeks. The service had three physiotherapists, four physiotherapy assistants, one of whom was on extended leave, and nine treatment bays, two of which were shared with the gym rig. Referrals arrived with inconsistent urgency notes, and the triage tool scored the same presentation differently depending on which clinician completed it. Melissa, the service lead, had to decide how to allocate sessions for the next six weeks without adding staff.
The challenge
Every option moved risk somewhere. Prioritizing urgent referrals would lengthen routine waits, which carried their own deterioration risk. Group sessions could reach more people but could not replace individual assessment for some patients, and assistants could deliver only delegated sessions under supervision, which limited how many clinician reviews were available each day. Moving equipment between bays would relieve one shortage and create another, and the gym rig was already booked for most of the afternoon.
Analysis
The first question was which patients needed a clinician in the room and which could safely receive a delegated programme. The evidence was thinner than the team would have liked. Referral notes did not consistently record urgency, and the triage scores varied by clinician, so the waiting list did not reflect clinical need as cleanly as its order suggested. A reasonable first step was to re-score a sample of current referrals using the same criteria, so that the team could see how much of the backlog was truly urgent before choosing which trade-off to accept.
Allocation decisions were also governance decisions. Local policy required that delegated sessions remain under a named supervising clinician and that any new episode of care be assessed by a physiotherapist first. That meant the assistants' capacity could absorb follow-up sessions but not new assessments, and the weekly plan had to show which was which. The team agreed on a short weekly allocation meeting, with a documented rationale for each shift of sessions between urgent, routine, and group provision, so that later reviews could see why a decision was made, not only what it was.
- Triage Re-score referrals with one agreed set of criteria and flag urgent cases.
- Schedule Place assessments first, then follow-ups, then group sessions in bay order.
- Allocate Assign assistant sessions under named supervision and confirm bay and gym bookings.
- Review Compare waiting times and missed sessions against the decision rationale.
Actions taken
- Agree one triage scoring set for all clinicians and re-score the current waiting list within the first week, recording the reason for each change in urgency so the backlog can be read accurately.
- Create a two-tier weekly plan that reserves assessment capacity for new referrals and uses assistant-delivered follow-up sessions only where a named supervisor has agreed the caseload.
- Introduce a group exercise session for patients whose delegated programme is stable, run in the gym rig outside its individual booking times, and review attendance after the first month.
- Hold a short weekly allocation meeting with a written rationale for each decision, and report waiting times by urgency band to the clinical governance group every fortnight.
Results
Within the peak period, the waiting list stabilized at about 1,050 patients, and the urgent band was seen inside the target window in every week after the first. Routine waits grew for some patients, and Melissa wrote to them with a revised timeframe and the option of a group session. Group attendance reached a steady level in the second month, and the gym rig was no longer double booked. The rationale log became the basis for the service's next capacity review, and the team found that two of its earlier decisions had been made on out-of-date urgency scores.
Questions for discussion
- Which of the three options would you protect first if assessment capacity were cut by a third, and what evidence would you need before accepting that risk?
- How would you explain a decision to extend routine waits to a patient who asks why their referral was not prioritized?
- What should a weekly allocation rationale record so that a later review can tell a reasoned trade-off from a habit?
Case Study 4
Explaining uneven outcomes across four community sites
Mercer Row Community Physiotherapy, a service of four sites handling about 9,800 episodes a year, with a shared assistant workforce and a central quality team.
The situation
Mercer Row's quality team reviewed twelve months of anonymized episode data and found that programme completion differed by almost a fifth between its best and weakest sites. Patient-reported improvement scores were broadly similar, but the spread around each site's average was wide at two locations. Sites A and D showed lower completion and more variation in discharge timing. The team had no shared definition of when an assistant should step up a programme, and two sites recorded missed sessions differently. Haruto, the quality lead, asked for a review before the next governance meeting.
The challenge
The data showed a pattern but not a cause. Completion differences could reflect case mix, booking lead times, staffing patterns, or how consistently assistants recorded progression decisions. Each explanation predicted something different in the records, and the team had only one quarter of linked data with clear progression notes. Staff at the weaker sites were understandably wary of a review that might read as blame, and the central team needed their knowledge to interpret what the numbers meant.
Analysis
The indicators pointed to patient experience as well as process. Completion was the most useful single measure, because a patient who stops early has usually been let down somewhere, whether by timing, progression, or communication. Patient-reported change was similar across sites, which suggested that people who finished their programmes improved at comparable rates, and that the difference lay in who stayed. A useful next step was to split completion by case type and by the first three sessions, to see whether early attrition explained most of the gap.
Process causes were likely to sit in the handoffs between assistants and supervising clinicians. Local protocol set out criteria for progressing or holding a programme, but the criteria were applied in different ways. At one site, progression decisions were made in the session and noted briefly. At another, they waited for a weekly clinician review. Missed sessions were coded as cancellations at two sites and as non-attendance at the others, which can make completion look worse at those sites for reasons unrelated to patient behavior. Standardizing the codes and the progression criteria was a precondition for reading the data honestly.
Actions taken
- Agree a single definition of progression and hold criteria, with one line in the record for each decision, and apply it at all four sites from the start of the next month's sessions.
- Standardize missed-session codes across sites so that cancellations and non-attendance are recorded the same way, and reconcile the last two quarters of data before any site comparison is shared.
- Run a plan-do-study-act cycle at the two weaker sites, with monthly run charts of completion and progression timing, and a named assistant and clinician owner for each chart.
- Review the cycle at the governance meeting after three monthly points, deciding whether to extend it, adopt it service-wide, or stop, and record the reasons in the quality log.
Results
After the shared criteria and codes were in place, the team found that part of the completion gap had been a recording artifact. Once cancellations were separated from non-attendance, one site moved close to the service average without any change in care. The two weaker sites showed a steady rise in completion over three monthly points, most visibly in patients whose progression was decided at a scheduled review rather than in the session. The service adopted the shared criteria across all four sites and kept the run charts running for another quarter.
Questions for discussion
- Which of the four quadrants would your own service find hardest to place its sites in, and what would you need to see to move a site from one to another?
- How would you separate a real gap in completion from one created by how missed sessions are recorded?
- What should a monitored improvement cycle report to staff at the weaker sites so that the review does not feel like a judgment on their practice?
Case Study 5
A son's request for information during a contested discharge
Northgate Physiotherapy and Community Rehabilitation, a charity-run service with three sites and an information-sharing policy reviewed by its governance group.
The situation
Iris, an adult patient attending a community rehabilitation programme, had been discussing her discharge plan with the supervising physiotherapist, Kwame. Her adult son, Tomas, attended the last two sessions and asked the assistant, Lena, for detailed progress notes and a view on whether his mother could manage at home alone. Iris had asked earlier, in front of Lena, that information not be shared with Tomas without her agreement. Her decision-making capacity for this discharge question had been noted as variable in the last review, and Kwame had not yet documented an assessment of it.
The challenge
Lena had a duty to be helpful to a family member who was clearly involved, and a duty to respect the confidentiality Iris had requested. She could not decide the capacity question herself, and she had no written record of the patient's current wishes beyond the remark she had heard. Tomas was pressing for an answer by the end of the week. The service's policy required a documented decision from a clinician before any disclosure, and it set out steps for involving family where a patient had given consent.
Analysis
Iris's needs in this case were both practical and procedural. She needed a discharge plan that matched what she could actually manage, and she needed her stated wishes to be the starting point for every conversation about it. The clinical evidence was incomplete in a specific way. Capacity had been flagged as variable, but no assessment specific to this decision had been documented. A remark made in one session is a valid statement of wishes, but it does not settle whether Iris can weigh the options now. Those are separate questions, and treating them as one would be a mistake in either direction.
The assistant's role here was narrow and important. Lena could not assess capacity, could not decide on disclosure, and should not offer Tomas a view on his mother's ability to live alone. Her duties were to record what she had heard accurately, to tell Kwame promptly, and to avoid informal reassurance to the son. Escalation ran to the supervising physiotherapist first, then to the service lead for the information-sharing decision, and the policy required that any decision to share be documented with the reasons. Shared decision making depends on the patient knowing who is in the room, so the family conversation needed to be arranged with Iris present or with her explicit agreement.
Actions taken
- Lena records Iris's words from the session verbatim in the note and tells Kwame the same day, without giving Tomas any view on his mother's ability to manage at home.
- Kwame documents a capacity assessment specific to the discharge decision before any information is shared, and records what Iris wants shared, with whom, and for how long.
- Hold a joint meeting with Iris present, offering Tomas a place in the discussion if Iris agrees, and set out in writing what the service can and cannot share without her consent.
- Refer the information-sharing question to the service lead for a governance decision if the capacity question stays open, and log the referral with its reasons and the agreed review date.
Results
Kwame completed the capacity assessment in the next session, and it found that Iris could weigh the discharge options with support, while her preference on information sharing was clear and consistent. Tomas attended a joint meeting with her agreement, and the service agreed a short list of information he could receive. Lena's note was used as the reference for what Iris had said. The discharge plan was revised to reflect Iris's own goals, and the file now records each decision with its reasons and the person who made it. Tomas has since asked for a single point of contact, which the team arranged.
Questions for discussion
- What would you need to document before an assistant could say anything to a family member about a patient's progress, and who should hold that record?
- When a patient's stated wish about information sharing conflicts with a relative's reasonable request, how would your service decide which to act on first?
- How should a team separate a question of capacity for one decision from a general view of a patient's ability, and what would each require in the record?
Learning Resources
Healthcare CASE STUDIES
China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.