Specialist 1
Order evidence agent
Retrieve the purchase order and supplier update. Preserve the original commitment and source record identifiers.
Normalized order evidence
Procurement / Purchasing / Solution blueprint
Supplier delivery exceptions
A supplier changes a delivery date. Keep the order, the decision, and the people affected connected.
Business problem & expected outcomes
The challenge behind
supplier delivery exceptions.
Delivery updates arrive across email and purchasing tools. Buyers have to reconstruct the commitment before they can assess a change.
What this workflow is designed to deliver
Exception brief
Compare the new date with the recorded commitment, identify missing facts, and prepare an exception brief for the buyer.
How to measure the improvementTime to prepare a complete exception brief; completeness of evidence; unauthorized changes blocked.
Start with the right information.
Purchase orders, supplier correspondence, promised dates, and owner assignments.
Interactive workflow diagram
From supplier update
to a clear next step.
Compare the new date with the recorded commitment, identify missing facts, and prepare an exception brief for the buyer.
ProcurementSelect a stage to explore
Context
Supplier update
Purchase orders, supplier correspondence, promised dates, and owner assignments.
Prepared outputException brief
Designed around the work
Specialists with clear responsibilities.
An orchestrator passes evidence between specialists, checks that required facts are present, and holds the workflow at the review boundary.
Specialist 2
Delivery impact agent
Compare promised and proposed dates, identify affected items, and flag missing planning context.
Impact assessment and open questions
Specialist 3
Review coordinator
Combine the evidence and assessment into a buyer brief. Route the proposed change to the accountable buyer.
Buyer review package
Connected tools & context
Bind only the operations this workflow needs. Keep credentials in ART and choose the permitted tools explicitly.
ERPNext · Get Purchase Order
Read-only lookupUse erpnext_get_purchase_order to read the order by its document ID through an authorized ERPNext connection. Include the record version with the evidence used for the decision.
Dynamic tables
Project & environment scopeStore source correspondence in buckets and track the original date, proposed date, decision, and owner in a dynamic table.
The decision boundary
Require the buyer’s approval before writing a revised commitment to the purchasing system.
ART product mapping
Components used.
Chosen for this case.
Agent Lab prepares the work described below. These are the capabilities that support this workflow.
Agent Lab
Connectors & MCP
Retrieve the required records through scoped tools; begin with read-only access.
Datalake
Dynamic tables
Track the case, owner, source references, and review state as structured records.
Agent Lab
Multi-agent orchestration
Coordinate specialist agents with explicit inputs, handoffs, and review checkpoints.
Agent Lab
Execution governance
Validate required facts and evaluate explicit rules before an action can proceed.
Agent Lab
Human approvals
Pause the proposed action for the designated owner to review its evidence.
The implementation, step by step
From source context
to a reviewed result.
- 01
Supplier update
Purchase orders, supplier correspondence, promised dates, and owner assignments.
Agree the trigger or manual request, record identifiers, and the process owner. - 02
Compare commitments
Compare the new date with the recorded commitment, identify missing facts, and prepare an exception brief for the buyer.
Define instructions, permitted tools, and the expected output. Keep missing information explicit. - 03
Buyer review
Require the buyer’s approval before writing a revised commitment to the purchasing system.
Configure the selected policy or approval capabilities before enabling write actions. - 04
Exception brief
Time to prepare a complete exception brief; completeness of evidence; unauthorized changes blocked.
Compare outputs with reviewed examples and test incomplete, conflicting, and unauthorized inputs.
Inside the ART workspace
Explore the agent configuration behind this example. Select a screen to inspect it at full size.
Agent Lab / Configured example
Configure the supplier review agent
Agent Lab / Configured example
Define a buyer-ready output
Before you build
What this implementation needs.
Connectors & MCP
Source-system APIs or MCP tools, scoped credentials, and an integration owner.
Dynamic tables
Typed fields, record identifiers, relationships, and a table-retention policy.
Multi-agent orchestration
A responsibility for each agent, typed handoff data, stopping conditions, and an accountable workflow owner.
Execution governance
Registered actions, required facts, and explicit allow, block, or approval rules.
Human approvals
Named reviewer roles, escalation ownership, and timeout and rejection behavior.
Also prepare an ART project and environment, the model configuration appropriate to your agent, an accountable process owner, and approved sample data.
Authority stays with your team
Define the boundary
before enabling the action.
Require the buyer’s approval before writing a revised commitment to the purchasing system.
Explore execution governanceConnect deliberately.
Map the source material and responsible owners first. Where the selected components require system access, configure scoped APIs or tools. A document-based pilot can start with approved material already available in the workspace.
Make each handoff inspectable.
Keep source references with the prepared output and review representative results before expanding scope. If the implementation includes executable actions, define their required facts and authority first. Apply retention to any stored records, files, or memory used by the case.
Build evidence from your own work
Start small.
Agree what good looks like.
What to measure for this case
Time to prepare a complete exception brief; completeness of evidence; unauthorized changes blocked.
Establish a baseline
Choose a bounded sample of completed cases, record the current process, and agree review criteria with the process owner.
Run in review mode
Use approved sample data and read-only connections. Compare prepared outputs with reviewer expectations, including incomplete and conflicting inputs.
Expand with approval
Enable a limited set of actions only after the team accepts the results. Check approvals, failures, and handoffs before increasing scope.
Make it your workflow
Try this approach
in Agent Lab.
Start with supplier update. Connect your approved tools, configure the review boundary, and adapt the output to your team's process.
Try Workflow in Agent Lab
Open your ART workspace to configure this use case.
Discuss the setup with usIndustry & department library
Find your next use case.
3 use cases in Procurement
ProcurementWorkflow design
- ContextSupplier documents
- Agent LabCheck required evidence
- Your teamProcurement review
Prepared outputOnboarding checklist
Solution blueprint
Supplier onboarding reviews
Turn a collection of supplier documents into a review the procurement team can act on.
Used in this case
Explore the implementation - File storage
- Dynamic tables
- Agent Skills
- Multi-agent orchestration
- Human approvals
Inside Agent LabConfigured example
Solution blueprint
Purchase request validation
Prepare a complete requisition before the buyer reviews it.
Used in this case
Explore the implementation - Agent Skills
- Execution governance
- Human approvals
ProcurementWorkflow design
- ContextRenewal date
- Agent LabCollect terms & evidence
- Your teamCommercial review
Prepared outputRenewal preparation brief
Solution blueprint
Contract renewal review preparation
Bring renewal dates and contract evidence into the same review.
Used in this case
Explore the implementation - Knowledge Base
- File storage
- Dynamic tables
Procurement / Let’s explore the fit
Discuss your
industry use case.
Tell us where work slows down. We’ll discuss how ART could fit your process, your systems, and the decisions your team needs to own.
Pull gently. Let the conversation move.