How to scope a consulting engagement before you sign anything
Most consulting engagements that go badly wrong do so in the first two weeks, not the last two. The problem is usually not the consultant's competence or the client's intentions. It is that neither party was specific enough about what the work was supposed to produce, by when, and for whom. Scoping is the part of the process that fixes that, and it is the part most clients are in a hurry to skip.
What a scope document should actually contain
A scope document is not a contract, though it often forms the basis of one. Its purpose is to make the implicit explicit: what problem are we solving, what will we produce, who will be involved, and what does done look like. A good scope document is short enough to read in ten minutes and specific enough that both parties would describe the engagement the same way if asked independently.
At minimum, it should name the deliverables (a written report, a facilitated session, a set of recommendations), the timeline with specific milestones, the fee and payment schedule, and the conditions under which the scope might change. It should also name what is not included, which is often more useful than what is.
How to set a realistic timeline
Clients consistently underestimate how much of their own time a consulting engagement requires. A strategic planning process does not happen to an organization; it happens with one. That means interviews, review sessions, feedback rounds, and decisions that only the client can make.
A realistic timeline accounts for the client's calendar, not just the consultant's. If your leadership team is unavailable for three weeks in July, the timeline should reflect that. If a board decision is needed before the next phase can begin, the timeline should include the board meeting date. Building these constraints in at the start prevents the frustration of a process that stalls in the middle for reasons that were entirely predictable.
Fixed fees versus time-and-materials
Fixed fees work well when the scope is clear. They give the client cost certainty and give the consultant an incentive to work efficiently. The risk is that if the scope is not actually clear, a fixed fee creates pressure to cut corners when the work turns out to be more complex than expected.
Time-and-materials arrangements work better when the problem is genuinely uncertain at the outset. They require more trust and more active oversight from the client. A monthly cap or a not-to-exceed figure can provide some cost certainty without the rigidity of a fixed fee.
The right answer depends on the engagement. For a process efficiency review with a defined output, a fixed fee is usually appropriate. For an interim advisory retainer where the issues will emerge over time, a monthly rate makes more sense.
The time spent on scoping is not overhead. It is the work. An engagement that begins with a clear, agreed scope is more likely to produce something the client can use.