Ask most operations leads what a specific recurring process actually costs, and you'll get a shrug or an estimate from a spreadsheet nobody's updated in months. The work happens, invoices come in from different places, and by the time anyone adds it up, the process that ran over budget is long finished. There's no moment where anyone could have caught it.
The fix isn't a better spreadsheet. It's attaching cost to the process itself, at the stage level, before the process ever runs.
Budget the stage, not the project
A process is made of stages: inspection, approval, procurement, repair, whatever the real steps are. Each stage consumes something, whether that's a technician's hours, a piece of equipment, materials, or a flat fee for an outside vendor. If you attach a resource, a quantity, and a rate to each stage at design time, the process's total budget is just the sum, calculated automatically rather than guessed.
This matters because it turns budget into something you set once, when you design the process, not something you reconstruct after the fact from receipts.
Freeze the number the moment work starts
Rates change. A technician's hourly cost goes up, a material's price shifts, a vendor renegotiates. If your budget math re-reads live rates every time someone looks at a report, last year's completed runs quietly change value depending on when you check them, which makes historical reporting meaningless.
The right approach is to snapshot the budget the moment a process run starts: the resources, quantities, and rates in force right then, locked in for that run's entire lifetime. A rate change next month affects next month's runs. It never rewrites history.
Let actuals roll up automatically
As the process actually runs, whoever does the work logs what they actually used: hours, materials, trips, whatever the stage calls for. That actual consumption, multiplied against the frozen rate, becomes the actual cost. Compare it to the budget, and variance is just subtraction; no manual reconciliation, no waiting for the accounting close.
The payoff is that an overrun becomes visible while the process is still running, not three weeks later when someone happens to review it. That's the entire difference between managing cost and reporting on it after the fact.