Loading
Rotas are published against the personnel record, clock-ins land against the shift they belong to, and corrections are requested and approved rather than typed over the original. The timesheet is the output of that process, not a separate document.
Attendance reports show planned against actual, so a pattern of consistent overtime is visible before it appears as a payroll surprise.
Because they are produced by different people from different systems. The rota is planned in advance in a spreadsheet; the timesheet is assembled afterwards from clock-ins, memory and correction requests.
Somebody then spends a day a month making the two agree, and the version that reaches payroll is whichever one that person trusted.
The day a month spent reconciling stops. More usefully, the hours that reach payroll are the same hours that reach project cost, so finance and delivery cannot disagree about what a week cost.
Corrections keep their trail. When somebody asks why a shift was paid at a different length than it was planned, the approval that changed it is on the record.
It will not tell you whether a shift pattern is legal in your jurisdiction. Working time rules vary and change; Nest records what happened and flags what you configure it to flag.
It also does not do biometric or geofenced clock-in. Clock-ins are app and web based, which some operations will find insufficient.
Start with one team and one shift pattern for a full cycle before rolling out. Rota rules that look sensible on paper tend to reveal their exceptions in week three.
Agree the correction workflow before go-live. Who can request, who approves, and how long after the fact — those three answers prevent most of the disputes.
Approved hours become the payroll line in Books and the project cost in Loop — the same hours read twice, which is why the two figures cannot drift. Capacity planning in Loop reads shifts and leave together, so a plan cannot be built on somebody who is rostered elsewhere.
Rotas are published against the personnel record, clock-ins land against the shift they belong to, and corrections are requested and approved rather than typed over the original. The timesheet is the output of that process, not a separate document.
The day a month spent reconciling stops. More usefully, the hours that reach payroll are the same hours that reach project cost, so finance and delivery cannot disagree about what a week cost.
It will not tell you whether a shift pattern is legal in your jurisdiction. Working time rules vary and change; Nest records what happened and flags what you configure it to flag.
Start with one team and one shift pattern for a full cycle before rolling out. Rota rules that look sensible on paper tend to reveal their exceptions in week three.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.