Shifts move out of the spreadsheet
and into the operation
Plan, attendance, timesheets and leave sit in one system and are read next to call volume. Who works when, who is on leave and which hour is left uncovered live on the operation's own screen rather than in a separate file.
Planning and swaps
Building the roster is one job; managing how it changes afterwards is the system's job too.
Plan from a template
Repeating weeks attach to a template, so the plan is not rebuilt from scratch every week. When the team grows the template is duplicated.
Availability
People mark the hours they are available themselves. That information is in front of whoever builds the plan, which cuts down the objections that arrive later.
Open shift offers
An uncovered shift is offered to eligible people; the first to accept takes it. Nobody has to ring around asking who is free.
Swap and approval
Two people request a swap and a manager approves. Approval is not one click: the request goes through checks first.
No swap is approved before the checks pass
The approval screen and an approval coming from a chat card go through the same steps. Two paths, one set of rules.
- Labour law check: rest periods and consecutive working limits are verified.
- Conflict check: the same person appearing on two shifts after the swap is blocked.
- Leave clash: if the swapped day is a leave day, the request does not pass.
- The result is shown to the manager with its reason, so "why could I not approve this" is answered on screen.
Attendance, timesheets and leave
Whether the plan held can only be seen through what actually happened.
Clock in and out
Attendance is compared against the shift; late starts, early finishes and missing days are flagged on their own.
Correction request
For a wrong entry the employee opens a correction request and a manager approves it. Records are not silently deleted; a trace remains.
Absence patterns
Patterns invisible one by one come out: leave that always lands on the same weekday, sickness clustering on Mondays.
Timesheet
Worked hours are totalled per period, so the data that feeds payroll is not calculated by hand.
Leave and the personnel file
Leave balance and the personnel file live in the same system; HR is not a separate world.
Balance and ledger
Accrual, usage and carry over sit line by line in a ledger. The argument about the balance ends with "where did this number come from".
Working day calculation
When counting working days between two dates, weekends and public holidays are deducted; leave days are not counted by hand.
Clash check
Leave requests from the same team landing on the same day are visible in advance; before approving it is clear whether the operation is left exposed.
Personnel file
Employment documents are tracked with their gaps, and sensitive files are held on a restricted disk. The org chart and onboarding steps live in the same place.
Frequently asked
Does it suggest shifts based on call volume?
The planning screen shows past volume side by side; which hour is busy and how many people are on it are read together. The person building the plan decides, and the system does not hide the volume. Teams that want the headcount computed from volume against their own service level target use the Workforce Intelligence add-on.
Can people see their own shifts?
They can. Everyone manages their own plan, availability, leave balance and swap requests from their own screen, which cuts down the repeated questions aimed at managers.
Does the manager approve a swap with one click?
No. The request first goes through labour law and conflict checks; if a check fails, the approval button shows the reason. The same checks run for an approval coming from a chat card.
Can we export data to our payroll system?
The timesheet can be exported per period. For payroll systems that need a direct link, transfer over a generic webhook is discussed; we agree the scope together.
Where are employment documents kept?
Sensitive personnel files are held on a restricted disk rather than the general file area. Who is missing which document appears in a list, but access to the document itself is limited by permission.
Let us build your roster together
In the demo we set up your own shift pattern: template, availability, the swap flow and the leave balance, with your team's actual structure.