
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
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.
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 process | Chased in the meeting | Prepared by an agent |
|---|---|---|
| Missing fields | Discovered at the board | Sent back to the requester before the meeting |
| Conflicts | Noticed if someone remembers | Overlapping windows and shared systems flagged |
| Context | Each member digs it up | Recent incidents and past changes to the same system attached |
| The packet | Assembled by hand, if at all | One packet per meeting, in your format |
| The decision | The board's | Still the board's |
How it works, step by step
The agent checks and assembles. The board judges risk and decides.
Take in the request
Check it against your required fields
Flag conflicts
Attach the context
Human gate: the board approves, defers or refuses
Record the decision
Follow up after the window
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
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?
| Question | General request | Change request |
|---|---|---|
| Who decides | Whoever owns the queue | A change board |
| What must be included | A description | A plan, a rollback, test evidence and a window |
| What can go wrong | A delay | An outage |
| What is recorded | The response | The decision, the conditions and the outcome |
Related reading
- Approval gates: why each approval has one accountable name.
- Internal request routing and triage: where requests that are not changes go.
- Exception detection and routing across your ops stack: catching a change that went wrong.
