liveBook · Manning

Change request

A change request is a proposal for modifying a system, service, process, or design, submitted for review and discussion.

How 2 Manning books explain it

Shipping Go: Develop, deliver, discuss, design, and go again

An RFC is a written proposal for a software design or change that invites review and discussion before implementation.

How it is used
Prevents premature implementation by making designs reviewable before development.
How deep it goes
Explains the practice and repository placement but stops short of prescribing an RFC template or approval workflow.
Examples
Uses a rushed refactor and repository design documents as concrete examples.
What you can do after
Apply it by documenting a design in the repository and inviting discussion before writing the implementation.

Read how Shipping Go: Develop, deliver, discuss, design, and go again explains change request →

AI for Everyday IT

A change request is a formal IT document seeking approval to modify a system, service, or process.

How it is used
Supports systems administration by accelerating approval documentation for system and process changes.
How deep it goes
Defines the document and demonstrates its sections through a detailed DHCP migration, without covering approval governance beyond small edits.
Examples
Uses a ChatGPT-generated request for moving DHCP from a domain controller to a dedicated server.
What you can do after
Apply it via ChatGPT to draft an approval request, then make the small edits needed for organizational acceptance.

Read how AI for Everyday IT explains change request →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.