Review, correct, and approve time records with a clear history
Give workers and authorized reviewers a transparent path from period review and correction through submission, approval, resolution, and governed release — with human authority and evidence preserved.
That an authorized reviewer accepted a defined record version for a configured workflow. Not proof of universal correctness, and not a guarantee of payroll, legal, tax, or compliance outcomes.
ZoikoTime Timesheets & Approvals assembles reviewable time records into a defined period, shows workers and authorized reviewers sources, status, exceptions, corrections, and policy context, routes submissions through configured human approval, records reasons and changes, and releases approved record versions to authorized downstream workflows. Approval does not guarantee payroll, legal, or compliance outcomes.
Human authority
ZoikoTime may validate, organize, classify deterministically, route, and explain. It does not autonomously approve, reject, discipline, determine pay, or decide legal outcomes.
Worker rights
Visible review, correction, explanation, status, and escalation paths — according to authorized scope and applicable policy.
What “approved” means
An authorized reviewer accepted a defined record version for a configured workflow. Nothing broader.
What evidence means
History records what the system and authorized users did, using available sources and versions. It does not create missing facts.
Review → Correct → Submit → Approve → Resolve → Release
Six stages, each with a named owner. Nothing here is instantaneous and nothing here is automated.
Review
Assemble a defined period and show records, sources, status, issues, policy context, and version.
Correct
Request or make permitted factual corrections with reason, impact preview, evidence, and lineage.
Submit
Confirm the reviewed version, unresolved items, destination, and a neutral declaration.
Approve
Review assigned scope and make an attributable human decision with reason and evidence context.
Resolve
Request information, return, correct, escalate, reopen, or supersede — without hiding prior states.
Release
Send the approved version downstream and track acknowledgment and reconciliation.
Eleven Field Groups Behind Every Total
Every displayed total or status resolves to underlying records, source context, version, and an available action. A number with nothing behind it does not appear.
Identity & scope
Ownership
Record summary
Completeness
Policy context
Change context
Decision & evidence
Handoff & privacy
Understandable, Correctable, Safe to Submit
Workers can see period scope, source, status, issues, corrections, reviewers, and history — everything permission and policy allow.
What a worker sees
- Period range, time zone, and version
- Each included record and its source
- Issues, with what each one means
- Correction status and assigned reviewer
- Full change and decision history
What a worker can do
- Request a correction with a reason
- Add permitted evidence or context
- Submit the reviewed version
- Ask for an explanation
- Escalate or get help
Visible checks, not an opaque score
.png)
Five Steps, and the Original Is Never Erased
A correction is a proposal with a reason and a lineage — not a silent edit.
Select
Identify the record, field, interval, context, or classification being questioned.
Explain
Choose a structured reason. Free text is minimized and never sent to marketing analytics.
Propose
Enter the proposed factual value, with local and canonical time where relevant.
Evidence
Attach only permitted evidence, with purpose, visibility, and retention qualification shown.
Preview
See affected totals, records, approvals, and downstream impact before submitting.
Submission is a confirmation, not a waiver
Approved confirmation wording
“I reviewed the information shown for this period and understand it will be submitted for the configured review process.”
No waiver of wage, correction, appeal, privacy, legal, or collective rights. No “all information is legally accurate” claim. No blame language. Any checkbox is used only where product and legal evidence require it — and is never preselected.
What the submission review shows
- Period, version, and included records
- Visible totals and corrections
- Unresolved items, carried forward not hidden
- Policy context and destination
- Current reviewer or queue
Primary action: Submit for review. Secondary: Back to review · Save and return · Request correction · Get help.
Sorted by Workflow State —
Never by Person
Summary counts are objective workflow states, not performance metrics. There is no risk, productivity, trustworthiness, or worker-value rank available as a sort.
Cards: assigned · needs information · correction pending · ready · returned · reconciliation required
Filters: period, status, unit in scope, workflow, assignment, exception type, source status
Search covers case and period references — not free-text reasons or evidence content
Bulk actions absent unless each is specifically approved — never bulk approve by default
| Worker | Period | Version | Issues | Status |
|---|---|---|---|---|
| A. Ferreira | Week 32 | v2 | 0 open | Ready for decision |
| D. Okafor | Week 32 | v1 | 1 conflict | Needs information |
| M. Halvorsen | Week 31 | v3 | 0 open | Correction pending |
| S. Iqbal | Week 31 | v1 | 2 open | Returned |
| K. Duarte | Week 30 | v2 | 0 open | Reconciliation required |
Approval queue, synthetic. Due dates are configured cutoffs, not pressure devices.
Empty state reads “No assigned timesheets need review” and explains the active filters — it never backfills with unrelated records.
Nine Regions a Reviewer Sees Before Deciding
Evidence and change comparison come before the decision panel. A reviewer should not be able to approve without having passed the reasons to.
Header
01Worker and period, submitted version, status, workflow, assigned role, policy and jurisdiction, source health, last update.
Period summary
02Included records, totals where appropriate, completeness, exceptions, correction status, change since prior version.
Record detail
03Date, time and time zone, source, context, deterministic classification, exception, worker correction, evidence reference, status.
Change comparison
04Previous versus submitted version, changed fields, actor, reason, impact, unresolved conflict.
Policy panel
05Policy, version, effective date, configured rule reference, jurisdiction qualification, shared-responsibility note.
Worker context
06Permitted structured note or correction request, with visibility stated. No hidden sentiment analysis of any kind.
Evidence panel
07Source, event, version, timestamp, integrity and availability state, Evidence Ledger deep link.
Decision panel
08Request information · Return for correction · Approve · Escalate. Each shows impact and requires a reason according to policy.
Conflict guard
09If reviewer authority, assignment, or period state changed while the case was open, decision controls are disabled and the change is explained.
Structured Non-Final Paths
Every non-final action identifies the issue, the owner, the next action, and the history — without implying anyone did anything wrong.
Describe the record issue, not the person. “Careless,” “suspicious,” “dishonest,” “non-compliant,” and “low quality” are never applied as worker labels.
Notification content, channel, timing, recipient, and privacy are availability-qualified. The interface always shows the in-product state even when a notification fails to send.
Configurable, and honestly qualified
Exact approval steps, parallel or sequential behavior, conditions, limits, and plan availability must be confirmed in current product documentation. This page does not assert a topology it cannot evidence.
Workflow definition
- Name, purpose, scope, period type
- Applicable groups, policy and jurisdiction
- Effective version, steps, permitted decisions
- Reason requirements and fallback
Delegation
- Delegator, delegate, reason, scope
- Start and end dates
- Prohibited conflicts
- Worker visibility where applicable
Escalation, aging & coverage. Dashboards aggregate counts by objective state, workflow, period, and source health — they do not rank individuals. Executive views aggregate where individual detail is unnecessary. Coverage and aging support workflow continuity without monitoring behavior or scoring people.
Policy & jurisdiction context
Every period carries its policy name, version, effective date, configured rule references, and jurisdiction qualification — plus an explicit note that this is configuration, not legal advice.
Exceptions & conflicts
Neutral states only: needs review, information requested, conflict, incomplete, returned, unresolved. Where sources conflict, both are shown with authority and version — the system does not pick a winner.
Locked periods & late corrections
A locked period shows its lock reason, authority, effective timestamp, locked version, downstream status, and available correction path. Reopening or superseding requires permitted roles, checked at action time.
| Impact area | What the preview shows |
|---|---|
| Open approvals | Which in-flight decisions this change would invalidate. |
| Reports | Which published outputs referenced the superseded version. |
| Handoff | Whether the version was already released downstream, and to which target category. |
| Reconciliation | What must be reconciled, and who owns it. |
| Communication | Which worker and reviewer notices are required. |
| Evidence history | How the superseding version links to the original — which is preserved, never deleted. |
Late-correction impact preview. Every affected area is named before anything is reopened.
Every Submission, Decision, and Reason
Traceable history records what the system and authorized users did, using available sources and versions. It does not create missing facts, and it does not promise legal admissibility.
- Submission · assignment · views where appropriate
- Information requests · corrections · decisions
- Reopen · supersede · release · reconciliation
- Each with actor, role, reason, timestamp, and source reference
Checked immediately before release
Release gate
- Only an approved, current, authorized version can be selected
- Correction, conflict, and lock state re-checked at the moment of release
- Release authority separated from approval authority where configured
- Payload preview shows included fields, exclusions, transformations, and privacy minimization
Release states
A named integration target appears only when verified, with direction, purpose, mapping version, and availability stated.
What Administrators Configure
Periods & workflows
Period types, cutoffs, workflow definitions, permitted decisions, reason requirements, fallback.
Assignments
Roles, scope, effective dates, delegation rules, prohibited conflicts, coverage.
Reasons & policies
Structured reason codes, policy versions, effective dates, jurisdiction scope.
Sources & support
Eligible source categories, health thresholds, support routes, escalation owners.
Non-negotiable, at every tier
No screenshots, keystroke content, URL history, application-name monitoring, or clipboard collection under any tier or configuration.
Visibility — period scope, source, status, issues, corrections, reviewers, and history, as permission and policy allow.
Correction — a defined request path with reason, permitted evidence, and human review.
Explanation — what a status means and which policy version applied.
Escalation — a documented route when a correction is declined.
What Prepares a Decision, and What Makes One
Deterministic classification
Policy-bound, jurisdiction-aware, and reviewable. It prepares records for review. It is not AI, and it does not approve anything.
Kairos Assistant
May retrieve, summarize, and explain permitted records with sources and limitations. It decides nothing and cannot approve, return, or reopen.
Zoiko Sema
Any connected context is optional, mapped, permissioned, and reviewable — and both products keep independent identity. Communication context never becomes an approval.
Who this serves, and where it connects
Reviewers & managers
An assigned queue with evidence before action controls.
Finance & payroll
Approved versions released with acknowledgment and reconciliation.
HR & people teams
Correction rights and neutral language as product behavior.
IT & identity
Roles, scopes, delegation, and separation of duties.
Privacy & legal
Minimum-necessary fields, retention qualification, evidence limits.
Audit
Versions, actors, reasons, decisions, and handoff history.
Procurement
Controlled evidence and current commercial terms.
Enterprise overview
Administration, deployment, and support pathways.
Start with one period
Start Free lets you assemble a period, raise a correction, route an approval, and follow the version history end to end.
Honest expectation: approval topology, integrations, and jurisdiction handling depend on verified configuration and current availability.
Already a customer?
Task-first routes, none requiring a marketing form.
Bring review, correction, and approval into one traceable workflow
See how ZoikoTime can help your organization prepare reviewable periods, preserve worker correction paths, route accountable human approvals, and release governed record versions to authorized downstream workflows — subject to verified configuration and availability.
.png)