scope creep

Why you need a client Engagement Letter and, importantly, why you need to keep it updated: Two recent cases

First off, for those who don’t know differently: in the world of professional services firms an ‘Engagement Letter’ isn’t an expression of love to another. Indeed, for us an ‘Engagement Letter’ might better be phrased as a ‘Pre-nup agreement’!

What is an Engagement Letter and why are they so important?
In the world of professional services firms, an ‘Engagement Letter‘ can generally defined as being:

“A document that sets out the business relationship between a client and their law firm. This letter serves as an agreement between the parties on the terms of their engagement. This includes details on the services being offered, client responsibilities, deadlines and compensation.”

Engagement Letters can include more, but in short they set out:

  • Exactly what the Scope of Services being provided are
  • Who is assigned to do what, and
  • How much the law firm will be paid by the client for doing said Scope of Services.

They are important for two main reasons: (1) on the part of the law firm they set out what the client’s expectations are – thus limiting the potential professional indemnity risk on the part of the firm; and (2) on the part of the client they set out the service standards, the expectations – they hold the law firm to account.

So, for both parties: a properly agreed to Engagement Letter sets out the expectations and assigns the risk – “win/win” as they say.

Two recent case studies
So let’s take a look at two recent cases that evidence just how important Engagement Letters are.

In the first case (a US-based medical case), a [medical] patient was billed US$230K for surgery having previously been advised – in their Engagement Letter – that the cost of the said surgery was estimated at US$1,300.

The Supreme Court in that case held that the estimate was protected by contract law, as no formal extension of scope letter had been issued and so the patient was only required to pay the US$1,300 original estimate.

Lesson Learnt: Send your out of scope (or extension of scope or variation of scope) letter out as soon as you are asked to do something that is not in your Engagement Letter.

In the second case (UK-based legal matter), a properly executed retainer agreement allowed a law firm to keep its agreed £300K fee, even though the bond issue that it related to was aborted.

Interestingly, the judge in the second case, His Honour Judge Paul Matthews, previously (as in a week earlier) made a comment – in reducing costs sought by a receiving party because all of the work was handled by a solicitor claiming grade A rates, that:

“it was not for the paying party to identify which work could have been delegated.”

See here

Lesson Learnt: Engagement Letters need to be properly drafted; but, importantly – get yourself a Project Manager to manage the case so that they can constantly review the work and ensure that any Out of Scope work is immediately communicated.

My 5 hints on how to manage Engagement Letters
If you follow these 5 hints, I think you’ll find you have far fewer issues with getting your fees paid:

  1. The most important thing to remember is to have an Engagement Letter with your client!
  2. Once you have the Engagement Letter, remember that it is not a ‘set and forget’ document. Don’t sign it, then put it in the file and forget it. Keep a copy close to hand and review it daily.
  3. If, at any time, you see Scope Creep happening, send an immediate notification to your client that you are being asked to do tasks outside of the originally agreed Scope of Works.
  4. And by ‘client’ here, I don’t mean the person asking you to do the work, but the person who will be paying the bill (accepting they may be the same).
  5. Finally, if your project is big enough, put a Project Manager in charge of reviewing and managing all of this.

As usual, comments are my own and I welcome feedback.

Have a great week all.

rws_01

Image credit goes to Scott Graham on Unslpash

Okay you can keep the ‘Legal’ tag; but it’s just Project Management!

I’ve been ‘white-boarding’ legal matters since my days helping out on front-end major projects back in 1996; so the concept of ‘mapping out’ how a transaction might progress, what may be ‘in scope’ and ‘out of scope’, the approximate amount of time the transaction may take and how we are going to resource it are not new to me. In more recent times (largely following the GFC in 2008) the legal industry has formalised my approach of ’white-boarding’ matters to become Legal Project Management. 

While I was never really that sure over the years how Legal Project Management differed from the more general Project Management, I have been assured – on numerous occasions – that there is a difference. When asked how, the most common response I received was that:-

  • Legal Project Management is the discipline of project managing ‘tacit knowledge’ – as ‘knowledge workers’, while
  • Project Management is the discipline of project managing tangible products, e.g., the construction of a hospital.

And until the last month or so I thought that was a pretty good answer.

So what changed?

Well, in the last month and a bit I have attended a collective 5 day (2 day and then a 3 day) course on Project Management Fundamentals run by PM-Partners Group here in Sydney.

The two day Fundamentals (essentially, theory) session was outstanding and broken-down into the following nine (9) modules:

  1. What makes projects succeed (and by implication, fail)
  2. The essential project management philosophy
  3. The project life cycle
  4. Project planning – project definition and scoping
  5. Project planning – creating the WBS & schedule
  6. Project planning – estimating
  7. Project risk
  8. Project execution & control
  9. Project closure

In turn, if you were on a course where you learnt all about: 

  • scope creep
  • the difference between what a risk is and what an issue is (hint, one has happened and the other hasn’t)
  • how to do a business case and a project plan
  • the triangle of scope, cost, time and quality
  • the four dependency types [finish-start; start-start; finish-finish; and start-finish], and
  • you get to work on creating a Work Breakdown Structure and Estimating (Optimistic, Pessimistic and Most Likely – also looking at the Cone of Uncertainty)

Wouldn’t you think you had been on one of the best Legal Project Management training courses around?

Well, that’s exactly what the two day PM-Partners run Project Management Fundamentals course taught me and I have walked away from that course thinking to myself that you can keep the classify ‘Legal’, at the end of the day it’s project management and it’s this type of project management we need to get better at.

My biggest take-out though?

Understanding the difference between a risk and an issue, because anyone doing pricing should get their head around this because it really is as important (and probably goes hand-in-hand with) as what happens with scope creep [helpful extra tip: want to understand scope creep, look up what happens with the formula: n (n – 1) /2].

Get in touch if you want to hear/find out more, otherwise get yourself on a really good PM Fundamentals course because I can guarantee it will pay for itself!

rws_01