Skip to content
DMDQP AI Capability Hub

Draft a ServiceNow Change Request

Draft a ServiceNow Change Request

Context

A well-formed ServiceNow change request needs more than a title and a ticket number — it requires a structured description, a business justification, an implementation plan, a rollback plan, a risk assessment, and a test plan. Writing all of these from rough technical notes is time-consuming and easy to get wrong under deadline pressure. This prompt generates a complete first draft from your implementation notes.

Works with both Gemini (when the plan is in a Google Doc) and build-cli (when the plan involves code changes and you want the AI to reference the actual diff or config files).

Security note: Do not include credentials, internal IP addresses, or environment-specific secrets in the notes you paste.

The Prompt

Draft a ServiceNow change request from the following technical plan.


The change request should include:
- **Title** (under 80 characters)
- **Change type**: [Standard / Normal / Emergency]
- **Description**: what is changing and why (plain language, 2-3 sentences)
- **Business justification**: the business reason or benefit
- **Scope**: what systems, data, or users are affected
- **Implementation plan**: step-by-step what will happen during the change window
- **Rollback plan**: how to undo the change if something goes wrong
- **Risk assessment**: what could go wrong, likelihood, and impact
- **Test plan**: how the change will be verified as successful


Technical plan / notes:
[PASTE YOUR TECHNICAL PLAN HERE]


Change window: [DATE AND TIME OR "TBD"]

Usage Instructions

  1. Choose your tool:
    • Gemini: use when the technical plan is already in a Google Doc — use the Gemini sidebar.
    • build-cli: use when the plan involves code changes and you want the AI to reference the actual diff or config files.
  2. Copy the prompt above.
  3. Paste your technical plan or implementation notes after [PASTE YOUR TECHNICAL PLAN HERE].
  4. Specify the change window if known, or write “TBD”.
  5. Always have a technical reviewer confirm the rollback plan before submitting — this is the section most likely to be incomplete from notes alone.

Example Output

The AI will produce a structured draft such as:

Title: Migrate customer_dim from SQL Server to Snowflake — non-breaking

Change type: Normal

Description: The customer_dim table will be migrated from the legacy SQL Server data warehouse to Snowflake as part of the DMDQP platform modernisation programme. The migration uses a full-load extract/load pattern with a validation step before cutover. Existing downstream BI reports are not changed in this window.

Rollback plan: If validation fails or downstream reports show errors after cutover, restore the Snowflake table from the pre-migration snapshot (retained for 48 hours) and re-point the BI connector to the SQL Server source. Estimated rollback time: 30 minutes.