What is Obligation of Result vs. Obligation of Means?

The distinction between obligation of result and obligation of means is one of the most practically relevant distinctions in contract law, but it is rarely discussed explicitly in everyday procurement.

An obligation of result is absolute regardless of the effort expended. An installer fitting a lift has an obligation of result: either the lift works or it does not. A lawyer handling a case typically has an obligation of means: they make their best effort to win, but cannot guarantee the outcome.

Many business services fall into a grey area. A cleaning company servicing a hotel lobby: is that a result (the lobby is clean) or a means (staff work for two hours)? An IT supplier implementing a system: is the result that the system functions, or that the team invests sufficient hours?

The contract wording is decisive. Phrases such as "the contractor will use its best efforts" or "the contractor will endeavour to" indicate an obligation of means. Phrases such as "the contractor delivers X by date Y" point to an obligation of result.

As a buyer, it is worth thinking through for each service which type of obligation is appropriate and having that explicitly reflected in the contract. The conversation itself often surfaces useful information about the supplier's own expectations.

With an obligation of means, you as the buyer bear the burden of proving that the supplier fell short when results are disappointing. That is difficult. With an obligation of result, the result itself is the proof: either it is there or it is not.

For SMBs who want to be able to act quickly when a supplier disappoints, an obligation of result is the strongest position. Ensure the contract wording clearly describes the obligation and avoid vague formulations that drift towards best efforts.