Features — WMS360

01 — Attendance capture

Proof, not paperwork.

Every punch answers three questions at once — who, where, and when — and keeps the evidence that backs the answer.

Face-verified punch in and out from the employee's own phone. No biometric hardware to buy, install and maintain at every site.
GPS-stamped punches, with the location captured at the moment of the punch rather than inferred afterwards.
Photographic evidence attached to every punch and retrievable later, so a disputed day is settled by a record instead of a recollection.
Supervisor proxy punch — a supervisor can mark attendance for a crew member whose phone is dead or missing. The action is attributed to the supervisor and logged as theirs.
Manual attendance entry for administrators, permission-gated and audited.
Self-mark for approved scenarios, such as office staff and exception days.
Live "today" board for the whole organization, and a self-service history for each employee.
Team view so a supervisor sees their entire reporting line in one screen.
Day close — a controlled end-of-day process that finalises the day rather than leaving it open indefinitely.
Monthly period lock and reopen — freeze a payroll period so the numbers stop moving. Reopening requires its own permission and leaves a trace.

Why period locking matters

Most attendance disputes aren't about what happened — they're about a number that changed after payroll was calculated. A locked period makes "the figure moved" a deliberate, permissioned, logged act instead of an untraceable edit. Finance stops reconciling against a moving target.

Related: exception workflows — the sanctioned way for a number to change before the lock.

02 — Face biometrics

From enrollment to erasure.

A face template can't be reissued like a password, so every stage of its life is deliberate — including the end of it.

Enrollment with multiple samples per employee, so verification isn't hostage to one bad photograph.
An approval queue. A new face profile is not trusted until an administrator reviews it. Profiles can be rejected with a reason and re-submitted.
Verification at punch time, returning a clear match verdict rather than a raw score for someone to reinterpret.
A pluggable recognition provider, selected by configuration. You are not locked to one vendor's pricing or one vendor's roadmap.
Right to erasure — a dedicated permission permanently erases an employee's profile, including cleaning up identities orphaned at the recognition provider.
Encrypted at rest, never logged, never returned raw over the API.

The approval queue is the point

Self-service enrollment without review is how the wrong face ends up attached to the right employee ID. Making approval an explicit, permissioned step is a small amount of administrative work that removes an entire category of fraud.

See Security & privacy for how biometric data is stored and erased.

03 — Geofencing

Presence you can draw on a map.

Define where work counts, assign it to the people it applies to, and check every punch against it automatically.

Define fences per site, zone, ward, office or project — whatever your operation actually calls its boundaries.
Assign fences to employees, individually or by group. One employee can be valid at several fences, which is how real routes and rotations work.
Validate at capture time — inside or outside is determined when the punch happens, not reconstructed later.
Test a fence against a coordinate before you roll it out, so you find a bad boundary at a desk rather than at 6am with a crew standing outside it.
Live map view of the workforce in the admin dashboard.

A fence per site, assigned per employee. Punches outside an assigned boundary are flagged at capture, not discovered at month end.

04 — Leave management

Policy that holds up at month end.

Different groups get different rules, balances stay defensible, and an application finds its approver without being chased.

Configurable leave types — casual, sick, earned, comp-off, unpaid, and whatever else your policy names.
Leave policies you can create, update and retire, with different policies for different employee groups.
Balances with audited adjustments. A manual correction is permission-gated and leaves a record of who made it.
Self-service application from the mobile app, so a request doesn't start life as a text message.
Approval and rejection workflow routed to the right approver, with a "pending with me" queue on their side.
Holiday calendar as master data, respected by both attendance and leave calculations.

Balances are the trust surface

Employees rarely argue about the leave policy. They argue about their balance. Making every adjustment permissioned and attributable turns a recurring dispute into a two-minute lookup.

05 — Exception workflows

Everything that goes wrong has a path.

Real operations run on exceptions. If the system has no route for them, they route around the system — into spreadsheets nobody audits.

Attendance corrections — the employee raises it, an approver accepts or rejects it, and the change is attributable.
On-duty requests for legitimate work away from an assigned fence: raise, approve, reject.
Overtime claimed, approved or rejected per employee per date — so extra hours are authorised before they reach payroll, not explained afterwards.
"Pending with me" inboxes across corrections, on-duty, overtime and leave.
A pending-approvals count on the dashboard, so a queue can't quietly grow for three weeks.

