Most fee disputes between clients and law firms are not really about money. They are about two honest, diverging memories of what was agreed. The client remembers commissioning "the contract work"; the firm remembers being asked to review one draft. Both acted in good faith; neither wrote the shared understanding down. Months later, the invoice becomes the first document that states what the engagement was — and by then it is too late to agree.
The cure is unglamorous: one page, written before the work starts, that both sides can point to later. Not an engagement letter full of liability boilerplate — a scope document. Here is what belongs on it.
The questions being answered
Start with the client's questions, in the client's words. "Can we terminate the distribution agreement without exposure?" "What does the financing round require from the board and the shareholders?" Three to five questions, concrete enough that at the end of the work anyone can check whether each one was answered.
This section does quiet, important work. Writing the questions forces the conversation about what the client actually needs — which is regularly not what was first asked for. And it gives the engagement a definition of done that both sides share from day one.
Deliverables, not activities
"Advising on the transaction" is an activity; it has no natural end. A deliverable is a thing: a memo answering the questions above, a marked-up draft with comments, a negotiated final version, a set of signing-ready corporate resolutions. Name each deliverable, and say what form it takes.
The test for this section: could a third party, holding only this page, verify that the work was delivered? If the answer is no, the scope is still an intention, not a scope.
Assumptions and exclusions
This is the honest heart of the page, and the part most often skipped. Assumptions state what the price relies on: the facts provided are accurate and complete, the counterparty is the entity named, the documents to review are the ones listed, no proceedings are pending. If an assumption fails, the scope conversation reopens — visibly, not resentfully.
Exclusions state what the work does not cover: tax structuring, foreign law, regulatory filings, negotiation beyond the agreed rounds. Clients sometimes read exclusions as stinginess. They are the opposite — every clearly excluded item is a dispute that cannot happen, because nobody can later assume it was included. The narrower and more explicit the boundary, the less room for diverging memories.
Timeline, price and the change mechanism
The timeline should show stages and dependencies, including the client's: the review starts when the documents arrive; the filing follows the board decision. A date without its dependency is a promise nobody can keep.
The price attaches to the deliverables — ideally per deliverable, so that partial changes have partial consequences. And then the clause that does the most work on the page: what happens when scope changes. New question, new counterparty, third round of negotiation nobody expected — the mechanism says that additional work is named as additional, priced before it starts, and agreed in writing, even if the writing is two lines in an email. Fee disputes almost never come from the original scope. They come from the changes that were absorbed silently and surfaced on the invoice.
What a good one looks like
One page — genuinely. Plain language a board member could read without a lawyer translating; if the scope needs jargon to be stated, it is not yet understood. Written before the work starts, acknowledged by both sides, and then actually used: referred to when a new request arrives, updated when the matter changes, checked when the work is delivered.
And where a matter is genuinely unpredictable — litigation is the honest example — the scope document says so, prices the phase that can be seen, and states when the next phase gets its own page. That is not a weaker scope; it is a truthful one.
We write a page like this at the start of every engagement, because our own pricing depends on it: fixed prices are only possible when scope is defined, and the discipline of questions, deliverables and change control is the same discipline that lets systems do the structured work while a named lawyer answers for the result. If your last legal invoice surprised you, the interesting question is what the scope page would have said — and we are happy to show you ours.