A staff dashboard rebuilt in 41 days
The system we built for an Australian physiotherapy practice got so slow the owner nearly replaced it. We rebuilt it in 41 days while her staff kept working. Here is how, including the parts that took longer than planned.
The problem, in their words
The practice runs its staff on checklists, training modules, quizzes and action items. We first built all of it for them on WordPress, and it worked for about a year. Then it slowed down. Switching pages took at least five seconds, reports for a whole team took longer, and checklists misbehaved: a tick sometimes did not save, or only showed after a reload. Team leaders also found the WordPress back end confusing when they created or edited checklists and training.
What we saw
This was our system, so it was our problem to fix. The owner had started looking at other tools for checklists and was close to keeping ours only for training. WordPress was not built to store this kind of data, and patching it would not make it fast. So we rebuilt it as a custom system, with the data stored in plain tables that are quick to read and write.
How we solved it
We rebuilt each part from scratch: checklists that save instantly without a reload, including weekly and monthly ones; training modules with the same progress tracking, but simpler to create and assign; action items with clearer assignment and tracking; and a quiz builder with grading for both written and practical assessments. Team groups now connect to checklists and training in one place, and team leaders manage everything from the dashboard instead of digging through back-end pages. We also removed fields nobody used, which made the screens much easier to follow. The staff kept using the old system while we built, so we wrote a WordPress plugin that copied data from the old system to the new one as it changed. The owner and our developer met every week to review progress, and the staff started testing once about 90% was built.
What went wrong
Keeping the two systems in step was harder than we expected. After each batch of changes, the staff or the owner would spot numbers that looked out of date, and each time we traced the gap in the copying and closed it. Quizzes took the longest: the copying we had relied on for weeks did not include quiz data at all, so we rebuilt it to carry every result, grade and the training chapter each quiz belongs to, while also building the new quiz builder from scratch. The fix that stuck was simple: we now check all the data after every batch, before anyone else sees it.
The effect
The work started on July 30, 2026, and the last bug fix went in on September 9: 41 days in total, at about 10 hours a week alongside the developer's other work for this client.
What changed
- Page switches that took at least five seconds now load with no wait, by the owner's own account.
- The owner edits checklists herself, without asking us.
- Staff training progress is easier for her to find and read.
Where it stands now
The owner told us she was close to dropping the old system, and she was relieved to have one that works. Since then she has brought us new things to add. One was an activity log her physiotherapists use for their year-end report, which they might have had to start paying for elsewhere. We rebuilt it inside the dashboard, for recording only, and her staff now reach it from the same place as everything else.
What we do differently now
This is the second time a WordPress system we built was outgrown, so we now watch for the early signs: slow pages, workarounds, and a client trying other tools. When we see them, we propose the rebuild before the client has to ask. What we would do again: weekly reviews with the owner, letting staff test only once the work is nearly done, and switching over without stopping anyone's day. A client who nearly left now brings us her next idea.
Related
Send us your brief and get a price.
A short brief, then a written proposal within 1 working day. We talk once the work needs it.
