A change request checked, scheduled and approved before anything runs.
The agent lists what the change touches, checks it against your change policy and proposes a window. The change owner approves. A window inside a change freeze is refused, and the agent never runs the change itself.
DesignedThe steps and approvals are designed. It has not run yet.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
An AI agent for IT change approval prepares a change for the person who accepts its risk. Before a change to a live service is approved, someone has to find what depends on it, check that the test evidence and the back-out plan are attached, look at the change calendar and tell the owners of each affected service. The decision is quick once that work is done. The work is what takes the time.
This workflow is designed. The steps below are how we build it in a pilot. It has not run in the sandbox yet.
What the change owner gets
- The change with every dependent service listed, from your configuration records.
- The policy check: the change class, the evidence attached and any gap named.
- A proposed window that is clear of every freeze on the calendar.
The agent prepares and books the change. Your engineer or your release pipeline runs it, under its own permission. The IT page shows the other IT workflows, and the full library is on the workflows page.
One configuration change, from the request to the result.
The service, the change and the calendar are examples. The refusal comes from the calendar. The approval comes from the person who owns the risk.
- 01Ticketing
Take the change request from the change queue and receive a credential for this change only.
- Who approves
- No approval on this step
- On the record
- credential issued · one change
- 02Source control
Read the proposed configuration change and its script in source control.
- Who approves
- No approval on this step
- On the record
- read-change · allowed
- 03In-house tool
List the services that depend on the target, from your configuration records.
- Who approves
- No approval on this step
- On the record
- list-dependencies · allowed
- 04Documents
Check the request against the change policy: the class, the test evidence and the back-out plan. The back-out plan is missing, and the agent asks the requester for it.
- Who approves
- No approval on this step
- On the record
- check-policy · allowed · back-out plan requested
- 05Office suite
Try to book the window the requester asked for. It falls inside a freeze on the change calendar, so the step is refused. The agent proposes the next open window.
- Who approves
- No approval on this step
- On the record
- book-window · refused · change freeze
- 06Ticketing
The change and the proposed window. The step waits until the change owner approves it.
- Who approves
- Change owner
- On the record
- approve-change · approved by change owner
- 07Email
Book the approved window and send the notice to the owner of each dependent service.
- Who approves
- No approval on this step
- On the record
- notify-service-owners · allowed
- 08Ticketing
After the engineer runs the change, attach the result and close the request.
- Who approves
- No approval on this step
- On the record
- close-change · allowed · result attached
The systems, by type
We name systems by type. Yours are named in the assessment.
Ticketing
Holds the change queue and the approval. The agent prepares the request there and closes it with the result.
Source control
Holds the change and its script. The agent reads them. It does not merge or run them.
In-house tool
Your configuration records: which services depend on which systems.
Documents
Holds the change policy and the evidence each class of change needs.
Office suite
Holds the change calendar and its freezes, if you keep them in a shared calendar.
Carries the notice to the owner of each dependent service.
The approval, the refusal, the record
- A person approves: The change and the proposed window. The step waits until the change owner approves it.A change to a live service is a risk the change owner accepts for the business, so the booking waits for that person.
- Refused: Try to book the window the requester asked for. It falls inside a freeze on the change calendar, so the step is refused. The agent proposes the next open window.A freeze is the business saying no change in that window, and a request does not override it, so only a person may grant an exception.
- On the recordThe request, the dependencies found, the policy check and the gap it raised, the refused booking with its reason, the approval with a name, the notices and the result.
What goes on the record
- credential issued · one change
- read-change · allowed
- list-dependencies · allowed
- check-policy · allowed · back-out plan requested
- approve-change · approved by change owner
- notify-service-owners · allowed
- close-change · allowed · result attached
One record per step, as designed. This workflow has not run yet.
What it does not do
- It does not run the change. Your engineer or your release pipeline does, under its own permission.
- It does not judge whether a change is technically sound. Your reviewers and the change owner do.
- Its dependency list is as complete as your configuration records. The assessment says where they are ready.
Questions and answers
Tell us about one workflow.
We will say whether an agent should do it, and what the first step costs.
A senior member of the team replies within two business days.