Progress notes drafted. Clinicians keep the final word.
Amana Community Services
Amana Community Services is a Sydney NDIS provider. Their therapists spent their evenings on session notes. Now a therapist sends a voice note, a recording of the session or a photo of handwritten notes, and the progress note comes back drafted on the right template, ready to check and sign.
The reported timing relates to the first implementation. It has not been re-measured on the later Microsoft rebuild. System-check figures describe the review recorded in this case.
Case record updated 30 September 2026- Recorded saving per note, first version, four therapists
- 25 to 40 min
- Recorded saving per note, first version, four therapists
- Later rebuild, timing not re-measured
- Microsoft
- Later rebuild, timing not re-measured
A draft to review, with the result kept in context.
The case record describes 25 to 40 minutes saved per session note on the first version, used by four therapists. That historical timing has not been re-measured on the Microsoft rebuild. The workflow gives the therapist a draft to check and sign.
The 28 August 2026 review of the Microsoft rebuild recorded monitoring checks and a test in which the same note was submitted twice, with both notes retained. That is evidence from a particular review, rather than a guarantee of future reliability or a new timing result.
Saad Ramadan
Principal, Amana Community Services, Sydney. 37 seconds, in his own words.
Abbas Ramadan
Occupational Therapist, Amana Community Services. 60 seconds, in his own words.
The notes came home with the therapists.
The practice needed progress notes in its required formats. For the therapists described in this case, writing continued after the last session. Starting each note from a blank page was the problem the drafting workflow addressed.
A voice note in. A drafted progress note out.
The system transcribes what the therapist sends, picks the right template and drafts the progress note. The therapist owns every note. They read, correct and sign off before anything enters the record. Consent is sought before a session is recorded, and a participant can say no at any time with no effect on their supports.
The August rebuild moved transcription and drafting into Amana's own Microsoft environment. The recorded design used Australian Microsoft services, with retention requirements set by Amana's compliance lead. Those details describe that implementation; data handling and provider settings need to remain aligned with the practice's requirements.
What was hard, and what Amana had to do.
The 25 to 40 minutes was measured on the first version. The system has since been rebuilt inside Amana's own Microsoft environment, and we have not re-measured the timing on the new version yet. When we do, the number on this page will change to match.
The hardest part was the switch. The old way stayed available as a fallback while the team settled in. Amana's compliance lead went through consent, retention and complaints line by line. We built the system and the documentation. Compliance decisions stay with Amana.