Agentic AI Capability

A named person approves each action at the supervised level.

At A2 supervised the agent decides and drafts; a named person approves each action before anything changes in your systems.

Approvals · D. Okafor · PO cancellation · Mon 21 Sep 08:50 · 29 drafts · $187,300 · window closes Thu 24 Sep
LineWhat the agent proposesValueBasisConfidenceDecision
4500067123 · 00020Cancel 200 of 7741-X at plant 1210$8,420excess 11.4 wk · window Thu 24 Sep · standard91%Approved 09:12 · DEC-0417
4500068004 · 00020Cancel 1,200 of 8802-K at plant 1210$24,100excess 9.3 wk · window Wed 23 Sep · standard93%Approved 08:58
4500067990 · 00030Cancel 300 of 5513-B at plant 1220$7,160excess 8.6 wk · window Thu 24 Sep · standard88%Edited to 200 · approved 09:03
4500068110 · 00010Cancel 150 of 9021-M at plant 1220$5,900excess 12.1 wk · window Fri 25 Sep · standard90%Approved 09:05
4500068221 · 00050Cancel 80 of 4410-T at plant 1210$2,280excess 10.2 wk · window Thu 24 Sep · standard90%Approved 09:10
24 more lineseach under $25,000$139,440three conditions matched on eachAll approved by 09:12
D. Okafor’s Monday queue as chapter 5 shows it: 29 drafts worth $187,300, five of them in full and the 24 behind them, each with its basis and its confidence. Showcase estate.
29
drafts worth $187,300 in D. Okafor’s queue on Monday 21 September, opened at 08:50
showcase estate
22 min
for the whole queue: 28 approved as drafted, one edited, the last at 09:12
showcase estate
203 of 212
drafts approved as written over six weeks, with 9 edited, before lines under $25,000 moved up a level
showcase estate
61%
of organisations require approval processes for agent actions (KPMG, Q2 2026)
dated source
Where this sits

Stage 5 of six: act

Step by step

What happens between a drafted action and a closed record

Six steps: arrive, rank, read, decide, act, record.

ONE DRAFTED ACTION, FROM THE QUEUE TO THE RECORD01The draftarrivesaction, basis,confidence, value atstake02The queueranks itby what is at stakeand the time left03The approverreads itthe reason, in thewords of the policy04A decision ismadeapprove, edit andapprove, or setaside05The actiongoes outthrough theinterface yoursystem supports06The recordclosesname, time,decision, reason,answerevery decision returns as evidence, so the next drafts fit your practice more closely
Six steps for every drafted action. The dashed line is what makes the next draft better.

A draft reaches the queue with everything a decision needs: the action in one sentence, the conditions that matched, the values they read, a confidence and the money and cover at stake.

The queue ranks the drafts, so the first row is the one that earns the most attention. Filters narrow it to one plant, one supplier or one material, and a group of related lines can be read together.

The approver decides. An approval sends the action to your system through the interface that system supports, and the answer it returns is stored beside the decision.

The record then closes with the name, the role, the time, the decision, any reason given and the answer from your system. That record is what an auditor reads, and what the learning loop reads for the next cycle.

Three decisions

Approve, edit and approve, or set aside with a reason

Each of the three decisions closes the record, and each one teaches the next draft.

Approve as draftedThe action goes out as the agent proposed it. The record holds the approver, the time and the version of the rule behind it.
Edit, then approveThe approver changes a quantity, a date or a value and approves the edited action. Both the drafted values and the approved values are stored.
Set aside with a reasonThe action stays unsent and the reason joins the record. A reason picked from the list teaches faster than one typed by hand.
Confirm a blockDrafts that share a supplier, a material or a plant can be read as a group and approved in one action, each keeping its own record.
1
The draft enters the queuecancel 200 of 7741-X on order 4500067123, worth $8,420, with 28 others
06:06
2
The queue waits for its ownerthe drafts hold until D. Okafor opens the queue; the window on the earliest closes Wednesday
2 h 44 min
3
D. Okafor opens the queuethe basis, the confidence and the facts as read sit on each row
08:50
4
The buyer checks the windowthe supplier portal confirms the window closes on Thursday 24 September
confirmed
5
D. Okafor approves as draftedname, role, session and the time are stored with the decision, after 3 h 06 min in the queue
09:12
6
The action goes to your systemthe purchasing interface answers with the document number
09:14 · acknowledged

Edits and reasons are the most valuable thing a queue produces. In the showcase estate the buyer made 9 edits across 212 drafts, and each one told Juno something about how this team works.

One reason appeared on five of the nine edits: the supplier is on allocation. Juno proposed an exclusion for that supplier class, and j.park approved it as rule version 4.

Working through a block keeps the detail. A group of nine lines for one supplier is read once, and the nine records still carry their own values, their own confidence and their own answer from your system.

Every decision, whichever of the three it is, ends in the same record: who, when, what, why, and what your system replied.

