Freelance and small business
List the assumptions behind a project estimate
Every estimate rests on assumptions about scope, revisions, and tools. Writing them down before you send a number makes a dispute less likely if the project turns out differently.
A text to start with
I am preparing an estimate for [brief project description]. My current thinking is roughly [estimated hours or range] across these tasks: [list tasks]. List the assumptions that would have to hold for this estimate to be accurate, including revision rounds, client response times, content or assets the client provides, and tools or access I will need. Do not add hours or suggest a different total.
Example request. Change the details to fit your situation.What to check in the answer
Mark each assumption as confirmed, awaiting an answer, or your own working estimate. Check which ones already appear in the proposal. If the estimate depends on the client supplying finished copy, say so and ask when it will arrive. Recalculate the hours when an assumption changes, and explain material changes to the client before work starts.
What to do next
Put the most important assumptions into the proposal so the client sees them before agreeing. Keep the full list for yourself. If the project runs long, that list is where a candid conversation about the reasons can begin.