Why are renovation overruns found so late?
Most renovation overruns are found when the invoice arrives. By then the work is finished, the decision was taken weeks earlier, and the only choice left is whether to pay. Three habits cause the delay: the invoice follows the work, extras are agreed on site without paperwork, and the budget lives in a spreadsheet that is updated once a month.
None of these is careless on its own. The contractor needs an answer at the wall, the owner wants the problem fixed, and the bookkeeper cannot record what has not been sent. The result is a budget that looks healthy in the month end figures while the commitments grow out of sight.
What does an extra agreed on site look like?
An extra is any change to the scope, the price or the time of the work that was agreed without a signed change order. A moved socket, a different floor, an upgraded bathroom fitting and a longer period for the electrician all count. They are often agreed in a sentence at the wall, with a nod, and recorded nowhere.
An extra that lives only in memory has no date, no price and no owner, so nobody can check it later. It also does not move the budget, because the budget only moves when someone enters it. That is why the first sign of an overrun is often a missing entry rather than a large number.
What are the early signals of a renovation overrun?
Four signals usually appear before the invoice. Each one can be checked on the day it happens, and each one asks a different question.
- A commitment or extra was agreed but not entered. The work is on site, but the budget item still shows its original plan.
- Spend is ahead of progress. Money leaves the account faster than the work moves on the phase, which is a question to ask before the next payment and not after it.
- A stage forecast is past its date. The end of a stage is now later than its planned date, and every week of waiting keeps the site costs running.
- The site has gone quiet. No new fact has come from an active stage for 7 days, so the figures describe a past that nobody has checked.
How does an overrun show up in the budget?
An overrun is spending more than the plan of a budget item, or taking longer than the planned date. The useful number is the forecast spend: what the item will cost in the end. In Reperline the forecast spend of an item is what is invoiced plus what is committed, so an agreed extra moves the forecast when it is entered as a commitment, and not when the invoice comes in.
A contingency line can absorb a known risk, but spending it should be a decision that stays visible, with the reason written next to it. Otherwise the contingency disappears into the total, and the next overrun has nothing to absorb it.
What does a system need to catch an overrun early?
A system does not need to be clever. It needs to hold three things in one place: the plan for each budget item, every commitment as it is signed, and a dated fact from site for each stage. With those in place, a rule can compare them every time something changes, instead of once a month.
- A plan amount for every budget item, changed only by a decision that leaves a trace.
- Commitments entered on the day they are agreed, each linked to the item it spends.
- Site facts with a percentage, a note and photos, reported from the site itself.
- Rules that raise a signal when spend passes the plan, when spend runs ahead of progress, when a forecast moves past its date, or when a site goes quiet.
How does Reperline catch these signals?
Reperline keeps the plan, invoices, payments, commitments and forecast spend for each budget item, and site staff report progress from Telegram as a site report. Six checks review each report before it counts. The default rules raise a signal when an item is forecast more than 5% over its plan, when the share of an item's plan that is invoiced is more than 1.2 times the share of its phase that is done, when a milestone is overdue, when a forecast end runs more than 7 days past its planned date, and when an active phase has no new fact for 7 days.
Critical and high signals go by Telegram to the owner, finance and site manager roles, and critical signals also go by email. The owner can change the thresholds on Project Pro and Enterprise. Transactions are never erased: a wrong one is voided with a reason and stays visible in the journal.
Every change is kept in a permanent audit log, so the record of who changed what, and when, is still there at the final account. The renovation and flipping template on the flipping page starts with eight stages and six budget groups, including contingency, and every amount starts at zero for the owner to enter. Plans and prices are on the pricing page. For the margin side of the same project, read how to calculate your real flip margin.
What does a silent site cost you?
A site that stops reporting hides cost, because the work carries on while the figures stand still. A stage can run for weeks with no fact, and the budget shows nothing until the invoice arrives. A silent site is one of the clearest early signs of an overrun, and it is also the easiest to miss, because nothing in the spreadsheet changes.
Reperline cannot see work that nobody reports, and it cannot price a day of delay. What it can do is turn the silence into a signal once the seven days have passed, so the question reaches a person while it can still be answered. The field facts module explains how the reports are made.
What can you check this week?
A short weekly check finds most of these signs before they reach the invoice. Ask the same questions each week, write the answers down with a date and a name, and compare them with the week before.
- List every commitment entered this week, and check each one against a signed document.
- List every extra agreed on site this week, and confirm that it has a budget item and a commitment.
- Compare the invoiced money of each phase with its progress, and ask about any phase where money leads the work.
- Check when each active stage last reported, and ask the site manager about any stage that has been quiet for a week.