Workforce Truth Infrastructure
From approved signals
to reviewable workforce records
ZoikoTime turns documented time, attendance, approval, policy, jurisdiction, and approved integration signals into deterministic, evidence-backed records that people can review, correct, approve, and deliver to supported payroll, billing, reporting, and audit workflows.
Workforce record · WR-84213 · lifecycle
Record ID
WR-84213
Worker
A. Okafor
Organization
Northwind Ops
Date
Aug 5, 2026
Policy Version
Meal / Rest v4
Evidence Events
9
Clock event · 09:00 · UTC
ValidatedAttendance state · Present
ReceivedApproved integration event
LateBinding Anti-Surveillance Invariant
No screenshots, keystroke content, URL history, application-name monitoring, or clipboard collection under any tier or configuration.Visit Trust Center
In One Answer
How ZoikoTime works
ZoikoTime begins with documented time, attendance, approval, policy, jurisdiction, and approved integration signals. It applies deterministic, reviewable rules; presents neutral states for worker and authorized human review; records approvals, corrections, and evidence; and delivers governed record versions to approved payroll, billing, reporting, or audit workflows. Human authority and shared responsibility remain controlling throughout.
ZoikoTime does not guarantee payroll accuracy, legal compliance, legal admissibility, or correct outcomes in every configuration or jurisdiction.
The Lifecycle
One map: Capture → Classify → Review Approve → Export & Defend
A persistent record & evidence spine and a shared-responsibility spine run beneath every stage — sources, records, people, policy, evidence, outputs, and responsibility stay connected.
Capture
Documented time, attendance, approval, policy, jurisdiction & approved integration signals.
Classify
Deterministic, policy-bound, jurisdiction-aware, reviewable rules.
Review
Neutral states, worker visibility, correction, authorized human review.
Approve
Authorized approval, correction, rejection or escalation — with reason & history.
Export & Defend
Governed version delivered to approved workflows, with status & evidence.
Stage 1
Capture documented workforce signals—not worker activity surveillance.
Approved signal categories
Source intake & record provenance
Synthetic data| Signal | Source | Time · Zone | State |
|---|---|---|---|
| Clock event | Web app | 09:00 UTC | Validated |
| Attendance | Schedule ref | 09:00 UTC | Received |
| Approval action | Reviewer | 17:40 UTC | Received |
| Integration event | HRIS | 18:02 UTC | Late |
| Missing exit | — | — | Incomplete |
Provenance kept per signal: source, actor/service identity, organization, worker, timestamp, time zone, validation, version.
What Capture uses — and what it never collects:
Signals used
Never collected
Stage 2
A deterministic function bound to approved policy and jurisdiction context—with reviewable inputs, rule path, result, limits, and effective version.
Neutral Classification States
Rule trace · policy & jurisdiction
Synthetic data| Element | Value |
|---|---|
| Policy | Meal/Rest • v4 • effective Jan 1 |
| Jurisdiction | US-East • schedule-aware |
| Matched rule | Regular hours • break satisfied |
| Result | Classified |
| Conflicting policy | Jurisdiction review |
Deterministic — not AI. Classification never determines pay, discipline, or misconduct.
Deterministic classification is not AI. Any separately approved AI or anomaly function remains assistive, explainable, and non-decisional—and classification never determines payroll, discipline, misconduct, or termination.
Stage 3
Two synchronized views — the worker record detail and the reviewer case workspace. Workers see what was captured, the explanation, the current state, and a correction route.
What a worker can see & do
Worker record & reviewer case
| Record | State | Owner | Action |
|---|---|---|---|
| Aug 5 · regular | Approved | — | — |
| Aug 4 · missing exit | Requires review | Worker | Correct |
| Aug 3 · conflict | Insufficient context | Reviewer | Request info |
Neutral states only — never labeled a violation before authorized human review. Workers see the record, its explanation, and a correction route.
Stage 4
Every material decision carries actor, role, authority, reason, timestamp, effective period, before/after values, evidence, downstream instruction, and an audit reference.
Permitted decisions
Approval inbox & action review
| Field | Value |
|---|---|
| Actor · role | J. Rivera · Reviewer |
| Decision | Approve w/ modification |
| Reason | Verified schedule; corrected exit |
| Before → After | —:— → 17:20 |
| Downstream | Authorizes payroll input ·not execution |
| Audit reference | EV-2291 |
Separation of duties: request, review, approval, configuration, export, and execution may require different roles.
Approval is not execution. Approval changes record state or authorizes a downstream action — it does not guarantee payroll, billing, legal, or compliance correctness.
Stage 5
An approved record version is delivered to permitted payroll, billing, reporting, audit, or approved data destinations — and remains explainable, traceable, and reconcilable.
Supported workflow categories
Delivery, acknowledgment & manifest
| Destination | Version | Sent | Status |
|---|---|---|---|
| Payroll input | v3 | 18:30 | Acknowledged |
| Billing input | v3 | 18:31 | Accepted |
| Reporting | v3 | 18:31 | Reconciled |
| Audit export | v3 | — | Permission required |
Delivery, acceptance, and reconciliation are distinct states. Defend = trace source, policy, decisions, corrections, versions, delivery & limits. No universal legal-admissibility claim.
Evidence Ledger
One traceable history across the lifecycle
Every material transition becomes an event with actor, reason, time, object/version, and evidence context — chronology and version links are never silently overwritten.
Signal received
Clock event · Web app
09:00 · WR-84213
Classification
Regular · Meal/Rest v4 · deterministic
09:00 · rule EV-1180
Review opened
Aug 4 missing exit · neutral state
10:12 · A. Okafor
Correction submitted
Worker provided schedule context
10:20 · reason logged
Decision · approval
Approve w/ modification · before→after
11:05 · J. Rivera
Version generated
Package v3 · evidence manifest
11:06 · owner Finance
Delivered · acknowledged
Payroll input · reconciled
18:30 · integration ack
Evidence may support review, reconciliation, and audit. ZoikoTime does not claim universal legal admissibility or guarantee an external decision. Explore Evidence Ledger →
Shared Responsibility
Who configures, submits, reviews, approves,
delivers, and reconciles
Responsibility is explicit across every role — and customer, professional, and downstream-system responsibilities are non-transferable.
Organization / customer
Define lawful and appropriate policy, jurisdiction scope, roles, permissions, data sources, approval authority, integrations, retention, support, and downstream use.
Worker
Provide or review permitted information, submit corrections, follow applicable process, and use support/escalation routes.
Manager / reviewer
Review context within authority, request information, decide permitted items, provide reasons, and escalate conflicts.
ZoikoTime
Apply configured deterministic logic, preserve configured records/evidence, enforce approved access and workflow behavior, expose states, and provide documented product/support boundaries.
Connected system / provider
Authenticate, receive/send approved data, return acknowledgments/errors, preserve processing integrity, and support reconciliation per contract.
Non-transferable boundary. ZoikoTime does not replace customer employment decisions, payroll validation, legal advice, tax analysis, compliance review, or downstream system responsibility.
By Role
The same lifecycle, seen from each seat
Selection personalizes emphasis only — it never creates an account or infers identity.
What you can see
Your record date, source summary, captured time, the policy/classification explanation, current state, and the evidence visible to you.
What you can do
Request a correction, track a neutral pending state, see the human decision, view your updated history, and reach support or escalation.
When something is missing, conflicting, stale,
or fails delivery
Not every unusual record is a problem. Exceptions route into governed correction and reconciliation — never silent drops or automatic judgments.
Missing or late data
Incomplete, duplicate, conflicting, late, or future-dated signals are quarantined for review with a clear recovery path.
Conflicting or stale policy
Conflicting rules or unavailable/superseded policy raise a neutral state and route to jurisdiction or policy review.
Authority conflict
Conflicting authority blocks completion and routes to escalation — high-impact decisions require confirmation and reason.
Failed delivery
Rejected packages, schema mismatch, duplicates, or downstream conflicts enter governed reconciliation flows.
Corrected & superseded
Corrections create reviewable versions; superseded records stay linked in the ledger, never overwritten.
Human-controlled resolution
Every exception resolves with an authorized human, a reason, and a preserved evidence trail.
Connected Work
Apps and connected work
Desktop & Mobile Apps
Supported worker and administrator experiences for the same governed lifecycle.
Zoiko Sema
An approved integration surface — Zoiko Sema remains an independent product with its own permissions.
Kairos Assistant
Kairos retrieves, summarizes, and explains governed organization data. It decides nothing.
Integrations
Approved payroll, billing, reporting, identity, and data destinations with governed delivery.
Get Ready
Implementation and adoption
A controlled first lifecycle — readiness, configuration, validation, launch, and support, with the right owners at each stage.
Readiness
Scope, roles, policies, jurisdictions, systems, and success measures.
Configure
Policy versions, permissions, review routes, integrations, and evidence.
Validate
Pilot a real lifecycle end to end and reconcile before launch.
Launch & support
Sequence rollout, train roles, and monitor exports and evidence.
Questions
How ZoikoTime works — answered
Choose Your Path
See the full workforce record lifecycle in
your own context
Start a self-serve evaluation, review integration and governance needs with the enterprise team, or head to the Product Overview.
30-day trial for eligible plans · Existing customers can reach apps, approvals, reporting, help, and status without starting a lead form.
No screenshots, keystroke content, URL history, application-name monitoring, or clipboard collection under any tier or configuration.