A consulting assumptions log makes uncertain inputs visible before they turn into rework. Record, test, and retire assumptions with this simple process.
Every consulting project begins with incomplete information. You estimate how quickly the client can provide data, which stakeholders need to approve the work, and whether the current process works the way people describe it.
Those assumptions are normal. The risk comes from letting them hide inside plans, estimates, and recommendations.
An assumptions log gives uncertain inputs a visible place in the project. It helps you test the most important ones early and adjust before they create expensive rework.
Write assumptions as statements you can test
“Data may be a problem” is a concern, not an assumption. Write the belief that the plan currently depends on.
- The client can provide twelve months of complete transaction data.
- The legal team can review the draft within five business days.
- Regional teams follow the same intake process.
Specific statements make it possible to ask for evidence. They also show what would need to change if the assumption is wrong.
Record the consequence of being wrong
Not every assumption deserves the same attention. Add the consequence so the team can focus on the beliefs that could change the project.
| Assumption | If wrong | How to test | Owner | Status |
|---|---|---|---|---|
| Transaction data is complete | Analysis must use a smaller sample | Review an export before analysis starts | Client data lead | Open |
Keep the consequence practical. Name the work, timing, or decision that would change. Avoid dramatic labels that make routine uncertainty sound like a crisis.
Test high-impact assumptions first
Prioritize assumptions by impact and uncertainty. A belief that is both uncertain and capable of changing the recommendation should be tested early.
You can often run a small test instead of waiting for perfect information:
1. Inspect a sample data export.
2. Walk one real case through the stated process.
3. Ask the decision owner to confirm the approval path.
4. Compare the planned capacity with the team's actual calendar.
The goal is not to eliminate uncertainty. It is to learn soon enough that the project still has options.
Connect assumptions to decisions
When an assumption supports a recommendation, name it in the decision material. For example: “This timeline assumes the client team can complete two reviews in the first week.”
That sentence helps the client evaluate the recommendation honestly. It also prevents the timeline from looking like an unconditional promise.
If the assumption changes, update the related decision, estimate, or plan. An assumptions log is useful only when it affects the work around it.
Retire assumptions when you learn
Review open assumptions at project checkpoints. Mark each one confirmed, disproved, or replaced. Preserve the result so the team can understand why the plan changed.
Do not let the log become a permanent list of vague possibilities. Close items when evidence arrives, and add new assumptions only when the project genuinely depends on them.
Good consulting does not pretend uncertainty is absent. It makes uncertainty manageable. A short assumptions log shows the client what the project relies on, what you are testing, and where an early answer can protect time and budget.
[Keep your consulting projects clear as new information arrives](https://getconsultkit.com)
ConsultKit makes it systematic
Each app starts at $9/month. Monthly billing only. See the current pricing steps and caps.
The Solo Consultant Brief
Weekly tips on referrals, pricing, and client management — straight to your inbox.
Prefer shorter ideas? Follow @getConsultKit on X.