Skip to content

How are staff shifts and timesheets managed?

Updated

The staff module ties shift rosters, timesheets, leave and advance/bonus calculations into one personnel file. The timesheet is never an estimate — it is produced from realised trips and shifts; a deduction never shows up without evidence, and staff on approved leave cannot be reassigned by mistake.

Who uses it

Any business that runs a field team — drivers, wait staff, technicians, guides — and settles pay or bonus at month end: the driver roster at transfer and taxi companies, shift staff at cafes and restaurants, crew at boat or yacht operators. The shared need: month-end timesheets that aren’t guesswork, a deduction that never appears without evidence, and an instant answer to “who was on this vehicle at this hour.”

How it works: timesheet from realised data, evidenced deductions, frozen periods

The timesheet is produced from completed trip and shift records; if a completed record’s hours are corrected later, the timesheet line changes with it — it is never a hand-typed estimate. Every deduction (a fine, an advance, damage) carries its own evidence row and a dispute path; a deduction with no evidence cannot enter the system.

An approved leave request lands on the relevant shift or trip plan and locks that person out of being assigned on that date — the “you were on leave but got scheduled anyway” problem never happens. Document validity is never a second copy; it is read from document tracking, and two people can never be written to the same vehicle/cabin at the same time, a lock that comes from the booking module’s resource lock. “Who was on this vehicle at this hour” resolves straight from a date-time to a person.

The weekly roster can be copied from last week, is scoped by branch/campus, and notifies affected staff of any change. Overtime, weekly rest and public holidays are counted separately and produce a period document. Salary, IBAN and advance data are closed to operations — a staff member sees and can dispute only their own record. Period close freezes the month: a closed period cannot change retroactively, and reopening one leaves its own audit line.

Example

Example: A transfer company’s 25-driver team starts its weekly roster by copying last week’s. A driver’s approved leave lands on the shift plan; the system leaves that day empty, and blocks operations if they try to assign that driver to a trip anyway. At month end, the timesheet is generated automatically from every trip completed that month; one driver’s late-arrival penalty shows up with an evidence row linked to the trip record, and the driver can dispute it from the panel. When the period closes, the timesheet freezes and exports to the accountant as a CSV on the 26th of the month.

How it is done in Rotenta

  1. Operations copies the weekly roster from last week on the Staff rail item, filtering by branch or campus.
  2. Once a leave request is approved, that date closes on the shift plan; that staff member can no longer be assigned on it.
  3. Completed trip and shift records post directly into the timesheet through the month; if a completed record’s hours are corrected, the timesheet recalculates.
  4. A deduction (fine, advance, damage) is added with its evidence row; staff can open a dispute from their own timesheet.
  5. Advance balance and advance ceiling are tracked; the period-end offset is calculated automatically.
  6. At period close, “Close month” freezes the timesheet; payroll input exports as CSV/Excel on the calendar day the accountant needs.
  7. Staff working a contract-bound shuttle route also match against the billing breakdown inside contracts and progress billing.

Frequently asked questions

Is the timesheet an estimate or built from real data?

It’s built from realised trips and shifts. If a completed record’s hours are corrected later, the timesheet line updates automatically — month end is never a guessed number.

Can I dispute a deduction?

Yes. Every deduction carries its own evidence row, and staff can open a dispute from their own timesheet; a deduction with no evidence cannot enter the system in the first place.

Can I accidentally assign someone who is on leave?

No. An approved leave locks that person out of that date the moment it lands on the shift/trip plan; an assignment attempt is blocked.

Who can see salary information?

Only users with the relevant permission; a staff member sees and can dispute only their own record. Salary/IBAN data never appears on operational screens.

Can I reopen a closed period?

Yes, but it’s an exceptional action, and every reopening leaves its own audit line — a closed period never changes silently. See how staff connects to the rest of the platform in our module guide, or reach us through contact.

More in this category

Get a quote

Leave your details and we'll get back to you the same day.

By submitting you acknowledge the Privacy Notice.