A twelve module course for physicians, run from one site

The brief

A certificate course for practising physicians has an administrative tail most people underestimate. Applications arrive over weeks. Payment has to be taken and reconciled. The schedule shifts. Every session needs feedback, and feedback collected on paper never gets counted. Then somebody has to know who actually attended.

Done with forms and spreadsheets, that is a part time job for the organiser. The brief was to make the website do it.

What we built

• An application and payment flow that is resumable, so a doctor who closes the tab halfway does not start again
• A schedule and a calendar feed the organiser edits directly, with no developer needed for a date change
• Session feedback forms opened by QR code in the room, while the session is still fresh
• A private results dashboard behind a passcode, so the teaching faculty can see how each module landed
• Public course pages that explain the curriculum, the faculty and what the certificate is

The principle behind it

The person running the course should not have to ring us to change anything that changes often. Dates, sessions, faculty and feedback are all in the organiser's hands. We are only needed when the shape of the thing changes, not when its contents do. That is how software for a small organisation should be built, and it is the difference between a site that stays current and one that is six months stale by the second batch.

How it runs now

One address does enrolment, scheduling, feedback and reporting for the whole course. The organiser opens a dashboard instead of asking anyone to run a query.