The Assumption Trap: Why 2026 Project Teams Need a Written Log, Not a Verbal Promise

Every project has a sentence that sounds helpful at the time and expensive later. It often begins: 'We'll confirm that separately.' A verbal assurance is given, a nod is exchanged and the meeting moves on. Months later, the same sentence reappears in a dispute about scope, cost or responsibility.

In 2026, UK organisations can ill afford that pattern. Margins are tighter, buyers are more accountable for value and suppliers are expected to evidence delivery. The quiet risk is not usually a dramatic failure. It is a chain of small assumptions that were never written down, never priced and never owned.

The assumption trap

An assumption is a belief about something outside the contract's explicit words: that access will be available, that data will be clean, that a third party will respond on time, that a licence is included. Some assumptions are reasonable. The problem is when they remain private. The buyer assumes the supplier has allowed for a task; the supplier assumes the buyer will provide something by a date. Both are acting in good faith, but neither has a record.

Public sector procurement makes this risk sharper. Tender documents, evaluation criteria and contract schedules create a formal framework, but delivery still depends on operational detail. A contracting authority may assume that existing systems will be ready for integration. A supplier may assume that named staff will be available for workshops. If those points are not recorded, the contract may not resolve them, and the project team is left to negotiate under pressure.

What a written assumptions log is

An assumptions log is a simple table. It does not need software or a lengthy procedure. It needs four columns: the assumption, the owner, the evidence or decision that supports it, and the impact if it proves wrong. A fifth column for review date is useful on longer projects.

The log should sit alongside the proposal, the statement of work and the change control process. It is not a substitute for either. It is the place where the unwritten becomes written. For example:

• The buyer will provide test data in the agreed format by week two.
• The existing system exposes an API with documented rate limits and no additional licence cost.
• Site access is available during normal working hours and does not require out-of-hours permits.
• Third-party software licences are excluded from the fixed price.
• Acceptance will be based on the criteria in the agreed schedule, not on a wider business outcome.
• Handover includes recorded knowledge transfer for up to six named staff.

These are not legalistic points. They are delivery facts. Writing them down does not create conflict; it exposes where conflict could arise while there is still time to solve it.

Where to use it

The log should appear at four points. First, in the proposal: state the assumptions that underpin the price and timetable. Second, in the statement of work: convert the material assumptions into obligations or explicit exclusions. Third, in change control: record new assumptions created by a change, and confirm which old ones no longer apply. Fourth, at handover: check which assumptions held, which failed and what remains outstanding.

In public sector work, the log can also support clarification questions during procurement and provide an audit trail after contract award. It shows that the supplier has thought about dependencies rather than simply priced a wish.

How to review it

A log that is written once and never read is just another document. Review it at kick-off, at each governance meeting and before any change is approved. Give every assumption an owner and a date. Close assumptions when they are confirmed, and convert them into contract terms when they become material. If an assumption is wrong, record the impact before the team absorbs it as unpaid work.

The tone matters. An assumptions log should be factual and calm. It is not a list of excuses or a way to reopen every commercial point. It is a shared register of what must be true for the plan to work.

A mark of quality

Some suppliers worry that an assumptions log looks cautious or bureaucratic. The opposite is usually true. A supplier that can write down its assumptions understands its delivery model, its dependencies and its pricing. A buyer that welcomes the log is signalling that it wants a mature relationship rather than a surprise at the end.

At CLI Ltd, we treat that discipline as part of commercial partnership, not an administrative extra. Clarity at the start is not overhead. It is the cheapest form of risk management available to a project. In 2026, with more scrutiny on public spending and commercial performance, the organisations that thrive will be those that make the invisible visible before signature. If a point matters to delivery, it should have a line in the log.