Back to the software solutions

Example site for an entirely fictional business — not a real company.

ShiftWorksRiverside Meadows Care Center

Sample data

Absences

Leave, time off in lieu, training and sick notes — recorded as date ranges, not as reasons.

Name or date range
  • August 2026
  • all units
  • annual leave
  • sick leave
  • training
  • open requests only

Requests

A request only shows up in the schedule once it has been approved.

Received

4 requests

  • Ellen Whitmore — annual leave

    21 Sep – 2 Oct

    10 working days2 days ago

  • Jonas Cooper — time off in lieu

    18 Aug

    1 day1 day ago

  • Sabrina Radcliffe — training

    7–9 Sep

    3 daysfunding not confirmed

  • Dominic Taylor — annual leave

    24–31 Dec

    5 working daysleave embargo

Under review

3 requests

  • Michael Lawson — annual leave

    17–28 Aug

    10 working dayscheck cover

  • Farah Nasrallah — annual leave

    5–16 Oct

    10 working dayscover not named

  • Neil Truman — time off in lieu

    22–23 Aug

    weekendnight rotation

Approved

already in the schedule

  • Anna Wells — annual leave

    3–14 Aug

    10 working daysrostered

  • Tobias Grant — training

    12 Aug

    1 daypractice supervision

  • Karen Fielding — annual leave

    28 Sep – 2 Oct

    5 working daysrostered

Absences in August

Staff memberUnitTypeFromToCoverStatus
Anna WellsUnitRiverviewTypeannual leaveFrom3 AugTo14 AugCoverNeil TrumanStatusApproved
Michael LawsonUnitOrchardTypeannual leaveFrom17 AugTo28 AugCovernot namedStatusUnder review
Farah NasrallahUnitRiverviewTypereported sickFrom27 JulTo18 AugCoverrelief poolStatusOngoing
Tobias GrantUnitOrchardTypetrainingFrom12 AugTo12 AugCoverSabrina RadcliffeStatusApproved
Ellen WhitmoreUnitRiverviewTypereported sickFrom30 JulTo3 AugCoverKaren FieldingStatusOngoing
Jonas CooperUnitOrchardTypetime off in lieuFrom18 AugTo18 AugCovernot neededStatusRequested
Sabrina RadcliffeUnitRiverviewTypeannual leaveFrom24 AugTo4 SepCoverDominic TaylorStatusApproved

This view is for management and the HR office. In the schedule itself every one of these entries reads simply “away”.

Record an absence

The request goes to the unit lead and only becomes visible in the schedule once it is approved.

Staff member
Ellen Whitmore
Type of absence
annual leave

No reason is recorded — for planning purposes the type is enough.

Derived from the shift rotation, editable by hand.

Cover
not named yet

Visible to shift planning and the HR office. No health information.

This form does not submit anything.
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 solutionBack to the software solutionsThe service page: Business software

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