Operations platform
Dutyrex turns your daily operations into clear procedures, puts them in the hands of the right people, and shows you what actually got finished — with the record to back it up.
Built for teams whose work happens on a floor, a ward, a site or a route — not at a desk.
Illustrative interface, shown with sample data. Not a customer account.
The problem
Not because anyone is careless. Because the system holding it together is a group chat, a clipboard, and whoever happens to be on shift.
What the night shift noticed never reaches the morning. It was in a chat, and the chat moved on.
The task was assigned. Whether it was finished, and to what standard, is a question with no answer.
There is a policy for this. It is a PDF somebody emailed in 2023, and the person who needs it is standing in a corridor.
The problem surfaces in a complaint, an inspection, or a bad month — long after it could have been cheap to fix.
None of this is a people problem. It is a missing system.
How Dutyrex works
Define the work once. Put it in front of the right people. See what came back. Act on what it tells you.
Build the real steps of a job once — the checks, the order, who signs it off. No code, no consultant. Import an existing policy document and Dutyrex drafts the procedure for a manager to review.
Work goes to a person, in a unit, at a branch — with the role and permission rules your organisation already has. Everyone sees their own day, nobody sees someone else's.
A clear list on a phone. Tick off each check, raise an exception when something is wrong, and hand over cleanly at the end of a shift.
Completed work goes to a supervisor to approve, send back for rework, or escalate. This is the step most tools skip, and it is the one that makes the record mean something.
Completion trends, workload across units and teams, which procedures keep failing, which days run late. Measured from the work itself, not from a survey.
Change the steps, publish a new version, and watch whether it worked. The loop closes where it started.
The platform
Not a task list with extras bolted on. The pieces an operation needs to run, built to work together.
Assign work, collect the result, and have a supervisor approve it, return it, or escalate it.
Build the real sequence of a job without a developer, and version it as it changes.
Model your real structure — branches, units, teams — and change it without losing history.
Completion, workload and reliability, computed from the work itself.
An assistant that reads your own operational data and proposes — never decides.
Make consistently good work visible, with a reward programme the employer actually controls.
Staff ask a question in their own words and get an answer from your documents, with the page it came from.
Turn a procedure or policy into a short course, with a review step before anyone sees it.
AI, grounded
Dutyrex's AI reads your operational records and your published documents. That is all it reads. It proposes, cites, and stops.
“What do I do with a damaged infusion pump?”
Take the device out of service immediately, then report it to technical services and open an incident record.
Sources
From your documents
“Where are we losing time this month?”
Closing checks ran late on 9 of the last 14 weekdays, concentrated on Fridays. Opening checks were unaffected.
Sources
From your documents
“What should I look at before the board meeting?”
Verification time has risen in two units while volume stayed flat. Three procedures account for most of the rework.
Sources
From your documents
Every claim the assistant makes is checked back against the record it came from. If a statement cannot be traced to a document you published or a figure in your own data, it is dropped before it reaches the screen — and if nothing survives, the assistant says it could not find an answer. An invented procedure is worse than no answer at all.
Inside the product
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.
Submitted work waits in one list with the evidence attached. Approve, send back, or escalate — and the record keeps the reason.
A branch supervisor sees their branch. A regional director sees the region. The permission model is the product, not a setting bolted on afterwards.
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.
Who it is for
Dutyrex does not assume your industry. Your units, procedures and roles are configured to match how you actually operate.
The non-clinical work a hospital runs on
Cleaning schedules, equipment checks, reception handovers, maintenance rounds and supply tasks — tracked and verified across wards and shifts.
Every branch to the same standard
Opening and closing routines, stock checks, hygiene and safety procedures, and multi-site oversight for the people responsible for all of it.
Work that happens away from any office
Job procedures, site checks and completion records for crews who are rarely in the same place twice.
Buildings, rounds and reporting
Inspection rounds, maintenance procedures and compliance routines across a portfolio, with a record per building.
Repeatable delivery, visible progress
Standardised client onboarding and delivery procedures, with oversight of what each team has actually completed.
Dutyrex is built for non-clinical operations. It does not store patient records, diagnoses or treatment data, and it makes no clinical decisions.
Trust
Dutyrex is early. We would rather tell you exactly where we are than show you badges we have not earned.
Every record carries its organisation, and every query is scoped to it. Separation is enforced in the database layer, not by filtering results afterwards.
Six roles, with each permission evaluated server-side. Hiding a button is not access control, so we do not rely on it.
Daily backups are encrypted before they leave the server, using a key we cannot read. Automated checks verify that a recent backup exists and is well-formed.
Consequential actions are recorded with who did them and when. Audit history is never deleted as part of normal operation.
Documents are scanned for national ID and card numbers before any AI processing. A flagged document is refused, not quietly redacted.
Messages shown to users are written for users. Database details, stack traces and file paths are logged privately and never rendered.
We hold no SOC 2 or ISO 27001 certification and we do not claim HIPAA or GDPR compliance certification. We have no customer logos to show you and we are not going to invent any. If a formal certification is a requirement for you, tell us on the demo call and we will be straight about where that sits on our roadmap.
Security and trustA short call, your real operation, and an honest answer about whether Dutyrex fits it.