REUTERS | Mike Blake

The meaning of fitness for purpose

Few expressions are more likely to get construction practitioners hot under the collar than “fitness for purpose”. But is the hype justified? And what does it really mean? I was pondering these questions when recently reviewing a client’s in-house (bespoke) form of design and build contract.

What’s the problem?

The client, an intelligent and experienced construction professional, was adamant that he did not want to impose a fitness for purpose design obligation on his contractor. He had heard that they were onerous, uninsurable and generally a Bad Thing.

However, when I asked him if he expected the contractor to produce a building that met his requirements as set out in his brief, his tune changed. Surely that was the least he was entitled to expect? Wasn’t that exactly what he was paying for? Quite, I said. But we are entering dangerous territory here, since (at least on one view) this comes very close to a fitness for purpose obligation.

So how should we square this circle?

Professional men and contractors

Let’s take a step back. As every lawyer (and insurer) knows, the common law imposes on a professional person a standard of reasonable skill and care (the Bolam test). Specifically, he is not required to guarantee results.

There is nothing to stop the parties agreeing to set a higher standard in their contract. Many clients take the view that at least some obligations of their consultants (such as the timely delivery of information) should be expressed as absolutes, rather than measured against the Bolam standard. However, consultants will frequently object to this, not least because their professional indemnity (PI) insurance cover will generally respond to common law liabilities only.

On the other hand, design and build contractors are required at common law to produce a building that achieves the contracted result (IBA v EMI Electronics and BICC Construction Ltd 14 BLR 9). They are treated in the same way as any other manufacturer of a complex product, such as a car or a computer.

Again it is possible to alter this obligation by contract. The JCT seeks to do this by watering down the contractor’s design liability to that of an architect or other professional designer (that is, to reasonable skill and care only). But many clients fail to see the logic in this. Why should some of the contractor’s obligations (like workmanship and materials) be subject to an absolute test and others (like design) be measured by a lower standard? After all, they are both steps towards the same end, namely delivery of a working finished product. In short, what the client wants and expects is a package deal: “design and build”, not “design” and “build”.

Contractors often plead that absolute design obligations fall outside the scope of their PI cover. That may or may not be true, but (in my humble opinion) it is a red-herring. Many of the contractor’s obligations are not insurable, for example, to build in a good and workmanlike manner and to use suitable materials. But no reputable contractor would object to them for that reason alone. In other words, professionals and contractors are in a different position as far as design liabilities are concerned.

I am not for a moment suggesting that design and build contractors should not be seen as professionals with specialist skills in their own right. That would be very much against the zeitgeist. But the overall service they offer is different, and it is right that the law should reflect this.

So where does “fitness for purpose” come in?

I think the problem is that “guaranteeing a result” and “fitness for purpose” have become confused. There is nothing at all wrong with asking a contractor to produce a building that meets specified performance requirements. Indeed (as my client pointed out) that is exactly what he is being paid to do.

What is objectionable is being asked to provide a facility that is suitable for any unspecified purpose that the client may choose to put it in future. It is unreasonable to expect an office building to serve as a process plant, any more than a family car is designed to negotiate the Cresta Run. This is an extreme example, but it nicely illustrates where fitness for purpose becomes a real problem.

The answer?

I suggest that we should say what we mean in our contracts, and not allow the glib term “fit for purpose” to muddy the waters. Contractors should deliver what they have bargained for, and clients should not expect contractors to guess what their future intentions might be. Then we can all stop worrying about fitness for purpose and get on with our day jobs.

5 thoughts on “The meaning of fitness for purpose

  1. I do like this article as it illustrates yet again the need for contracting parties to (a) really think about what it is they intend and then (b) simply write that intention into the contract in plain English (rather than relying on time-worn phrases which – simply through repeated usage – have acquired a certain cachet but, when tested, actually turn out to be unclear).

  2. Excellent blog John – the most sensible thing I have ever read on the subject. Many thanks.

  3. Good series of points.
    But I rather think it depends whether what is being produced under the contract is susceptible to being used for a variety of purposes (in which case the “fitness for purpose” phrase is unclear) or whether there is actually only one purpose.

    For example, an instrumentation and control system for a nuclear plant has only one application. Even if the phrase “fit for purpose” was not used in the contract at all, one would expect a court to conclude that the sophisticated parties at the time of contracting knew full well what the purpose would be, and no argument regarding unfitness for purpose would be admitted.

    My solution – to strike a balance between an internal client who wishes to maintain the phrase and subcontractors who often do not – is to agree its deletion, and to allow sole reference to Specifications/Scope of Supply; but to include a “Statement of Purpose” at the top of the Specificaitons document, which just describes in plain English what the Scope is expected to do.

Comments are closed.

Share this post on: