Freelance client work · 2024
CareLoop — booking that patients actually finished
A community health provider in Geelong had a booking portal nobody finished. 71% of appointments still came in by phone, the reception team was drowning, and the no-show rate sat at 18%. I knew this world — I'd worked a desk like theirs.
- Role
- UX/UI Designer — solo, freelance
- Client
- CareLoop Health, Geelong
- Timeline
- 10 weeks
- Platform
- Responsive web

tablet first — that's what Marg uses
01
The problem
The portal existed, technically. But it asked for a Medicare number before a preferred time, used words like "service stream", and ended on a confirmation screen with no date on it. Patients quite reasonably concluded it was easier to call.
Every call is a two-minute task for the patient and a six-minute task for reception, multiplied by ~180 appointments a week. The brief from the practice manager was "make the website better". The real brief, which took me a fortnight to understand: give reception their mornings back without abandoning the patients who'll always need the phone.
02
Research & personas
I shadowed reception for three full days before interviewing a single patient. That was the right call — the receptionists knew exactly where the portal failed because they fielded the fallout: "it said booked but there's nothing written down."
Then eight patient interviews, deliberately skewed toward low digital literacy, plus an audit of two weeks of call logs to categorise why people phoned.
Marg, 68
Books for herself and her husband · iPad user
“If I can't print it, how do I know it's real?”
- Books appointments for two people, not one
- Reads every word — twice
- Distrusts confirmations she can't keep

4 of 8 patients booked for someone else. Nobody had planned for that.
03
User flow
- 01
Who is this for?
Me / someone I care for — asked first, not buried
- 02
What are you coming in for?
Plain words, not 'service streams'
- 03
Next available appointments
A list with dates, not a calendar grid
- 04
Your details
Medicare asked here — after intent is established
- 05
Confirmation
Big date and time. Print / text / save buttons
'book for someone else' was the branch nobody scoped
Two structural decisions did the heavy lifting. First: ask who the booking is for up front, because nearly half of patients book for a partner or parent. Second: kill the calendar. A month grid is a lovely pattern for people who plan; our patients mostly wanted "the soonest Tuesday morning with Dr Ahmed".
04
Wireframes

the calendar picker died right here
I ran the lo-fi screens past Dee — nine years on that reception desk — before any patient saw them. She crossed out my "appointment type" label in about four seconds: "Nobody knows what that means. Ask them what they're coming in for." That phrase shipped unchanged.
05
Hi-fi & prototype

tested at 200% zoom, because Marg does
The UI is intentionally quiet: one calm teal, large type, nothing animated. The constraint that shaped it most wasn't aesthetic — it was Medicare claiming rules, which dictated the order I could collect details in. More than any design principle did, honestly.
06
Usability testing
Five patients (three over 60) and both receptionists, moderated, on the clinic's own iPad and their own phones.
F01The date-picker was a wall
3 of 5 patients stalled on the calendar grid; one gave up entirely and said she'd 'just ring'.
FixReplaced it with a 'next available' list — real dates in words, grouped by practitioner. Completion went to 5/5.
F02'Appointment type' meant nothing
Participants guessed. Two picked the wrong type, which in the real system books the wrong length slot.
FixRenamed to 'What are you coming in for?' with plain-language options and a 'not sure' path that flags for reception.
F03The confirmation didn't feel finished
Two participants screenshot the confirmation 'just in case'. One asked where she should write it down.
FixRedesigned confirmation as a printable slip: big date, practitioner, address, and print / text-me buttons.
07
Outcome & reflection
Three months after launch: phone bookings down from 71% to 38%, no-shows from 18% to 11%, and reception estimated about nine staff-hours a week back. Dee's verdict — "the phone's quieter and the ones who call are the ones who should" — is the metric I'm proudest of.
What I'd do differently: I designed for the patient first and treated staff as an edge case. Halfway through I had to invert that — the 'not sure' path, the flagging, the printable slip all came from reception's reality. If I ran it again, staff workflows would be in the brief from day one, not week four.
And a small humility note: the patients who'll always call still call. The goal was never to eliminate the phone — it was to make ringing a choice instead of a workaround.
design for the front desk too — they absorb every failure
Next project
worth a look →
A bushfire preparedness planner people might actually open before late December.