Clocks and escalation

What happens while a decision waits, and when it runs out

The Monday as it ran, the escalation route the agent carries, and the clock a queue can add.

Mon 06:06
The drafts enter the queue29 drafts worth $187,300; the earliest window closes on Wednesday 23 September
Mon 08:50
D. Okafor opens the queueeach row with the action, the three conditions it matched, the value at stake and the confidence
Mon 09:12
The 29 are decided28 approved as drafted, one edited from 300 to 200: 22 minutes for the whole queue
Mon 09:12 to 09:21
Write-back, confirmedeach change acknowledged by SAP S/4HANA and stored word for word
Thu 24 Sep
The window closesa line still waiting stays open, and the next run raises it again while it can be acted on

The showcase estate’s cancellation queue uses the window itself as its clock, and its escalation route has three legs: a line at or above $25,000 goes to D. Okafor as buyer, for his judgement; a failed write-back goes to the owner, L. Tan; a limit breach pauses the run and tells her.

A queue can also carry a service-level clock, set by the team that owns the decision: hours for a queue that works against a closing window, days for a safety-stock queue. A reminder goes out before the clock runs out, on the channel the approver already uses, and cover for holidays is a setting: a named colleague receives the queue while the owner is away.

When a clock runs out, the escalation route sends the item to the next desk named in advance, so the item always has somewhere to go, and both desks appear on the record.

An item that reaches the end of its window stays open. The agent raises the same finding on its next run, so the case returns while it can still be acted on.

Limits

What decides whether an action waits, and when a second person is asked

Six limits decide whether an action goes out, waits for one person, or waits for two.

LimitWhat it doesExample from the showcase estate
The levelDecides whether an action needs an approval at allA2 asks every time; A3 asks for exceptions only
Value thresholdSends an action above a set value to a named approver$25,000 on a cancellation line
Daily action budgetCaps how many actions one agent may take in a day60 actions a day for the cancellation agent
Confidence floorHolds back an action whose evidence agrees less well0.80; below it the finding goes to a person
Rate limitSpreads actions over time so a source stays healthy20 writes a minute to the purchasing interface
Two-person approvalAsks a second named person for sensitive fieldsBank details and payment terms on a supplier record

Limits are checked before an action leaves, and every check is stored with the decision. A limit that sends an action to a person is the same mechanism as the level: it decides who signs for this one.

Two-person approval applies to the fields where a single mistake is expensive. The record then holds two names, two times and two sessions.

Market practice runs the same way. A KPMG pulse survey reports 61% of organisations requiring approval processes for agent actions (KPMG, Q2 2026).

The AWS agency scoping matrix makes a related point: as autonomy rises, oversight shifts from approving each action to auditing what was done (AWS, 21 November 2025). Juno holds both, because the level is yours to set per agent.

The running example

Monday 09:12: 29 drafts decided in 22 minutes, one of them edited

Showcase estate.

The running example

D. Okafor opened the queue at 08:50. Twenty-eight of the 29 drafts were approved as drafted and one, line 00030 of order 4500067990, was edited from 300 to 200 pieces and approved at 09:03. The last decision was made at 09:12: 22 minutes for the whole queue. The 9 lines at or above $25,000 reached him as buyer, for his judgement, with the reason for each.

From 09:12 the 29 changes went to SAP S/4HANA, and by 09:21 every acknowledgement was stored. After six weeks and 212 drafts, 203 approved as written and 9 edited, J. Ridley moved lines under $25,000 to A3 at the level review on Friday 30 October, and D. Okafor sees exceptions only on those.

Next capability

Write-back to the ERP, confirmed

How an approved action reaches SAP or Oracle through the interface that system supports, and how its answer is kept.

Terms on this page
Approval queueThe list of drafted actions waiting for the named person who owns that decision.
Service-level clockThe time a queue allows for a decision before the item escalates.
Escalation routeThe named desk an item goes to when its clock runs out.
EditA change an approver makes to a drafted action before approving it.
Set asideA decision to leave an action unsent, with the reason stored on the record.
Two-person approvalA rule that asks a second named person to sign for a sensitive field.
Questions
What happens when the approver is away?

A named colleague receives the queue as cover, and every item still carries its clock. When a clock runs out the escalation route sends the item to the next desk.

Can we approve many drafts at once?

Yes. Drafts that share a supplier, a material or a plant are read as a group and approved in one action, and each line keeps its own record and its own answer from your system.

What does an edit record?

The values the agent drafted, the values the approver sent, the reason and the person. The learning loop reads those pairs, so the next drafts arrive closer to your practice.

Does approving slow the team down?

It replaces the work of assembling evidence. In the showcase estate the buyer decided 29 drafts in 22 minutes, because the reason and the facts sat on the row.

In the platform

Where Juno sits among the four capabilities

Each one builds on the one before it.

One shared foundationCatalogLineageAccess policyWrite path

See Juno answer and act on your own data

Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.