Workday already holds the record and the schedule; //AIRGAPT adds a signed evidence layer via API so the same record answers when a claim is filed.
Workday manages HR records, payroll, and workforce data at enterprise scale, including leave, absence, and time-tracking reporting.
Workday timestamps are editable in the same HR system that defines the policy. When a former employee files an overtime or working-time claim, an HR-administrable timestamp is an assertion, not a defence, courts and labour inspectors discount editable records by default.
//AIRGAPT exposes a REST API. For every work-state event relevant to a Workday time record, //AIRGAPT returns a tamper-evident, attributable entry signed by the individual's own FIDO2 key. Workday ingests that entry alongside its existing records; the existing workflow is unchanged.
When a wage, overtime, or working-time claim is filed, the signed entries answer the central question: was the out-of-hours work directed, or was it the employee's voluntary act? Fabricated or estimated hours have nothing to rest against. //AIRGAPT proves when work happened and who initiated it; Workday continues to govern what is owed.
US FLSA places the recordkeeping burden on the employer, and an unexplained gap or contradictorily edited record shifts evidential weight against the employer; for EU staff, the C-55/18 line on objective, reliable time-recording applies.
Honest scope: //AIRGAPT proves when work happened and who initiated it, not the amount owed; that stays with Workday/the customer's HRIS. Windows endpoints today.
"Workday owns the record and the schedule. //AIRGAPT signs each work-state event and returns it to Workday via API, so the same record answers when a regulator or court asks "did this actually happen?""
One REST API. No new hardware. Works alongside Workday without replacing any existing workflow.