Why Residential Construction Projects Go Wrong (And How to Stop Yours Doing It)

So folks, I have been a quantity surveyor in Dublin for a long time now. I have worked on hundreds of residential projects — extensions, renovations, new builds. I have seen projects that went brilliantly. And I have seen projects that went very wrong indeed.

And I want to tell you something that took me a long time to fully understand.

The projects that go wrong almost never go wrong over bricks and mortar.

They go wrong because expectations were not managed.

That's it. That is the whole thing. Not the foundations. Not the weather. Not the price of materials. Not the builder. Expectations. Pre-contract expectations that were never made explicit. Post-contract expectations that were never written down. Expectations that both sides held, differently, and never compared until they were standing in a half-finished room arguing about money.

I wrote a book about this — The Psychology of Residential Construction Projects. Because the more time I spent on sites, the more I understood that construction is not primarily a technical problem. It is a human one. And the QS who understands that is a very different QS from the one who just measures things and gives you a number.

So. Let me tell you the seven ways residential construction projects go wrong in Ireland. And then let me tell you what to do about each one.

1. The number in your head is not the real number

Every homeowner starts a project with a number in their head. Where it came from is almost irrelevant — something they read, something a neighbour said, something the architect mentioned at the first meeting. That number is almost always lower than the real cost of what they want to build.

The gap between the imagined number and the real number is the first and most common source of expectation failure. Get a proper cost plan done before you commit to detailed drawings. Not after. Before.

2. The spec is too vague

A vague specification produces incomparable tenders, unenforceable contracts, and disputes about what was agreed. A tight specification — product by product, finish by finish, performance standard by performance standard — is the single most practical protection a homeowner has on a build.

Less is more. A tighter, simpler spec that is clearly written is better than a comprehensive spec full of ambiguity.

3. The wrong builder was chosen

Choosing a builder on price alone is the second most common mistake I see. The cheapest tender is nearly always the most expensive tender by the time the job is done. A builder under financial pressure does not build well. He survives.

Check the references. Check the capacity. And ask the question my father Fran used to ask: would you trust him with the keys?

4. Variations were not managed

Variations are inevitable. They are not the problem. Unmanaged variations are the problem — changes agreed verbally on site, never written down, never priced, accumulating silently until the final account arrives and both sides are shocked.

Every variation in writing. Every variation priced before the work is done. Every variation agreed by both sides before it proceeds. This is basic contract administration. It is what a good QS does every week on every project.

5. Payments were not certified honestly

Payments made on the basis of what the builder says he has done, rather than what has actually been done, create two problems. They overpay the builder for work not yet complete — giving him less incentive to finish — and they leave the homeowner with reduced retention and reduced leverage if problems emerge later.

Interim payments should be certified by an independent person against work actually completed. That is the QS's job.

6. Nobody held the room

I want to talk about something that is rarely discussed in the context of construction projects, but which I think is the most important thing of all.

Every project needs someone who can hold the room together when it gets difficult. And it always gets difficult. The homeowner is stressed about money. The architect is under pressure from both sides. The builder is managing multiple jobs and multiple subcontractors. And the engineer has raised something that requires a structural solution nobody budgeted for.

In that moment, somebody needs to keep the communication clear, the relationships intact, and the focus on the outcome rather than the grievance. That is containment. It is listening, asking the right question, holding silence when silence is needed, and speaking plainly when plainness is needed.

A QS who understands this is worth more than a QS who can simply read a tender.

7. The contract was not read before it was signed

Almost nobody reads the contract before they sign it. And the contract is the document that governs everything — what is being built, what is being paid, what happens if things go wrong.

Read the contract. Or send it to someone who will read it for you and tell you what it says. Before you sign. Not after.

What to do — the short version

Get a cost plan done before you commit to detailed drawings. Write a tight spec before you go to tender. Choose your builder on character and capacity, not just price. Manage every variation in writing. Certify payments honestly against work done. Make sure someone is holding the room when it gets difficult. And read the contract before you sign it.

None of this is complicated. All of it requires discipline — doing the right thing at the right time, even when everyone is in a hurry to get started.

That discipline is what separates the projects that finish well from the ones that don't.

Anyway, that is the honest answer to why construction projects go wrong in Ireland. And the equally honest answer to how to stop yours doing it.

If you want a QS who watches for this from week one, here's how I work.