ShiftWorksRiverside Meadows Care Center
Signed in as Care management and shift planning
Sample dataCare management and shift planning
Schedule, week 33
The draft for the week of 10 to 16 August — early, late and night shifts.
- week 33
- Riverview unit
- early shift
- late shift
- night shift
- unfilled shifts only
- show relief pool
Draft schedule — Riverview unit
A draft, not yet signed off. Until it is posted it can still change without notice.
Mon 10 Aug
6:00 AM–2:00 PM
Early shift — 8 of 8
in charge: Karen Fielding
1:30 PM–9:30 PM
Late shift — 6 of 6
in charge: Michael Lawson
9:00 PM–6:15 AM
Night shift — 2 of 2
Anna Wells, Neil Truman
Tue 11 Aug
6:00 AM–2:00 PM
Early shift — 8 of 8
in charge: Karen Fielding
1:30 PM–9:30 PM
Late shift — 5 of 6
relief pool asked
9:00 PM–6:15 AM
Night shift — 2 of 2
Anna Wells, Neil Truman
Wed 12 Aug
6:00 AM–2:00 PM
Early shift — 7 of 8
practice supervisor training
1:30 PM–9:30 PM
Late shift — 6 of 6
in charge: Michael Lawson
9:00 PM–6:15 AM
Night shift — 2 of 2
Dominic Taylor, Jonas Cooper
Thu 13 Aug
6:00 AM–2:00 PM
Early shift — 8 of 8
in charge: Ellen Whitmore
1:30 PM–9:30 PM
Late shift — 6 of 6
in charge: Michael Lawson
9:00 PM–6:15 AM
Night shift — 1 of 2
no registered nurse rostered
Fri 14 Aug
6:00 AM–2:00 PM
Early shift — 8 of 8
in charge: Ellen Whitmore
1:30 PM–9:30 PM
Late shift — 6 of 6
Fielding swap request open
9:00 PM–6:15 AM
Night shift — 2 of 2
Dominic Taylor, Jonas Cooper
Sat 15 Aug
6:00 AM–2:00 PM
Early shift — 6 of 7
one place open
1:30 PM–9:30 PM
Late shift — 5 of 5
in charge: Sabrina Radcliffe
9:00 PM–6:15 AM
Night shift — 1 of 2
relief pool asked
Sun 16 Aug
6:00 AM–2:00 PM
Early shift — 6 of 7
one place open
1:30 PM–9:30 PM
Late shift — 5 of 5
in charge: Sabrina Radcliffe
9:00 PM–6:15 AM
Night shift — 2 of 2
Anna Wells, Neil Truman
Cover against requirement
| Day | Early | Late | Night | Note |
|---|---|---|---|---|
| Mon 10 Aug | Early8 / 8 | Late6 / 6 | Night2 / 2 | NoteComplete |
| Tue 11 Aug | Early8 / 8 | Late5 / 6 | Night2 / 2 | NoteRelief pool asked |
| Wed 12 Aug | Early7 / 8 | Late6 / 6 | Night2 / 2 | NoteTraining |
| Thu 13 Aug | Early8 / 8 | Late6 / 6 | Night1 / 2 | NoteNo registered nurse |
| Fri 14 Aug | Early8 / 8 | Late6 / 6 | Night2 / 2 | NoteComplete |
| Sat 15 Aug | Early6 / 7 | Late5 / 5 | Night1 / 2 | NoteTwo shifts open |
| Sun 16 Aug | Early6 / 7 | Late5 / 5 | Night2 / 2 | NoteOne shift open |
Required cover follows the unit staffing key · nights need at least one registered nurse per house
From draft to posted plan
Collect preferences and blocked times
deadline was 20 Jul
Build the draft
shift planning, 24 Jul
Check rest periods and maximum hours
three warnings open
Consult the union steward
covered by the union contract
Post the plan and notify staff
by 7 Aug at the latest
How Awelior would approach this project
Riverside Meadows Care Center 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 Riverside Meadows Care Home the rota is built in a spreadsheet, printed and pinned up. Leave requests arrive on paper, everybody counts their own overtime, and whether the early shift has somebody with the right qualification is something the care manager knows from experience. When somebody drops out at short notice, the search starts from scratch.
Decisions
Qualification belongs to planning, not to the personnel file
Who may cover a shift follows from recorded qualifications — visible while planning, not only at audit. That is exactly where spreadsheet rotas fail: they can move names around, but they cannot object.
Draft and published are two states
A draft rota may change; a published one may not without notice. Carrying that distinction in the system is the difference between a tool and a shared file in which every version counts equally.
Working-time accounts run continuously, not at month end
Plus and minus hours are kept as they accrue and are visible to staff. That removes the basis for the month-end argument — and is the point where a system like this wins or loses trust.
Deliberately left outNo automatic schedule generation. An algorithm that writes the schedule moves responsibility to a place that cannot carry it — and under a collective bargaining agreement that is not a technical question but an organizational one.
What is in it
- Screens
- 5
- Content blocks
- 19
- Languages
- 4
Five screens, in all four languages, with sidebar, header and stated role. Navigation works; calendar, tables, board, history, charts and forms are rendered and inert. Names, shifts and balances are invented.
How it would go on
Working time law and collective agreements
Rest periods, maximum hours, premiums and collectively agreed rules have to live in the system, or it plans against the law.
The union contract
Schedules and hour banks are usually written into the collective bargaining agreement. Where one applies, introducing them belongs on the table with the union steward before it is decided technically.
Staff access
View the rota, request leave, swap a shift — on a phone. Without that route, the printout on the wall stays the real rota.
An application like this for your business?
ShiftWorks is invented — the way it is cut is not. Applications like this come out of the processes a business already runs.
Sample application by Awelior. Invented business, invented data, nothing stored.