Policy-bound · reviewable
Close-readiness reporting
See completeness and approval status by site and period before payroll cutoff.
Improve Payroll Accuracy →Shift Integrity Controls
Accurate shift
records, built on
human review
ZoikoTime keeps shift records policy-bound and reviewable — with worker transparency, neutral exception states, and traceable evidence at every step. Workforce Truth Infrastructure, not employee monitoring.
- No screenshots or keystrokes
- No GPS tracking
- Human review, always
Policy-bound · reviewableShift Integrity Control Center
- 1,204
- Records verified
- 22
- Needs review
- 98.4%
- Policy health
Selected recordLate Clock-In — Pending Review
Policy, Record & Responsibility Overview
Three things every shift record depends on
Policy
Effective-dated rules define what a valid shift looks like — grace windows, rounding, and required context — versioned and owned by your organization.
Record
Every shift event, evaluation, flag, correction, and approval is preserved with actor, timestamp, and rationale.
Responsibility
Workers add context. Reviewers decide. ZoikoTime evaluates against policy — it never makes the consequential call.
Operating Model
Configure → Evaluate → Record → Review → Resolve → Preserve
Configure
Policy owner sets rules, thresholds, and effective dates
Evaluate
Deterministic rules assess captured events against policy
Record
Shift event and evaluation preserved with source and time
Review
Worker adds context; reviewer assesses and decides
Resolve
Decision, rationale, and any correction are logged
Preserve
Full version history retained per approved retention policy
Neutral State Model
Every state describes the record — never the worker
| State | Meaning | Owner |
|---|---|---|
| Captured | Shift event received; evaluation pending | System |
| Verified | Evaluated against policy with no unresolved conflict | System |
| Needs Context | A required detail is missing or conflicting | Worker |
| Pending Review | Context provided; awaiting reviewer decision | Reviewer |
| Corrected | Authorized change recorded with full history | Reviewer |
| Approved | Required controls complete; ready for downstream use | Approver |
Canonical example: “Late Clock-In — Pending Review.” Never “no-show,” “tardy,” or any label implying fault before review.
Source & Policy Context
Where a shift event comes from — and what governs it
| Source | Captures | Policy dependency |
|---|---|---|
| Mobile app | Clock-in/out, break events, source timestamp | Grace window, geofence rules where configured |
| Desktop / web | Clock-in/out and approved manual entries | Approval requirements for manual entry |
| Kiosk / terminal | Shared-device clock events with identity check | Identity verification method configured per site |
| Scheduling integration | Expected shift start/end for comparison | Schedule source and sync freshness |
Worker Experience
My Shifts — clear, and yours to review
Every shift, explained in plain language
Workers see their own shift record, its current state, and exactly what’s needed to resolve it — without digging through a manager’s tool.
- See today's shift, breaks, and current state at a glance
- Add context or request a correction directly from the record
- Follow review history — who decided, and why
Reviewer Experience
A focused queue, not a flood of alerts
Review Queue
Site: Northwind Ops
| Record | Issue | Status | Next action |
|---|---|---|---|
Worker #2291 Shift Aug 4 | Late clock-in, 6 min | Needs Context | Awaiting worker input |
Worker #2304 Shift Aug 4 | Missed break event | Pending Review | Context received · decide |
Worker #2318 Shift Aug 3 | Clock-out mismatch | Approved | Ready for export |
Shift Integrity Control Center
The full picture, in one dashboard
Production-faithful, shown here with synthetic data.
Control Center · Full view
Aug 5, 2026 · Rolling 7 days
- 1,204
- Records verified
- 22
- Needs review
- 98.4%
- Policy health
- 99.1%
- Source freshness
↑ 3.1% week over week
6 due today
No unresolved conflicts
All sources syncing
| Exception | Site | Correction | Status |
|---|---|---|---|
| Late Clock-In | Northwind Ops | Worker submitted | Pending Review |
| Missed Break | Meridian+ | Not yet submitted | Needs Context |
| Duplicate Clock-Out | Astera Retail | Reviewer corrected | Approved |
Audit timeline
- Policy v4.2 publishedAug 3
- Grace window updated · Site BJul 29
- Kiosk source reconnectedJul 27
Activity feed
- Reviewer approved #23182 min ago
- Worker context added #229118 min ago
- Schedule sync completed1 hr ago
Schedule & Boundary Alignment
Compare captured time against expected shift boundaries
Expected vs. captured
When a schedule source is connected, ZoikoTime compares captured events against the expected start, end, and break windows — surfacing conflicts, not assuming intent.
Grace & rounding
Configured grace windows and rounding rules apply consistently, versioned and auditable, so the same policy produces the same outcome every time.
No schedule, no assumption
Where no approved schedule exists, ZoikoTime evaluates against configured shift-length policy only — it never infers an expected shift on its own.
Timezone & DST aware
Boundary comparisons account for worker/location timezone and daylight-saving transitions, so effective time is never ambiguous.
Recorded Shift Record Anatomy
What’s inside every record
| Field | Description |
|---|---|
| Captured events | Clock-in/out, break, and time source, each with its own timestamp |
| Policy applied | Rule set, version, and effective date used for the evaluation |
| Evaluation outcome | Deterministic state and the specific conditions that produced it |
| Worker context | Comments, attached context, and correction requests |
| Reviewer decision | Actor, decision, rationale, and timestamp |
| Version history | Before/after values for every authorized change |
Correction Request Workflow
From flagged record to resolved outcome
- 1
Record flagged
A neutral exception state appears with the exact issue and who owns the next action.
- 2
Worker adds context
The worker explains what happened or requests a correction, visible to the assigned reviewer.
- 3
Reviewer assesses
An authorized reviewer accepts, corrects, requests more context, or escalates — never automated.
- 4
Decision recorded
Rationale, actor, and timestamp are preserved alongside the before/after values.
- 5
Worker notified
The outcome and updated status are visible on the worker's own record immediately.
Exception Resolution
Common exceptions, resolved consistently
Late clock-in
Compared against the configured grace window, then held for worker context — not counted against anyone automatically.
Missed break event
Surfaced as incomplete, not judged — worker and reviewer resolve together with the applicable policy in view.
Duplicate or conflicting event
System-level detection with reviewer confirmation for anything ambiguous — never silently discarded.
Reviewed by people, not left to a black box
Every exception on this dashboard was resolved by a named reviewer — never an automated decision.
Reporting & Enterprise Trust
Evidence your team can stand behind
Policy governance
Version history and change timelines keep every policy update accountable and traceable.
Visit Trust Center →
Audit-ready evidence
Every decision, correction, and approval carries an actor, timestamp, and rationale.
Create Auditable Time Records →Implementation Journey
A measured path to go-live
- 1
Discovery
Confirm populations, sources, existing policies, and success measures.
- 2
Policy mapping
Translate grace windows, rounding, and escalation rules into versioned configuration.
- 3
Pilot
A representative site runs real shifts with full review and correction workflows active.
- 4
Rollout & operate
Training, worker communications, go-live, and ongoing policy governance.