Free template · change order

Software change request template

Not an internal IT ticket: the document a freelance developer sends a client when they ask for something outside the agreed scope. It says what was asked, why it's new work, what it costs, what it does to the dates, and gets it approved before you start.

Sections
9
Estimate
6 lines, 32 hours
Example total
$3,520.00
Payments
100%
Proposal

Change request 2: Spanish version of the field app

Prepared for Fieldnote

Investment
From $3,520
Payments
One payment

What you asked for

On 3 November, Dana (operations lead) asked for the field app to work in Spanish as well as English, so the new Madrid team can record site visits in their own language from launch.

This change request prices that work and shows what it does to the launch date. Nothing changes until you approve it.

Why it's a change, not a fix

The approved proposal (“Fieldnote: field reports app, design and build”, version 1, approved 14 October) covers an app in English only. Everything built so far works as agreed, so adding a second language is new scope. The rest of the agreed work and price stay exactly as they are.

What's added

Spanish version

  • Every screen, button and message in the app available in SpanishS-1
  • A language switch in each person's settings, remembered on their phoneS-2
  • Dates, times and numbers shown the Spanish way when Spanish is chosenS-3
  • Client reports generated in the language the visit was written inS-4

Not included

  • A Spanish version of the marketing siteX-1
  • Right-to-left languagesX-2

Cost

Priced at the same rate as the original proposal. Translating the help pages is optional: tick it if you'd like it included.

TaskHoursRateAmount
Language support across the app10$110.00$1,100.00
Spanish text for every screen and message8$110.00$880.00
Language switch in settings3$110.00$330.00
Spanish dates, times and numbers3$110.00$330.00
Reports in the visit's language4$110.00$440.00
Testing both languages on real phones4$110.00$440.00
Optional extras
Translate the help pages (8 pages)6$110.00+$660.00
Subtotal$3,520.00
Total$3,520.00

Effect on dates

Adds one week: launch moves from Friday 12 December to Friday 19 December. The design approval date doesn't change. If you approve after 14 November, the new launch date moves by the same number of days.

How it's billed

  1. Added to the launch invoiceWeek 9$3,520.00100%

Assumptions

  • You provide the Spanish wording for any text you write yourselves (report templates, email footers); we translate everything in the app
  • One person on your side reviews the Spanish screens in the week before launch
  • Not included: a Spanish version of the marketing site, or right-to-left languages

Terms

Everything else in the approved proposal stays the same, including its terms. If this change isn't approved, the original scope, price and dates stand and nothing extra is billed. Once approved, this change becomes part of the project and is billed as shown above.

Next step

Approve below to add the Spanish version to the project. We start on it the next working day and update the project plan the same day.

A worked example for a fictional client. Every word and number is yours to change.

How to write a change order

  1. Write down the request in their words

    Who asked, when, and what for. Quoting the request back (“so the Madrid team can record visits in Spanish”) shows you understood it, and stops the change growing between the call and the invoice.

  2. Point back to what was agreed

    Name the approved proposal or statement of work, its version and the date it was approved, and say which part this changes. That one paragraph is what makes it a change rather than a fix, without sounding defensive.

  3. Price it the way you priced the project

    Same rate, line by line, so the client can compare it with the original estimate. Optional parts (like translating help pages) go in as extras they can tick.

  4. Always show the effect on dates

    Even when it's zero. Moving launch by a week is fine if it's written down and approved; it's a dispute if it's discovered in the last week. Say what happens if approval comes late.

  5. Say what happens if they say no

    The original scope, price and dates stand, and nothing extra is billed. Saying it plainly makes “no” an easy answer, which makes “yes” feel like a real choice.

  6. Get it approved before you start, and keep it with the project

    An approval by email gets lost. In Devposal the change goes out as an update to the original proposal: your client sees what changed, approves it on the same page, and the earlier approved version stays on record next to it.

Questions people ask

Is there a change request form for software development projects?

Yes: the example above is a change order a developer sends a client, with the request, why it's outside the agreed scope, the price, the effect on dates and an approval. Copy it, download it as Markdown, or open it in Devposal to send it as a link.

What happens if the scope changes after the SOW is approved?

The approved scope stays in force until a change is agreed in writing. You write up the change with its cost and date impact, the client approves or declines it, and an approved change becomes part of the project.

Should I charge for every change?

Not necessarily. Some developers agree a small allowance for tiny tweaks (a couple of hours a month, say) and write up anything bigger as a change. What matters is that the rule is written into the proposal before work starts.

Is a change request billable if it isn't a bug fix?

Usually, yes. If the work does what was agreed and the client wants it to do something more or different, that's new scope. Defects against the agreed scope are fixed free, typically within a warranty period.

What's the difference between a change request and a change order?

A change request is the client's ask. A change order is your written, priced answer to it, with the date impact, which becomes binding once the client approves it.

Can a client approve a change order online?

Yes. Send it as a link they can read on a phone and approve with a typed signature; keep the approval with the original proposal so the current scope is always clear.

Related