Time-Out Zone

An audit log that answers "who changed what?"

Every sensitive change in Time-Out Zone is recorded — who did it, when, and each field's before and after. When the auditor, the works council, or a confused manager asks, the answer already exists.

Get startedView pricing
  • Lab Test Analyzer logo
  • Promics Edge logo
  • SelfHacked logo
  • SelfDecode logo
  • OmicsEdge logo

Proof beats memory

2.71×

what non-compliance costs compared to staying compliant

15

entity types tracked, from requests to policies to people

Field-level

every change stored as before → after, per field

10,000

rows per CSV export, filterable before you download

  • Research puts the average cost of non-compliance at 2.71 times the cost of compliance — $14.8M versus $5.5M a year. The paper trail is the cheap part.
  • An audit trail is only useful if it answers questions precisely. Field-level diffs mean you see exactly which value changed, from what, to what — not just "record updated".

Ponemon Institute & Globalscape, "The True Cost of Compliance" (2017). Averages across 53 multinational organizations.

Before and after, per field

Not "profile updated" but "allowance: 25 → 28, changed by Maria, Tuesday 14:02". Each field's old and new value, stored at write time.

Every entry has an author

Who made the change is part of the record — admins, managers, or the system itself on scheduled jobs.

Decisions in the same breath

Approvals and denials are written to the audit log in the same database transaction as the decision. If the log can't be written, the decision doesn't happen.

Filter, then answer

Slice by date range, action, entity type, or actor. "All policy changes by admins last month" is three clicks, not a support ticket.

Where the trail shows up

Company-wide log

The Admin Audit tab shows the whole company's trail, newest first, with expandable per-field diffs.

Per-person history

Every profile has its own Audit Trail tab — every change to that person, in one place.

CSV for the auditor

Export the filtered view as CSV, up to 10,000 rows — columns for date, actor, action, entity, and changes.

Written once

There is no edit button and no delete button for audit entries in the product. Entries are written once and stay as written.

Managers additionally get their own decision log with CSV and Excel export, covering their approve/deny history.

Coverage

What gets recorded

The sensitive stuff, systematically.

  • Approval decisions, request edits, policy changes and assignments, profile and balance mutations, org changes, invitations, tags, tasks, and company settings.
  • Fifteen entity types in total — people, requests, policies, teams, locations, holidays, and more.
  • Scheduled jobs write to the same log, so automated changes are just as visible as human ones.

Precision

From decision to record, atomically

Log and action are one unit.

  • Approve and deny decisions write their audit entry in the same database transaction — no decision without a record.
  • Request timelines assemble those entries into a readable history for each request.
  • Policy Change History gives admins a policy-scoped feed of updates, assignments, and reconciliations.

Answers

Audit-ready by default

Built for the day someone asks.

  • The company-wide Audit tab answers "who changed what" with filters for time, action, entity, and actor.
  • Per-person audit tabs answer "what happened to this employee's data".
  • CSV export turns any filtered view into a file your auditor can keep.

More resources

Feature

Security

Feature

Analytics & Reporting

Feature

Multi-step approvals

Ready to get started?

Give us a call. We'll change an allowance live and show you the field-level audit entry it leaves behind.

Analytics & Reporting

Reports that deliver themselves.

Explore

Security

Roles, isolation, encryption.

Explore

Frequently asked questions

What gets recorded in the audit log?
Sensitive changes across the product: approval decisions, request edits, policy changes and assignments, profile and balance changes, org structure updates, invitations, tags, tasks, and company settings — fifteen entity types in total, with actor and per-field before/after values.
Can audit entries be edited or deleted?
No. The product has no edit or delete function for audit entries — they are written once and stay as written. Approval decisions even write their entry in the same database transaction as the decision itself.
Who can see the audit log?
Owners and admins see the company-wide log and per-person trails. Managers see their own decision log — the approvals and denials they made — with export. Employees see their own request history.
Can I export the audit log?
Yes. The filtered view exports as CSV with up to 10,000 rows — date, actor, action, entity, and the changes themselves. Managers can export their decision log as CSV or Excel.
Does it log logins and sessions?
No, and we say so honestly: the audit trail records changes to data, not sign-in events. Identity and session security are handled by the authentication layer.
How precise are the entries?
Field-level. An entry stores each changed field's old and new value — "allowance: 25 → 28" — plus who changed it and when. You see the exact difference, not a vague "record was updated".