The platform
One platform for the whole operating day
From the procedure you write once to the report you read on Monday morning.
Tasks that end in a verified result
Assignment is the easy half. Dutyrex is built around the other half.
Write the procedure once
Then change it, version it, and see whether the change worked.
Measured from the work, not from a survey
Analytics computed from the same records your team produced by doing the job.
Everything the day actually needs
| One platform for the whole operating day | The platform | Available now |
|---|---|---|
| Tasks and verification | Assign work, collect the result, and have a supervisor approve it, return it, or escalate it. | Available now |
| No-code procedures | Build the real sequence of a job without a developer, and version it as it changes. | Available now |
| Organisation and teams | Model your real structure — branches, units, teams — and change it without losing history. | Available now |
| Workforce analytics | Completion, workload and reliability, computed from the work itself. | Available now |
| AI operations assistance | An assistant that reads your own operational data and proposes — never decides. | Available now |
| Recognition and rewards | Make consistently good work visible, with a reward programme the employer actually controls. | Available now |
| Knowledge Assistant | Staff ask a question in their own words and get an answer from your documents, with the page it came from. | In preview |
| Training and courses | Turn a procedure or policy into a short course, with a review step before anyone sees it. | On the roadmap |
Inside the product
A supervisor's Monday morning
One screen holds the whole shift: what is due, what came back, what needs a decision. Nothing here is a mock-up of a feature we intend to build.
Illustrative interface shown with sample data. Not a customer account, and no figure here describes a real organisation.
The queue is the job
Submitted work waits in one list with the evidence attached. Approve, send back, or escalate — and the record keeps the reason.
Scoped to what you run
A branch supervisor sees their branch. A regional director sees the region. The permission model is the product, not a setting bolted on afterwards.
Every decision is written down
Who verified what, when, and on what basis. The audit trail is produced by people doing their jobs, not by someone filling in a spreadsheet later.