A contract is a memory of past arguments

The clause is the scar. The wound is not in the document, and it is the only part worth knowing.

3 min read

Contents

Producing a set of master service agreement templates is not a writing job. It is collection. You gather agreements from everywhere you can reach, from previous engagements, from whatever the last few clients sent over, from the public versions of firms who do similar work, and you sit and read them, and the reading is closer to archaeology than to drafting.

The consultancy that asked me for a set had been working without any. Not a set to improve. A set to have.

Every strange clause is a story with the story removed

Standard agreements are boring in the middle and strange at the edges, and the strange parts are where all the information is.

A clause specifying who owns the partially finished work if the engagement stops halfway. A clause stating that the absence of any particular individual does not suspend a deadline. A clause that pins down exactly how many rounds of review are included and what happens on the fourth. None of those is a general principle. Each one is somebody’s specific afternoon, and you can very nearly reconstruct the afternoon from the clause.

Somebody stopped halfway and both sides discovered they disagreed about a folder of half finished work. Somebody’s one indispensable person left and the client was told the date had moved. Somebody reviewed a deliverable eleven times.

The document is the scar. The wound is not in it anywhere, which is the whole problem, because the scar is what you inherit and the wound is what would tell you whether you need it.

The test I ended up using

Reading it as history gave me the only drafting rule I trust. If I could not reconstruct a plausible story behind a clause, it came out.

Not because a clause with no story is wrong. Usually it is fine, and often it is somebody’s genuine best guess. It comes out because nobody in the building can defend it. The first time a client pushes back on it, whoever is on the call will drop it, because they have no reason not to, and a clause that gets traded away in every negotiation is worse than an absent one. Its only observable effect is to teach the other side that our paper is negotiable, and that lesson gets applied to the clauses we do care about.

So the test is not whether a clause is good. It is whether anyone here can say what it is for without reading it aloud again.

Where I had it exactly backwards

The reading is seductive, and I over-applied it for the better part of a year.

Once you decide that clauses are compressed history, every clause becomes legible, and legibility feels like understanding. I could produce a story for anything. Give me an odd notice period and I will give you a fluent account of the dispute that must have caused it, and the account will be well constructed, and I have no way of knowing whether it happened.

Because a great many clauses are not scars. They are copies. Somebody assembled a template from other templates, exactly as I was doing, and kept a clause because it was there and looked responsible, and their document was then copied by somebody who assumed it meant something. Boilerplate propagates by imitation at least as much as by injury, and from inside the document the two are identical. Compressed trauma and compressed imitation read the same on the page.

Which makes my own test weaker than I want it to be. I was not asking whether a clause had a story. I was asking whether I could invent one, and I am good at that, and being good at it is precisely the disqualification.

What is actually being chosen

The honest description of building a template from scratch is that you are choosing whose history to inherit, mostly without being told what any of it was.

You end up with a document that is largely other people’s memories of arguments you were not in, arranged by somebody who could not verify a single one of them. It will work. It will probably work for years. And the only clauses in it I will ever be genuinely sure about are the ones added later, after something goes wrong on an engagement I ran.

By then the story will not be in the document either. It will be one sentence that reads like all the others, and somebody assembling their first template will find it, and keep it, because it looks like it must be there for a reason.

All essays