WMS360
Know who worked, where, and for how long.
Your people aren't in one building. WMS360 turns every shift into a record you can actually prove — face verified, inside a geofence, timestamped, and signed off through an approval trail nobody can quietly edit.
A register nobody trusts is worse than no register.
When work happens across dozens of sites, the attendance record becomes a negotiation. Every one of these costs real money, every month.
Buddy punching
One person marks four. Nothing in a paper register or a shared terminal can tell you otherwise.
Unprovable site presence
A supervisor says the crew was there. The client says they weren't. Nobody has evidence either way.
Timesheets that arrive late
Payroll waits on WhatsApp photos and spreadsheets, then re-keys them under deadline.
Overtime nobody approved
Extra hours appear at month end with no record of who authorised them, or whether they happened.
From a phone in the field to a locked payroll period.
Four steps. The first three take your employee about six seconds; the fourth is where your administrators get their month back.
Employee opens the app
On their own phone. No terminal to queue at, no hardware to install at a site you might leave next quarter.
Face and location verified
The face is matched against their approved profile, and the coordinates are checked against the geofences assigned to them.
Punch recorded with evidence
Time, place, verification verdict and photographic evidence are written together — as one record, not four systems.
Exceptions approved, period locked
Corrections, on-duty and overtime clear their approval queues. Then the month is locked and the numbers stop moving.
The punch is the proof.
A WMS360 punch isn't a row with a timestamp. It carries the verification verdict, the coordinates, the geofence it was measured against, and the image captured at that moment. Months later, when a client disputes a day, you open the record instead of opening an argument.
- Face verified against an administrator-approved profile
- Inside or outside the fences assigned to that employee
- Evidence attached and retrievable for dispute resolution
- Attributed — including who marked it, when a supervisor punches for a crew member
Hold steady — verifying
Everything the month actually requires.
Attendance is the entry point. What makes it survive contact with a real workforce is everything around it — the exceptions, the approvals, the policy, and the audit trail.
- WMS
- Workforce Management System
- 360
- Every side of the working day, not one slice of it The name is a scope, not a suffix. What follows is the whole of it.
Attendance capture
Face-verified, GPS-stamped punches with evidence. Supervisor proxy punch, manual entry, day close, and monthly period locking.
Face biometrics
Enrollment with multiple samples, an administrator approval queue, verification at punch time, and permanent erasure on request.
Geofencing
Fences per site, zone or project. Assign them to employees, validate every punch against them, and test a boundary before you roll it out.
Leave management
Configurable types and policies, balances with audited adjustments, self-service applications, and an approval chain that routes itself.
Exception workflows
Attendance corrections, on-duty requests and overtime claims — each with a raise, approve and reject path, and a "pending with me" inbox.
Shifts & structure
Shift master and assignment, plus the organization hierarchy — zones, offices, departments, designations — and an org chart over it.
Employees & documents
Employee master with bulk import for onboarding at scale, profile management, and permission-gated document attachments.
Roles & permissions
Around 65 discrete permissions, custom roles, and data scoping so a supervisor sees their zone and nothing beyond it.
Notifications
Push to the mobile app with device registration handled for you, organization-wide announcements, and SMS for OTP and critical alerts.
Reports & analytics
Operational dashboards, multi-site rollups, trend and insight views, and standard reports ready for payroll hand-off.
Audit & compliance
An immutable log of privileged actions, three-tier soft delete so records retire rather than vanish, and non-enumerable public identifiers.
See all capabilities
The complete inventory, module by module, with what each one does and who it is for.
One system, met three different ways.
Your crew, your administrators, and your other software each need something different from the same record.
Mobile app
For employees and field supervisors. Punch in and out, apply for leave, view payslips, shift and profile. One codebase, Android and iOS — so a release reaches your whole workforce at once.
Admin dashboard
For HR, operations and administrators. Live monitoring on a map, the approval queues, master data, org structure, analytics and the audit log.
REST API
For everything else you run. Every capability in the product is reachable by your payroll, ERP or BI systems — documented with OpenAPI, not reverse-engineered.
Engineered for the size you'll be, not the pilot you're starting.
Attendance is a time-series problem that grows every single day. WMS360 is built on a modern, actively supported .NET and PostgreSQL stack, with partitioned storage sized for years of history.
If your workforce is spread out, this is the same problem.
The industry changes the vocabulary — sites, wards, routes, wings, branches — but the question is identical: was the right person at the right place for the right hours, and can you show it?
Biometric data raises the bar. We designed for that first.
A face template is not a password — it can't be reissued. WMS360 treats it accordingly: encrypted at rest, never written to a log, never returned raw over the API, and permanently erasable on request through a permission held by almost nobody.
Read the security overview- Encrypted at rest — face data is never logged and never leaves the API in raw form
- Right to erasure — a dedicated permission wipes a profile, including at the recognition provider
- Argon2id password hashing; refresh tokens and one-time passwords stored only as hashes
- Non-enumerable identifiers — nobody walks your employee list by counting upward
- Immutable audit trail over every privileged action
See it against your own sites.
A working demo with your geofences, your shift patterns and your approval chain — so you're evaluating WMS360 on your operation, not a sample dataset.