Versioned product and governance materials for employers, representative bodies, advisors, workers, privacy, security and accessibility reviewers, and deployment owners — each with its scope, owner, review date, and stated limitations.
Representative bodies and advisors can review public materials without a ZoikoTime account, a purchase, or accepting product terms.
What this page does not do
It does not determine whether consultation is required, calculate a deadline, get a rollout approved, or certify that any obligation has been met.
Professional and legal boundary
Employers remain responsible for applicable law, collective agreements, representative rights, notice, timing, bargaining, consultation, consent, independent advice, and implementation decisions. ZoikoTime explains product behavior and provides evidence — it does not determine what your obligations are or whether you have met them.
Delivery is not consultation. Sending materials does not prove meaningful dialogue occurred.
Attendance is not agreement. A meeting record shows a session happened, nothing more.
Acknowledgment is not consent. Evidence of receipt is not evidence of acceptance.
Agreement, approval, and consent are different things. The terms are not interchangeable and each must be supported for the jurisdiction, body, scope, and authority in question.
We will not label a consultation Ready, Complete, Approved, Agreed, Consented, Compliant, or Legally Sufficient unless that exact term is supported for the jurisdiction, body, scope, and authority. Product readiness and legal sufficiency are separate — and this page keeps them separate.
Statement owner: Trust & Governance · Last reviewed 12 Jul 2026 · Next review 12 Jan 2027
Compliance & AssuranceWorker-Trust Commitments
These are product invariants, not settings. A representative body reviewing ZoikoTime should be able to check each of them directly.
No screenshots, keystroke content, URL history, application-name monitoring, or clipboard collection — under any tier or configuration.
Anomaly and signal-quality flags exist to prompt human review. They do not conclude anything about a person.
Payroll, discipline, employment, scheduling, accommodation, legal, and labor-relations outcomes remain with accountable people.
Deterministic Time Classification is policy-bound and reviewable. It is not presented, branded, or sold as artificial intelligence.
Approved ML may support anomaly or signal-quality review. Kairos retrieves, summarizes, and explains governed data — and decides nothing.
Administrative visibility does not remove worker rights. Both exist at the same time, by design.
Resource Directory
Sorted by current core resources and direct answers — not by popularity. Every card states its owner, status, review date, and limitations before you open it.
What the product is for, which workforce groups are affected, and what is explicitly out of scope.
Limitation: describes product behavior, not your deployment configuration.
Categories, sources, purposes, recipients, retention, and location context in one table.
Limitation: residency statements apply only where contractually operational.
The exact invariant, what it covers, and how it is enforced across tiers and configurations.
Limitation: none. This invariant does not vary by plan.
Visibility, explanation, correction, challenge, representation, and escalation as product behavior.
Limitation: availability of specific routes depends on your configuration.
Deterministic classification, approved ML scope, the Kairos boundary, and where decisions sit.
Limitation: model and provider detail is not published on marketing surfaces.
Administrative roles, policy controls, audit logging, and what administrators can and cannot see.
Limitation: describes capability, not your assigned role model.
Security controls, incident handling, and reliability evidence at review-appropriate depth.
Access: governed request route. Detailed findings are never public.
Rollout stages, training dependencies, support routes, and what triggers renewed review.
Limitation: stages are operational guidance, not legal deadlines.
WCAG 2.2 AA position, known limitations, remediation status, and accessible format options.
Limitation: conformance is stated per surface, not as a blanket claim.
Customer-specific packs and restricted artifact titles never appear in this directory. A generic template is never presented as jurisdiction-approved.
Resource Detail
RES-0142 · version 6 · Data category & collection map
Intended audience: representative bodies, advisors, privacy reviewers
Vary by deployment
Contractual, not product
Describes product behavior as configured by default. It does not describe your deployment, and it is not a legal opinion about your obligations.
No legal advice, customer facts, participant identities, or representative-body membership. Translated wording is not authoritative unless reviewed for that use.
Consultation Lifecycle
This describes how ZoikoTime supports a customer-owned process. It does not automate law, and rollout does not advance merely because materials were sent.
Customer owns
Jurisdiction, representative body, and process owner. ZoikoTime supplies product facts, not a legal determination.
Customer owns
Proposal, scope, workforce groups, use cases, and configuration assumptions.
Both
Current resource pack assembled, with evidence gaps identified rather than hidden.
Both
Share, explain, meet, receive questions, and provide evidence-led responses.
Customer owns
Commitments, conditions, unresolved issues, and the customer-reported outcome.
Both
Verify the rollout gate, train, pilot, deploy, monitor, and reassess on material change.
Twelve lifecycle statuses
Status boundaries
“Not assessed” never means consultation is not required. “Ready for customer review” is an internal preparation gate, not a legal conclusion. “Shared for review” means delivery occurred — not that meaningful consultation happened. “Rollout gate satisfied” proves operational prerequisites, not legal approval.
Prepare a Consultation Pack
Preparation begins with purpose, scope, and a responsible owner. The assumptions and the professional boundary are shown before anything is generated.
Never collected in this flow
Worker lists, union membership, representative identities, or protected-activity data. The flow also never infers that a representative body exists, or that a legal duty applies to you.
Pack Contents & Manifest
A manifest makes the pack inspectable. It is not proof that consultation requirements were satisfied.
| Module | Resource ID | Version | Owner | Access | Status |
|---|---|---|---|---|---|
| Cover, scope & limitations | RES-0101 | v4 | Product governance | Public | Current |
| Product overview & proposed use cases | RES-0118 | v4 | Product governance | Public | Current |
| Data category, source, purpose, retention & location map | RES-0142 | v6 | Privacy | Public | Current |
| Collection limits & anti-surveillance statement | RES-0150 | v3 | Trust & Governance | Public | Current |
| Worker visibility, correction, challenge & representation | RES-0163 | v5 | Product governance | Public | Current |
| Human authority, deterministic classification & AI boundaries | RES-0171 | v4 | AI governance | Public | Current |
| Administration, roles, logs, integrations & security | RES-0180 | v7 | Security | Controlled | Request required |
| Rollout, training, pilot, support & accessibility | RES-0195 | v2 | Implementation | Public | Current |
| Data residency statement | — | — | — | — | Excluded — not operational |
Illustrative manifest. Resource IDs, versions, owners, status, and access level are always shown; checksums appear where approved.
Pack states: Draft · In preparation · Internal review · Ready for customer review · Shared · Superseded · Withdrawn. A draft carries a visible status watermark and makes no external completion claim.
Questions & Evidence Requests
Each question carries an ID, topic, submitter role, date, scope, and — where the customer owns one — a requested response date. Responses identify owner, source, scope, limitation, version, and follow-up.
Question statuses
Never applied to a question or its author
No automated sentiment, hostility, union-risk, or legal-risk scoring. Participant identity is never exposed publicly, and related questions can be linked without erasing distinct concerns.
Sessions & Minutes
Attendance does not equal agreement or consent. Corrections and objections to minutes remain visible rather than being edited away.
Commitments & Conditions
Negotiated assurances become governed objects. ZoikoTime records them and enforces technical gates where configured — it does not decide their legal enforceability.
| Commitment | Type | Owner | Due | Evidence | Status |
|---|---|---|---|---|---|
| Screenshot capture remains unavailable in all tiers | Collection limit | Product | Ongoing | Product invariant | Verified |
| Worker correction route enabled before pilot | Configuration | Implementation | 01 Sep 2026 | Config baseline | Implemented |
| Manager training completed for all reviewers | Training | Customer HR | 15 Sep 2026 | Attendance record | Partially met |
| Quarterly report to the representative body | Reporting | Customer process | Quarterly | Report reference | Accepted by customer process |
| Retention shortened for exception records | Retention | Privacy | 01 Oct 2026 | Pending | Not met |
Illustrative commitment register. Types include configuration, collection limit, access, retention, notification, training, support, incident, reporting, accessibility, pilot, and review.
Statuses: Draft · Proposed · Under review · Accepted by customer process · Implemented · Verified · Partially met · Not met · Waived by authorized customer process · Superseded · Withdrawn · Expired. There is no hidden waiver and no unilateral bypass.
Customer-Recorded Outcome
An accountable customer or advisor process records the outcome using its own approved vocabulary and authority source. ZoikoTime records the source, scope, date, and limitation — and certifies nothing.
No ZoikoTime approved badge
There is no generic certification mark, and there never will be. Acknowledgment, agreement, consent, and approval remain distinct terms with distinct meanings.
Statuses: Draft · Recorded · Under review · Superseded · Withdrawn · Reassessment required. Public product pages never expose customer-specific outcomes.
Rollout Gates & Implementation Handoff
A gate connects verified customer conditions to controlled configuration and deployment. When a required gate is blocked, nothing activates quietly.
Gate states
Operational verification does not prove legal sufficiency. Break-glass and exception use is attributable, limited, and reviewed.
Change & Reconsultation Triggers
Two things we will not do
We do not automatically decide that a change is legally material — your rule determines whether it triggers review, notice, reconsultation, approval, pilot, or block. And we do not hide changes inside release notes or a generic terms update.
Direct Answers
ZoikoTime cannot determine that. Requirements depend on jurisdiction, collective agreements, representative rights, purpose, and deployment scope. Employers should obtain independent advice — and nothing on this page should be read as concluding that consultation is or is not required.
Route to what you actually need
Review public consultation resources, prepare a scoped pack, or request controlled evidence through the approved review path. Deployment evaluation and customer support are separate routes — and none of them gates the materials above.
Request controlled evidenceRequest Enterprise DemoEnterprise Support
