Why companies don’t sign contracts by Tom Moore

Posted on October 29, 2014 by

9


It is surprising how often contracts between companies are not signed or executed properly. Case law is full of examples of disputes occurring between organisations who are both working to an unsigned contract. These usually centre on ‘contract by performance’ issues, i.e. there was a contract sort of agreed but it was never actually signed. One company is claiming that its version of the contract is the correct one and the other is relying on a different version. This unfortunately can end up in the infamous ‘money for lawyers’ scenario.

So, based on the premise that a signed contract is a good thing, why don’t companies sometimes sign contracts? I would speculate that the principle reason for this is bureaucratic inertia. It is often more difficult to sign a contract than to start working without anything signed-off. For example, in the following scenario:

In Big Company Ltd, the business process for signing contracts is as follows:

  • All contracts must be signed by the company secretary
  • All contracts must be presented to the company secretary with a fully signed recommendation report, which as a minimum, is to be signed by the relevant procurement manager, the relevant category manager, the main business stakeholder, the responsible business director and the relevant finance manage
  • In addition, a legal report must be presented, signed by the relevant lawyer

This would be a fairly typical scenario for a contract worth say £8m. Whilst this may seem like a reasonable and cautious approach to ensuring the business does not commit to rash contracts, it has a number of inherent weaknesses. Primarily, there are too many people in the approval process and the incentives are often mixed on whether it is better for them to sign the report or to ignore it. In addition, it is an administrative problem to get so many people signing a report, leaving aside the separate legal report.

Many is the hour I have spent traipsing around corporate headquarters with a bundle of reports and a pen, ready to hand to a signatory. If a signatory is ill or goes on holiday, this process stops, but the business driver for mobilising the contract continues. For example, an immoveable date such as ‘launch the product in time for the Christmas sales’ will not be delayed but the contract signing will be.

contracts

Returning to the scenario, next the signed reports are submitted to the company secretary, who promptly goes on holiday and doesn’t delegate his sign-off.  When he gets back from holiday, he has a query and returns the contract for further review. By this time the actual contract, i.e. the people doing the work, has already started. A PO was raised on the premise that the contract would be agreed but the PO refers to a contract that is not signed. The supplier is now being paid for a contract that was never signed as they are invoicing on the PO. So, we end up in a position where the contract is underway and the agreement was never executed.

To add to the inertia over signing, now that more information is known as the contract is underway, it is not unusual for one party to avoid executing the document. The performance of the contract may have unearthed something that may be counter to what they were going to sign up to, i.e. it is less risk for one party to never sign the agreement, and rely on ambiguities in what was the agreed version.

So, how do we minimise contracts not been signed? This probably deserves a book rather than a single post but if I could suggest one thing, it would be more delegation in sign-offs. It should be the people who have the true responsibility to successfully deliver who sign the contract, e.g. the programme manager or the senior procurement manager. This ensures that they have direct accountability for the outcomes of the contract and what was written in it.

30

Posted in: Guest Columnist