Plan the work.
See what actually happened.
Chronum turns planning, activity tracking, and approvals into one governed timeline — with the audit trail built in, not bolted on after the fact.
Most organizations run a time tracker, a project tool, an analytics platform, and an approval process as four separate systems that don't talk to each other — and none of them can tell you whether the time actually advanced the plan.
Chronum is a governed work-intelligence platform, not a time tracker. It requires intent up front, records what happened, and makes the difference reviewable.
Every correction is a first-class, reviewable event. Employees see exactly what is recorded and can challenge it — which is what makes the resulting evidence worth anything.
Six things, joined into one record
Each pillar is a working surface in the product today — not a roadmap item.
Plan every day
Mandatory daily and weekly planning — tasks, effort, priorities, and carryover — so there is always an intended plan to reconcile against.
Learn more →Track what happened
Desktop, web, and integration-based activity capture, with policy-triggered screenshots and full employee transparency into what's recorded.
Learn more →See the gap
A planned-vs-actual timeline surfaces mismatches automatically — the core view every role in the product comes back to.
Learn more →Route exceptions
Corrections, unplanned work, and leave requests flow through manager approval with a full before/after audit trail.
Learn more →Understand the workforce
Productivity, capacity, wellness, and profitability analytics — plus an AI layer for next-best-action and skills intelligence.
Learn more →Prove it later
Every approval, correction, and policy change lands in a tamper-evident audit spine — evidence as a by-product, not an exercise.
Learn more →Intent, evidence, and the gap between them
Three steps that run every working day. Screenshots are real captures from the product.
The day starts with a plan
Planning is mandatory and blocking — the planner opens on sign-in and stays until a valid plan exists. Tasks carry effort estimates, priorities and carryover, and can arrive from Jira, GitHub, calendar imports or natural language.
Activity is captured as it happens
The agent records application, window and URL-level activity, merged with integration events into a single chronological timeline. Employees can see every entry that exists about them in the Transparency Panel.
The gap becomes a reviewable decision
Where actual diverges from plan, the difference is surfaced rather than silently absorbed. Corrections, unplanned work and exceptions route to a manager with a mandatory justification and a before/after record.
Planned vs actual, side by side
An illustrative week — planned blocks against what was actually tracked, with one exception routed to approval.
Seven people have to agree on one record
Chronum is bought by operators and finance, defended by HR and security, and lived in by employees. Each gets a surface built for them.
| Persona | What they need | What Chronum gives them |
|---|---|---|
| Founder / COO | Know where work time goes without chasing status | Planned-vs-actual timeline, leakage metrics, approvals, reports |
| HR / People Ops | Reduce surveillance risk and employee distrust | Transparency Panel, consent, retention, wellness, export rights |
| Compliance / Auditor | Produce evidence quickly and prove tamper resistance | Audit spine, legal hold, evidence packs, immutable logs |
| IT / Security Admin | Deploy securely across SaaS, hybrid or on-prem | RBAC, SSO, MFA, IP controls, agent deployment, infra assets |
| Delivery Manager | Connect execution to Jira/GitHub/build activity | Integrations, task associations, CI/CD reconciliation |
| Finance / PMO | Map effort to clients, projects and profitability | Billable rates, finance export, payroll export, profitability |
| Employee | Understand what is tracked and correct mistakes fairly | Daily plan, personal timeline, correction flow, Transparency Panel |
Built so the record survives scrutiny
Every user action, system action and configuration change lands in an append-only audit spine. Records are hash-chained so tampering breaks the chain, and the spine is queryable by auditors with filters for actor, action, entity and date range.
- Append-only — updates and deletes blocked at the database level
- SHA-256 hash chain across every record for tamper detection
- Auditor role with zero write privileges, enforced server-side
- Evidence packs and legal hold for e-discovery workflows
Run a pilot on one team
Bring a single team onto Chronum for a fortnight and compare the plan against what actually happened. No rollout commitment.