Verified records of who worked,
where, and when.
Records strong enough to take into a payroll audit, a certified payroll filing, or a wage dispute. Neltli is verification infrastructure for the physical workforce. We are entering through construction, where the law already compels the records.
The records are mandatory. The punches behind them are not.
- On federally funded construction, about $217 billion of work a year by the Labor Department's own count, contractors submit certified payroll every week on form WH-347 with a signed statement of compliance, and False Claims Act exposure behind a false one.
- Clean energy projects claim the Inflation Reduction Act's 5x tax credit only if their prevailing wage and apprenticeship records hold up, with the apprentice ratio measured for each day worked. Underpaying prevailing wage costs $5,000 per worker on top of back pay.
- New York City's Local Law 196 requires a daily log of every worker on site and their training status.
Nearly all of those records trace back to self-reported time: a punch anyone could have made, hours reconstructed at the end of the week, a name typed into a spreadsheet. When a record is challenged, in an audit, a wage claim, or an injury dispute, "we wrote it down" is the whole defense.
In 2025, FLSA collective settlements totaled $418 million, averaging $1.2 million per case.
Built today: compliance records from verified presence.
Neltli generates the records the law names, from punches verified at the moment they happen. These artifacts exist now, covered by roughly 1,300 automated tests. They support your filings. They do not file for you, and no software can guarantee compliance.
Certified payroll support (WH-347-ready)
Weekly per-worker, per-day verified hours with admin-assigned classifications, shaped to support your WH-347 filing.
IRA prevailing wage record pack
Per-worker, per-day, per-classification hours with apprentice flags: the record shape 26 CFR 1.45-12 expects contractors to retain.
Daily site log
Everyone present on a site each day, first and last device-verified sighting, and credential status against the site's requirements. Shaped for Local Law 196-style daily logs.
What honest records mean here
- Device-verified hours and admin-entered corrections never blend. Originals are immutable; corrections are separate, labeled entries.
- Auto-closed and unresolved punches add zero to verified totals and are flagged for review, never silently counted.
- Unassigned classifications export as empty cells. The system never invents data.
- Offline punches carry both the tap time and the server receipt time, and are permanently flagged as offline.
A biometric time clock that never sees biometrics
How a punch becomes a record.
- Identity, proven on the device. The phone verifies the worker's fingerprint or face locally, or a device passcode if they choose. That check unlocks a hardware-bound key, which signs a single-use challenge from our server. Raw biometrics never leave the phone. Neltli never sees or stores a face or a fingerprint.
- Place, decided by the server. The server determines inside or outside the geofence from raw sensor readings. A phone can never simply assert "I am here."
- Time, recorded both ways. Offline punches queue durably on the device, are re-verified when they sync, and record both when the worker tapped and when the server received it.
- A tamper-evident trail. Every event lands in a hash-chained audit log, so a record altered after the fact becomes detectable.
Verification that respects the worker.
Neltli verifies punch moments. It is not a tracking app. Location is checked when a worker clocks in or out, never continuously, under a plain-language consent the worker can read in full, narrow, and revoke. Workers keep a free credential wallet and a portable verified profile that stays theirs when the job ends.
What we do not claim.
GPS and location signals can be spoofed by a determined actor, and no vendor honestly solves that today. So we lead with what cannot be faked: the on-device biometric check and the hardware-bound key. Where a record has limits, the record says so.
The same pattern repeats.
A verified workforce record matters wherever a law or a counterparty compels proof of who was there. On our roadmap: industrial site access and contractor gates, with the same buyers and mandates as construction. Healthcare, where every US nursing facility submits quarterly staffing data that must trace to auditable records, and states are adding credential-verification laws for nurse staffing agencies. Staffing, where agencies vouch for workers they have never met.
We start in construction because the mandates there are weekly, the penalties are federal, and it is the industry our founder comes from.
From the founder.
I have spent almost six years as a field engineer on industrial construction sites: badging crews in, chasing certified payroll, watching disputes come down to whichever spreadsheet someone kept. The record layer that is supposed to protect both workers and contractors is self-reported all the way down.
Neltli is the layer I kept wishing existed: verification at the moment of presence, records that hold up later, and credentials workers keep when they move on. If you run crews on covered work and want to shape this with us, I want to hear from you.
Early access.
We are recruiting a small group of design partners: contractors on Davis-Bacon or IRA-covered work who want verified records ahead of their next filing or audit. Working in another industry with a verification mandate? Start the conversation.
This page sets no cookies and runs no trackers. Just email.