PhysioSync — software that speaks a clinician's language.

Physiotherapy doesn't fit that shape. A patient isn't a booking — they're a course of care for a specific problem, which might run twelve sessions across six weeks. They might come back a year later with something unrelated, and that has to be a separate story in the same chart.

Progress isn't a feeling, either. It's a measurement: range of motion in degrees, muscle strength on a nought-to-five scale, pain on a numeric rating, and a validated questionnaire score that has to be calculated exactly right or it means nothing.

So the build started from the clinical vocabulary rather than the database. Episodes, not appointments. Assessments with real instruments. Sessions structured the way a physiotherapist already writes their notes.

Before calling anything finished, the codebase was put through a written audit — not a skim of folder names, but tracing each feature from route to controller to service to migration, running the type checker and the full test suite, and verifying every claim against the code itself.

The audit confirmed what the platform was built to guarantee: both apps typecheck clean, the unit suite passes, money handling is exact to the paisa throughout, and concurrency is guarded at the two points where a clinic's data genuinely depends on it — package consumption and slot booking.

That document is a deliverable, not an internal note. When we hand over a platform, the client gets a written account of how it was verified — feature by feature, with the evidence. It's the difference between “trust us, it works” and “here's how we know it works.”