Kuzhu rosters put people on shifts in advance — rotating patterns, week-offs, and night shifts with their allowances — and attendance evaluates every punch against the shift the person was actually rostered on. Factories, hospitals and support teams run on this.
Why it exists
Shift management software exists because a factory, a hospital ward and a support floor cannot run on "9 to 6". Kuzhu lets you define shifts with their own timings, grace, breaks and night allowances, then roster people onto them — weekly rotation, fixed patterns, or a supervisor dragging names onto a grid for next week. Attendance is then judged against the shift each person was actually on, which is the entire difference between a fair muster and a monthly fight.
Rotation is where spreadsheets die. A three-shift rotation with alternating week-offs across forty operators is a pattern here, applied for months in one action, with exceptions edited on top. When someone swaps, the roster records who swapped with whom and attendance follows the new reality that same day.
Night shifts get the arithmetic they deserve: a shift that starts at 22:00 and ends at 06:00 is one working day, the punch after midnight belongs to it, and the night allowance you configure lands in payroll for exactly the nights actually worked — counted from attendance, not claimed on a form.
The outcome
“The roster is the plan, and attendance is checked against the plan.”
Feature by feature
Start
01
Shift patterns with rotation rules, applied to teams in one action
02
Week-off management that respects statutory limits
03
Night shift allowances flagged for payroll automatically
Outcome
How it works
Most teams have this live inside the first month — the workspace exists on day one, and week three is a parallel run against whatever you use today.
Timings, grace, half-day thresholds, break windows and night-shift flags. A shift is policy, so changing it changes the judging everywhere it is used.
Weekly rotations and week-off cycles as reusable patterns — morning-evening-night with a rotating off day is configured once, not redrawn monthly.
Assign patterns to teams, then handle real life: swaps, stand-ins and one-off changes, each recorded with who changed what.
Everyone sees their own upcoming shifts in the app. "What shift am I on Thursday" stops being a WhatsApp message to the supervisor.
Every punch is read against that day’s rostered shift — late, overtime and night allowance computed per person per day, feeding payroll directly.
Worth a closer look
Buyer questions
2 answers
The answer
The monthly roster spreadsheet has a known failure mode: it is right on the 1st and fiction by the 12th. Because Kuzhu’s roster is live, a swap or a stand-in edits the actual schedule attendance will judge against — and the audit trail keeps the original, so "who moved me to nights" has an answer. Supervisors manage exceptions, not the whole grid.
The answer
Overtime is minutes past the rostered shift, counted from punches, subject to the policy you set — thresholds before it starts counting, caps per day, and rates that payroll applies. Because it derives from the same judged day the employee can see, the number on the payslip and the number in the worker’s head match, which is what stops the month-end queue at the HR window.
Questions
Something else on your mind? +91 82093 73274 — a person answers, mon–sat, 10am–7pm ist.
Terms used here
Shift roster
A shift roster is the plan of who works which shift on which day, published ahead of the week, against which attendance is judged.
Week-off
A week-off is the paid weekly rest day every employee is entitled to, fixed by roster and not necessarily a Sunday.
Yes — that is the standard pattern case. Define the rotation once, assign it to the team, and the roster extends itself until you change it.
The shift owns the whole span: the day counts once, punches after midnight pair with it, and night allowance accrues for nights actually worked.
Yes — swaps and stand-ins from the app, each recorded. The employee sees the change immediately in their own schedule.
Yes, as minutes beyond the rostered shift from actual punches, with your thresholds and caps, flowing into payroll at your configured rates.
Yes. Shifts and patterns are defined per your structure, so the factory, the office and the store each roster their own reality.
Works best beside
Other people modules that share the same employee record, so information moves with the person instead of between spreadsheets.
No polished slides. No imaginary employee data. Walk us through how your HR actually works today and see where Kuzhu can take the work off your team.
30 minutes · Your numbers · Your questions
What happens in the demo
Attendance, payroll, approvals — whatever is creating the most work.
You see exactly how the workflows connect instead of hearing a feature list.
If Kuzhu is not the right answer, we will tell you.
Ready when you are.
Kuzhu HRMS
WhatsApp us
WhatsApp us