Project proposal checklist: scope, price and assumptions

State the outcome and the deliverables

Describe the decision or behavior the work supports, then list the concrete outputs. For a website, specify page templates, integrations, content responsibility, supported environments and handoff materials. For an advisory engagement, define the evidence, interviews, analysis and recommendation. Link each deliverable to a way the client can review and accept it.

Define the boundary and the client inputs

List exclusions, included review rounds, client-provided materials, access and the person who consolidates feedback. Explain which dates depend on those inputs. Avoid a sentence that promises a fixed date while silently assuming immediate approvals. The software workflow shows how dependencies control delivery; the consulting workflow covers evidence and discovery boundaries.

Make the price assumption explicit

Record the scope version, currency, quote and the cost basis used internally. An illustrative 18,000 delivery cost priced at 24,000 has a 25% gross margin, not a 25% markup. Check the margin calculator and distinguish any confidence-based cost allowance from profit. There is no need to publish every internal cost line to the client; there is a need to know which scope the quote buys.

Specify the collection sequence

Name the deposit and milestone collection assumptions. Distinguish when an invoice is issued from when funds are expected to arrive. In the illustrative 24,000 project, four equal collections can still leave a 2,400 gap when the first two phases each cost 7,200. Check the cash sequence and consider the effect of late collections before deciding the job is funded.

Explain how changes will be estimated

Describe how a requested change is identified, costed and reviewed before work starts. A new feature can affect testing, dependencies, direct expenses and delivery time as well as implementation hours. Use the scope-change tool for a deterministic first pass and the change-request guide when uncertainty affects the whole plan.

Record the assumptions that need revisiting

For each material assumption, write the evidence, owner and review trigger. Examples include vendor access by a date, a confirmed data format or a maximum number of review rounds. “Subject to assumptions” is too vague to help the next conversation. The bid-review checklist connects those assumptions to the internal decision to quote.

Finish with an actionable next step

State what the client needs to review, who can resolve questions and what information is needed to finalize the estimate. Keep an internal copy of the assumptions behind the proposal. Download the checklist below and use the estimate templates as supporting working files. This page does not establish enforceability, tax treatment or jurisdiction-specific contractual requirements.

These guides were prepared with AI assistance. Examples are illustrative calculations checked against the calculator code, not client case studies or market benchmarks.