Use case · Operator field guide
The approved estimate should become the first production budget without translation
Sales and production use the same dollars for different decisions. The handoff works when the approved promise remains visible while the team adds commitments, forecasts, and actuals around it.
Trace 01 · Signal → cause → consequence
Diagnose the operating failure before buying a tool
Visible signal
After award, someone creates a new budget spreadsheet, rearranges categories, changes allowances, and asks the seller what the client actually approved.
Underlying cause
The estimate and budget are separate artifacts without a controlled transformation or a reconciliation check.
Business consequence
The team can start a job already off-plan, then spend the rest of production debating whether a variance is real or merely a handoff difference.
Control 02 · Operating principles
Three controls that survive the software
Preserve the sold baseline
Never erase the approved scenario. The operating budget can become more detailed, but every production line should roll back to the promise that funded it.
Split detail without changing truth
A sold camera package may become body, lenses, support, media, and labor internally. The split is valid only if its initial total reconciles to the approved line.
Treat change as a transaction
New client requests, producer concessions, and internal reallocations are different events. Record type, owner, amount, and approval instead of simply editing a cell.
Runbook 03 · Smallest useful workflow
Run this on one real job
Do not begin with a company-wide migration. Prove the control on representative work, record the exceptions, and expand only when the operator can trust the new state.
Freeze the award package
Store the selected scenario, amount, assumptions, exclusions, client decision, and source estimate version before production planning changes anything.
- Approval state is valid
- Currency and tax treatment are consistent
- The selected option is unambiguous
Seed the budget
Create the project and initial budget from normalized estimate lines. Preserve stable identifiers so later reporting can compare sold, budgeted, committed, and actual amounts.
- Initial budget equals approved total
- Line categories map consistently
- Percentage-based lines retain their basis
Run a producer handoff
The seller and production owner review the ten highest-risk lines, every allowance, every client dependency, and the current unknowns. This is a decision meeting, not a file transfer.
- Risk owner is named for each material unknown
- Quote deadlines and release dates are scheduled
- Potential change orders are identified early
Start variance tracking from day zero
Record commitments and forecast-at-completion as soon as quotes are accepted. Waiting for invoices means the budget is a historical report, not a control system.
- Committed costs are distinct from paid actuals
- Forecast changes carry notes
- Material variance has an owner and next action
Instrument 04 · Evidence
Measure whether the control is earning its place
- Approved jobs whose initial budget exactly reconciles to the winning scenario
- Time from award to accountable production-owner handoff
- Unmapped or manually re-keyed lines per job
- Value of changes with no recorded source or approval
Boundary 05 · Product truth
Where Production Engine fits today
The current build is strongest from company rate card through estimate, option approval, and initial budget creation. The design-partner program exists to test the next control on live work without pretending the whole production stack is finished.
Present in the current repo
- Normalizes generated line items into integer-cent records
- Stores estimate scenarios and immutable snapshots
- Creates an initial project and budget from a client-approved scenario
Design-partner scope
- Map your estimate categories into the initial budget shape
- Test the award handoff on a selected live job
- Prioritize the commitment, forecast, and actual controls your operators need next
Honest boundary: The current repo proves the initial approval-to-budget transaction. It does not yet prove a complete live cost, purchase-order, or accounting workflow, so those needs must be validated during the design partnership.
Paid design-partner program
Put one live workflow under control in 90 days.
Implementation, rate-card and workflow mapping, access for five operators, and direct product-team collaboration.
$2,500 implementation + $499/month for five operators · 90-day commitment
FAQ 06 · Buying questions
Questions to resolve before implementation
Should the production budget look exactly like the client estimate?
It should reconcile exactly at the baseline, but it may need more internal detail. Preserve the parent relationship so internal splits still roll up to the sold line.
When should actuals start?
Start with commitments and forecast changes as soon as the job is awarded. Paid invoices arrive too late to protect the job on their own.
Who owns the handoff?
The seller owns the accuracy of the promise; the production owner accepts operational responsibility. Both should sign off on the baseline and named risks.
Index 07 · Internal route
Continue the operating system
Paid invoices are too late to manage a live production
A practical control model for production companies that discover budget overruns after wrap because commitments and forecasts were never visible.
Read the field guideGive clients a decision they can approve, not three PDFs they have to decode
A practical workflow for presenting production estimate options, protecting scope, and recording a clean client decision.
Read the field guideThe most expensive line in a production estimate is often the assumption nobody wrote down
A practical assumptions checklist for commercial video and photo estimates, including scope, schedule, labor, locations, post, usage, and client dependencies.
Read the field guidePaid design-partner program
If this failure costs real producer time or margin, test it on a live job.
Implementation, rate-card and workflow mapping, access for five operators, and direct product-team collaboration.
$2,500 implementation + $499/month for five operators · 90-day commitment