How it works

Approve or reject. The run responds either way.

Every action type has its own expiry window in hours, so a request never sits pending forever. Open the queue on its own screen, or beside the Agents that raised the requests.

  • Oldest waiting request: Deviation: torque spec change WO-118342 3d 6h Deviation

Approvals

Work one list, oldest request first

Every pending approval for your site lands in one list, oldest at the top. The list pages, so a long backlog stays as easy to read as a short one.

  • One list per site, oldest request at the top
  • Paged, so a long backlog stays readable
  • Open it on its own screen or beside the Agents that raised it
  • Cure dwell change, WO-118342Reason: spec out of tolerance 21 min
  • Cure dwell 21 min, WO-118342 Approve Reject

Request detail

See the detail before you decide

Open a request and you see what the Agent wants to do, why, and how far it reaches, all in one dialog. Approve or reject from the same screen. You never dig through a thread to find out why it wants to hold a line or change a work order.

  • The action, its reason, and its scope in one dialog
  • Approve or reject from the same screen
  • No hunting through a thread for the context
  • S. Oyelaranapproved 14:39
  • Agent run resumed

Approval outcome

Approve a request and the paused run resumes

Approve and the paused Agent run picks up exactly where it stopped, mid-shift or between runs. Reject and the action never happens. Either way, the decision carries the name of the person who made it.

  • Approve resumes the Agent thread that was waiting
  • Reject closes the request and the action is not taken
  • Every decision carries the person who made it
  • Deviation expires in 6h

Approval expiry

See the time left before it expires

A request doesn’t sit pending forever. Its window is set in hours, and the time left shows right on the request. When the window closes, the request stops waiting.

  • Each action type carries its own window in hours
  • Time remaining sits on the request
  • Nothing stays pending past its window
  • Same request, twice Submitted 13:58:41, applied Submitted 13:58:43, no change

Decision history

Click approve twice and it still counts once

A decision that’s made stays made. Double-click, leave a stale tab open, or retry after a timeout, and nothing changes. The first decision stands, kept with who made it and when.

  • A repeat decision on a decided request changes nothing
  • The first outcome stands
  • Every decision is kept with its actor and its time
  • Decision record: Hold, Weld Line 1 T. Nakamura 09:12 Rejected

Approval scope

It holds the request. A person makes the call

The queue holds approvals and keeps the record. It doesn’t pick who approves, chase an approver on a night shift, or decide anything for them. What an Agent may do alone in the first place is set in the Authority Matrix.

  • What an Agent may do alone is held in the Authority Matrix
  • It does not chase an approver or send reminders
  • It holds the Agent actions raised inside the platform

What a supervisor sees when an Agent asks to act

    • Cure dwell extensionWO-118342 21 min
    • S. Oyelaranreviewing now
    • Approve or reject Approve Reject

    Action, reason, and scope in one dialog.

    Open a request and see the action, the reason, and how far it reaches, all in one dialog. Approve or reject from the same screen. No digging through a separate thread.

    How review works
    • Queue, oldest first Deviation WO-118342 Waiting Hold release Weld Line 1 Waiting Reschedule Cell B Approved
    • Deviation expires in 6h

    Each request shows the hours left in its window.

    Every open request sits in the queue, oldest at the top, so a long backlog stays as easy to read as a short one. Each request shows the hours left before its window closes.

    See the queue

FAQ

Bring the approval stuck in someone's inbox.

30 minutes on your sign-off process and what belongs in the Approval Queue.