Working-time accounts

Contracted against actual hours, overtime, and the warnings to settle before the plan goes up.

+312.50 h

across all overtime accounts

over 46 staff

accounts above 60 hours

reduction plan agreed to 30 Sep

rest-period warnings in week 33

under 11 hours between two shifts

−41.00 h

total hours in deficit

nine accounts below zero

Warnings from the working-time check

The draft is checked automatically. Every warning has to be decided; none is quietly passed over.

Rest period too short — 13 to 14 Aug
late shift to 9:30 PM, early shift from 6:00 AM
8.5 hours of rest. The rule is eleven hours, reduced to ten in care work if the time is made up within a month.
week 33 draft
Seven shifts in a row
Orchard unit, 10–16 Aug
The draft leaves no day off. Suggestion: bring in a relief worker on 14 Aug.
week 33 draft
Two accounts above the agreed ceiling
as at 31 Jul
Above 60 hours a reduction plan has to be agreed. The deadline in the collective bargaining agreement falls on 30 Sep.
July
Night premium to be added
three shifts in July
Shifts that ran past 10:00 PM were booked as late shifts. To be corrected before the payroll run.
July

Accounts as at 31 Jul 2026

Staff member	Unit	Weekly hours	Contracted, July	Actual, July	Balance	Status
Karen Fielding	UnitRiverview	Weekly hours30.0 h	Contracted, July138.0 h	Actual, July156.25 h	Balance+18.25 h	StatusWithin range
Michael Lawson	UnitOrchard	Weekly hours39.0 h	Contracted, July179.4 h	Actual, July241.9 h	Balance+62.50 h	StatusReduction plan needed
Anna Wells	UnitRiverview	Weekly hours35.0 h	Contracted, July161.0 h	Actual, July155.0 h	Balance−6.00 h	StatusWithin range
Farah Nasrallah	UnitRiverview	Weekly hours20.0 h	Contracted, July92.0 h	Actual, July88.0 h	Balance−4.00 h	StatusWithin range
Tobias Grant	UnitOrchard	Weekly hours39.0 h	Contracted, July179.4 h	Actual, July246.4 h	Balance+67.00 h	StatusReduction plan needed
Ellen Whitmore	UnitRiverview	Weekly hours30.0 h	Contracted, July138.0 h	Actual, July129.5 h	Balance−8.50 h	StatusWithin range
Neil Truman	UnitOrchard	Weekly hours35.0 h	Contracted, July161.0 h	Actual, July213.0 h	Balance+52.00 h	StatusKeep an eye on it
Sabrina Radcliffe	UnitRiverview	Weekly hours25.0 h	Contracted, July115.0 h	Actual, July118.25 h	Balance+3.25 h	StatusWithin range

Accounts roll forward on the first of each month · balances are worked off as time in lieu, not paid out

How the accounts are spread

As at 31 Jul 2026. The chart shows accounts, not people — the individual figures are in the table above and stay with management.

below zero: 9
0 to 10 hours: 14
10 to 30 hours: 13
30 to 60 hours: 6
above 60 hours: 4

The project frame

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.

Talk through your project

Sample data

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.

Talk about a solution Back to the software solutions The service page: Business software

Sample application by Awelior. Invented business, invented data, nothing stored.