Shift scheduling
Define shifts, put people on a schedule or let a working-time policy generate the days, and see the whole week at a glance. Late, early and absent are worked out against what was planned, and shift changes are requests a manager approves.
In plain words
Scheduling is deciding in advance who works when and where, so that real attendance can be compared with a plan. Without a plan, "late" has no meaning and an absence cannot be told from a day off.
dayFlow lets you plan in two ways at once. A working-time policy (fixed hours, a flexible window, or just a weekly target) generates every working day automatically, and the roster covers the days that are different: a night shift, a rotation, a one-off swap. Timesheets then measure each person against whichever applies.
What you get
Fixed hours for office-like teams, a flexible window where the day starts when the person arrives and runs for the required hours, and hours-only for part-timers who must reach a weekly total. Set per company, per location or per person.
In practice
The schedule shows a column per day and a row per person, with shifts, weekly offs, holidays and leave side by side. Assign a shift to many people for a range of dates in a few clicks.
In practice
A shift that ends after midnight belongs to the day it started, so a night's hours are not split across two days. Rotations are just roster entries, and a person can have their own shift pattern.
In practice
When a shift or a working-time policy is edited, the change counts from that day on. Days already worked keep the times and rules they were judged by, so last month's lateness does not change when you adjust this month's shift.
In practice
The difference
Without dayFlow
With dayFlow
Rosters live in spreadsheets and chats
One schedule that timesheets are checked against
Late and early are guessed
Computed from the plan and the real punches
Changing a shift rewrites last month
Edits count from today; past days keep their times
Examples
A supermarket
Three shifts across the week with different days off. The store manager plans the roster once; the timesheet shows who was late against each person's own shift.
A logistics depot
Nights rotate every two weeks. The rotation is entered for the period, and hours worked after midnight stay with the day the shift began.
An office with flexible hours
People can start between nine and ten and must work eight hours. Arriving at ten past ten is late; arriving at nine thirty is not.
The details
How it works
Create the shifts or set the working time for the company, a location or one person.
Assign people for the days that differ from the default.
Timesheets compare real punches with the plan.
Who it is for
Part of a whole
The plan is what makes the rest meaningful: late, early, overtime and absence are all measured against it. Leave and holidays remove expected days from it, and shift-change requests from the app edit it after a manager approves.
Questions
No. Set the working time for the company, a location or one person, and the days are generated. Use the roster only for days that differ.
The day starts when the person arrives inside the allowed window and ends after the required hours; arriving after the latest start is late.
Yes, from the app. A manager approves, and the day is replaced on the schedule.
No. A working-time policy generates the days. Use the roster only for people or days that differ from it.
Holidays are removed from the expected days, and work done on one counts at the holiday's own rate.
They send a shift-change request from the app for a day; when a manager approves, that day's shift is replaced on the schedule.
Yes. A location can use its own working time, and an employee can override both.
Set up your locations, register faces and let your team clock in. Your company gets its own address.
