The costliest line in a bid is often the assumption nobody wrote down

Find the real problem first

• What you see

  The bid total is ready, but the producer can't say whether it assumes a ten-hour day, one company move, two rounds of client feedback, client-supplied product, or paid media usage.

• Why it happens

  The assumptions live in the producer's head, scattered through line notes, or tacked onto a cover email after the number is already locked in.

• What it costs you

  The client and your team read the same number two different ways. A routine question turns into scope you're not getting paid for, a rushed change order, or a strained relationship.

Three rules that hold in any tool

• Assumptions are part of the scope

  A price only makes sense next to the facts that made it possible. Keep the assumptions with the estimate version and carry them through option review and the hand to production.

• Not knowing is a fine answer

  Don't turn an unknown into a rosy default without flagging it. Name the open question, the working assumption, what it costs if you're wrong, who owns it, and the date you need an answer by.

• Give the big assumptions a trigger

  Say up front what happens if a fact changes: re-price it, dip into contingency, cut a change order, or eat the difference by agreement. Decide that now, not on the day it happens.

Run this on one real job

Don't move the whole company at once. Try it on one job you are bidding now, note what doesn't fit, and roll it out once your producers trust it.

1. 1

   Lock deliverables and usage

   Write down the number, format, length, aspect ratio, cutdowns, stills, captions, languages, where it runs, the territory, the term, paid media, and who owns the footage.

   • Every deliverable has a way to sign off
   • Usage and licensing are spelled out
   • Versions and languages aren't assumed
2. 2

   Nail down the shoot-day mechanics

   State the day length, number of shoot days, prep and wrap, locations, company moves, travel, turnaround, your weather plan, access, permits, and whether the client is on set.

   • Overtime is defined
   • Locations and moves are named
   • Travel days and mileage are spelled out
3. 3

   Name what the client provides and what you're not pricing

   List client-supplied product, talent, locations, brand assets, scripts, music, approvals, and insurance requirements. Say what's excluded without it sounding like an accusation.

   • Client items have due dates
   • A missing item has a stated consequence
   • Third-party costs are named
4. 4

   Set the rules for post and feedback

   Define edit rounds, who reviews, how feedback gets combined, revision timing, color, mix, graphics, music, the archive, delivery, and what counts as new scope.

   • Review rounds and reviewers are capped
   • Feedback deadlines fit the schedule
   • The change-order trigger is clear

How to tell it's working

1. Bids that went out with a full assumptions review
2. Questions after award that changed cost or schedule
3. Change orders you can trace back to a written assumption
4. Producer hours spent digging up what an old bid assumed

Where Production Engine helps

What the product does for this today, and where it stops.

Where it stops: Production Engine keeps assumptions with the estimate and shows them to the client, but it doesn't know your shop's risk appetite. Deciding what to flag, and what to do when a fact changes, is still a job for your producers.

Questions producers ask

• How long should an assumptions section be?

  Long enough to cover what actually affects price or schedule, short enough that someone will read it. Group it by topic and keep boilerplate separate from what's specific to this job.

• Should the client see the assumptions?

  Any assumption that touches price, scope, schedule, or what the client is on the hook for, yes. Keep internal risk notes private, but don't let them contradict what the client sees.

• What if the client can't answer before the bid is due?

  Price a stated working assumption, flag what it costs if you're wrong, and say what triggers a re-price. Both sides can live with uncertainty as long as they can see it.

More field guides

• Estimating software should make the handoff safer, not just the math fasterA plain guide to picking estimating software for production companies, covering rate cards, approvals, and getting bids into the budget without retyping.→
• An estimate version is a client promise, not a filenameA plain way to version production estimates so revisions, options, assumptions, and approvals all stay tied to the number the client saw.→
• Margin leaks before the shoot, when risk gets sold as a sure thingA step-by-step way to find where margin leaks in your bids: the hand-off, price overrides, assumptions, and how changes get approved.→