Search for what a fractional engagement contract looks like and you will find templates to buy, law firms offering to draft one, and very little from anybody who has actually run a practice on the paperwork they are describing.
This is the structure I used across my own consulting engagements, why each part of it exists, and the specific mistakes that produced it. It is not legal advice and it does not reproduce any clauses. It is document architecture and commercial practice - the part your solicitor will not tell you because it is not their job to know how a two-day-a-week engagement gets sold and re-sold inside the same client.
Offer, proposal, contract: three documents people merge
People mess this up constantly, and LinkedIn does not help, because it uses offer and proposal interchangeably. They are three separate things with three separate jobs.
| Document | Who sees it | Its only job |
|---|---|---|
| Offer | You. Never the client | Design what you take to market |
| Proposal | One specific client | Seek permission to proceed to contract |
| Contract | Both parties, legally | Protect both sides once agreed |
Your offer is an internal design document. It sets out what you sell, who it is for, what problem it solves, how it is structured and what it costs. You design it once, it lives alongside your ICP, and you refine it over time. It is not a capability statement, it is not a job title, and it is not a long list of things you could theoretically do. And you never send it to a client.
Your proposal is the client-facing document, and it is specific to that client. It explains what you are recommending, why it is the right next step, what it involves, what it costs and what happens next. That is the whole document.
A proposal is nothing more than a formalisation of a conversation you have already had. It is a statement of intent. It is not binding, it is not a legal document, and its only job is to seek permission to proceed to contract.
I have seen proposals containing biographies, pitch decks, logo lists and a great deal of philosophical nonsense. You already did the pitch when you did the discovery call. Nobody needs sixty pages of your heritage.
The failure mode here is common and expensive: a consultant has a good discovery call and then sends something contractual. That frightens the client away. At that point in the process they want the conversation written down so they can give you permission to proceed - not a document their legal team has to look at.
The contract comes after permission is granted. It is the legal formalisation of what the proposal already agreed: scope, intellectual property ownership, payment terms, termination, liability, confidentiality, and twenty other phrases.
Never work without a contract
This should be obvious and it is not, because I have met a great many people over the years who skip it.
It is not a question of whether you will get burned. It is a question of when. You might get away with it three or four times. Dopamine and excitement seem to eradicate common sense - the client says yes, everyone is delighted, work starts on Monday, and a month later there is no document backing any of it.
When it goes wrong it stings, and it usually goes wrong in the least dramatic way imaginable: not fraud, just two people who remember the conversation differently and no paper to settle it.
Why the contract should be two documents
Here is the lesson that produced everything below.
Early on I could win work verbally and on principle very quickly. Then I would write a monolithic statement of work covering everything - terms, scope, price, the lot - hand it over for signature, and watch it disappear into a compliance black hole. Sometimes a week. Sometimes four. On one engagement it took nearly two months to get the paperwork signed.
Any team with a name - legal, audit, compliance, procurement - can slow a process down dramatically. When I was getting contracts signed off with clients, procurement was reliably my biggest headache.
Now look at the shape of a fractional business. You usually start by doing something small. And if it goes well, you assume you will produce multiple pieces of work for that client over time. What you cannot afford is for every single one of those to fall into the same black hole.
So separate the legalities from the work.
| Master Services Agreement | Statement of Work | |
|---|---|---|
| Contains | All standard terms. No description of the work | All the work. No standard terms |
| Lives for | The whole client relationship | That one engagement |
| Signed off by | Procurement, legal or compliance | Your sponsor, on their budget authority |
| Signed | Once | Every new piece of work |
| Facing | Compliance and audit | Procurement and the commercial decision |
The Master Services Agreement is the umbrella. It gets signed off once and it lives for the rest of the relationship with that client. Every subsequent Statement of Work pops in underneath it.
The Statement of Work is smaller and lighter, which means your stakeholder can very often sign it themselves if they have budget authority. It does not have to go back through the procurement cycle at all.
The practical effect: the second engagement with a client can start in days rather than weeks, and the third one in hours. That difference compounds across a practice.
There is a second-order benefit worth naming. Once the relationship looks like it is heading somewhere, you can send the Master Services Agreement into the client early - before the commercial terms are settled - precisely because it is the document that takes time to clear. By the time you agree the work, the slow half is already done.
I ran this on genuinely large engagements too. On a multi-million pound programme I had an overarching Statement of Work setting out the end-to-end cost over three years, with individual Statements of Work underneath it for each phase. The structure scales in both directions.
What belongs in each
The Master Services Agreement carries the standard terms and definitions and none of the engagement: payment terms, termination, liability, confidentiality, intellectual property ownership, data protection, force majeure, right of replacement. The boring, load-bearing material that is identical across every client you will ever have.
Which is the point. Roughly ninety per cent of the content of my Master Services Agreement was in every Master Services Agreement I ever sent, because the template was strong. Build it once, properly.
The Statement of Work carries scope, assumptions, risks and cost. That is the list. About sixty per cent of what goes into a Statement of Work goes into every Statement of Work, which gives you a substantial head start each time without pretending the document is generic.
One warning on templates. Build a master template and generate each new document from it. Do not copy the last completed one and adjust it - that is how a client's name survives into somebody else's contract, and how a bespoke concession you made once quietly becomes your standard terms. Keep the masters in one place with version control so you know which one you are using.
On data protection specifically: my own view is that it belongs on the privacy side of the relationship rather than the commercial one. If a client wants extensive data protection clauses, the cleanest answer is usually to sign into a separate privacy agreement on their paper rather than inflating the commercial document.
Scope, assumptions, risks: the three lines that let you reprice
This is the part that matters most, and it is the part people skip.
A fixed-price Statement of Work is priced on value, not on days. That only works if you can point at what the price was built on. Scope, assumptions and risks are your get-out-of-jail cards.
Each one is a condition. If the scope changes, if the assumptions fall apart, or if a risk crystallises, that is an event that entitles you to look back at the document and ask whether it still holds. If it does not, you have options: change the scope, change the timetable, change the cost, or change the blend of what you are doing.
What you do not change is quality. Time, cost, scope - you can move any of those. Quality stays out of the negotiation.
I have had the argument with people who would rather take day-rate work because pricing a fixed Statement of Work felt too dangerous. The reason it feels dangerous is that it was never scoped properly. When the wheels come off and you have no document saying this was the scope, these were the assumptions, these were the risks, you are walking into a conversation that sounds like you want more money.
Do the work up front, and in my experience - having done this a hundred-odd times - even the most obstinate founder or CFO will have the conversation. It becomes: this is what we thought it was at the beginning, this is what it now is, I am not saying it cannot be done, I am saying it is not achievable on the original cost base. That is a reasonable conversation between adults. The other one is a row.
The pricing decision underneath all of this is covered separately in fractional consulting rates, including why day rates create the ceiling that a scoped fixed price does not.
A retainer contract and an outcome contract are different shapes
Every recurring engagement is a retained contract, and there are really only two commercial models underneath everything: recurring revenue, or a single number split across milestones or paid up front.
The retainer Statement of Work is short. Two pages. A table of key parameters, the headline scope, why you are doing this and what it achieves, the service parameters - board meetings, board packs, holding the function, delivering the annual plan - the agreed outcomes, the communication protocols, and the term. Is this a one-year agreement with twelve monthly payments, or a three-year agreement with a discount for the commitment? That is close to the whole document, because the Master Services Agreement is carrying the weight.
The outcome Statement of Work is heavier. Same front page, same table of key parameters, and then appendices covering scope, assumptions and risks in detail - because those three are what make the fixed price defensible for both sides.
The NDA, and whose paper you sign on
An NDA is a simple document: you will not repeat what you heard, they will not repeat what you said. It stands alone, and sometimes it travels with the Master Services Agreement.
I offer one on instinct, and the trigger is specific. When a founder or CEO says we have got this going on but we cannot really talk about it, or there is a potential transaction we are not allowed to discuss - if it is relevant enough for them to raise, it is relevant enough for me to unlock. So I offer an NDA so they can talk freely, because whatever they are holding back is usually the thing that determines whether I can help at all. A good number of organisations read the offer itself as a proactive, professional move.
On whose paper: I am asked this a lot, and no, I do not insist on my own. The question is whether their paper adversely affects me. If it does not, I do not mind. NDAs are, ironically, relatively inert documents once you actually read them, and if signing theirs greases the wheels then sign theirs.
The same principle held on the heavier documents, with one caveat from experience. Two enterprise clients wanted me on their paper for the Master Services Agreement and Statement of Work. In both cases the first draft their procurement team sent through was poor, so I sent back a copy of mine as an illustration of the level of detail and completeness we needed to reach. In both cases they adopted it.
Send it as a PDF
Small point, expensive lesson.
If you send a Word document, you are handing somebody a document in an editable condition. Early in my consulting career a client modified key aspects of a document before signing it and sending it back, and I did not notice. When a difference of opinion arose later and I went back to the contract, I could not argue it, because I had accepted a signed copy that had been changed.
It does not happen often. It only has to happen once. Ship final documents as PDFs.
Scope control is not about saying no
The last thing, and it is the one I would most like people to take away.
People see the word scope and they believe it is about saying no. It is the opposite. It is about putting the work in the right vehicle and then delivering it.
When a client comes to me and asks whether I could also do X, Y and Z, my strongest answer is: yes, absolutely I can. And it does not fit within the Statement of Work we are running at the moment, and if I bring it inside, it puts that work at risk. So why do we not structure it as its own Statement of Work, price it, timetable it and deliver it?
I may well have the capacity to run both in parallel. But the two should never be the same document, because otherwise the successes of one are undermined by the failures of the other. A single delay on the new work becomes a delay on the engagement that was going perfectly well.
This is why the two-document structure earns its keep a second time. Adding a Statement of Work under an existing Master Services Agreement is a light, fast, familiar act. Reopening a monolithic contract to add a workstream is neither, which is exactly why people absorb the work instead and quietly lose money on it.
Frequently Asked Questions
What does a typical fractional engagement contract look like?
Two documents rather than one. A Master Services Agreement carries the standard terms - payment terms, termination, liability, confidentiality, intellectual property ownership, data protection, force majeure, right of replacement - and describes none of the work. A Statement of Work sits underneath it and carries the scope, assumptions, risks and costs, and repeats none of the standard terms. The MSA is signed once and lasts the whole relationship. A new Statement of Work is issued for each piece of work.
Is a proposal the same as a contract?
No, and treating them as the same thing costs deals. A proposal is a statement of intent. It formalises a conversation you have already had and it has exactly one job: to seek permission to proceed to contract. It is not binding and it should not read like a legal document. The contract follows once permission is granted and is the legal formalisation of what the proposal already agreed. Sending a contract when the client expected a proposal frightens people off.
Why split the contract into a Master Services Agreement and a Statement of Work?
Speed. The heavy document is the one that goes to procurement, legal, audit or compliance, and those reviews take weeks. Once the Master Services Agreement is signed it lasts the length of the relationship, so every subsequent Statement of Work only needs the sponsor's signature and their budget authority rather than another trip through the review cycle. One monolithic contract per engagement means starting that cycle again every time.
What should be in a fractional Statement of Work?
Scope, assumptions, risks and cost. Those four, and nothing that belongs in the standard terms. Scope, assumptions and risks are what make a fixed-price engagement safe to sign, because each of them is a condition the price was built on. If the scope moves, the assumptions turn out to be wrong or a risk materialises, you have a document to hold up rather than a conversation that sounds like asking for more money.
Do I need an NDA as a fractional consultant?
Not always, but offering one is useful more often than people expect. When a founder or CEO says there is something going on that they cannot really discuss, that is the moment to offer an NDA, because whatever they are holding back is usually the thing that determines whether you can help. Many organisations read the offer as a professional signal. If they would rather use their own paper, that is normally fine - NDAs are comparatively inert documents.
Should I send contracts as Word documents or PDFs?
PDF. A Word document is shipped in an editable condition. A client once modified key aspects of a document before signing it and returning it, and the modification went unnoticed - which meant that when a difference of opinion arose later, the signed copy could not be argued with. It is rare, and it only has to happen once. Send the final document in a format that is harder to alter quietly.
How do I handle a client asking for work outside the scope?
Put it in its own vehicle rather than refusing it. Scope control is widely misread as saying no; it is the opposite. The answer is yes, this is worth doing, and it does not fit inside the Statement of Work we are running - so let us structure it as a separate one, price it and timetable it. Absorbing extra work into a running engagement means the failures of the new work undermine the successes of the original.
Where to go from here
If you take one structural thing from this, take the split. Two documents instead of one is a twenty-minute decision that removes weeks of delay from every engagement after your first with a given client, and it is the single change most likely to make your second sale to an existing client feel easy.
If you take one behavioural thing, take the scope point. The consultants who lose money on fixed-price work are almost never the ones who priced it wrong. They are the ones who never wrote down what the price assumed.
Once the contract is signed, the next question is when you get paid, which has its own set of decisions: invoicing and payment terms for fractional consultants. And delivering the engagement covers what happens after the paperwork is done.
The Ultimate Guide to Fractional Consulting is free and it goes deeper on this. The paperwork follows the product, and the guide covers the three ways this market pays before you get to documenting any of them - including why a scoped, fixed-price piece of execution needs more work up front than a day rate and repays it every time something changes.
The Fractional Formula builds the commercial side - ICP, offer, profile, pipeline and price - in six weeks. Pieces like this one go out first in Fractionally Thinking, every Friday.
