A stale rate rides into your next bid inside an old file
A stale rate never announces itself. It slips in through a copied bid, survives because the total looks about right, and quietly becomes the company's price one job at a time.
Who it's for: Commercial shops with more than one estimator, rates that move with the market, client-specific deals, or owned gear that gets priced differently from job to job.
Find the real problem first
What you see
Recent estimates show several different numbers for the same role or package, and producers can't tell a negotiated deal from an outdated default.
Why it happens
An old bid is easier to copy than the rate card is to look up. Exceptions aren't tagged, nobody reviews them, and they never make it back onto the card.
What it costs you
The company can't tell whether it's deliberately pricing a relationship or just inheriting old numbers by accident. Margin gets harder to read and the fix arrives too late.
Three rules that hold in any tool
Drift can be measured
Compare what you actually sold against the card that was active when the estimate went out. The gap, the reason, who made the call, and the dollars at stake should be visible without digging through the old file.
An exception is not a new default
A discount for a client, a bundled package, or a strategic price can be the right call. Keep it tied to that one decision instead of letting the next copied bid turn it into the new normal.
Only a pattern should move the card
Update rates from real vendor quotes, crew expectations, market changes, and how closed jobs actually performed. A single anecdote should trigger a look, not an automatic repricing.
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.
Run a 90-day check
Pull the roles, packages, and markup lines that show up most in recent bids. Compare each one against the rate card that was actually in effect on the day that estimate went out.
- Compare against the card as of the estimate's date, not today's card
- Set client-specific deals aside from the rest
- Put a dollar figure on the revenue and margin at stake
Give every real exception a reason
Use a short, fixed list of reasons: market moved, client concession, package logic, one-off scope, correction, or an exception nobody approved. A free-text note can add color, but it shouldn't stand in for one of these.
- You've defined how big a gap has to be before it counts
- Who made the call and who approved it are both on record
- Every unapproved exception has an owner chasing it down
Make the rate card the easy path
The rate card should be faster to use than an old estimate. Show matching rates right inside the estimate, flag anything that's a fallback, and say why a suggested number is being used.
- The rate card shows up inside the estimate itself
- A missing match is visible, not silent
- Copying an old estimate doesn't quietly carry old numbers forward
Review the pattern once a month
Look for the same exception showing up again and again by role, client, market, or producer. Then either change the card, write a client-specific rule, coach the producer, or decide to accept it on purpose.
- Every repeat exception gets an actual decision
- A short note goes out whenever something changes
- New rates carry a clear effective date
How to tell it's working
- Dollar-weighted gap between sold rates and the active card
- Exceptions with no recorded reason
- Repeat exceptions that turned into an actual reviewed rule
- Estimates that used a fallback rate even though the company card had a match
Where Production Engine helps
What the product does for this today, and where it stops.
What it does today
- Keeps your company's active rate card separate from the numbers baked into old estimates
- Puts a matching company rate in front of the estimate first, ahead of any fallback
- Records which option the client approved and when
Where it stops: Production Engine doesn't have a report that flags drifted rates for you. It keeps the rate card and each estimate's line rates intact, which is what the review needs, but running the monthly review is still on your producers.
Questions producers ask
How far off the rate card is acceptable?
Set a threshold by category and how much risk it carries. The target isn't zero variance. It's that any real gap is intentional, traceable to a person, and gets reviewed.
Should a client's negotiated rate live on the main card?
Usually not as the market default. Keep it as a scoped rule tied to that client, or a documented exception. Otherwise one relationship quietly resets pricing for every later bid.
Can actual costs set the sell rate on their own?
They should inform the call, not make it by themselves. The sell rate also has to account for overhead, how busy your crew is, risk, where you sit in the market, and what the approach is worth.
More field guides
- Your rate card should be the one place rates live, not a copied tabHow a production company keeps crew, gear, post, and markup rates in one place so every estimate prices off the same numbers.
- 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.
- 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.
If this is costing you time or margin, try it on your next job.
Start free with a job you have already bid. If the estimate, the budget, and the wrap don't hold up against how you actually work, you've lost an afternoon.
Plans from $149 a month. If you cancel, your work stays readable.