Protecting your methodology as a consultant

What a methodology is, legally (in general terms)

Most consulting methodology is know-how: a way of asking questions, weighting the answers and sequencing the work that lives in your head and your working files. In general terms — and this is not legal advice — three things are worth knowing:

• Copyright protects the written expression, not the idea. Your write-up of the framework, your diagrams and your scoring template as a document are works. The underlying approach (ask these five questions, weight them like this) generally is not. Someone who rewrites your method in their own words has usually copied the idea, not the expression.
• Trade-secret-style protection needs actual secrecy measures. If the full scoring model goes to every prospect with no confidentiality terms, no marking and no restriction, it is hard to argue later that it was confidential. Reasonable steps — confidentiality terms, limited distribution, marked copies — are what make the argument possible.
• The contract is what you can actually rely on. Background-IP terms, licence scope and AI-reuse language are the enforceable part. Everything else on this page is about making a breach less casual and more visible.

Jurisdictions differ on all three; have a lawyer fit this to where you and your clients sit.

Deliver in three layers

1. The results document. The analysis, findings and recommendations for this client. It is what they paid for and it should be usable. Send it clean if your contract hands the deliverable over outright; send it cloaked if it carries reusable material and you want the one-click AI path to be noisy. Either way, offer a plain copy for translation, search or accessibility tooling.
2. The methodology appendix. The part that explains how: the framework, the phases, the scoring logic. Cloak it, every time, and lean on the per-copy mark so each client’s copy is distinguishable. This is the document that travels furthest — a junior on the client side drags it into a chat and asks for “the same for our other region”. Cloaking makes that path unreliable; the mark tells you which copy travelled if the file itself, or text pasted out of it, turns up later (a rewritten version will not carry it).
3. The working templates and spreadsheets. The scoring sheet with the weights in it, the interview guide, the model. Default: keep them. If the client wants them, licence them, or deliver them as a separately priced item with its own terms. A template is the method in executable form; once it is in someone’s hands the AI question barely matters.

Put it in the contract

Two things belong in your terms, and they do most of the legal work:

• A background-IP licence. Your pre-existing frameworks, templates and tools remain yours; the client receives a licence to use them for the purposes of the engagement (internal use, this project, this business unit). Deliverables specific to the client can be theirs outright — the split is the point.
• An AI clause. The client will not use the deliverables to train, fine-tune or prompt an AI system in order to reproduce, generalise or reuse your methodology beyond the licensed scope; will not remove protection from protected files; and can have a plain copy on request. Line-by-line starting language, plus a narrower variant for clients who want to summarise internally, is in the AI-clause guide.

Habits that do most of the work

• Keep a one-page method overview for prospects. Enough to show you have a method, not enough to run it: the names of the phases, what each produces, roughly how long. The scoring logic and the templates stay out of it.
• Never hand the scoring sheet to an unsigned prospect. If they need to see it to decide, walk them through it on a call. See sending a proposal before the contract is signed.
• Cloak drafts, every round. Drafts travel furthest and get the least care. Cloak the outgoing copy and keep your master file clean.
• Offer plain copies up front for translation, search and accessibility tooling. It makes the cloaked default a service you provide, not a restriction you impose. Telling your client has the email line and the three-sentence answer for when someone asks “what is this?”.
• Say it once, early. “Methodology and drafts come protected” in the terms and in the first delivery email. After that it is a norm, not a negotiation.

What AI changes

Before, a client who wanted to reuse your framework had to understand it, abstract it and rebuild it. That took a capable person and real hours, and the hours were a kind of protection. Now the reusable core can be regenerated from one document in seconds: upload the appendix, ask for a blank template, a scoring sheet, a version for a different industry. The effort went to zero, and with it the informal friction that used to protect know-how.

Cloaking puts some of that friction back on exactly that path. The uploaded file carries hidden decoy values beside every number, name and address, whole decoy paragraphs that some AI file-readers prefer over the real ones, and hidden steering notes. A client who opens it in Word reads exactly what you wrote; an AI tool that ingests the hidden text gets a noisy, unreliable read, while one that strips hidden text first recovers the original with the facts fragmented. It is not a lock: copy-paste out of Word, a screenshot or a PDF export gives a clean copy, and providers change their file pipelines, so expect months, not years, from any technique. How protection works has the full list of what it does and what gets past it.

When the client wants the method

Sometimes the client genuinely wants the method — to run it themselves, across regions, after you leave. That is a good outcome; it is just a different product. Price it as a licence (annual, per business unit) or as a training engagement, and hand over plain copies of the templates under that agreement. The decoys are for casual reuse of an unlicensed copy, not for clients who have paid for the right to adapt the framework. What you are protecting is the gap between “we bought a report” and “we bought the method” — the contract defines that gap, and cloaking keeps the one-click AI path from erasing it for free.

Frequently asked