Break & Rest
Policy, state model, exceptions
Product Updates
Explore verified product changes by role, outcome, and product area, with clear availability, current guidance, and next steps.
No roadmap promises. No silent rollout assumptions. No unsupported benefit claims.
Reviewer Experience
Reviewers with multi-site scope can now triage exceptions grouped by location instead of one flat queue.
Verified availability
Exact state, scope, and last verification
Audience impact
Role-specific implications, not one-size-fits-all
Current guidance
Linked to authoritative documentation
Release-linked facts
Exact records live in Release Notes
Visible revisions
Corrections are never silently overwritten
Featured Update

Reviewers with scope across multiple locations previously worked from one flat exception queue. Grouped queues are rolling out to organizations on the Enterprise plan.
What to do: Admins can enable location grouping under Review Settings — no data migration required.
Browse by Product Area
Policy, state model, exceptions
Control center, exceptions, audit
Rules, sources, review states
Exports, retention, access
Latest Updates
Break & Rest
Workers can see the note a reviewer attached when resolving a correction request.
Shift Integrity
Available to pilot organizations; general availability has not been verified yet.
Time Classification
Admins can schedule a policy pack to take effect on a future date they choose.
Reporting & Evidence
Exports now include who changed a record and when, for organizations in the rollout scope.
Developer Platform
A new event fires when a reviewer resolves an exception, with the resolution note attached.
Break & Rest
An earlier version of this update overstated the regions covered — scope has been corrected below.
Meaningful Change Collections
Product Evolution
Every meaningful change to the Break & Rest product area this year.
9 updates
Role Collection
Changes to queues, notes, and the review workflow.
6 updates
Trust Collection
Updates affecting data, access, or worker-visible records.
5 updates
Developer Collection
Contract, event, and integration changes for developers.
7 updates
Before and After
Before · v6.2
Reviewers with scope across multiple locations saw every exception in a single list, sorted only by time — location context required opening each record.
After · v6.4
The same queue now groups exceptions by location automatically, with a count badge per site. Sort by time is still available within each group.
What didn't change: reviewer permissions, resolution workflow, and the audit trail format.
Trust, Privacy & Worker Impact
Purpose, retention, and access scope stated explicitly for any change touching stored data.
What changes for a worker's own record, and how they can request a correction.
What a feature can and cannot decide on its own, and where human review is required.
Where automation stops and a named reviewer must decide, correct, or approve.
We don't present screenshots, keystrokes, application usage, continuous location, online time, meeting counts, response speed, or productivity scores as product progress. Any update affecting workforce data preserves purpose limitation, worker transparency, correction, role-based access, and human authority.
Developer & Integration Updates
Fires when a reviewer resolves an exception. Existing webhooks are unaffected.
Adds a change-history field; v1 remains supported through the deprecation window.
New key scope limits access to reporting endpoints only.
Adoption & Readiness
Plain-language summary
Prerequisites & impact
Apply current settings
Notify affected teams
Verify in a safe scope
Confirm in production
Search & Archive
Methodology & Corrections
Every claim links to a release record, capability source, or current documentation.
State, scope, and last verification are confirmed before publishing.
Corrections, availability changes, and withdrawals stay visible in revision history.
Stay Current
Browse verified updates by role and product area, or explore the rest of ZoikoTime.
No roadmap promises. No silent rollout assumptions. No unsupported benefit claims.
FAQ
Product Updates explains meaningful ZoikoTime changes in plain language, with verified availability, audience impact, and next steps — it doesn't publish unverified roadmap promises.