All insights / Scope and pricing
Practical guide
Price and schedule the work the client must supply
Make missing inputs visible before they become an unplanned delivery cost.
ContractCanvas insights
Assign the input
A project dependency should identify the material, responsible role and required stage. “Client to cooperate” is difficult to operate. “Client coordinator to supply the agreed sales extracts before analysis begins” gives both sides a clear task. Confirm that the client has permission to provide the material.
Describe the consequence
If the extracts arrive late, the consultant may have to resequence interviews or move the workshop. Decide how the parties will assess timing and additional effort. Do not automatically treat every delay as chargeable or silently absorb it. Record the decision in the change process.
Use an explicit assumption
For a sample engagement, assume three consolidated feedback rounds from one client representative. Five conflicting sets of comments create a different workload. The estimate should say who consolidates feedback and what happens when the agreed rounds are exceeded.
Check before approval
Review unresolved dependencies alongside fee and timing. In ContractCanvas, a dependency belongs in the scope record and should be visible in the client output. A green pipeline stage cannot resolve an unknown input. Keep the approval pending when an essential dependency prevents the parties from knowing what they are agreeing to.
Related reading
How to price an extra workshop before it becomes a promise
A consulting proposal and statement of work should tell the same story
Direct contribution and markup answer different consulting questions