Consulting & AdvisoryFree
Consulting Engagement Scope Boundary Note
Every boundary line in your scope given a unit and a threshold, then scored against what your first week of intake already found.
River reads the signed scope, the proposal behind it and everything the first week turned up, then writes the boundary note and the change trigger register together. Every line in scope carries a unit and a baseline count. Every line out of scope names the countable condition that would bring it back in, who causes that condition, and what it costs in days. Then the register is scored against the intake findings, which is how you find the triggers that fired before day one.
Search this and you get the same outline everywhere: objectives, deliverables, in scope, out of scope, assumptions, then a paragraph promising a written change request process. Out of scope is always a list of nouns and assumptions are always a list of hopes. Neither gets a unit. A boundary you cannot count is a boundary you argue about, and the argument lands in month two, when the work is half done and the sponsor has already given their board a number.
Built for the independent consultant on a fixed fee, the boutique principal who signs the scope and then delivers it, and the delivery lead who inherited somebody else's statement of work. Run it at the end of week one, once the data room has a reading order and the stakeholder list is real. The register then supplies the trigger reference behind every variance in the weekly status report. Every threshold quotes the scope section it came from.
Out of scope is a number, not a noun
Public buyers stopped accepting adjectives a long time ago. Federal agencies have to describe work in terms of required results and enable assessment against measurable performance standards. Federal grant recipients need prior written approval for any change in scope or objective, and the rule says so even where no budget revision follows. A change that costs nothing still goes on the record, because it moves what the work rests on.
Brindlemere Foods, a chilled food distributor running nine depots, bought an eight week cost to serve diagnostic for a fixed $198,000. At the blended $1,650 a day the fee was built from, that is 120 days sold. Intake produced sixteen triggers against the signed scope, and five had already fired before the first workshop. Priced at the rate the fee assumed, those five come to 30 days and $49,500, a quarter of the fee, owed on the day of signature.
Eighteen of those 30 days are client caused, so one change order in week one prices them at $29,700 against a baseline both sides wrote down. Twelve came from the consultant's own estimate and get named as theirs before they are spent. Raised in month two as four separate asks with no register behind them, the same 30 days is $49,500 of overrun. A fixed price adjusts nothing for cost experience, which is why only the week one version pays.
How it works
Send the scope
The signed statement of work, the proposal behind it, and whatever the first week turned up.
Give the rate
The fee and the blended day rate, so every trigger comes back priced in days and in money.
Read what fired
The triggers your own findings have already tripped, with the cause and the cost on each.
Raise it early
Take the priced change order to the sponsor while it is still a baseline conversation.
What you get
- A boundary note where every line in scope and out carries a unit and a number
- The change trigger register, one row per trigger, with its threshold and day cost
- Cause named on every row, so chargeable and absorbed separate before the argument
- Each assumption inverted into a trigger, and the ones with no unit rewritten
- The triggers your own intake findings have already fired, priced and ready to raise
- Zero cost changes that still need written approval, which change processes miss
Common questions
What does it need from me?
The signed scope, the proposal or RFP behind it, and the notes from your first week. Add the fee and the blended day rate and every trigger comes back priced in both days and money. Without the rate you still get the register, priced in days, with the money column waiting on one number.
The scope is already signed. Is it too late?
Signed is the normal case and the better one. A trigger only means something against a baseline somebody agreed to, and a signed scope is exactly that. What changes after signature is that the register is scored against real findings rather than guesses, so the rows that fired come with evidence attached.
How is this different from a change control clause?
A change control clause says how a change gets approved. It never says what counts as a change, which is the part every dispute turns on. This produces the list your clause needs: the specific countable conditions, agreed in advance, so the week two question is whether a threshold was crossed rather than whose reading is fairer.
What makes a trigger enforceable?
A unit, a baseline and a source. Twelve interviews with the twelve people named in Appendix A is enforceable because anybody can count it. Reasonable stakeholder access is not, because the count is an opinion. Every row cites the scope section it came from, so the threshold is the client's own language rather than yours.
Who decides whether a trigger is my fault?
You do, in writing, before the days are spent. The cause column carries client, ours or neither, and putting your own estimating misses in the second bucket is what makes the first bucket credible. A register that files every surprise as client scope creep loses its authority the moment somebody checks one row.
What if the client will not sign a register?
It still works, because most of its value is internal. Knowing that 30 days are already exposed in week one changes how you staff, sequence and pace the work. It also means the eventual conversation opens with dated evidence rather than a feeling that the engagement got heavier than it was sold.
Where does this fit in the engagement?
End of week one, after the rest of engagement intake has run and the previous firm's work has been read for what it already refused. From then on the register supplies the baseline behind the workplan's forecast to complete. One boundary outlives the work: what you destroy afterwards, on the destruction schedule.
Consulting Engagement Scope Boundary Note
Fill in the form and your workspace opens with the work already underway.