Why do projects finish late when everyone is busy?
A late handover is rarely a surprise to the people on site. Crews are working, invoices are arriving and meetings are held. The problem is the gap between the plan and the facts, and that gap grows slowly enough to look normal. Each week a milestone is a few days behind, and nobody writes it down as a finish date that has moved. The words for this drift are slippage and variance.
The useful question is not why a project finished late. It is which cause was visible, and when. Most causes below leave a sign months before the handover, if someone is looking at the right figure.
Which seven root causes should you check first?
- An unrealistic baseline: planned dates were set from the sales date or the handover date, not from the amount of work.
- Dependencies nobody wrote down: a package starts before the work it depends on is ready.
- Progress reported late, or not at all, so the office works from the last meeting rather than from the site.
- Progress reported too generously: a package marked 100% while an earlier package in the same phase is still open.
- Decisions and changes that wait: design queries, change orders and approvals that sit in an inbox.
- Procurement and subcontractor gaps: long lead items that arrive late, or a tender that closes with too few bids.
- Money that runs short: late payments from buyers or from the company, which slow the crews before anyone says so.
How do a weak baseline and missing dependencies cause delay?
A baseline built backwards from the handover date has no room for the work itself. Say a package needs about 15 working days of a four person crew, but the plan gives it 10 days because the frame must be finished by a fixed date. The plan looks fine on paper, and the package is late on day one. The fix is to test each planned duration against the crew and the work content before the baseline is approved, not after the first slip.
Dependencies cause a different kind of delay. A list of dates can show every package on time while one predecessor, a delivery or an approval, quietly holds three others. If the links between packages are not written down anywhere, the late predecessor looks like a small problem until it blocks the whole sequence. Record the predecessor for each package in the planning tool, and read the list with the question: what does this package wait for?
How do late and generous progress reports hide delay?
A progress figure is only as good as the day it was measured. When the office receives progress from a weekly meeting, the figure is already old, and the real pace is unknown until the next meeting. A silent site looks like a quiet week, not like a missing report. A milestone with no new fact for a week is a warning in itself, because nobody can say how far the work has moved.
Progress can also be too generous. A package marked 100% while an earlier package in the same phase is still open usually means the work was reported by the calendar and not by the building. Ask for a note with every large jump and every figure that goes down, because the reason is where the truth is. A progress figure that never falls and never has a reason is a figure to question.
How do decisions, procurement and tenders slow the work?
Late decisions are a cause that nobody on site controls, which is why they are easy to blame on the wrong people. A design query that waits two weeks for an answer stops the crew for two weeks, even when the contractor has done everything correctly. Track each open query and approval with a date, so the wait is visible and can be raised with the person who owes the answer.
Procurement works the same way. A long lead item that is ordered late arrives late, and the work that depends on it waits. A tender with too few bids, or one that closes after the date the work needs the subcontractor, pushes the start back in the same way. The early sign is a tender deadline that is close and a planned start that is not. Chasing the tender a week before it closes costs far less than explaining the delay afterwards.
How does money pressure slow a site?
Money problems often arrive last and spread quickly. A subcontractor who is not paid stops booking crews. A buyer who falls behind on an instalment changes the cash the company can use for the next stage. The schedule then slows, and the cause does not appear in the schedule at all.
Watch the money next to the progress. An item where invoices run ahead of the work done is a sign of a prepayment or an inflated claim, and it also means cash will be short later. A payment that is overdue from a buyer is a fact, not a guess, so it should reach the person who can act on it the same day.
How do you spot a late finish early?
Four checks catch most of the causes above while there is still time. First, compare the forecast end of each milestone with its planned date every week, not only at the end of the month. Second, ask which milestones have no progress at all after their planned start, because missing progress is the first sign of a stall. Third, read every large change in progress and every fall in progress with its note. Fourth, look at the open decisions and tenders with a date beside them, and ask who owes each answer.
None of these checks needs a new tool. They need the same facts, updated often, and someone whose job is to act on the first sign rather than the last.
How does Reperline handle this?
Reperline is built around the early sign. Site staff report progress with a note and up to five photos from Telegram, and six checks review every entry before it is saved. Those checks catch a lowered figure without a note, a big jump, 100% while an earlier package of the phase is unfinished, a date in the future or too far back, 100% without a note, and progress on a phase that has not started. A milestone gets a forecast end from its actual pace, and a milestone with no progress gets no forecast at all.
Signals then watch the same facts. A milestone that is overdue is high priority after 14 days. A milestone whose forecast ends more than 7 days after its planned date is forecast behind plan. An active phase with no new fact for 7 days is silent. On the cost side, an item whose forecast is more than 5% above its plan raises a signal, and a tender with its deadline three days away or less does too. Critical and high signals go by Telegram and email to the roles the owner chooses.
The limit matters as much as the features. Reperline does not calculate dependencies or the critical path, so it cannot tell you that one predecessor is driving the finish date. Keep the predecessor links in your planning tool, and use Reperline to see where each package is and where it is heading. The field facts module covers the site reports, the schedule module the forecasts and the signals module the warnings. For the cost side, see the budget module. To set the baseline these checks compare against, read the baseline schedule guide. Plans and prices are on the pricing page.