The assumption document: The one-page attachment that prevents project friction

When a project goes off the rails, it usually happens because of a mismatch in expectations. The client assumes a certain task is included, and you assume it is not.

Most proposals try to fix this by listing every single thing you will do. But no matter how detailed your list is, it is impossible to list every single thing you will not do.

To solve this, you need to define the negative space of your project. You do this by creating an Assumption Document.

The power of defining what is not included

An Assumption Document is a simple, one-page attachment to your proposal. Instead of focusing on deliverables, it focuses on the boundaries and conditions of the project.

It explicitly states the parameters that you are operating under. When both parties agree to these assumptions upfront, you eliminate the "I thought that was included" conversation before it ever happens.

What to include in your assumption document

Keep it clear, objective, and focused on the mechanics of the project. Here are the standard sections to include:

1. Client responsibilities

Clearly state what you need from the client to succeed.
Example: "We assume the client will provide all final text and images by [Date]. Delays in receiving these assets will push the final delivery date accordingly."

2. Revision limits

Define exactly what a "revision" means so it does not become an endless loop.
Example: "The project includes two rounds of revisions. A revision is defined as minor tweaks to the existing layout. A complete redesign or new structural direction will require a new change order."

3. The technical reality check

Give specific examples of hidden friction to protect yourself from messy legacy systems.
Example: "We assume your current CMS allows for custom CSS injection. If we discover during development that your template is locked (e.g., a restrictive Wix or Squarespace tier), unlocking that functionality will require a separate scope and budget adjustment."

How this changes your workflow

When you send a proposal with an Assumption Document, you are not being restrictive. You are being professional. You are giving the client a clear map of how the project will run.

This document acts as a silent referee. When a client asks for something outside the boundaries later on, you can simply point back to the agreed-upon assumptions. It removes the personal friction and keeps the project moving smoothly.

Your next step

Defining your project boundaries upfront is one of the most effective ways to protect your time and ensure a smooth delivery.

To see how your current project boundaries impact your broader business health, run your business through our free check. In two minutes, it will score your business across the 4 key areas, identify your single highest-leverage constraint, and hand you the exact first fix and the order to execute it.

Zero paywalls on clarity.