One dashboard.One record.Every module.
Time, people, leave, approvals, pay, reports, tasks, and wiki — one operator surface. When leave approves, the timesheet row appears. When time closes, reports read live data.
Leave approves.Time reflects it.
Most tools treat PTO and timesheets as separate products. Kriyos writes both to the same record — so month-end is a read, not a reconciliation.
Leave approved
Ops approves PTO in the same queue as time. The decision is written once.
Timesheet row appears
The week’s hours show leave automatically — no “I was out that day” fixes.
Reports read live
Utilisation, cost, and payroll exports pull from the same row. No second spreadsheet.
Time
Time is the foundation. Every hour your team works is logged once against the right client, project, and task, then moves through approval in a single queue. The record that results is what every other module reads from.
- Weekly timesheet entry with project and task breakdown
- Submit, approve, amend — with full audit trail
- Utilisation, billable, and project cost views for managers
- CSV export for payroll and client invoicing
Directory
Directory is the canonical list of who works at the company — full-time, contract, intern, advisor. Roles, managers, employment terms, and start dates live here, and every other module reads this one source of truth.
- Full org chart with manager, role, and employment type
- Hire, offboard, and role-change workflows
- Employment terms, pay band, and contract details
- Invite via email or bulk CSV upload
Leave
Leave sits next to Time because the two have to agree. When someone takes PTO, their timesheet reflects it automatically — no "oh wait, I was on leave that week" reconciliation at month-end.
- Accrual, balance, and carry-over policies per tenant
- Request, approve, and audit in one queue
- Company holiday calendar with region-aware rules
- Auto-reflects in timesheets — no double entry
Approvals
Every approval in the company — time, leave, reimbursements, form submissions — flows through one queue. Managers approve on mobile in the time it takes to read a paragraph.
- Unified queue across time, leave, reimbursements, forms
- Mobile-first review with one-tap approve / decline
- Escalation rules and delegation for out-of-office
- Full audit trail on every decision
Payroll
Payroll reads from the record — not a re-entry exercise. Time, leave, and salary roll up into a pay run that any operator can close. Payout integrates with regional providers (Razorpay, Deel, Gusto) rather than trying to be a payout rail.
- Pay runs derived from time + leave + salary — no spreadsheet
- Region-aware tax and statutory deductions
- Payout via Razorpay / Deel / Gusto integrations
- Payslips, Form 16 / W-2, and audit export
Reports
Reports read the record directly. Utilisation, cost, leave liability, headcount trend — every report is a saved query, not a statically built dashboard that drifts from reality.
- Utilisation, billable rate, and cost per project
- Leave liability and headcount trend
- Saved queries — share a URL, get the same report
- Scheduled email digests to owners and operators
Tasks
Most teams run tasks in one tool, time in another, and spend Friday reconciling. Kriyos puts tasks next to the time that gets logged against them, so the two never disagree.
- Projects, tasks, and assignees inside Kriyos
- One-click time entry against an open task
- Kanban and list views, kept deliberately simple
- Integrates with Linear, Jira, or stays standalone
Wiki
We're not building Google Docs. The wiki is for the handbook, the leave policy, the on-call rota, the stuff every new hire asks for on day one — a small, searchable set of living documents that lives next to the people they describe.
- Handbook, policies, and runbooks in one place
- Role-aware visibility — new joiners see what they need
- Linkable, searchable, versioned
- Markdown in, markdown out — no lock-in
One dashboard.Every role.One record.
Every module reads from the same record. Every role sees their own view. One platform, one truth.