The RIAI Blue Form of Contract — What Homeowners Need to Know

So folks, I want to tell you about something that happens on almost every residential build in Ireland.

The contract arrives. The architect sends it over, or the builder brings it to the site meeting. It is a document — a real, legally binding document that sets out everything about your project. Who does what. What gets built. What gets paid, and when. What happens if things go wrong.

And in my experience, most homeowners sign it without reading it.

Not because they are careless. Not because they do not care about their project. But because it looks complicated, nobody has explained it to them, and there is a builder standing there waiting to get started.

That is the moment I want to talk about. Because that moment — the moment before you sign — is the most important moment on the entire build.

It's one of the seven reasons I see residential projects go wrong in Ireland — and it's the easiest one to fix, because it happens before a single block is laid. If you want the full picture of where projects typically go off track, I've written about that separately.

What is the RIAI Blue Form?

The RIAI Blue Form of Contract is the standard form of building contract used on most residential construction projects in Ireland. RIAI stands for the Royal Institute of the Architects of Ireland. The Blue Form is what your architect will typically issue when your project goes to tender, and it is the document your builder will sign when he accepts the job.

It covers everything. The scope of the works. The contract sum. The programme. How variations are handled. How payments are certified and made. What happens if there are defects. How disputes are resolved. What insurance is required. And what either party can do if the other fails to perform.

It is not a long document by legal standards. But it is a dense one. And there are sections in it that have significant financial consequences for homeowners who do not know they are there.

If you want a step-by-step walkthrough of completing the document itself, I've covered that separately.

The section most homeowners miss — Clause 2

Clause 2 of the RIAI Blue Form covers the contractor's obligations in relation to the works. It sounds straightforward. And in outline, it is.

But Clause 2 is also where the scope of the works is defined — and scope is everything. If something is not clearly in the scope, it is not clearly in the price. And if it is not in the price, it becomes a variation. And variations, as I have said many times on this site, are the most expensive way to add anything to a build.

The homeowners I see who have the most trouble with variations are almost always the ones whose scope was loosely written at the start. Not because the builder was dishonest. But because nobody sat down before the contract was signed and said: right, let us be absolutely clear about what is and is not included here.

That is the conversation I have with every client before anything is signed.

Why the spec matters as much as the contract

Here is the thing. The RIAI Blue Form is only as strong as the documents it refers to. And the most important of those documents is the specification.

The spec is where the standard of work is set. The materials. The finishes. The products. The performance requirements. If the spec says 'good quality timber flooring', that means different things to different builders. If it says 'engineered oak, 18mm, Boen or equivalent, approved by architect prior to installation', there is no wriggle room.

I'll be honest with you. Most of the disputes I see on residential projects in Dublin and across Ireland do not happen because a builder did something wrong. They happen because the spec was not tight enough to prevent a misunderstanding. And by the time the misunderstanding surfaces — usually mid-build, when nobody wants to stop — it is very expensive to fix.

The spec is not paperwork. The spec is protection. Really the most practical protection a homeowner has on a build.

What to check before you sign

When a contract lands on your table, here are the things I look at immediately.

First — is the scope of works clearly and completely described? Not in general terms. Specifically. Room by room, element by element.

Second — what is the contract sum, and what provisional sums are included? Provisional sums are allowances for items not yet fully designed or priced. They will almost certainly change. You need to know what they are and what they are for before you sign.

Third — what are the payment terms? How often are interim payments certified? What is the retention percentage, and when is retention released?

Fourth — what is the programme, and what are the consequences of delay? Is there a liquidated damages clause? If the builder overruns, what are your rights?

Fifth — what are the architect's powers under the contract? The architect acts as the contract administrator on most RIAI Blue Form projects in Ireland. Understanding what the architect can and cannot certify, instruct, or decide is important for both sides.

For a fuller checklist, see my Top 10 Things to Consider Before Signing a Construction Contract.

Now. I am not saying you need to become a construction lawyer. That is not the point. The point is that someone who understands this document should sit down with you before you sign it, and walk you through the parts that matter for your specific project.

The client who signed without reading it

Here's a composite example, based on situations I see regularly on residential projects across Dublin — not a specific client, but a pattern that comes up again and again. A couple in Donnybrook, Dublin 4, renovating a Victorian terraced house. Good architect, good builder, good project in principle.

They signed the contract at the first site meeting. The builder had it ready. They did not want to seem difficult. They signed.

Six months in, a dispute arose over a variation. The builder's position was that a certain element of work was not in the original scope and therefore not in the price. The homeowners' position was that they had always assumed it was included.

Both were right, in a way. The scope had not been written tightly enough to settle the question either way. The contract could not resolve it because the ambiguity had been built into it from the start.

It cost them money and six weeks of stress to resolve. Not because anyone was dishonest. But because nobody had read the contract before it was signed.

If you want to understand what recourse you have when this goes wrong, I've written about breach of contract in Irish residential construction.

That is the most common story I know. And it is the most preventable one.

What I do — and when to call me

If your architect has sent you a draft contract, or your builder has arrived at a site meeting with one, do not sign it that day. Send it to me first.

I will read it. I will mark up the sections you need to understand. I will tell you what questions to ask the architect. And if there are gaps in the scope or the spec that need tightening before you commit, I will identify them before they become expensive problems on site.

Most projects that go wrong in Ireland do not go wrong over bricks and mortar. They go wrong because expectations were not managed. And the contract — properly read, properly understood, properly negotiated before it is signed — is the single best tool there is for managing them.

Anyway, that is my way of saying: read the contract. Or let me read it for you. ─────────────────────────────────────────────