Under throughput pressure, controls get traded for speed. Operations managers should never let an agent raise its own depth, release held work on a timeout, loosen a limit to clear a backlog, drop a second approver, reassign its own reviewers, or keep working through a lapsed certificate.
Why do operations managers need their own red lines?
Reviewers protect individual cases. Operations managers protect the system those cases flow through. Their red lines are less about what an agent does to a customer and more about what the operation does to its own controls under pressure.
Every operations manager knows the moment: the queue is long, a service level is at risk, and someone suggests a shortcut. With agents, the shortcuts are tempting because they are one setting away. The red lines below name those settings and keep them out of reach.
Which shortcuts stay off the table?
| Never let the agent, or the operation | Why |
|---|---|
| Raise its own depth or extend its own certificate | Depth is earned on evidence; self-promotion removes the evidence |
| Auto-release a held item when it ages past a deadline | A hold that expires into an approval is not a hold |
| Run on with a lapsed certificate through a workaround | A lapse drops the agent to depth 1 for a reason; bypassing it hides a failure |
| Loosen the organisation's own limits to clear a backlog | Limits are risk decisions, owned by the risk owner, not by the queue |
| Remove the second approver on hard-to-undo actions | Two-person rules exist for actions that cannot be undone |
| Route held items back to an agent for "review" | The reviewer must be a named person independent of the preparer |
Risk managers keep a complementary list about appetite and acceptance; see what risk managers should never let an agent do. Property managers face the same temptations with contractors and tenants; see what property managers should never let an agent do.
How is each line enforced?
Some are enforced by the platform. Depth cannot be configured upward past what Attest evidence supports; the agent's role sets a ceiling, the evidence sets the depth, and the lower wins. A run that clears no depth drops the agent to depth 1 the same day, with no manual override. Actions withheld at the platform floor cannot be switched on by anyone.
Others depend on the organisation's governance, and that is where operations managers matter. Who can change limits? Who can alter reviewer assignments? Is a held item ever released by a rule rather than a person? Managers should know the answers and make sure every change to these settings is approved by someone outside the operations line and filed in the record.
What does pressure look like in practice?
Take a logistics firm's operations team running an agent that books carrier collections at depth 3 and pays carrier invoices at depth 4 within limits. A peak week arrives. The queue of invoices over the limit, drafted for a person to pay, reaches 600 items. A supervisor proposes raising the payment limit for the week and letting items older than 48 hours pay automatically.
The operations manager refuses both. Instead she moves two people from a quieter team to review, asks the agent's builder to check why so many invoices exceed the limit, and finds that a carrier has started invoicing weekly rather than per shipment, which pushes every invoice above the threshold. The fix is a new sub-limit for that carrier, approved by the risk owner. The queue clears in two days, and no control was traded for speed.
French and Nigerian logistics operations run the same rhythm under different rules; see operations manager training in logistics in France and in Nigeria.
How do managers keep the line under pressure?
Write the red lines down and share them with the risk owner. Measure the held queue and certificate calendar weekly, so pressure is seen early. And make sure there is always a route to more reviewers that does not involve loosening a control. The deeper argument is in why operations managers are the real control; the role map is in AI agent skills by role.
Where the Academy fits
Pryme Intelligence Academy's Operator track includes a module on running the rhythm and another on what to do when something goes wrong, both aimed at managers who face exactly these trade-offs. Managers can track the team's progress, results and certificate expiry dates in the admin view that comes with seats on paid plans.
Questions people ask
Is it ever acceptable to raise a limit temporarily?
Yes, if the risk owner approves it as a risk decision, with an end date and a recorded reason. It should never be done by operations alone to meet a service level.
What should happen to held items over the deadline?
They should escalate to a more senior person, not release. Ageing is a signal to add people, not to remove the check.
Can an agent help manage the held queue?
It can sort and summarise held items for reviewers at depth 1 or 2. It must not approve them.