Build time records
that can explain
themselves.
Keep every original event, classification, correction, approval, export, and downstream acknowledgment connected to one governed record history.
Auditability for accountable administration — not employee surveillance or automatic judgment.
Record TR-88232
Why Time Records Lose Trust
A final approved total doesn't explain source, classification, edits, notices, or downstream use. ZoikoTime is built to answer what changed, why, and by whom.
Multiple capture sources
Which event is original, duplicate, delayed, or authoritative becomes unclear.
Manual correction
What changed, why, by whom, and whether the worker was informed gets lost.
Policy change
Which rule applied at the record date is silently forgotten.
Legacy migration
Whether imported data is complete or reconstructed is rarely labeled.
ZoikoTime positions itself as a governed time-record system — not a legal conclusion, not a surveillance log.
Every Record, Fully Explained
Time Record Ledger
Search, filter, and open records by source, version, policy, approval, export, and downstream state.
Explore the Ledger →Record Detail & Lineage
See how one record's current value links to original source, derivation, changes, and use.
Inspect Lineage →Policy Snapshot
Preserve the exact rule and context applicable at the record date — no silent reclassification.
See Policy Evidence →Correction & Approval History
Append-only changes, rationale, notices, and authority — auditable without becoming punitive.
Review History →Evidence Bundle & Export
Purpose-based, manifest-backed evidence packaging — never just a downloaded spreadsheet.
View Bundle →Worker Record View
Role-appropriate transparency and correction rights for the record subject.
View Worker Experience →See the Record Before You Rely on It
Original, derived, corrected, approved, exported, and reconciled states stay connected — and distinct.
| Record | Age | Source | Policy | Status |
|---|---|---|---|---|
| TR-88233 | 1d | Import batch 41 | v3.1 | Needs review |
| TR-88236 | 2d | Mobile app | v3.2 | Approval pending |
| TR-88240 | 3d | Manual entry | v3.2 | Needs review |
Version 1 — original event received from desktop app
Aug 3, 09:02 · Deterministic classification applied
Version 2 — correction proposed (unlogged lunch break)
Aug 4, 08:40 · Reason attached, worker notified
Version 3 — approved by M. Alders (HR)
Aug 4, 09:12 · Prior version preserved
Export bundle EB-2291 generated for Payroll Aug Period 1
Manifest: 1,204 records · purpose: payroll export
Target acknowledged and reconciled
Append-only audit event
Every panel above reflects the actual review workflow your team uses — no invented dashboards.
Get a demo — see this with your recordsThe Worker Record View
Auditability isn't one-sided. Every worker sees their own permitted history, not just administrators.
Workers can see
Where the record came from and when it was received
The applicable historical policy in plain language
Full version list — changed fields, reason, role, outcome
Who can see the record and why
Workers can do
Request a correction and add permitted evidence
Save a draft, submit, or withdraw where allowed
Receive confirmation and track the response
Export a permitted personal record summary
No page or screen uses employee surveillance, productivity ranking, behavior scoring, or guilt language. Corrections show what changed and why — never who to blame.
Integration, Transformation & Reconciliation
Source connection
Provider, connection ID, scope, last verified sync, and freshness expectation.
Identity & mapping
Subject mapping, workspace, project, pay period, and policy scope with mapping version.
Transformation
Input fields, calculation version, rounding, timezone, and rejected-value handling.
Transmission
Target, object ID, payload version, idempotency key, and response state.
Reconciliation
Expected versus returned record, amount, version, and status.
Provider names, real-time claims, and reconciliation capability are shown only when verified in the integration registry — Get a demo.
Every connection stays inspectable.
Mapping versions, transform versions, and reconciliation rules are first-class evidence — linked to the records they affect, not buried in a technical log only IT can read.
What You Can Measure
Approval cycle time — last 8 pay periods
No dashboard ranks workers by corrections, exceptions, access events, or record volume — every metric defaults to aggregate view.
Cleaner records mean fewer late-night payroll fire drills — measured in aggregate, never by individual.
Proof, Without Overstating It
Customer stories publish once they're signed and approved.
We only feature a name, logo, or quote with written customer approval. Until then, evaluate ZoikoTime on product evidence — the actual ledger, lineage, and audit workflows shown above.
Frequently Asked Questions
Source provenance, policy version, original and corrected values, actor and authority, approvals, notices, exports, and downstream status — all connected to one record history.
The original record history is preserved. Corrections do not silently overwrite prior values; changes are appended with the relevant reason, authority, and resulting state.
No. An audit trail can provide useful evidence of provenance, history, and control, but legal admissibility depends on the applicable jurisdiction, rules of evidence, and surrounding circumstances.
Yes. A correction can create a new version while preserving the previous state, the reason for the change, the actor, and any applicable notification or approval information.
Workers can see the permitted history associated with their own records, including relevant changes, corrections, and outcomes according to their access rights.
An evidence bundle can include the relevant record, source provenance, policy version, lineage, correction and approval history, export manifest, and downstream reconciliation information.
Migrated records retain available source and migration context. Imported or reconstructed information is distinguished so that its origin and completeness are not silently represented as original system events.
No. Auditability is focused on preserving accountable record history. It does not require productivity ranking, behavior scoring, surveillance, or punitive interpretation of employee activity.
Implementation depends on the number of sources, integrations, policies, mappings, and downstream systems involved. The appropriate implementation scope can be established during an evaluation.