Weirdly, avoiding disputes does not seem to be a key factor driving the drafting of contracts (although PPC2000 might be an exception). However, given the rising cost and time involved in resolving disputes, as well as the damage to reputations and the sustainability of a company, it should be.

My newsletters [sign up] consider how you can use your contracts to avoid disastrous disputes which take time, money and your energy away from running a successful business.

What should you do before you sign?

Here are some tips to help avoid disputes before you sign on the dotted line, in rough chronological order:

  1. Focus on clarity and certainty of terms (2 March)
  2. Record what has been agreed, without adding nasties ‘just in case’ (17 February)
  3. Write your scope so clients can tell when works or services are extras (6 July)
  4. Read and read and read again to ensure your contract cannot possibly be misunderstood (30 March)
  5. Get your contract peer-reviewed to see if it really makes sense and accurately records your deal (8 June)
  6. Build good frameworks rather than relying on tried and tested clauses (26 May)

What should you do after you sign?

Once your contract is in place then you need to:

  1. Use your contracts to provide processes to resolve problems, not wriggle out of liability (27 April)
  2. Keep on innovating rather than sue imitators (22 December)
  3. Follow the procedures properly (8 December)
  4. Don’t let bad payment practices become the norm – gently nudge those who get it wrong (24 November)
  5. Admit failures by interpreting the data (10 November)
  6. Rely on limits to cut off old claims (25 October)

You should not assume that other businesses are ‘out to get you’ (5 Jan), or pin your hopes on a watertight contract (12 May). Instead draft a contract based on the 97% who will be trustworthy (more on trust).

Like this article?

Share on facebook
Share on Facebook
Share on twitter
Share on Twitter
Share on linkedin
Share on LinkedIn
Share on pinterest
Share on Pinterest

Leave a comment