Logging from anywhere
Office, branch or home office, from the phone's browser, with absences and overtime on the same screen.
orbit labor
/
Labor compliance · Working time
/
In implementation
It's not a time clock. It's your working-time evidence.
Mexico's labor reform cuts the work week from 48 to 40 hours between 2027 and 2030 and makes electronic time records mandatory. orbit labor logs start, breaks and end of day from the employee's phone, with no app to install, calculates regular and overtime hours against each year's limits and keeps a file that cannot be altered.
orbit labor
working hours · compliance
01 · Context
Overtime gets paid, but it can't be proven.
At many companies, working time lives in a biometric clock, a spreadsheet or a manager's word. When a labor inspection or a lawsuit arrives, there is no record the employee confirmed and no way to show nobody changed it. Overtime is approved in payroll without checking it against the hours actually worked. With limits changing every year until 2030, reviewing by hand who is close to the cap stops being workable.
02 · What it is
orbit labor in one sentence
A multi-company platform where each employee logs and confirms their working day from their phone's browser, a rules engine calculates regular and overtime hours against each year's legal rule, and the company gets alerts, reconciliation against payroll and a sealed evidence file that no user can overwrite or delete.
03 · How it works
Four steps. No magic.
From the tap on the phone to the file handed over in an inspection.
01
Logging
The employee signs in with employee number, password and an authenticator app, then taps start, lunch break, resume and end. The time always comes from the server.
02
Calculation
The engine splits regular and overtime hours by day and week against that year's legal rule and the assigned schedule, and warns before a limit is crossed.
03
Confirmation
When the week closes, the employee reviews it and confirms it or leaves a note. Every correction is stored next to the original, never over it.
04
Evidence
The admin generates a case file by period, site or employee, with a reference number and a SHA-256 hash, as a printable PDF and as Excel or CSV.
How it works · orbit labor live
What it does not promise
orbit labor is the working-time control record; it does not run payroll or approve payments. Its alerts are not a legal ruling and its case file is not an official labor ministry form. Overtime limits for 2027 to 2029 are being checked with legal counsel against the decree text before go-live. Connectors for HR systems, payroll and biometric clocks exist, but their layouts are validated with each client.
04 · What it does
Where it goes to work.
What it solves for everyone who touches working time.
HR command center
Unclosed days, unresumed breaks, unconfirmed weeks and shifts over 12 hours across the whole workforce, in real time.
Payroll reconciliation
Paid overtime is uploaded and the platform returns what was paid without a record and what was recorded without pay.
Inspection or lawsuit
A file with clock-ins, corrections, confirmations, usage-notice acceptances and an audit-log extract, verifiable by its hash.
Unusual patterns
Recurring long shifts, clock-ins repeated to the minute and frequent corrections, flagged for review with a note.
Groups with several legal entities
One account with several companies isolated from each other and a consolidated dashboard for the group admin.
05 · Benefits
What changes when you have it.
What changes when working time stops depending on someone's memory.
Request demo1
Evidence that holds up
No record is overwritten or deleted, and the audit log is hash-chained.
2
Employees confirm their own week
The sealed weekly confirmation is the core of the file, not a manager's word.
3
Minimal personal data
In pseudonymous mode it runs on employee number alone: no name, email or phone.
4
The legal rule is updated once
rocket code maintains each year's base rule; each company can tighten it, never relax it below the law.
5
Works without the client's IT
Workforce data goes in and out by file; the API and connectors are optional.
06 · Before and after
What changes, side by side.
The same working day, before and after orbit labor.
Before / Without orbit labor
Today's day-to-day
- ✕ Working time lives in a clock, a spreadsheet or someone's memory
- ✕ A correction wipes out the original entry
- ✕ Nobody knows who is near the cap until they cross it
- ✕ Paid overtime is never checked against hours worked
- ✕ Evidence for an inspection is assembled by hand
After / With orbit labor
With working time logged and confirmed
- ✓ Every clock-in comes from the phone with the server's time
- ✓ The correction is stored next to the original
- ✓ Alerts arrive before the daily or weekly limit
- ✓ Reconciliation shows paid-not-recorded and recorded-not-paid
- ✓ The case file comes out of a wizard with reference number and hash
07 · Industries
Where it applies today.
Every company with staff in Mexico is covered; the product adapts through configuration, not custom development.
01 / Corporates
Several legal entities and thousands of employees
A bank is validating the most restrictive setup today: pseudonymous, no line managers, overtime approved in its HR system and reconciled here.
02 / Mid-size companies
50 to 1,000 employees with no HR IT team
Guided onboarding, managers with a team dashboard and approvals inside the platform.
08 · Contact
Let's see it with your operation.
In 30 minutes we'll tell you whether orbit labor fits your process, what it integrates with and what it doesn't, and what a pilot looks like. If it doesn't fit, we'll tell you that too.
Run the discovery with rocky