Before the next shift takes over

Imagine the supplier-confirmation pilot moving beyond a demo. The agent prepares an update, the buyer reviews it, and an approved change is saved in a test purchasing system. It must leave quantities, production commitments and blocked stock alone. Approval covers that workflow, that system version and those permissions. It does not approve every agent the plant might build later. Put those limits where everyone reviewing the pilot can see them.

Write the expected results before testing. A passing ordinary case has the right supplier and order line, current evidence, the approved change and a final record you can trace. A rejected or ambiguous case stays assigned and leaves the order unchanged. Use the plant’s existing process to decide how much review work the buyer can reasonably keep. A savings figure from another customer cannot make that decision for you.

Glean says source permissions apply to reads and writes. Relevance AI lists approvals for individual tools. Nexus describes audit trails and access based on roles.^1,2,3

Create test accounts for a buyer, a planner who can only read and someone without access. Try allowed and forbidden requests, remove a permission and repeat after the documented time for that change to take effect. Then change the sample order while a draft waits. Require another check before the update proceeds. Save the input, draft, approval and final record together, so a reviewer can see whether the permission and evidence still matched.^1,2,3

Add a supplier message telling the agent to ignore the normal procedure or send information somewhere else. That message is evidence to read, not permission to widen access. Have the security and process owners agree the expected refusal or handoff first. Check prohibited actions separately from answer quality. An accurate summary still fails this exercise if it causes a change the agent was never allowed to make.

In the test environment, interrupt a connection after an update may have reached the purchasing system but before the agent gets confirmation. Have the operator inspect the purchasing record before retrying. The difficult part is that the first action might already have worked. Decide how the workflow recognizes completed work and who investigates a mismatch. An error message alone cannot tell the operator that nothing changed.

UiPath describes processes that pause and resume, with context passed to people. Workato documents audit records for runs and configuration changes.^4,5,6

Also try a repeated event, an absent approver and a supplier correction arriving while an earlier draft waits. For each, agree whether to stop, replace the draft, ask again for approval or change the owner. Read the run log alongside the purchasing record and the list of unresolved cases. The log may help explain an attempt without proving that the system received exactly one intended update. Keep that distinction visible in the result.^4,6

Nexus describes continuing improvement after its first version. Relevance AI describes training the customer’s staff after deployment. Workato offers onboarding and training packages.^7,8,9

Turn the service offer into named duties. Who manages credentials, fixes connections, changes process rules, approves model or agent updates and decides unresolved business cases? Write support hours in the plant’s local time and name a backup when the main contact is absent. If coverage misses a shift, agree how that shift uses the manual process before releasing the agent. Have both sides accept this division of work in writing.^7,8,9

Try a shift card with the workflow and approved version, latest completed case, waiting cases and owners, blocked connections, forbidden actions and pause control. Add the manual fallback and next review time. Give it to the receiving operator and ask them to find a pending case, explain the evidence and pause the workflow. That exercise shows whether the handover is usable. Attending a training presentation does not show the same thing.

Microsoft documents release pipelines and approval gates. Relevance AI says changes rerun evaluations before publishing and lists draft, active and pinned agent versions.^10,11,12

Bring together the agreed scope, connections, permission checks, difficult cases, open defects, operating procedure and support agreement. Keep the expected and actual results with the version tested. Ask the business owner to accept the process result and the system owner to accept access and recovery. The supplier’s delivery milestone should point to that evidence. It cannot replace the plant’s decision that the work is ready to use.^10,11,12

Release only the agreed work after mandatory cases pass and the operating owners accept their duties. Narrow it to reading and drafting if updates remain unreliable. Stop and use the manual procedure if forbidden changes, unexplained disclosure or unreconciled updates appear. When a connection or process changes later, repeat the affected cases. Keep the new version and decision alongside the old record so the next shift knows which instructions apply.