Working hours, shifts and overtime in one traceable flow.
Every organisation that pays people by the hour — or simply needs to prove who worked when — repeats the same cycle: someone builds a roster, someone records what actually happened, someone approves overtime, and then payroll closes the period. When those four things happen in different tools, the month ends with a reconciliation argument. Tenderely BPM ties shift planning, daily attendance, exception handling and period sign-off into one connected record that plugs straight into the person form you already have.
What does working-time management repeat every period?
01
Defining shifts
Morning, afternoon, night, rotating — each pattern has its own hours and rules. When those definitions live only in someone's head, inconsistency creeps in the moment a manager changes.
02
Building the weekly roster
Matching available staff to required coverage, accounting for leave and public holidays. A roster built in a spreadsheet breaks the moment two people swap days.
03
Recording daily attendance
What actually happened versus what was planned: late starts, early finishes, absences. The gap between plan and reality is where payroll disputes begin.
04
Handling overtime
Extra hours need a request, a reason and a manager decision before they happen — not an argument about them afterwards. Without a record, the hours either vanish or inflate.
05
Exceptions and corrections
A forgotten punch, a shift swap, a public holiday worked. Each exception needs to be noted, approved and reflected in the period total before payroll runs.
06
Closing and locking the period
Once payroll is calculated the figures must be frozen. An editable spreadsheet that anyone can still change after submission is not a closed period — it is a liability.
Where does this break down today?
The roster and the timesheet are never in sync
One lives in a shared spreadsheet, the other in a payroll export. Reconciling the two is a manual job done under time pressure at month end, and it always finds something that does not match.
Overtime approval happens after the fact
A manager nods in a corridor, the hours go into the sheet, and the approval arrives — if it arrives at all — as a WhatsApp message nobody can attach to anything.
Exceptions depend on institutional memory
One HR person knows which team has which shift pattern, which site has which public holidays, and which employee has a standing arrangement. When that person leaves, the knowledge goes with them.
Nothing is auditable
Who changed a cell, when, and why? A spreadsheet cannot answer that. In a wage dispute or an inspection, the absence of an audit trail is as damaging as the error itself.
What changes with Tenderely BPM
01
Shifts are structured definitions, not free text
Each shift pattern is a named, reusable record with its own hours and rules. The roster references those definitions, so a change to a pattern propagates correctly instead of being patched cell by cell.
02
Overtime goes through an approval step
Conditional and parallel approval steps are configured without code. An overtime request reaches the right manager, waits for a decision, and the outcome is attached to the same record as the hours — permanently.
03
Deadlines remind themselves
Give any step an SLA and it warns when the deadline passes. Timesheets that need signing off stop sitting quietly in an inbox waiting to be remembered.
04
Staff approve from their phones
The same flow runs in the iOS and Android apps, so a site manager confirms a roster or approves a swap with one tap regardless of where they are.
05
The period locks when it closes
A signed-off period becomes a read-only record. The figures that went to payroll are the figures that stay on the system, and the audit history shows who locked it and when.
06
Hours become a dashboard, not a report request
Tenderely BPM turns accumulated records into dashboards and reports. Overtime by department, attendance rates, open exceptions and upcoming shift gaps are visible now, not at the end of the month.
FAQ
Does this module work with our existing employee records?
+
Yes. The timesheet and shift records bind to the person form you already have in your workspace, so you are not duplicating staff data. If you are starting fresh, the module works alongside any sector package — it is designed to be sector-independent.
Can we handle multiple sites or departments with different shift patterns?
+
Yes. Shift definitions, roster rules and approval chains are configured per unit or role. A night-shift factory floor and a standard-hours office team can run entirely different patterns inside the same workspace without interfering with each other.
What stops someone editing a timesheet after the period closes?
+
Period locking makes the record read-only once it is signed off. Any subsequent change requires reopening the period through a defined step, and the audit history records who did that and why. The original figures are never silently overwritten.
Can employees submit their own hours or is this only for supervisors?
+
Both patterns work. You can configure the flow so employees record their own hours and a supervisor approves them, or so supervisors enter hours directly. Role-based access ensures each person sees and edits only what their role permits.
How does overtime approval fit into the flow?
+
Overtime is a request step inside the same flow, not a separate process bolted on afterwards. Conditional branching means the request routes to different approvers depending on the amount of overtime, the department or any other field you define — all without writing code.