TimeMark
Custom attendance management system
Shifts, punches, leave and overtime — accurate at month end.
For organisations with shifts, multiple locations, and staff who are not all sitting at a desk - site labour, field teams, factory shifts and office staff on the same system. Built so the record is accurate enough to pay from.
Screens
What it looks like
4 screens from the working demo — the same data you will see if you open it.
The problem
Why this gets built
Attendance disputes are expensive because they are unfalsifiable. Without a timestamped record everyone remembers the month differently, and payroll ends up negotiated rather than computed.
Who it is for
Fit
Factories, offices and multi-site operations where hours worked determine what people are paid.
Capabilities
What the system does.
Live attendance board
Present, absent, late and on-leave for today, visible without running a report.
Biometric device sync
Punches pulled from devices with sync status monitored, so a dead device is noticed the same day.
Shifts & rosters
Multiple shift patterns, week-offs and rotation, assigned per employee or team.
Leave management
Requests, approvals and balances by leave type, reflected in attendance automatically.
Overtime & late rules
Grace periods, half-days and overtime computed by policy rather than judgement.
Payroll-ready export
Attendance totals feed directly into the pay run with no re-keying.
See it running
TimeMark is a clickable demo — open the modules, browse the tables, see how the screens fit together.
Buying decision
Why off-the-shelf falls short here.
Attendance is only worth capturing if payroll can be computed from it, and most attendance systems fall short of that bar. They record in and out times accurately, then leave shift rules, overtime slabs, half-days, late-mark policies and leave interaction to be applied by a person in a spreadsheet afterwards. The precise timestamps end up feeding an imprecise process.
Coverage is the other gap. A biometric reader at the office door records office staff. It does not record the field engineer, the site gang or the delivery team, so those go into a register and arrive at payroll as a typed summary - which is the number that actually determines pay.
A custom build covers every category on one record, then applies your rules where the data is, so what reaches payroll is a computed figure rather than an interpreted one.
Comparison
Packaged product vs a custom build.
The differences that decide it, for this sector specifically.
| Aspect | Packaged product | Custom build |
|---|---|---|
| Capture | One method, usually a fixed reader | Biometric, RFID, geofenced phone marking and supervisor entry, chosen per group |
| Shifts | Fixed shifts | Rotating rosters, split shifts and night shifts spanning midnight, handled as rules |
| Overtime | Hours beyond a threshold | Your slabs and multipliers, including different rules by day type and worker category |
| Leave | A separate module | Applied against the same record, so a marked absence and an approved leave cannot disagree |
| Field staff | Excluded | Geofenced marking with location and a photo where the policy requires one |
| Payroll handoff | An exported summary | A computed figure payroll consumes directly, with the workings visible |
Integrations
What it connects to.
A system that cannot reach the tools already in use becomes another island. These are the connections this sector normally needs.
Biometric and RFID devices
Standard readers polled directly, including sites with intermittent connectivity.
Payroll
Days, overtime and deductions passed straight to the pay run, with no summary in between.
HR records
Joining, confirmation and exit dates driving eligibility without a parallel master.
Messaging
Absence and late alerts to the supervisor the same morning, when they can still act on it.
Accounting
Labour cost attributed to the site or cost centre the hours were worked against.
How it runs
From first conversation to cutover.
Indicative for a build of this shape. The parallel run is not optional — nothing is retired until the numbers agree.
- 1 week
Discovery
We take your shift patterns, overtime rules, leave policy and the list of locations and worker categories.
- 3-4 weeks
Core build
Capture, rosters and rule computation, tested against a month of your existing records.
- 2 weeks
Pilot
One location and one field team run live while the register continues, until both agree.
- 1-3 weeks
Rollout
Remaining locations, devices deployed, payroll feed switched on.
After rollout
What changes day to day.
- Payroll consumes a computed figure, so the monthly interpretation step disappears.
- Field and site staff are on the same record as office staff instead of arriving as a typed total.
- Overtime is applied by rule, which makes it both consistent and arguable with evidence.
- A supervisor learns about an absence in the morning rather than at month end.
Described qualitatively on purpose. We do not publish percentage improvements we cannot attribute to a named client with their agreement.
Questions
Common questions.
Does it work with existing biometric devices?
In most cases yes. Punches are pulled from the device and sync status is monitored, so a device that stops reporting is noticed the same day rather than at month end.
Can it calculate overtime and late marks automatically?
Yes. Grace periods, half-days, week-offs and overtime are applied by policy, so the monthly total is computed rather than negotiated.
Does attendance feed directly into payroll?
Yes. Attendance totals flow into the pay run without re-keying, which removes the most common source of payroll disputes.