Image
Workflow
Operations

Change request intake and change board packet preparation

Change requests arrive missing the rollback plan, and the change board spends its meeting asking for it. An agent checks each request against your required fields, gathers the context and builds the packet. The board approves or refuses every change.

The short answer

Short answer

An agent takes in change requests by checking each one against the fields your process requires, such as the plan, the rollback, the test evidence, the window and the owner, and sending incomplete requests back to the requester with what is missing.

It gathers the board's context into one packet. The change board approves, defers or refuses every change.

Today

Why does the change board spend its meeting chasing paperwork?

The meeting starts and half the requests are not ready. One has no rollback plan, another has no test evidence, a third conflicts with a maintenance window nobody noticed. The board spends its time asking for what should have been in the request, defers the incomplete ones to next week, and the changes that were ready wait behind them.

Who is this for?

An IT lead, change manager or operations engineer at a company that runs a change board, even an informal weekly one. It suits teams with a change request form or template and a list of what a complete request must contain. Assessing risk and approving changes stay with the board.

What changes when requests arrive complete?

Part of the processChased in the meetingPrepared by an agent
Missing fieldsDiscovered at the boardSent back to the requester before the meeting
ConflictsNoticed if someone remembersOverlapping windows and shared systems flagged
ContextEach member digs it upRecent incidents and past changes to the same system attached
The packetAssembled by hand, if at allOne packet per meeting, in your format
The decisionThe board'sStill the board's

How it works, step by step

The agent checks and assembles. The board judges risk and decides.

01

Take in the request

Requests submitted through your form or queue are logged with the requester, the systems affected and the proposed window.
02

Check it against your required fields

It confirms the request contains everything your process requires, such as a plan, a rollback, test evidence and a named implementer. A request missing any of them goes back to the requester with the gaps listed, and does not reach the packet until it is complete.
03

Flag conflicts

It checks the proposed window against other approved changes, maintenance windows and freeze periods, and lists any overlap on the same system.
04

Attach the context

For each request it attaches recent incidents and past changes involving the same systems, linked to their records, so board members do not have to look them up.
05

Human gate: the board approves, defers or refuses

The packet goes to the change board, which assesses the risk and approves, defers or refuses each change. The agent assesses no risk and approves nothing. NIST describes a configuration control board, also called a change control board, as a group of qualified people with responsibility for the process of controlling and approving changes throughout the development and operational lifecycle. Judging security impact is likewise a person's job: NIST defines security impact analysis as the analysis conducted by an organizational official to determine the extent to which a change to an information system has affected the security state of that system.
06

Record the decision

It records each decision with the board members present and any conditions, and tells the requester.
07

Follow up after the window

After the change window it asks the implementer whether the change succeeded or was rolled back, and records the outcome for the next board.

Never with a change

What does the agent never do with a change?

Approve

The board decides every change.

Assess risk. It gathers context. Risk is judged by people.

Implement

The named implementer makes the change.

Waive a required field

Only the board can accept a request with something missing.

Expedite on its own. Emergency changes follow your emergency process, with its own approver.

Where this fits

Workflow / Automate a Workflow

Taking one change from request to recorded outcome is a single process: Tier 1, Automate a Workflow. Your change template is what the readiness checklist will test first. Changes that run as scripted procedures can use the gated execution described in shadow mode before they are trusted, and failed changes feed exception detection and routing across your ops stack. The board's sign-off follows approval gates. The use case library lists neighbouring workflows.

How does change intake differ from general request routing?

QuestionGeneral requestChange request
Who decidesWhoever owns the queueA change board
What must be includedA descriptionA plan, a rollback, test evidence and a window
What can go wrongA delayAn outage
What is recordedThe responseThe decision, the conditions and the outcome
Tier 1 / Prove
How It Works

Questions, answered

No. If your board pre-approves a class of standard change, that standing approval is the board's decision, recorded with its scope. The agent checks a request fits that scope and logs it under the board's approval.
AI Opportunity Audit · Change management

Bring complete changes to the board

Bring last month's change requests and count how many reached the board incomplete.