{"id":33697,"date":"2026-10-13T16:23:25","date_gmt":"2026-10-13T16:23:25","guid":{"rendered":"https:\/\/writegenic.ai\/content\/?p=33697"},"modified":"2026-10-13T16:23:28","modified_gmt":"2026-10-13T16:23:28","slug":"what-is-change-request-form","status":"publish","type":"post","link":"https:\/\/writegenic.ai\/content\/what-is-change-request-form\/","title":{"rendered":"Change Request Form: Every Field Explained, With a Completed Example"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>Quick answer:<\/strong> A change request form is the document someone fills in to formally ask for a change to an approved project. It records what the change is, why it&#8217;s wanted, what it will cost in money and time, and who decided. Without it, changes happen quietly and the project quietly breaks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every project gets change requests. The question is whether they go through a door or a window.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A good form is the door. It takes ten minutes to fill in, it makes the cost visible before anyone commits, and it leaves a record of who said yes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This guide explains every field, gives you the template, and \u2014 the part most guides skip \u2014 shows a <strong>completed<\/strong> form with real numbers, so you can see what good entries actually look like.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ol><li><a href=\"#what-is-a-change-request-form\">What Is a Change Request Form?<\/a><\/li><li><a href=\"#when-do-you-actually-need-a-change-request\">When Do You Actually Need a Change Request?<\/a><\/li><li><a href=\"#what-are-the-four-types-of-change-request\">What Are the Four Types of Change Request?<\/a><\/li><li><a href=\"#what-fields-should-a-change-request-form-include\">What Fields Should a Change Request Form Include?<\/a><\/li><li><a href=\"#what-goes-in-the-change-request-form-template\">What Goes in the Change Request Form Template?<\/a><\/li><li><a href=\"#how-do-you-set-a-priority\">How Do You Set a Priority?<\/a><\/li><li><a href=\"#how-do-you-assess-the-impact\">How Do You Assess the Impact?<\/a><\/li><li><a href=\"#what-about-the-cost-of-not-changing\">What About the Cost of Not Changing?<\/a><\/li><li><a href=\"#what-does-a-completed-change-request-example-look-like\">What Does a Completed Change Request Example Look Like?<\/a><\/li><li><a href=\"#who-approves-a-change-request\">Who Approves a Change Request?<\/a><\/li><li><a href=\"#what-happens-if-a-change-request-is-rejected-or-deferred\">What Happens If a Change Request Is Rejected or Deferred?<\/a><\/li><li><a href=\"#how-do-you-number-change-requests\">How Do You Number Change Requests?<\/a><\/li><li><a href=\"#what-is-a-change-log-and-what-goes-in-it\">What Is a Change Log, and What Goes in It?<\/a><\/li><li><a href=\"#what-are-the-8-most-common-change-request-mistakes\">What Are the 8 Most Common Change Request Mistakes?<\/a><\/li><li><a href=\"#what-software-handles-change-request-forms-best\">What Software Handles Change Request Forms Best?<\/a><\/li><li><a href=\"#how-does-writegenic-ai-fit-in\">How Does Writegenic AI Fit In?<\/a><\/li><li><a href=\"#frequently-asked-questions\">Frequently Asked Questions<\/a><\/li><\/ol><\/nav><\/div>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 id=\"what-is-a-change-request-form\" class=\"wp-block-heading\">What Is a Change Request Form?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A change request form is a short document used to ask for a change to something that has already been agreed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It does four jobs:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Captures the ask<\/strong> in words everyone can read later<\/li>\n\n\n\n<li><strong>Forces the cost to the surface<\/strong> before anyone starts work<\/li>\n\n\n\n<li><strong>Routes it to the right person<\/strong> to say yes or no<\/li>\n\n\n\n<li><strong>Creates a record<\/strong> of what was decided and why<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">That third job is the one people underestimate. Most damage from uncontrolled change isn&#8217;t the change itself \u2014 it&#8217;s that nobody with authority ever saw it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Change request vs change order<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">These are two stages of the same thing, and mixing them up causes real confusion.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><\/th><th>Change request<\/th><th>Change order<\/th><\/tr><\/thead><tbody><tr><td>What it is<\/td><td>A proposal to change something<\/td><td>The instruction to go ahead<\/td><\/tr><tr><td>When<\/td><td>Before the decision<\/td><td>After approval<\/td><\/tr><tr><td>Who writes it<\/td><td>Anyone affected<\/td><td>Usually the project manager or contracts team<\/td><\/tr><tr><td>Binding?<\/td><td>No<\/td><td>Yes \u2014 often a contract variation<\/td><\/tr><tr><td>Can be rejected<\/td><td>Yes<\/td><td>No, it&#8217;s already decided<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The order is always:<\/strong> request \u2192 assess \u2192 decide \u2192 order.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If someone hands you a &#8220;change order&#8221; with no request behind it, something has been skipped.<\/p>\n\n\n\n<h2 id=\"when-do-you-actually-need-a-change-request\" class=\"wp-block-heading\">When Do You Actually Need a Change Request?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This is the question people really have, and almost no guide answers it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The test is simple: <strong>has the thing you&#8217;re changing already been approved and baselined?<\/strong><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Situation<\/th><th>Needs a form?<\/th><\/tr><\/thead><tbody><tr><td>Fixing a bug in work you&#8217;re still building<\/td><td>No. That&#8217;s just doing the work<\/td><\/tr><tr><td>Changing a requirement the client signed off<\/td><td><strong>Yes<\/strong><\/td><\/tr><tr><td>Adding a feature nobody asked for at the start<\/td><td><strong>Yes<\/strong><\/td><\/tr><tr><td>Correcting a typo in an approved document<\/td><td>No. Log it as an administrative change<\/td><\/tr><tr><td>Swapping a supplier named in the contract<\/td><td><strong>Yes<\/strong><\/td><\/tr><tr><td>Reordering tasks in your own schedule, same dates<\/td><td>No<\/td><\/tr><tr><td>Moving a milestone date<\/td><td><strong>Yes<\/strong><\/td><\/tr><tr><td>Spending money you already had approved<\/td><td>No<\/td><\/tr><tr><td>Spending more than was approved<\/td><td><strong>Yes<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">The one-line rule<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>If someone outside your team would be surprised to learn about it, it needs a form.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That catches almost everything that matters and excludes the day-to-day work that doesn&#8217;t.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What if you&#8217;re not sure?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Raise the form. A rejected request costs ten minutes. An unapproved change discovered at handover costs considerably more.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">How your organisation sets these boundaries belongs in your <a href=\"https:\/\/writegenic.ai\/content\/what-is-configuration-management-plan\">configuration management plan<\/a>, which defines what&#8217;s under control and who approves changes to it.<\/p>\n\n\n\n<h2 id=\"what-are-the-four-types-of-change-request\" class=\"wp-block-heading\">What Are the Four Types of Change Request?<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Type<\/th><th>What it is<\/th><th>Approval route<\/th><\/tr><\/thead><tbody><tr><td><strong>Standard<\/strong><\/td><td>A pre-approved, routine change you&#8217;ve agreed in advance<\/td><td>No decision needed \u2014 just log it<\/td><\/tr><tr><td><strong>Minor<\/strong><\/td><td>Affects a baselined item, but not scope, cost or the end date<\/td><td>Project manager, plus one reviewer<\/td><\/tr><tr><td><strong>Major<\/strong><\/td><td>Affects scope, cost, the deadline, or a contract<\/td><td>Full change control board, plus sponsor<\/td><\/tr><tr><td><strong>Emergency<\/strong><\/td><td>Needed immediately to prevent harm or a serious failure<\/td><td>Two named people can approve on the spot, with retrospective review<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Standard changes are the useful category people forget.<\/strong> If you pre-agree that certain routine changes don&#8217;t need a decision, your board stops drowning in trivia and starts spending its time on the ones that matter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Emergency changes need a route defined in advance.<\/strong> If you don&#8217;t write one down, people will invent one under pressure \u2014 and it won&#8217;t include a record.<\/p>\n\n\n\n<h2 id=\"what-fields-should-a-change-request-form-include\" class=\"wp-block-heading\">What Fields Should a Change Request Form Include?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Around 15 to 20 fields, in five groups. More than that and people stop filling it in.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Group 1: Identification<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>What to write<\/th><\/tr><\/thead><tbody><tr><td>Change request number<\/td><td>A unique reference, e.g. CR-014<\/td><\/tr><tr><td>Project name<\/td><td>The project, not the department<\/td><\/tr><tr><td>Raised by<\/td><td>A named person, plus their role<\/td><\/tr><tr><td>Date raised<\/td><td>The date, not &#8220;this week&#8221;<\/td><\/tr><tr><td>Contact details<\/td><td>So the assessor can ask questions<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Group 2: The change itself<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>What to write<\/th><\/tr><\/thead><tbody><tr><td>Title<\/td><td>One line someone can scan. &#8220;Add loyalty points at checkout&#8221;<\/td><\/tr><tr><td>Description<\/td><td>What exactly changes. Be specific enough that two people would build the same thing<\/td><\/tr><tr><td>Reason<\/td><td>Why it&#8217;s wanted. The business reason, not &#8220;the client asked&#8221;<\/td><\/tr><tr><td>Type<\/td><td>Standard, minor, major or emergency<\/td><\/tr><tr><td>Priority<\/td><td>See the scale below \u2014 not a guess<\/td><\/tr><tr><td>Date needed by<\/td><td>And say whether that&#8217;s a hard deadline or a preference<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Group 3: Impact<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>What to write<\/th><\/tr><\/thead><tbody><tr><td>Items affected<\/td><td>Which deliverables, documents or WBS codes change<\/td><\/tr><tr><td>Effort<\/td><td>Days of work, by role<\/td><\/tr><tr><td>Cost<\/td><td>The money, with your workings shown<\/td><\/tr><tr><td>Schedule impact<\/td><td>Days added, and whether it touches the critical path<\/td><\/tr><tr><td>Quality and testing<\/td><td>What needs retesting, and by whom<\/td><\/tr><tr><td>New risks<\/td><td>What this change makes more likely to go wrong<\/td><\/tr><tr><td>Cost of not changing<\/td><td>Often the most important field. See below<\/td><\/tr><tr><td>Alternatives<\/td><td>What else was considered, and why this option<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Group 4: The decision<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>What to write<\/th><\/tr><\/thead><tbody><tr><td>Assessed by<\/td><td>Who did the impact assessment, and when<\/td><\/tr><tr><td>Decision<\/td><td>Approved, rejected, deferred, or more information needed<\/td><\/tr><tr><td>Conditions<\/td><td>Any strings attached to an approval<\/td><\/tr><tr><td>Reason for the decision<\/td><td>Especially important for a rejection<\/td><\/tr><tr><td>Decided by<\/td><td>Named approver, with the date<\/td><\/tr><tr><td>Signature<\/td><td>Or a recorded digital approval<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Group 5: Afterwards<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>What to write<\/th><\/tr><\/thead><tbody><tr><td>Change log reference<\/td><td>Where it&#8217;s recorded<\/td><\/tr><tr><td>Documents to update<\/td><td>Scope statement, schedule, budget, specs<\/td><\/tr><tr><td>Implemented by and when<\/td><td>Closing the loop<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The field most often missing from real forms is &#8220;reason for the decision.&#8221;<\/strong> Without it, the same rejected request reappears in three months and nobody can remember why it was turned down.<\/p>\n\n\n\n<h2 id=\"what-goes-in-the-change-request-form-template\" class=\"wp-block-heading\">What Goes in the Change Request Form Template?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Copy this.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>CHANGE REQUEST FORM\n\nCR number:                      Date raised:\nProject:\nRaised by:                      Role:\nContact:\n\n1. THE CHANGE\nTitle:\nDescription:\n   &#91;What exactly changes. Specific enough that two people would\n   build the same thing.]\nReason \/ business case:\nType:      \u2610 Standard   \u2610 Minor   \u2610 Major   \u2610 Emergency\nPriority:  \u2610 Critical   \u2610 High    \u2610 Medium  \u2610 Low\nDate needed by:                 Hard deadline?  \u2610 Yes  \u2610 No\n\n2. IMPACT ASSESSMENT                 Assessed by:          Date:\nItems affected (deliverables \/ documents \/ WBS codes):\n\nEffort:        ____ days   Breakdown by role:\nCost:          \u00a3______     Workings:\nSchedule:      ____ days added    Touches critical path?  \u2610 Yes  \u2610 No\n               New end date if approved:\nQuality:       Retesting required:\nRisks created:\nDependencies:  What else must change as a result:\n\nCost of NOT making this change:\nAlternatives considered:\nRecommendation:\n\n3. FUNDING\nSource:  \u2610 Contingency reserve  \u2610 New budget  \u2610 Absorbed in plan\nReserve before:  \u00a3______   Cost:  \u00a3______   Reserve after:  \u00a3______\n\n4. DECISION\nDecision:  \u2610 Approved  \u2610 Approved with conditions  \u2610 Rejected\n           \u2610 Deferred  \u2610 More information needed\nConditions:\nReason for decision:\nDecided by:                     Role:              Date:\nSignature:\n\n5. AFTER APPROVAL\nLogged in change log:  \u2610      Reference:\nDocuments to update:\nImplemented by:                 Date completed:\n<\/code><\/pre>\n\n\n\n<h2 id=\"how-do-you-set-a-priority\" class=\"wp-block-heading\">How Do You Set a Priority?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Most forms say &#8220;circle high, medium or low&#8221; and never define them. So everyone circles high, and priority stops meaning anything.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Define the scale with a response time attached:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Priority<\/th><th>When to use it<\/th><th>Decision needed within<\/th><\/tr><\/thead><tbody><tr><td><strong>Critical<\/strong><\/td><td>Work has stopped, or there&#8217;s a legal, safety or security requirement<\/td><td>1 working day<\/td><\/tr><tr><td><strong>High<\/strong><\/td><td>Affects the go-live date, a contractual commitment, or a dependent project<\/td><td>3 working days<\/td><\/tr><tr><td><strong>Medium<\/strong><\/td><td>Improves the outcome, but the project can proceed meanwhile<\/td><td>Next scheduled board meeting<\/td><\/tr><tr><td><strong>Low<\/strong><\/td><td>Would be nice. No impact if it waits<\/td><td>Batched for review at the next phase gate<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The response time is what makes the scale real.<\/strong> &#8220;Critical&#8221; means someone has to look at it tomorrow. Once that&#8217;s true, people stop marking everything critical.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One more rule: <strong>the requester proposes the priority; the assessor confirms it.<\/strong> Otherwise the loudest requester sets the queue.<\/p>\n\n\n\n<h2 id=\"how-do-you-assess-the-impact\" class=\"wp-block-heading\">How Do You Assess the Impact?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Both competing guides have fields for cost and duration, and neither says how to work them out. Here&#8217;s a method that takes about twenty minutes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Six questions, in order<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>1. What has to change?<\/strong> List every deliverable, document and task affected. If you use a work breakdown structure, list the codes. This list drives everything else.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>2. How much effort?<\/strong> Estimate in days, by role. Ask the people who&#8217;d do the work, not the person who wants the change.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>3. What does it cost?<\/strong> Effort \u00d7 day rate, plus any new purchases, licences or subcontractor costs. Show your workings on the form so the approver can check them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>4. Does it touch the critical path?<\/strong> This decides whether the project moves. Work affecting a task with float may cost money without costing time. Work on the critical path costs both.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>5. What needs retesting?<\/strong> A change to one part can invalidate testing of another. Name the test cases and who re-runs them. This is routinely forgotten and routinely expensive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>6. What new risks does it create?<\/strong> Add them to your <a href=\"https:\/\/writegenic.ai\/content\/contingency-plan-in-project-management\">risk register<\/a> with owners. A change that introduces a new high risk may not be worth it even if the direct cost looks small.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Two rules for assessment<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The person who wants the change doesn&#8217;t assess it.<\/strong> Not because anyone is dishonest, but because optimism is involuntary.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Assess before you decide, always.<\/strong> An approval given before the assessment is a commitment to an unknown number.<\/p>\n\n\n\n<h2 id=\"what-about-the-cost-of-not-changing\" class=\"wp-block-heading\">What About the Cost of Not Changing?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This field sits on most templates and is almost never explained. It&#8217;s the most underrated question on the whole form.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Every change request has two costs: doing it, and not doing it.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Change<\/th><th>Cost of doing it<\/th><th>Cost of not doing it<\/th><\/tr><\/thead><tbody><tr><td>Add a security fix<\/td><td>5 days, \u00a34,000<\/td><td>A vulnerability shipping to production<\/td><\/tr><tr><td>Add a requested feature<\/td><td>18 days, \u00a314,400<\/td><td>Same work next year, with rework on top<\/td><\/tr><tr><td>Change supplier<\/td><td>10 days, \u00a38,000<\/td><td>Continued late deliveries<\/td><\/tr><tr><td>Improve a screen&#8217;s design<\/td><td>6 days, \u00a34,800<\/td><td>Nothing. It works fine<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Look at the last row. If the cost of not changing is &#8220;nothing,&#8221; you&#8217;ve found a change you should reject \u2014 however much someone wants it.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Three ways to express it<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Deferred cost.<\/strong> &#8220;Doing this in phase 2 would cost \u00a319,000 because of rework, against \u00a314,400 now.&#8221;<\/li>\n\n\n\n<li><strong>Opportunity cost.<\/strong> &#8220;Marketing expects this to raise repeat purchases. Without it, that benefit doesn&#8217;t arrive.&#8221;<\/li>\n\n\n\n<li><strong>Risk cost.<\/strong> &#8220;Without this, we carry a compliance risk into go-live.&#8221;<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Be honest when the answer is &#8220;no real cost.&#8221; A form that always justifies the change isn&#8217;t an assessment \u2014 it&#8217;s advocacy.<\/p>\n\n\n\n<h2 id=\"what-does-a-completed-change-request-example-look-like\" class=\"wp-block-heading\">What Does a Completed Change Request Example Look Like?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Here&#8217;s a filled change request example with numbers that reconcile.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Project:<\/strong> E-commerce replatform \u00b7 Budget \u00a3210,000 \u00b7 Go-live 4 February<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. The change<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>Entry<\/th><\/tr><\/thead><tbody><tr><td>CR number<\/td><td>CR-014<\/td><\/tr><tr><td>Date raised<\/td><td>12 October 2026<\/td><\/tr><tr><td>Raised by<\/td><td>Sana R., Marketing Director<\/td><\/tr><tr><td>Title<\/td><td>Add loyalty points redemption at checkout<\/td><\/tr><tr><td>Description<\/td><td>Allow customers to apply existing loyalty points as a discount during checkout. Points balance shown at basket and checkout. Partial redemption allowed. Excludes earning rules, which are unchanged.<\/td><\/tr><tr><td>Reason<\/td><td>Loyalty members can earn points but not spend them online. Support receives regular complaints about this, and it was always intended for a later phase.<\/td><\/tr><tr><td>Type<\/td><td>Major \u2014 affects scope and the go-live date<\/td><\/tr><tr><td>Priority<\/td><td>High \u2014 affects the go-live date<\/td><\/tr><tr><td>Date needed by<\/td><td>At launch. Hard deadline: no<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">2. Impact assessment<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Assessed by Tomas B., Technical Lead \u00b7 14 October 2026<\/em><\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>Entry<\/th><\/tr><\/thead><tbody><tr><td>Items affected<\/td><td>Checkout module, basket module, payment reconciliation, 2 design documents<\/td><\/tr><tr><td>Effort<\/td><td>18 developer days (14 build, 4 integration)<\/td><\/tr><tr><td>Cost<\/td><td><strong>\u00a314,400<\/strong> \u2014 18 days \u00d7 \u00a3800\/day. No new licences<\/td><\/tr><tr><td>Schedule<\/td><td><strong>+11 working days<\/strong>, on the critical path. New go-live: <strong>19 February<\/strong><\/td><\/tr><tr><td>Quality<\/td><td>12 new test cases. Full payment regression re-run \u2014 2 days of QA, included above<\/td><\/tr><tr><td>Risks created<\/td><td>Payment reconciliation becomes more complex. New medium risk, owner: Tomas B.<\/td><\/tr><tr><td>Dependencies<\/td><td>Loyalty provider API rate limits need confirming before build starts<\/td><\/tr><tr><td>Cost of not changing<\/td><td>Delivering in phase 2 is estimated at <strong>\u00a319,000<\/strong> because the checkout would be rebuilt. Doing it now saves <strong>\u00a34,600<\/strong><\/td><\/tr><tr><td>Alternatives<\/td><td>(a) Defer to phase 2 \u2014 costs \u00a34,600 more. (b) Show balance only, no redemption \u2014 4 days, \u00a33,200, but doesn&#8217;t solve the complaint<\/td><\/tr><tr><td>Recommendation<\/td><td>Approve. The saving is real and the complaint is recurring<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">3. Funding<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Line<\/th><th>Amount<\/th><\/tr><\/thead><tbody><tr><td>Project budget<\/td><td>\u00a3210,000<\/td><\/tr><tr><td>Spent to date<\/td><td>\u00a3138,000<\/td><\/tr><tr><td>Contingency reserve before<\/td><td>\u00a318,000<\/td><\/tr><tr><td>Cost of this change<\/td><td>\u00a314,400<\/td><\/tr><tr><td><strong>Contingency reserve after<\/strong><\/td><td><strong>\u00a33,600<\/strong><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">4. Decision<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Field<\/th><th>Entry<\/th><\/tr><\/thead><tbody><tr><td>Decision<\/td><td><strong>Approved with conditions<\/strong><\/td><\/tr><tr><td>Conditions<\/td><td>(1) Go-live moves to 19 February, communicated to all stakeholders by 20 October. (2) Loyalty provider <a href=\"https:\/\/datadome.co\/bot-management-protection\/what-is-api-rate-limiting\/\" target=\"_blank\" rel=\"noopener\">API limits<\/a> confirmed in writing before build starts. (3) No further scope changes funded from contingency without board approval, as the reserve is now low<\/td><\/tr><tr><td>Reason<\/td><td>The \u00a34,600 saving and the recurring customer complaint justify it. The date move is acceptable because no external commitment depends on 4 February<\/td><\/tr><tr><td>Decided by<\/td><td>Daniel K., Sponsor \u00b7 16 October 2026<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">What to notice about this example<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The reserve is nearly gone, and the decision says so.<\/strong> \u00a33,600 left on a project with four months to run is tight. Condition 3 exists because of that. A form that recorded the cost without recording the consequence would have hidden the real problem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The cost of not changing made the case.<\/strong> \u00a319,000 later versus \u00a314,400 now is the strongest argument on the page, and it&#8217;s the field most forms leave blank.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>One alternative was cheaper and got rejected anyway.<\/strong> Option (b) cost \u00a33,200 and didn&#8217;t solve the problem. Cheaper isn&#8217;t the same as better, and writing the alternatives down is what makes that visible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The date moved.<\/strong> Honestly, in writing, with a communication deadline attached.<\/p>\n\n\n\n<h2 id=\"who-approves-a-change-request\" class=\"wp-block-heading\">Who Approves a Change Request?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Agree this before the project starts, not when the first request lands.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Change size<\/th><th>Who approves<\/th><th>Typical turnaround<\/th><\/tr><\/thead><tbody><tr><td>Standard (pre-agreed)<\/td><td>Nobody \u2014 log it<\/td><td>Immediate<\/td><\/tr><tr><td>Under \u00a35,000, no date impact<\/td><td>Project manager<\/td><td>2 working days<\/td><\/tr><tr><td>\u00a35,000\u2013\u00a325,000, or a date change<\/td><td>Project manager plus sponsor<\/td><td>Next board meeting<\/td><\/tr><tr><td>Over \u00a325,000, or a contract change<\/td><td>Sponsor plus finance, sometimes the client<\/td><td>Within 2 weeks<\/td><\/tr><tr><td>Emergency<\/td><td>Two named people, acting immediately<\/td><td>Same day, reviewed retrospectively<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Adjust the thresholds to your project size. What matters is that they exist and that everyone knows them.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Name a deputy for every approver.<\/strong> Change requests don&#8217;t wait for holidays.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The membership and cadence of your change control board belongs in your <a href=\"https:\/\/writegenic.ai\/content\/what-is-configuration-management-plan\">configuration management plan<\/a>.<\/p>\n\n\n\n<h2 id=\"what-happens-if-a-change-request-is-rejected-or-deferred\" class=\"wp-block-heading\">What Happens If a Change Request Is Rejected or Deferred?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">No guide covers this, and it&#8217;s half of all outcomes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">If it&#8217;s rejected<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Write down why.<\/strong> One sentence. This is what stops the request returning in three months.<\/li>\n\n\n\n<li><strong>Tell the requester personally<\/strong>, not just by updating a status field.<\/li>\n\n\n\n<li><strong>Keep the form.<\/strong> Rejected requests are evidence that you controlled scope, which matters at closure and in audits.<\/li>\n\n\n\n<li><strong>Explain the trade-off, not the policy.<\/strong> &#8220;This would add 11 days and we have no float&#8221; lands better than &#8220;it&#8217;s out of scope.&#8221;<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">If it&#8217;s deferred<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Say what it&#8217;s deferred <em>to<\/em><\/strong> \u2014 phase 2, a named date, or a review point. &#8220;Deferred&#8221; with no destination means forgotten.<\/li>\n\n\n\n<li><strong>Record it in the backlog<\/strong> for whatever comes next, or it will vanish.<\/li>\n\n\n\n<li><strong>Re-estimate when it comes back.<\/strong> A six-month-old estimate is fiction.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">If more information is needed<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Say exactly what&#8217;s missing, who should provide it, and by when. &#8220;More info needed&#8221; without those three things stalls indefinitely.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">A note on saying no<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Rejecting changes is part of the job, and doing it well protects relationships rather than damaging them. The pattern that works: acknowledge the value, state the cost plainly, offer the alternative.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">&#8220;This would genuinely help, and I can see why you want it. It&#8217;s 11 days and \u00a314,400, and we&#8217;d have to move go-live. If we do it in phase 2 instead, we keep the date \u2014 shall I put it at the top of that list?&#8221;<\/p>\n<\/blockquote>\n\n\n\n<h2 id=\"how-do-you-number-change-requests\" class=\"wp-block-heading\">How Do You Number Change Requests?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Both competing templates have a &#8220;change request number&#8221; field. Neither suggests a scheme. Here&#8217;s one:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>CR-001, CR-002, CR-003 ...\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Sequential, per project, three digits. Four rules:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Number on receipt, not on approval.<\/strong> Rejected requests keep their numbers. The gaps in your approved list are part of the record.<\/li>\n\n\n\n<li><strong>Never reuse a number.<\/strong> If a request is withdrawn, the number retires with it.<\/li>\n\n\n\n<li><strong>Use the number everywhere.<\/strong> In the schedule, the budget, the change log, the status report, the meeting minutes.<\/li>\n\n\n\n<li><strong>Prefix by project on multi-project programmes.<\/strong> <code>ECOM-CR-014<\/code> beats two CR-014s in the same inbox.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">That third rule is where the value is. When a <a href=\"https:\/\/writegenic.ai\/content\/project-control-process\/\">status report<\/a> says &#8220;go-live moved because of CR-014,&#8221; anyone can find the reasoning.<\/p>\n\n\n\n<h2 id=\"what-is-a-change-log-and-what-goes-in-it\" class=\"wp-block-heading\">What Is a Change Log, and What Goes in It?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The change log is the running list of every request raised, whatever happened to it. One row per request.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Column<\/th><th>Example<\/th><\/tr><\/thead><tbody><tr><td>CR number<\/td><td>CR-014<\/td><\/tr><tr><td>Title<\/td><td>Add loyalty points redemption<\/td><\/tr><tr><td>Raised by<\/td><td>Sana R.<\/td><\/tr><tr><td>Date raised<\/td><td>12 Oct 2026<\/td><\/tr><tr><td>Type<\/td><td>Major<\/td><\/tr><tr><td>Priority<\/td><td>High<\/td><\/tr><tr><td>Cost<\/td><td>\u00a314,400<\/td><\/tr><tr><td>Days added<\/td><td>11<\/td><\/tr><tr><td>Status<\/td><td>Approved with conditions<\/td><\/tr><tr><td>Decided by<\/td><td>Daniel K.<\/td><\/tr><tr><td>Date decided<\/td><td>16 Oct 2026<\/td><\/tr><tr><td>Documents updated<\/td><td>Scope, schedule, budget, 2 design docs<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Why the log matters more than the forms<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The individual forms tell you about one change. The log tells you about the <strong>project<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fourteen requests in four months, nine approved, \u00a341,000 drawn from a \u00a360,000 reserve \u2014 that pattern tells a sponsor something no single form can. It&#8217;s also the first thing anyone will ask for at <a href=\"https:\/\/writegenic.ai\/content\/project-closure-guide-for-project-completion\">project closure<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Three rules: one log per project, update it the same day a decision is made, and show the running total of approved cost and days.<\/p>\n\n\n\n<h2 id=\"what-are-the-8-most-common-change-request-mistakes\" class=\"wp-block-heading\">What Are the 8 Most Common Change Request Mistakes?<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>No threshold for when a form is needed.<\/strong> So either everything needs one, or nothing does.<\/li>\n\n\n\n<li><strong>Approving before assessing.<\/strong> A yes given before the numbers is a blank cheque.<\/li>\n\n\n\n<li><strong>The requester assessing their own change.<\/strong> Optimism isn&#8217;t dishonesty, but it&#8217;s still wrong.<\/li>\n\n\n\n<li><strong>An undefined priority scale.<\/strong> Everything becomes high.<\/li>\n\n\n\n<li><strong>Leaving &#8220;cost of not changing&#8221; blank.<\/strong> It&#8217;s the field that decides borderline cases.<\/li>\n\n\n\n<li><strong>No reason recorded for rejections.<\/strong> The same request comes back forever.<\/li>\n\n\n\n<li><strong>Forgetting to update the documents.<\/strong> An approved change that never reaches the scope statement will be a dispute later.<\/li>\n\n\n\n<li><strong>Funding changes from contingency without saying how much is left.<\/strong> The example above shows how close this gets to the edge.<\/li>\n<\/ol>\n\n\n\n<h2 id=\"what-software-handles-change-request-forms-best\" class=\"wp-block-heading\">What Software Handles Change Request Forms Best?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Three jobs, three kinds of tool.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Job<\/th><th>What to look for<\/th><th>Type of tool<\/th><\/tr><\/thead><tbody><tr><td>Collecting requests<\/td><td>A form anyone can submit without a licence, with required fields<\/td><td>Form tools, or the request feature in a project platform<\/td><\/tr><tr><td>Routing and approving<\/td><td>Workflow states, named approvers, notifications, an audit trail<\/td><td>Project management platforms, or a service desk tool<\/td><\/tr><tr><td>The change log<\/td><td>Sortable table, running totals, export<\/td><td>Spreadsheets, or a database view in your project tool<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Four features that matter more than the brand:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>An audit trail nobody can edit.<\/strong> If approvals can be quietly changed, the record proves nothing.<\/li>\n\n\n\n<li><strong>Required fields.<\/strong> A form that lets people skip the impact section will be skipped.<\/li>\n\n\n\n<li><strong>A link to the affected items.<\/strong> The request should connect to the tasks and documents it changes.<\/li>\n\n\n\n<li><strong>Export.<\/strong> Someone will want the change log in a spreadsheet at closure.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">One caution: a form tool doesn&#8217;t give you a change request process. Decide your thresholds, approvers and priority scale first. Automating an undefined process just makes the confusion faster.<\/p>\n\n\n\n<h2 id=\"how-does-writegenic-ai-fit-in\" class=\"wp-block-heading\">How Does Writegenic AI Fit In?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Change requests generate a steady stream of short, structured writing \u2014 and usually under time pressure, because someone is waiting for an answer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/writegenic.ai\/\">Writegenic AI<\/a> can help you:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Turn a rough request<\/strong> \u2014 an email, a message, a note from a meeting \u2014 into a properly worded change request<\/li>\n\n\n\n<li><strong>Write the description<\/strong> so two people would build the same thing<\/li>\n\n\n\n<li><strong>Draft the impact assessment narrative<\/strong> from your numbers<\/li>\n\n\n\n<li><strong>Write the rejection<\/strong> in language that keeps the relationship intact<\/li>\n\n\n\n<li><strong>Summarise the change log<\/strong> into a paragraph for your status report or closure report<\/li>\n\n\n\n<li><strong>Draft the stakeholder note<\/strong> when an approved change moves a date<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">It sits alongside the rest of the documents: the <a href=\"https:\/\/writegenic.ai\/content\/how-to-write-a-project-scope-using-ai\/\">project scope<\/a>, the <a href=\"https:\/\/writegenic.ai\/content\/scope-management-plan-guide\/\">scope management plan<\/a>, the <a href=\"https:\/\/writegenic.ai\/content\/what-is-configuration-management-plan\">configuration management plan<\/a> that defines the process, and the <a href=\"https:\/\/writegenic.ai\/content\/project-closure-guide-for-project-completion\">closure report<\/a> where the change log ends up.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Explore <a href=\"https:\/\/writegenic.ai\/content\/ai-generators\/ai-for-project-management\/\">AI for project management<\/a> or use the <a href=\"https:\/\/writegenic.ai\/content\/prompt-generator\/\">prompt generator<\/a> for sharper instructions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Draft with the tool, keep the judgement.<\/strong> AI can make a change request read clearly in a minute. It cannot estimate 18 days of work, know whether your reserve can absorb \u00a314,400, or decide whether moving go-live is acceptable. Those numbers come from the people doing the work, and the decision belongs to whoever is accountable for the budget.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/writegenic.ai\/register\">Try Writegenic AI free<\/a><\/p>\n\n\n\n<h2 id=\"frequently-asked-questions\" class=\"wp-block-heading\">Frequently Asked Questions<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1791908014556\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What is a change request form?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>A document used to formally ask for a change to an approved project. It records what the change is, why it&#8217;s wanted, what it costs in money and time, and who decided.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908016407\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What is the difference between a change request and a change order?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>A change request proposes a change and can be rejected. A change order is the instruction issued after approval, and is often a binding contract variation. Request comes first.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908017937\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What fields should a change request form have?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>About 15 to 20, in five groups: identification, the change itself, impact, the decision, and what happens afterwards. More than that and people stop completing it properly.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908019328\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">When do you need a change request?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>When you&#8217;re changing something already approved and baselined. The quick test: if someone outside your team would be surprised to learn about it, raise a form.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908020424\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What are the four types of change request?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Standard (pre-approved and just logged), minor (no scope, cost or date impact), major (affects scope, cost, date or contract), and emergency (immediate, with retrospective review).<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908021504\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Who approves a change request?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>It depends on size. Set thresholds in advance \u2014 typically the project manager for small changes, the sponsor for larger ones, and finance or the client for anything affecting contracts.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908022628\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">How do you assess the impact of a change request?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Six steps: list what changes, estimate the effort, cost it, check whether it touches the critical path, identify retesting, and record any new risks. The requester shouldn&#8217;t do the assessment.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908023999\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What is the &#8220;cost of not changing&#8221;?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>What happens if you reject the request \u2014 deferred cost, a missed benefit, or a risk carried forward. It&#8217;s the field that decides most borderline cases, and most forms leave it blank.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908025822\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What should happen if a change request is rejected?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Record the reason in one sentence, tell the requester personally, and keep the form. The written reason is what stops the same request returning in three months.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908137478\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">What is a change log?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>A running table of every change request raised, with its cost, days added, decision and date. It shows the pattern across the project, which individual forms can&#8217;t.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908138481\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">How should you number change requests?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Sequentially per project \u2014 CR-001, CR-002 \u2014 assigned on receipt rather than approval, never reused, and quoted in every other document that references the change.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1791908139555\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">Can AI fill in a change request form?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>It can draft the wording quickly and clearly from your notes. The effort estimate, the cost, and the decision have to come from the people who own the work and the budget.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n<p class=\"wp-block-paragraph\"><strong>Related reading:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/writegenic.ai\/content\/what-is-configuration-management-plan\">What Is Configuration Management Plan: Template + Example<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/writegenic.ai\/content\/scope-management-plan-guide\/\">Creating a Scope Management Plan: A Step-by-Step Guide<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/writegenic.ai\/content\/contingency-plan-in-project-management\">Contingency Plan in Project Management: Template + Example<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/writegenic.ai\/content\/how-to-write-a-project-scope-using-ai\/\">How to Write a Project Scope Using AI<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/writegenic.ai\/content\/project-closure-guide-for-project-completion\">Project Closure: Checklist + Closure Report Template<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>What goes in a change request form, field by field. A free template, a completed example with real costs, how to assess impact, and when you need a form at all.<\/p>\n","protected":false},"author":4,"featured_media":33698,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[97],"tags":[],"class_list":["post-33697","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-project-management-guide"],"authors":[],"_links":{"self":[{"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/posts\/33697","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/comments?post=33697"}],"version-history":[{"count":1,"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/posts\/33697\/revisions"}],"predecessor-version":[{"id":33699,"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/posts\/33697\/revisions\/33699"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/media\/33698"}],"wp:attachment":[{"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/media?parent=33697"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/categories?post=33697"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/writegenic.ai\/content\/wp-json\/wp\/v2\/tags?post=33697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}