A Red Pen, Not a Solicitor: Three NDA Clauses I Always Query
Photo: The Société Commerciale Française de l'Indochine., Public domain, via Wikimedia Commons
An NDA turns up before almost every piece of work I do. Usually it arrives as a PDF with a filename like MUTUAL_NDA_FINAL_v3_signed_copy.pdf, which is a small lie on at least two counts. Nine times out of ten I read it, sign it, and get on with the actual job. It is not a document that deserves ceremony.
But there is a minority of NDAs that ask for considerably more than confidentiality, and they tend to give themselves away in the same three clauses. I have a standard response to each. None of it requires a solicitor, a call with a procurement team, or a dramatic email. It is mostly just a red pen, a polite covering note, and a willingness to be slightly boring about it.
When 'Mutual' Is Only a Word in the Title
The first thing I check is whether a document called a mutual NDA is actually mutual. It is surprisingly common to find a title page promising that both parties will keep each other's information confidential, followed by operative clauses that only bind one of them.
Sometimes it is a drafting error. Sometimes it is not. Either way, the fix is the same: make the obligations symmetrical, or rename the thing so it is honest about what it is. If a client genuinely only needs me to keep their information quiet, I am happy to sign a one-way NDA. I would just rather it says so on the front.
The subtler version of this problem is a mutual NDA where the definition of confidential information is broad enough to cover everything the client has ever said, but narrowly drawn for anything I might share. If I am disclosing my pricing model, my method, or the shape of a piece of work I have already delivered elsewhere, that deserves the same protection as their roadmap. Symmetry is not pedantry. It is the whole point of the word mutual.
What I ask for: a reciprocal definition, a reciprocal set of carve-outs, and a reciprocal term. What I strike: nothing, usually. The wording is normally fixable in a couple of tracked changes.
The IP Clause That Quietly Takes the Farm
This is the one that catches people out, because it rarely appears under a heading called Intellectual Property. It is more likely to be tucked into a definitions schedule or a sentence beginning 'all materials created in connection with the Services'.
The clause I look for is the one that assigns to the client everything I have ever created, or everything I create during the engagement, including things that have nothing to do with the engagement. I have seen NDAs — remember, NDAs — that purported to transfer background IP, tools, templates and methodologies I brought with me. That is not a confidentiality document. That is an asset transfer wearing a confidentiality document's coat.
The reasonable position is straightforward. The client should own the deliverables I am paid to produce for them, or have a licence to use them, depending on how the engagement is structured. I should keep the underlying know-how, the reusable frameworks, and anything I made before they turned up. If a clause cannot tell the difference between a deliverable and a method, it needs rewriting.
The second thing I check in this area is moral rights. Under UK law they can be waived, and plenty of contracts waive them by default. Usually I do not mind. Occasionally, on work that will be published under my name, I do. It is worth knowing which one you are signing.
The Non-Solicit That Bans You From Working
Non-solicit clauses are meant to stop one party from poaching the other's staff. Fair enough. The problem is that a carelessly drafted one can also stop me from doing ordinary business development with anyone the client has ever met.
I have been asked to agree that I will not 'solicit or otherwise deal with' the client's customers, suppliers, partners or contacts for the duration of the engagement and for two years afterwards. Read literally, that could rule out a conversation with a company that happens to be on their supplier list. For a consultant whose entire pipeline is built on warm introductions, that is a much bigger commitment than confidentiality.
The version I will sign is narrower. It restrains me from actively targeting named employees I have worked with during the engagement, for a defined period, for the purpose of poaching them. It does not restrain me from answering an inbound enquiry from someone who happens to know the client. It does not restrain me from working with a competitor. And it certainly does not restrain me from mentioning, in general terms, that I have worked in a particular sector.
If a client insists on the wider version, that is information. It usually means their procurement template was written for a much bigger supplier, and nobody has looked at it since. Sometimes a short conversation sorts it out. Sometimes it tells me something about how the engagement will run.
The Covering Note That Does the Work
I do not send redlined documents back with a lecture. I send them back with three or four sentences: here is what I have changed, here is why, happy to talk it through if helpful. I keep it friendly and I keep it short, because the person on the other end is usually an operations manager or a finance lead who did not draft the thing and would quite like to go home.
In my experience, most of these changes go through without argument. A minority get a small pushback. A very small number get escalated to someone in legal, at which point I decide whether the work is worth the wait. That decision is commercial, not personal.
When Walking Away Is the Sensible Move
I have turned down work over an NDA twice. Neither time was about confidentiality. Both times the document was trying to do something else — one was an IP grab dressed up as a mutual NDA, the other tried to lock me out of a sector I work in for three years.
For a small engagement, the right calculation is rarely 'can I win this argument'. It is 'is the argument worth more than the fee'. If a template is so far from reasonable that fixing it would take a week of emails, the sensible answer is usually to say thanks but no thanks and move on to the next enquiry. There is no shortage of people who will send you a normal NDA.
A Short Checklist Before You Sign
Three questions, in order. Is it genuinely mutual, or does it only bind one of us? Does it hand over IP I did not agree to hand over? And does it restrict my ordinary business development beyond the engagement itself?
If the answer is no, no and no, sign it and get back to work. If any answer is unclear, ask. That is not legal theatre. That is just reading the thing properly.