A fair rota with no gaps.
Shown in the product as “Rota”The week as a grid you type into — one shift per person per day. Leave that cannot overlap itself (the schema refuses the second request), decided with a recorded reason. Credentials — registrations, BLS cards — that announce their expiry instead of lapsing quietly. People: probation with an end date and a dated decision, never a silent roll-over; transfers between departments or branches signed by the releasing and the receiving side, two different people, and moved on their date; appointment, confirmation, increment, transfer, experience and relieving letters from the one staff record, numbered and never edited after issue. Appraisals: self-rating, the department head’s rating, a calibrated final rating and sign-off before any increment, and the key roles with who could step in. Registers: the employee, attendance and wage registers laid out from what is already recorded, and every contractor’s licence against the workers on site. For an agency that supplies nursing aides or housekeeping, the rate the contract agrees per role and shift is kept with its clause, each worker’s shifts as worked from the roster, the biometric reader or the gate register, and the agency’s monthly invoice is checked line by line against both — shifts billed but not worked, a rate above the agreed one, a worker not deployed — before HR passes it for payment or disputes it.
/staffrota.readWhat it does not do, by design. A listing with only benefits is an advertisement.
The design preview: every screen drawn with the product’s own blocks, on an example clinic’s demo data. Nothing here is a real patient.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.