Workflow failure · Operator field guide

Paid invoices are too late to manage a live production

Accounting actuals explain what happened. Operators also need committed cost and estimate-at-completion while there is still time to protect the job.

Trace 01 · Signal → cause → consequence

Diagnose the operating failure before buying a tool

Visible signal

The approved budget looks healthy until vendor invoices arrive, crew overtime is submitted, or the producer reconciles cards after wrap.

Underlying cause

The workflow tracks budget and paid actuals but omits commitments, known changes, and forecast-at-completion between them.

Business consequence

Overspend becomes historical information. The team loses the chance to rebalance, obtain a change order, adjust the plan, or escalate while options still exist.

Control 02 · Operating principles

Three controls that survive the software

Use four money states

Keep sold baseline, current budget, committed cost, and paid actual distinct. Add estimate-at-completion to express the operator's best current view.

Record knowledge before paperwork

A producer often knows a cost changed days before an invoice exists. Capture the expected impact with source and confidence, then reconcile it when formal documentation arrives.

Variance needs an action

A red number without an owner is decoration. Material variance should name cause, decision, responsible operator, and when the forecast will be updated.

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.

01

Establish the approved baseline

Start from the exact approved scenario and document internal reallocations separately. If the baseline is uncertain, every later variance discussion will be political.

  • Baseline reconciles to client approval
  • Contingency treatment is defined
  • Internal detail rolls up to sold categories
02

Capture commitments at decision time

When a quote is accepted, crew is confirmed, travel is booked, or a rental order is placed, record the commitment. Do not wait for the payment event.

  • Vendor or payee is identifiable
  • Amount and confidence are recorded
  • Cancellation or change terms are noted
03

Update forecast on a fixed cadence

Review high-risk departments daily during active production and the whole job at least weekly. A forecast is useful because it changes before actuals do.

  • Material changes carry notes
  • Unconfirmed costs have confidence
  • Owner and next update are visible
04

Separate client change from internal overage

New scope may justify a change order; an internal miss may require a production adjustment. Classify the cause before deciding whether to ask the client for money.

  • Original assumption is available
  • Change source is documented
  • Client communication is approved

Instrument 04 · Evidence

Measure whether the control is earning its place

  1. Committed cost captured before invoice arrival
  2. Forecast-at-completion accuracy by job phase
  3. Material variances with owner and action
  4. Days between internal awareness of change and recorded forecast

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

  • Preserves the approved estimate scenario and creates an initial budget baseline
  • Uses deterministic integer-cent money records
  • Provides tenant-scoped project and budget models for the next control layer

Design-partner scope

  • Map the shop's commitment and forecast events
  • Define the smallest live-cost view operators will maintain
  • Validate which accounting handoffs are required before expanding rollout

Honest boundary: The current standalone product does not yet prove a complete live actuals, purchase-order, or accounting-sync workflow. This page is an operating playbook and a design-partner problem statement, not a claim that those modules are shipped.

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

Are committed costs the same as actuals?

No. A commitment is an expected obligation based on a booking, quote, or decision. Actuals are posted transactions. Both are needed to understand the live job.

How often should a forecast update?

Update high-risk lines when material facts change, daily during an active shoot when needed, and run a whole-job review at a consistent cadence.

What if the amount is not final?

Record the best estimate with source and confidence. An explicit provisional number is more useful than a false zero, provided the uncertainty stays visible.

Index 07 · Internal route

Continue the operating system

Paid 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