Verified Time & Attendance
Verify time and attendance without surveillance
Know which records are complete, what needs context, who owns the next action, and when approved time is ready for payroll, billing, compliance, or audit.
From $8 per worker/month · annual options available
Deterministic · reviewableSelected record
Unverified Exit — Pending Review
ZoikoTime verifies time and attendance by combining captured time, approved context, deterministic classification, neutral exception states, worker input, human review, and versioned record history.
Why Verification Fails
The problems that make time records indefensible
Not surveillance failures — operational ones. Here's what breaks a record before it ever reaches payroll or audit.
Incomplete time events
Start, stop, break, or synchronization gaps leave the record unresolved.
Schedule & time conflict
Captured events and expected schedules differ and need context.
Inconsistent policy application
Different teams or reviewers interpret the same situation differently.
Late or unclear approvals
No one knows who owns the next action or whether a record is ready.
Disputed or changed records
Corrections occur without accessible rationale or history.
Downstream rework
Payroll, billing, or audit teams discover incomplete records too late.
Verification Lifecycle
How a record becomes verified and approved
Six stages, each with clear system and human responsibility, producing inspectable evidence at every step.
Capture
Approved time event received, source and timestamp preserved
System · Worker
Normalize
Timezone, duplicates, sync, ordering, calendar context
System · Admin
Classify
Deterministic policy rules, effective-dated configuration
System · Policy owner
Flag
Missing, conflicting, or unusual context surfaced neutrally
System
Review
Worker adds context; reviewer decides or escalates
Worker · Reviewer
Approve
Required controls complete; permitted fields released
Authorized approver
Deterministic Time Classification is policy-bound and reviewable — never branded as AI. AI, where used, is confined to verified anomaly flagging or signal quality; it decides nothing.
Verification Workspace
Status, ownership, and history — in one place
Production-faithful proof with synthetic data. Filters, bulk actions, and history stay role-bound and auditable.
Capture & Context
What can contribute to a time record — and what never does
Input / context
Purpose
Boundary
Time events
Start, stop, pause, resume, approved manual entries
Source depends on enabled desktop, mobile, web, or integration
Schedules
Compare expected vs. captured periods
Not a scheduling claim; label source and last sync
Breaks
Record meal and rest states distinctly where configured
No inferred legal sufficiency without approved policy mapping
Projects / cost codes
Attribute approved time to permitted context
No app content capture, no productivity judgment
Identity / access signals
Authentication, device trust, session integrity
No biometric or location implication unless disclosed
Worker / reviewer context
Comments, correction requests, rationale, approvals
Role and visibility controlled
Integration metadata
Import/export status, source IDs, error/retry history
Direction and ownership documented per connector
Negative capability set
Under any tier and any configuration, ZoikoTime does not collect screenshots, keystroke content, URL history, application names, or clipboard data. It does not create an individual productivity score. These are product invariants, not optional settings.
Attendance States
Every status has a neutral meaning, owner, and next action
State
Meaning
Owner
Next action
Time event exists; processing or context incomplete
System / admin
Normalize and classify
Required inputs and checks complete; approval may still be required
Reviewer / approver
Review and approve where required
Required field missing or conflicting
Worker / context owner
Provide context or request correction
Context exists; authorized reviewer must decide
Assigned reviewer
Accept, correct, request more, or escalate
Authorized change recorded with history
Reviewer / approver
Complete approval
All required review/approval controls complete
Downstream owner
Release or retain as final record
Approved record hasn't completed transfer
Integration / ops owner
Retry, correct mapping, or escalate
Period closed under configured rules
Policy owner / admin
Use governed reopening process
Canonical neutral example: "Unverified Exit — Pending Review." Prohibited: "time theft," "fraudulent," "dishonest," "idle," or any label that converts incomplete evidence into an accusation.
Exception Resolution
A controlled collaboration — not an automated punishment path
Notification
States the exact issue, date/time, evidence considered, who can act, due date, and support route.
Worker participation
Worker adds context, attaches permitted evidence where supported, requests correction, and sees status and history.
Reviewer authority
Role-bound, least-privilege access; segregation of duties where required; no self-approval for sensitive cases.
Decision
Accept, correct, request more context, reassign, escalate, reject with rationale, or reopen under governed conditions.
History
Before/after values, rule version, actors, timestamps, comments, approvals, and export impact — all preserved.
Break & Rest Records
Meal and rest periods, treated as distinct states
Component
Content
Evidence gate
Break types
Meal and rest are separate customer-facing categories
Production state mapping confirmed
Capture
Start/end, duration, source, edits, sync status
Supported devices and offline behavior tested
Completeness
Missing, short, overlapping, or conflicting context flagged neutrally
Policy/rule version and jurisdiction scope approved
Review
Authorized person reviews context and records rationale
Role permissions and audit events tested
Downstream use
Approved break records may support payroll or compliance
Integration direction documented
ZoikoTime configures and evidences policy workflows; it does not provide legal advice or guarantee compliance in any jurisdiction.
Integrations & Data Flow
Direction and ownership, not a logo wall
Every connector card states direction, supported objects, status, owner, and known limitations.
Identity / SSO
Identity & provisioning
Inbound identity and role lifecycle; outbound audit events where supported.
HRIS
Worker master
Inbound worker, employment, organization, and approved policy context.
Scheduling
Shift & schedule context
Inbound approved schedule/shift context; optional outbound status.
Payroll
Approved records export
Outbound approved records and statuses; optional inbound acknowledgment.
Project / ERP
Cost & billing context
Inbound project/cost dimensions; outbound approved allocations.
BI / Audit
Controlled data export
Outbound approved aggregate or record data under controlled access.
"Connects with" is used only for production-supported connectors; "Export options" covers documented generic file/API methods.
Implementation, Pilot & Adoption
A disciplined, low-risk path to go-live
Discovery
Confirm outcomes, populations, systems, and privacy/legal constraints. Exit evidence: approved scope, RACI, risk log.
Data & policy mapping
Map identity, worker master, schedules, sources, projects, breaks, policies, and roles. Exit evidence: signed data map.
Configuration & integration
Configure roles, policies, notifications, and connectors. Exit evidence: configuration review and security sign-off.
Pilot
Representative workers, managers, and payroll/operations run real workflows. Exit evidence: pilot scorecard.
Readiness & rollout
Training, communications, cutover, and support. Exit evidence: go-live checklist and acceptance.
Operate & improve
Close-readiness review, policy versioning, exception aging, and quarterly governance.
Questions
Verify time & attendance — answered
ZoikoTime combines captured time events with approved schedule, break, project, and policy context. Deterministic rules create a reviewable status. Missing or conflicting details are flagged neutrally, workers or authorized users can add context, and an authorized person approves the record before permitted downstream use.