How it works

From the plan to the proof, one working day at a time

Six steps, one record. Who works for you, what they were meant to do, what actually happened, what needs a decision, and what all of it tells you.

Six steps, from configuration to a decision, on one record.
Every employee, office, hybrid, shift and field, walks the same path.
Configured, not coded, so every step follows your own rules.

Book a demo

The story

One day, six steps.

Set up
Say who works for you, and how the day should run
Employees, branches and departments go in once. Then the rules that shape a day: shift patterns, geofences around sites, and which manager decides which request. All of it is configuration, not a release.
- Structure drives access, so a branch manager sees their branch
- Office, shift and field groups sit in one structure under different rules
- Independent, policy-driven rules per group
- Branch 04
- Shift 08:50 to 17:00
- Geofence 150 m
- Leave: line manager
Publish
The plan goes out to every phone
The month is planned once and every employee sees their own schedule in the app. Visits are booked against clients and services. Nobody screenshots a spreadsheet into a group chat.
- Shift master and monthly planner
- A personal schedule for every employee
- Rotations, split and overnight shifts, and swaps
- Roster, March
- My schedule
- Visit booked, 10:30
Work
The day happens where the work is
A mark is made from the app, with its location, inside a geofence where the work calls for it. A visit moves across the board from booked to running to done. A correction or a leave request is raised from the same phone.
- Location on every mobile mark, geofences around sites
- A visit board with booked, running and done
- Requests raised in the product, not in chat
- 08:58 In, inside
- Booked
- Running
- Done
Compare
The plan meets the proof on one record
The roster and the attendance sit on the same record, so the comparison is automatic. Planned 08:50, actual 08:58. Covered, or not. The gap is visible while the day can still be fixed, not at month end.
- Plan and attendance compared per person, per day
- Who is active and who is missing, in the console
- Overtime and labour rules
- Planned 08:50 to 17:00
- Actual 08:58 to 17:32
- 8 min late
- Covered
Decide
Exceptions become decisions, with a reason
A late start needs a reason. It is raised as a correction, lands in the manager's queue, and is approved or refused with the reason kept on the day. Every important action is written to a tamper-evident ledger.
- Corrections, out-duty, leave and expenses in one queue
- Decisions kept with the day they belong to
- Multi-level routing, delegation and escalation
- Late 8 min: reason needed
- Manager queue: 1 to decide
- Approved, reason kept
Act
The record goes to work
Attendance reaches payroll as an input. Reports read from the one record, so finance and HR bring the same numbers to the meeting. Exceptions are pushed to the person who can act, and events reach the systems that subscribe to them.
- Attendance, leave, expense and shift reports
- Structured import and export
- Exceptions pushed to supervisors and subscribable events
- Payroll input
- Reports
- Exceptions pushed

Roles

Who does what, at each step.

Step	Who	In the product
Set up	HR and an administrator	Employees, structure, shift master, geofences, request types
Publish	Operations and supervisors	Monthly planner, personal schedules, visit booking
Work	Every employee	Attendance mark, visit status, requests from the app
Compare	Supervisors	Active and missing today, plan against attendance
Decide	Line managers and finance	One queue: corrections, leave, expenses, out-duty
Act	Payroll, finance, leadership	Reports, exports, pushed exceptions and events

Along the journey

Everything the six steps run on.

One record underneath, and the enterprise layer inside every step.

Across the six steps

Employee records, structure, roles and scope
Shift master, monthly planner, personal schedules
Mobile and geofenced attendance, visit board, requests
Plan compared with attendance, active and missing today
Leave, expense, correction and out-duty decisions on the ledger
Attendance, leave, expense and shift reports; import and export
Policy-driven rules per group
Rotations, split and overnight shifts, swaps
Biometric, RFID, kiosk and supervisor marking
Overtime and labour rules
Multi-level routing, delegation, escalation
Exceptions pushed to supervisors; events other systems subscribe to

FAQ

Common questions

How long does set-up take?

Loading the employee list and structure is the first step of onboarding, usually through structured import. Most organizations start with one branch or one team, then widen.

Does every step work for office employees too?

Yes. An office employee marks from the app without location, has a schedule, raises requests and appears in the same reports. Location applies only to the groups whose work needs it.

Do the six steps work together?

Yes. Every step writes to the same record, so the plan, the proof and the decision always agree, from policies per group and rotations to multi-level approvals and pushed exceptions.

Can we see this against our own operation?

Yes. Bring an org chart, a shift pattern and an approval rule, and the demo walks the six steps with them.

Walk the six steps with your own day.

Bring an org chart, a shift pattern and an approval rule. The demo follows them from the plan to the proof.

Your structure, modelled live
Your roster against a real day
A straight answer on fit

Book a demo See pricing

From the plan to the proof, one working day at a time

One day, six steps.

Say who works for you, and how the day should run

The plan goes out to every phone

The day happens where the work is

The plan meets the proof on one record

Exceptions become decisions, with a reason

The record goes to work

Who does what, at each step.

Everything the six steps run on.

Common questions

Walk the six steps with your own day.