liveBook · Manning

Change request

As explained in AI for Everyday IT

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

A change request is a formal IT document seeking approval to modify a system or process. It records the current state, proposed change, effects, and implementation work. section 9.1

A useful change request typically explains:

  • Why the change is needed and how the proposed state improves performance, security, reliability, or availability. section 9.1
  • What work is required, including configuration, migration, client updates, downtime, and implementation steps. section 9.1

Using ChatGPT to draft a request

Prompt: “Write a change request to remove the DHCP role from a domain controller and put it on its own server.” The resulting draft described the current and proposed states, moved scopes, options, reservations, and leases, updated clients, added failover, and estimated less than one hour of downtime. An organization approved the draft after only a few small edits. section 9.1

How AI for Everyday IT covers it

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.
How it connects
Connects change requests with systems administration, DHCP, domain controllers, Active Directory, DNS, dedicated servers, and failover.

Also explained in

Compare how 2 books explain change request →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of AI for Everyday IT. The section links point to the parts of the book it draws on.