App demo
Willowmead RosterWillowmead Care Home, Traverse City
Reporting sick
At 5:40 AM, instead of ringing the ward: four entries, sent, done. Nobody here asks for a diagnosis — admin collects the certificate from the health insurer electronically.
- In the hands of
- Registered nurse on rotating shifts
- Shown on
- Android — title on the left, three system buttons below
- Replaces
- Replaces the roster on the notice board, the photo of it in the family chat and the 06:10 phone call “can you cover for me today?”. The swap for Saturday reaches nine colleagues with a free weekend instead of two calls into the dark, and the 40 minutes of overrun on 13 Aug are reported before payroll closes.
Everything in this demo is laid out and none of it acts: buttons only report that they have no effect in the demo, checkboxes are fixed, input fields lead nowhere. Nothing is stored, sent or fetched.
How Awelior would approach this project
Willowmead Care Home, Traverse City is invented — the way it is built is not. None of this is work delivered for a client. It is the shape we would give such a project — with the same depth, but without a client who would have to answer for it.
Where it starts
At Willowmead Care Home the rota hangs in the unit, and anyone wanting to know when they work on Saturday photographs it. A shift swap happens by phone, so does a sickness call at twenty to six, and the month's hours are known only to the office. That an app can do this is not in question; the real question is everything it must not do along the way.
Decisions
The app's limits get a screen of their own
Where a union contract applies, the start and end of working time and every temporary change to it are bargained, not set by the employer alone. So the app states what the agreement covers, which data are collected and which explicitly are not — rather than putting it in a notice nobody opens. In a shop without a union the employer decides, and the app says that just as plainly.
No location, no device identifier, no last-seen
A rota app that records where staff are is not a convenience feature but performance monitoring under another name. What is collected is start, end, break and premium type — a rota needs no more.
The app does not notify on days off
Swap requests wait until the app is next opened. A request appearing on the lock screen on a free Sunday turns a private phone into a work device — and turns the app into the reason to delete it.
Deliberately left outNo question about the diagnosis and no swap without approval. The sickness form asks four things, and any further question would be one an employer may not ask. A swap runs through qualification, eleven hours' rest and the shift lead — otherwise nobody is on the unit on Saturday.
What is in it
- Screens
- 5
- Tabs
- 4
- Content blocks
- 16
- Languages
- 4
Navigation responds, including the route from the rota into a single shift and back. The swap flow, the correction report and the sickness notice are fully rendered and inert; the four states have a view of their own, and one of them shows a swap failing on the rest period.
How it would go on
The union, before anything is built
An app touching schedules and time recording lands squarely on the collective bargaining agreement where there is one. That conversation belongs at the start of the project, not at hand-over; arriving late, it produces changes to the data model.
Planning and time management
The rota is made in the scheduling system and the hours end up in payroll. The app is the staff's view of that, not the system behind it.
Rules the software has to know
Rest periods, maximum hours, premiums, accrual caps, qualifications per unit. Which of those the app checks and which a person decides is the question that makes a project like this demanding.
An app like this for your business?
Willowmead Roster is invented — the fit is not. Apps come about exactly this way: from the routes that already exist in a business, only without the paper in between.
Sample app by Awelior. Invented business, invented data, nothing stored.