How long until we check less?
It depends on volume and on the steps you set. With the default steps, a request type arriving 300 times a month reaches the third level in about two weeks. At 30 a month it takes about five months. Select a level to see the rest.
We start where volume concentrates. Below about 30 items a month per task, autonomy moves slowly, so that work proves the answers and the fixed limits instead.
The steps are yours to set. Runs of 30, 150 and 750 approvals are the defaults, and your organisation can choose its own when it sets Xalios up. The four levels, the step back after 2 mistakes in the last 20 and the 5% spot checks stay the same.
Autonomy is per task.
Each task an agent handles keeps its own run of approvals. A long run on payment-date questions moves nothing on remittance queries.
Your team’s approvals move it.
A task moves up only after an unbroken run of approvals in the review queue, from the team that answers for the work.
It steps back on its own.
Two mistakes in its last 20 items step a task back automatically. Each step back and its cause go on the record.
What holds at every level
Your team’s approvals change how much of a task runs alone. These four rules stay the same whatever the level.
What if the approvals are just rubber stamps?
Approvals with edits count as neutral, 5% of work is spot-checked, and two mistakes in the last 20 step a task back.
We seed known mistakes into the review queue.
The pilot reports how many of them your reviewers caught, so you can see whether the approvals reflect real scrutiny.
Every pilot runs for 30 days on one stream of work and starts at level 1, with a person approving each item.