Agent responsibility
Assemble impact evidence
Check required facts and prepare an evidence packet with missing items clearly identified.
Change review pack
IT & operations / IT service management / Solution blueprint
Change request evidence preparation
Make change requests easier for the review board to assess.
Business problem & expected outcomes
The challenge behind
change request evidence preparation.
Change requests omit dependency, rollback, or validation information.
What this workflow is designed to deliver
Change review pack
Check required facts and prepare an evidence packet with missing items clearly identified.
How to measure the improvementEvidence completeness; requests returned by the change board.
Start with the right information.
Change templates, system dependencies, rollout plans, and rollback evidence.
Interactive workflow diagram
From change request
to a clear next step.
Check required facts and prepare an evidence packet with missing items clearly identified.
IT & operationsSelect a stage to explore
Context
Change request
Change templates, system dependencies, rollout plans, and rollback evidence.
Prepared outputChange review pack
Designed around the work
A focused agent. The right capabilities.
Give the agent the context and tools this process needs, with an explicit output and an accountable owner.
Connected tools & context
Bind only the operations this workflow needs. Keep credentials in ART and choose the permitted tools explicitly.
Agent Skills
Project & environment scopePackage the checklist, instructions, and expected output as a reusable skill.
File storage
Project & environment scopeRetain source references and review state only where this implementation requires persistence.
The decision boundary
The authorized change board approves execution; a missing mandatory fact blocks progression.
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
Agent Skills
Package the checklist, instructions, and expected output as a reusable skill.
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.
Datalake
File storage
Keep the supporting files accessible within the review’s project and environment.
The implementation, step by step
From source context
to a reviewed result.
- 01
Change request
Change templates, system dependencies, rollout plans, and rollback evidence.
Agree the trigger or manual request, record identifiers, and the process owner. - 02
Assemble impact evidence
Check required facts and prepare an evidence packet with missing items clearly identified.
Define instructions, permitted tools, and the expected output. Keep missing information explicit. - 03
Change-owner review
The authorized change board approves execution; a missing mandatory fact blocks progression.
Configure the selected policy or approval capabilities before enabling write actions. - 04
Change review pack
Evidence completeness; requests returned by the change board.
Compare outputs with reviewed examples and test incomplete, conflicting, and unauthorized inputs.
Before you build
What this implementation needs.
Agent Skills
A process checklist, example inputs, and a reviewer-approved output format.
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.
File storage
A document inventory, resource access scopes, and a file-retention policy.
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.
The authorized change board approves execution; a missing mandatory fact blocks progression.
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
Evidence completeness; requests returned by the change board.
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 change request. 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 IT & operations
IT & operationsWorkflow design
- ContextIncident signal
- Agent LabRetrieve the runbook
- Your teamResponder review
Prepared outputResponse brief
Solution blueprint
Incident response coordination
Turn an alert into a contextual handoff for the operator.
Used in this case
Explore the implementation - Multi-agent orchestration
- Events & triggers
- Connectors & MCP
- Knowledge Base
- Human approvals
IT & operationsWorkflow design
- ContextAccess request
- Agent LabCheck role & purpose
- Your teamAccess-owner review
Prepared outputDecision-ready request
Solution blueprint
Access request triage
Prepare complete access requests for the people who authorize them.
Used in this case
Explore the implementation - Agent Skills
- Execution governance
- Human approvals
IT & operationsWorkflow design
- ContextOperational question
- Agent LabRetrieve runbook context
- Your teamOperator decision
Prepared outputReferenced next steps
Solution blueprint
Runbook knowledge assistance
Help operators find the procedure that fits the incident.
Used in this case
Explore the implementation - Knowledge Base
- Connectors & MCP
IT & operations / 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.