The four queues

Correctionwrong punch timeApprove / reject

On dutyworked off-siteApprove / reject

Overtimeextra hoursApprove / reject

Leaveplanned absenceApprove / reject

Each one has a raise path, an approver, a rejection reason and an audit entry.

06 — Shifts & structure

The shape of your organization, encoded.

Shifts define when work counts. The hierarchy defines who sees it.

Shift master — define shifts and their timing rules, then assign them to employees.
Organization hierarchy — zones, wards, offices, departments and designations.
Org chart view of the reporting structure, so approval routing is something you can see rather than infer.
Employee assignments — place a person in the structure, and move them when they move.

Structure drives scope

The hierarchy isn't decoration. It's what data scoping attaches to — a supervisor assigned to a zone sees that zone's people and no one else's. Get the structure right and access control mostly configures itself.

See roles & permissions.

07 — Employees & documents

Onboard three thousand people without typing three thousand times.

The employee master is the spine everything else hangs from, so it has to be quick to populate and safe to change.

Employee master — create, update, view and deactivate.
Bulk import for onboarding at scale, which is what the first week of a rollout actually consists of.
Profile management, with self-service updates where your policy permits them.
Document attachments — upload, view and delete, permission-gated and backed by object storage.

Deactivate, don't delete

An employee who left last year still appears in last year's attendance records, and should. WMS360 retires records rather than destroying them, so historical reports stay truthful.

08 — Roles & permissions

Around 65 permissions, not four fixed roles.

Real organizations don't divide neatly into admin, manager, employee. WMS360 composes access instead of assuming it.

Fine-grained permissions in the shape Area.Entity.Verb — approving an attendance correction, configuring a leave policy, and erasing a face profile are three separate rights held by three different sets of people.
Custom roles — create, update and assign them, and grant individual permissions on top.
Data scoping — a supervisor sees their zone, ward or office and nothing beyond it. Scope is assigned explicitly, never implied by job title.
Self-service password change plus administrative password flows.

A few of the permissions

Attendance.Correction.Approve
Attendance.Period.Lock
Attendance.Period.Reopen
Attendance.Proxy.Punch
Face.Profile.Approve
Face.Profile.Erase
Geo.Fence.Configure
Leave.Balance.Adjust
Leave.Policy.Configure
Security.Role.Assign
Security.Scope.Assign
Report.Standard.View

Each one is granted deliberately. Nobody holds a right because it came bundled with a role name.

09 — Notifications

Reach a workforce that isn't reading email.

Deskless staff don't have an inbox open. They have a phone in a pocket.

Push notifications to the mobile app, with device registration handled for you and dead device tokens deactivated automatically instead of accumulating.
Announcements — publish organization-wide or targeted messages that appear in the app.
SMS for one-time passwords and critical alerts, for the moments where a push notification isn't enough.

Quiet reliability

Push delivery fails constantly in the real world — reinstalled apps, replaced handsets, revoked tokens. WMS360 retires dead tokens on its own, so your delivery rate reflects reality rather than a register of phones that stopped existing.

10 — Reports & analytics

Answers at the speed of a question.

If a report takes a day to produce, nobody asks the second question.

Operational dashboard with the headline numbers, plus a bulk view for rolling up many sites at once.
Trend analysis over time and insight views that surface what actually changed, rather than leaving you to diff two spreadsheets.
Standard reports for attendance, leave and overtime, shaped for payroll hand-off.
Charts and maps in the dashboard for the spatial and temporal views that a table can't give you.

On site

2,847

Verified

99.2%

Pending

18

Headline numbers first, with the detail one level down — the common question answered immediately, the rare one still reachable.

11 — Audit & compliance

Who did that, and when.

The questions that matter in an audit are all about privileged actions — and every one of them is recorded.

Immutable audit log over privileged actions: who approved what, who reopened which locked period, who erased which biometric profile, and when each happened.
Three-tier soft delete — records are retired rather than silently destroyed, so history stays intact.
Non-enumerable public identifiers on every externally addressable record, so nobody walks your entire employee list by counting upward from one.

Designed to be boring

A good audit trail is one nobody thinks about until the day they need it, and then it answers the question in a single query. That means recording the privileged action at the moment it happens — not reconstructing intent from a stream of database changes months later.

Everything a real month throws at you.