By workforce type
One platform, every kind of employee
Most organizations do not have one workforce. They have four or five, working under different rules, in the same company.
- One record,however many groups you run.
- Rules that differ,by group, not by product.
- No second system,for the group the first one could not serve.
What each group gets
The exceptions become a spreadsheet, then a second product, then a monthly reconciliation. Here is how each group avoids that.
Office and hybrid
- Today
- Marking from the app, leave, expenses, corrections and comp off, with or without location.
- In build
- Biometric, RFID and kiosk capture, and policies that set different rules for home days.
Shift teams
- Today
- Shift master, monthly plan and a personal schedule, compared against real attendance.
- In build
- Rotations, split and overnight shifts, swaps, bulk assignment and overtime rules.
Field and mobile
- Today
- Geofenced attendance, live location, route history, visit marking and a visit board.
- In build
- Work orders, dispatch, route planning, proof of service and offline capture.
Multi-location
- Today
- Branches, departments and designations, with access and reporting following the structure.
- In build
- Legal entities, business units, regions, and location-specific schedules.
Contract and agency
- Today
- Held in the same structure as employees, with the same attendance and approval behaviour.
- In build
- Shared device, kiosk and supervisor marking, and low-end device resilience.
Every group
- Today
- One employee record, one audit trail, and one set of reports that agree.
- In build
- Fully independent, policy-driven rules per group rather than by employee type.
Shared
Whatever the rules, every group shares
- One employee record and one organizational structure
- One attendance record, however the mark was captured
- One request and approval trail, and one schedule per person
- One set of reports, so headcount and hours agree across the organization
What configuration makes possible
Today behaviour follows broad employee types. The policy engine that makes each group independently configurable is the largest piece of the current release.
| Group | Attendance method | Location | Approval route |
|---|---|---|---|
| Head office | Biometric or RFID | Not required | Line manager |
| Hybrid staff | Mobile | Workplace days only | Line manager |
| Shift teams | Kiosk or mobile | At the site | Shift supervisor, then HR |
| Field engineers | Mobile and geofence | Required | Regional manager |
| Contractors | Supervisor marking | At the site | Site manager, then finance |
See also people and organization, attendance, what changes by role and your sector.
Common questions
Can two groups follow completely different attendance rules?
Today, rules follow the employee type. Fully independent, policy-driven rules per group are in build.
Do office employees need to share their location?
No. Location applies where the work needs it. Deciding that per group, in policy, is part of the work in build.
Do contractors need their own licences?
Pricing follows the people who use the platform, whatever their contract type. See what changes the number.
Which group should we start with?
Usually the one where the pain is loudest and the rules are simplest. Most organizations start with one branch or one team, then widen.
Describe your groups, and we will map them
Office, hybrid, shift, field, contract. Bring the mix and we will show you what is configuration today.