Attendance
Timesheets on trust
Hours written by hand and mileage reported by the technician: easy to inflate, impossible to check.
PILLAR III
From verified work to payroll, without the reconciliation week
Clock-ins proven by geofence, mileage measured by GPS, expenses checked by policy, and a payroll period that exports only what was verified.
- Weekly payroll run
- 14 min
- Timesheet disputes
- 0.0%
- Contractor overhead
- -97%
The problem
Self-reported hours cost more than they look
When hours and kilometers are self-reported, every payroll run becomes an investigation.
Payroll
A week of cross-checking
Controllers match chats, receipts, invoices and GPS exports before anyone can be paid.
Vendors
Contractors paid on their word
Invoices approved without proof the job was done, or that it passed quality checks.
How it works
How a shift becomes a payment
Each amount paid can be traced back to a verified record: a geofenced shift, a GPS trip, a photographed receipt or a job that passed QA.
Clock in where the work is
Clock-in and clock-out only count inside an authorized geofence (a client site, warehouse or depot) with an accurate, non-mocked GPS fix. Home clock-in exists only where the employee file allows remote work and the NOM-037 home-office checklist is complete.
not mocked → has a fix → accuracy ≤ 50 m → inside a fence
Shifts reconciled with the roster
Each clock-in is matched to the published roster. Lateness, breaks, legal rest and overtime are computed from the events, not typed in.
roster match window: 120 min
Trips become mileage
The GPS trail between clock-in and clock-out is split into trips at each arrival. Mocked, imprecise and impossible segments are left out and counted separately. Personal-vehicle trips are reimbursed at the policy rate.
excluded: mocked · low confidence · impossible travel
Expenses checked by policy
Receipts are photographed in the app and tied to the ticket and the place they were claimed. The policy engine approves clean claims, sends unusual ones to review and holds duplicates or claims missing evidence.
approved · under review · policy hold
Corrections, never edits
A wrong record is fixed through a correction request that keeps the original, answered by someone other than the person asking.
original + correction, both on the record
Payroll exported from verified data
The payroll period freezes approved hours, mileage and expenses and exports them to your payroll provider, bank or ERP. Contractor payouts follow jobs that passed quality checks.
export: verified records only
Clock-in and clock-out only count inside an authorized geofence (a client site, warehouse or depot) with an accurate, non-mocked GPS fix. Home clock-in exists only where the employee file allows remote work and the NOM-037 home-office checklist is complete.
not mocked → has a fix → accuracy ≤ 50 m → inside a fence
In numbers
Payroll gets shorter every week of the rollout
As more technicians clock in by geofence, fewer hours need checking by hand. By the end, the controller only reviews exceptions.
Hours to prepare the weekly payroll
From 14 hours of cross-checking to a 15-minute review of exceptions.
Show the numbers
| Hours | |
|---|---|
| W1 | 14 h |
| W2 | 13.5 h |
| W3 | 12 h |
| W4 | 9 h |
| W5 | 6.5 h |
| W6 | 4 h |
| W7 | 2.5 h |
| W8 | 1.5 h |
| W9 | 0.8 h |
| W10 | 0.5 h |
| W11 | 0.3 h |
| W12 | 0.25 h |
Rules that always hold
Fair to the company and to the technician
Traceability
Every payment traces to a record
A geofenced shift, a GPS trip, a photographed receipt or a job that passed QA. Estimates are never paid.
Integrity
Unreliable positions don't count
A clock-in is the whole evidence for a day's pay, so a mocked or imprecise fix doesn't count. The technician is told why.
Transparency
Technicians see what the system sees
Their own trail, hours and scorecard. Transparent data protects a technician's record as much as the company's.
Duties
Planning and approving are separate
Whoever builds the roster isn't the one who approves the hours worked against it.
Mexico
Mexican labor rules built in
Legal breaks, vacation entitlement and the digital employee file, following Mexican regulation.
Scope
Works with your accounting system
waydot sends verified payroll and payout data to the payroll provider, bank or ERP you already use. Your books stay where they are.
Configuration
Defaults that match how payroll is audited
- Clock-in radius
- 50 m
- Distance from a fence that counts as inside
- Clock-in accuracy
- ≤ 50 m
- Least precise fix accepted for a clock event
- Roster match window
- 120 min
- How far a clock-in may be from a rostered start
- Mileage source
- GPS trail
- Between clock-in and clock-out, split into trips
- Expense categories
- 6
- Tolls, parking, parts, meals, lodging and other
- Payroll export
- Per period
- Files or API for your payroll provider, bank or ERP
Who uses it
Who works with it every day
Financial controller
Victor
Runs payroll from verified attendance in minutes and approves vendor payouts with the evidence attached.
HR administrator
David
Handles attendance, leave, documents and certifications with no manual time entry.
Field technician
Faisal
Sees each day's trips, hours and expenses, and can flag a trip that looks wrong.
See it on your own operation
A 30-minute briefing with your dispatch, payroll and asset flows on screen.
Keep exploring
Intelligence
Every AI and ML capability
What each model answers, where it appears, and what it will never do on its own.
The visibility gap
What the office can't see
What running on WhatsApp and spreadsheets really costs, and what changes with one record.
Security
What your IT team will ask
Access by role and territory, sign-in, encryption, the audit log and devices in the field.
Changelog
What shipped, release by release
New capabilities and improvements across the console, field app and platform.