How to Track Overtime for Casual Construction Workers in Kenya

Ask most site foremen how many overtime hours their crew worked last week, and you'll get an estimate — rarely a number anyone would stake their payroll on. That gap between "roughly how long they worked" and "exactly how long they worked" is where disputes, over-payment, and under-payment all start.

Why paper timesheets get overtime wrong

A paper register captures a check-in time and a check-out time, written by hand, often hours after the fact. It can't tell you whether a worker actually arrived when the sheet says they did, and it gives no consistent reference point for what counts as a "normal" day versus overtime. Every foreman ends up applying their own judgment — which means every crew gets treated differently.

What accurate overtime tracking actually requires

Three things need to be true before an overtime number can be trusted:

• Real check-in and check-out times — captured at the moment they happen, not reconstructed later.
• A clear definition of "standard hours" — your company's own working-hours schedule, so a 9-hour day and a 12-hour day aren't both silently treated as normal.
• A consistent calculation — the same rule applied to every worker, every day, so overtime pay isn't a matter of who asked their foreman nicely.

What this looks like day to day

In practice, the workers who actually move the needle on overtime accuracy are the ones on site: a foreman checking a crew in and out from a phone, with the time captured automatically rather than written down. From there, overtime becomes simple arithmetic — total hours worked, minus the day's standard hours, taxed at whatever multiplier applies (a public holiday or a rest day should usually be a different rate than a normal weekday).

It's also worth deciding upfront how "late" gets defined. A worker fifteen minutes past their start time isn't the same situation as someone two hours late — a small grace period before lateness counts against a worker avoids penalizing normal variation in traffic or transport, while still catching genuine patterns.

Don't forget what happens if nobody checks a worker out

Even with good intentions, someone will forget to close out a shift. The safest default is a fallback: if a worker is still checked in well past your normal closing time, treat that day as ending at the standard closing time rather than crediting hours nobody can verify — and flag it for a supervisor to confirm rather than quietly accepting it as final.

The payoff

None of this is complicated once it's automatic. What it removes is the disagreement — a worker and a foreman looking at the same number, calculated the same way every time, with no argument to be had about who remembers what. That's worth more to a payroll cycle than any spreadsheet formula.