Complete AI Training

AI agent for technology managers

Change Request Risk Review Agent

Change requests that reach the board complete, conflict-free and risk-rated

Change Request Risk Review Agent: what goes in, what the agent does and what you get

What it does

Risky changes slip through because reviewers only see a short request form. For each change request, this agent checks for missing rollback steps, conflicting changes in the same window and the systems affected using your inventory. If something fails, it asks the requester to complete the form instead of passing it on. It then rechecks after the requester updates it. It also rates the change risk from its scope, timing and history of past failures. The change board approves or rejects. Edge case: two unrelated changes touch the same database cluster on the same night, so the agent flags the conflict.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueYes, continueApprovedNoNo 1 STARTS WHEN Change request is submitted 2 USES A TOOL Read the request and the affected systems 3 USES A TOOL Check the change calendar for conflicts in thewindow 4 CHECKS THE RESULT Is there a clear, tested rollback plan? If not: send the request back to the requester with themissing detail. Back to step 2. 5 CHECKS THE RESULT Is the window free of conflicting changes? If not: propose another window or merge with the otherchange. Back to step 3. 6 DOES Rate risk from scope, timing and past failures 7 DOES Prepare a summary for the board 8 YOU APPROVE Change board approves or rejects 9 RESULT Decision recorded on the change ticket
Read the steps as a list
  1. Change request is submitted
  2. Read the request and the affected systems
  3. Check the change calendar for conflicts in the window
  4. Is there a clear, tested rollback plan?If not: send the request back to the requester with the missing detail. Back to step 2.
  5. Is the window free of conflicting changes?If not: propose another window or merge with the other change. Back to step 3.
  6. Rate risk from scope, timing and past failures
  7. Prepare a summary for the board
  8. Change board approves or rejectsThe agent waits here for your OK.
  9. Decision recorded on the change ticket

How it decides

A request is ready when it has a tested rollback, no conflicts in the window and a complete list of affected systems.

  • Require a rollback plan for every change
  • Flag any other change on the same system in the window
  • Rate risk higher for changes during peak periods
  • Use past incidents on the same system as a risk input

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Risk rating rules
  • Required fields
  • Peak periods to avoid
  • Time the requester has to respond

What keeps you in control

It always asks you first

  • Change board approves or rejects each change

Hard limits

  • Never approves changes
  • Never edits a request without the requester

It stops when

  • Done: the request is complete and a decision is recorded
  • Stop: the requester does not respond within the set time

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensA request to patch a database cluster on Friday night had no rollback step. The agent returned it to the requester, who added one. The next check found a network change planned for the same window on the same cluster. The agent proposed Saturday at 2 am. The board approved the new time.

More agents for technology managers