Life events

Scope creep in a renovation: tracking change requests and their cost

Track scope creep in a renovation with a change-request log: date, change, who asked, extra cost, approval and a running total against the original estimate.

Editorial illustration for Scope creep in a renovation: tracking change requests and their cost

Scope creep in a renovation is easiest to control with a change-request log: one row for every change, with its date, what changed, who asked, the extra quoted, and whether you approved it in writing. Keep a running total of approved changes beside the original estimate. The total that matters is the original plus approved changes, shown next to what has actually been paid.

What goes in the change-request log?

No.DateWhat changedWho askedExtra (₹)Approved?Approved how
112 MayFour extra sockets in the living roomYou12,000YesMessage reply
220 MayUpgrade bedroom tileYou28,000YesSigned note
327 MaySkip false ceiling in the studyYou-9,000YesMessage reply
42 JuneExtra wardrobe in the guest roomDesigner suggested45,000PendingNot yet

Always record the extra as the amount quoted, a negative figure when work is removed, and the reason the change happened.

How do you keep a running total?

Say the original estimate is ₹5,00,000. These figures are only an example.

  • After change 1: 5,00,000 + 12,000 = ₹5,12,000
  • After change 2: 5,12,000 + 28,000 = ₹5,40,000
  • After change 3: 5,40,000 − 9,000 = ₹5,31,000
  • If change 4 is approved: 5,31,000 + 45,000 = ₹5,76,000

So the approved total today is ₹5,31,000 and the possible total is ₹5,76,000, which is ₹76,000 above the original. Seeing the pending change next to the approved total is the point; it turns a casual suggestion into a number you can say yes or no to.

Why does scope creep happen so easily?

  • Changes feel small when asked for one at a time.
  • Seeing the work in progress gives you ideas you did not have on paper.
  • Some contractors say 'we will adjust it in the final bill' and never state the figure.
  • Hidden conditions, such as damaged pipes or uneven walls, force changes that nobody chose.

What rules keep it in check?

  1. No extra work starts until a price is stated and you have approved it in writing, even by message.
  2. Every change gets a number in the log on the day it is raised.
  3. Review the log once a week, with the contractor if possible.
  4. Pay for changes on the same milestone basis as the main work, not all at the end.
  5. For work removed, ask for the credit in writing, since it is often forgotten.

How do you connect the log to payments?

Record each payment under the renovation category and note which change it covers, if any. If your bank statements are imported into SpendixAI, the transfers to the contractor are already there; group them by sub-category or filter by the contractor's name to see the total paid so far, then compare it with the approved total in your log. Keep any chat screenshot or signed note as the receipt for the entry.

How do you say no to a change without a fight?

Use the log as your reason. Say 'I will add it to the list and we can decide on Friday with the price in front of us.' That is not a refusal, and it gives you a few days to think. Many changes lose their urgency by Friday. Those that survive can be priced properly, approved in writing, and scheduled so they do not delay the main work. You stay in control of the total, and the contractor knows exactly what you have agreed.

What if you disagree about a charge?

Refer to the log and the written approvals. If something was done without approval and the contractor insists on payment, stay calm, keep paying what is agreed for completed work, and put your point in writing. For anything contractual or legal, ask a professional about the position in your agreement, since the answer depends on what you signed.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports