A change request form covers what needs changing, why it matters, what it affects, timeline impact, and how the change should be priced.
A feature request lands late in a build, or a stakeholder spots something that “should be quick”, and the project suddenly needs a way to talk about scope, cost, and knock-on effects before work starts. The change request form gathers the details in one place so the next reply can be an estimate instead of another round of back and forth.
The opening text frames what the form is for, then the questions move from contact details into the change itself. The client spells out what they want, what the change does to the timeline, the smallest version worth shipping, and whether anything already live might break, so a custom software team can assess risk before agreeing to build. The page sits under terracotta accents with a teal-blue call to action and Raleway headings, which keeps the document feeling like change control, not a sales pitch.
- Change Request Form A short intro that explains what the requester should provide and what happens after the submission.
- Your name Required contact name so the response can be tied to the right stakeholder.
- Email address Required email for sending next steps and any follow-up questions.
- Change details A written prompt that asks for what’s changing, why, and which parts the change touches.
- Which pricing model do you prefer for this change? A choice field that records whether the requester prefers a fixed price estimate, a day-rate approach, or has no preference.
Once the form is in Plutio, you share it and the answers come back as a single response, leaving you with a clear record of what was asked for and how the requester sees the trade-offs.
We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.
What to include in a change request form
| Part | What it covers |
|---|
Change Request Form | A short opener that explains what the form is collecting and that you’ll review the answers and reply with next steps. |
Your name | A required name field so each request has an accountable contact. |
Email address | A required email field for follow-ups and the assessment response. |
Phone number | An optional phone field for cases where talking it through is faster than more messages. |
Change details | A written prompt that asks for what should change, why the change is needed, and what areas the change touches. |
Project or proposal reference | An optional reference field to tie the request back to an existing project or earlier quote. |
Describe the change you want | A required long-answer field where the requester describes the change in their own words. |
What will this change do to the timeline? | A required long-answer field to capture expected timeline impact before any estimate is given. |
What is the smallest version we can ship? | A required long-answer field that forces a minimum viable scope into writing. |
Will this change break anything already live? | A required multiple-choice field to flag whether live features could be affected or need review. |
Which pricing model do you prefer for this change? | An optional multiple-choice field that records whether the requester prefers fixed price, day-rate or time-boxed work, or has no preference. |
Who it is for
Product teams, agencies, and consultants doing custom software work, including api & integrations and legacy modernisation, when a project needs a written change request before re-scoping.
The form in full
Change Request Form
Use this form to describe a change you want me to assess. I will review your answers and reply with next steps.
- Your name (required)
- Email address (required)
- Phone number
Change details
Tell me what you want changed, why, and which parts it touches.
- Project or proposal reference
- Describe the change you want (required)
- What will this change do to the timeline? (required)
- What is the smallest version we can ship? (required)
- Will this change break anything already live? (required)
- No, it is isolated
- Yes, it will affect live features
- Unsure, please review
- Which pricing model do you prefer for this change?
- Fixed price estimate
- Day-rate / time-boxed quote
- No preference