> **Template.** This is the structure of a change request. Square brackets are placeholders. It is not taken from a client project. # Change request [CR-number]: [short name] | | | | --- | --- | | Project | [Project name] | | Raised by | [Name, organisation] | | Date raised | [YYYY-MM-DD] | | Status | Draft / Estimated / Approved / Declined / Done | ## What's being asked for [One or two paragraphs in plain language. What should the site or application do that it doesn't do now, and who asked for it?] ## Why it's outside the current scope [Point to the section of the scope document this differs from, for example "Scope §3 lists email sign-in only; this adds Google sign-in."] ## What it involves - [Piece of work, for example "Add Google as a sign-in provider"] - [Piece of work] - [Any change to existing work, for example "Update the sign-in page design"] ## What it depends on - [Something the client or agency needs to supply, for example "Google Cloud project with OAuth credentials"] - [A third-party account, price or limit] ## Effect on cost and time | | | | --- | --- | | Estimate | [S$ amount, or hours × rate] | | Effect on launch date | [None / moves by N working days] | | Running costs | [Any new monthly cost, for example a paid plan] | ## Options 1. **Do it now.** [Cost, date effect.] 2. **Do it after launch.** [Cost, and why it might differ.] 3. **Don't do it.** [What happens instead, if anything.] ## Decision | | | | --- | --- | | Option chosen | [1 / 2 / 3] | | Approved by | [Name, role] | | Date | [YYYY-MM-DD] | Work starts only once this section is filled in. A reply to the email or a comment in the project chat that says "approved" is enough, as long as it's recorded here.