Use an Assumptions Log to Keep Consulting Projects Honest

Consulting projects rarely go wrong because nobody worked hard. They go wrong because two people made different assumptions and neither one wrote them down.

The client assumed the data would be ready. You assumed the decision-maker would attend. Everyone assumed the recommendation would fit the current process. By the time the mismatch becomes visible, the project has already absorbed the cost.

An assumptions log gives uncertainty a place to live. It is a short, shared record of what must be true for the work to succeed.

Capture assumptions before they become dependencies

Review the proposal, discovery notes, and kickoff conversation. Look for statements that sound settled but have not been verified.

Common examples include:

• The client can provide the last 12 months of data.
• The sponsor can approve the recommendation.
• The current process is documented accurately.
• The team has capacity to implement the next step.

Write each assumption as a testable statement. “The client is aligned” is too vague. “The operations lead will approve the new intake step by Friday” gives the project something specific to confirm.

Add an owner and a test date

An assumption without an owner is only a concern. Give every line two fields: the person who can verify it and the date by which you need an answer.

Use a simple table:

The owner is not necessarily the person who created the assumption. It is the person with the fastest path to evidence.

Turn uncertainty into a conversation

Do not send the log as a warning list. Use it to guide the next useful question.

Instead of saying, “We still have a data risk,” ask, “Can we confirm whether closed projects are included in the export? If not, should we change the baseline or request a second file?”

This keeps the discussion practical. The client does not need to solve the entire project. They need to make the next decision while there are still options.

Update the log at each decision point

An assumptions log is most useful when it changes. Review it at kickoff, before analysis begins, before a recommendation is finalized, and whenever the project plan changes.

Mark each item as confirmed, disproved, or no longer relevant. When an assumption is false, record the decision it triggered. That history prevents the team from reopening the same uncertainty later.

Keep it short enough to use

The goal is not to document every possibility. Keep only assumptions that could affect the outcome, timing, scope, or client decision. A focused list of eight useful items beats a spreadsheet nobody reads.

When assumptions are visible, surprises become decisions. Keep consulting projects clear from uncertainty to action