Orlaith Fennelly has spent eleven years in retail finance. When her company expanded from three stores to fourteen, the budget monitoring process that worked at small scale quietly fell apart. We spoke with her about what broke, what she changed, and what she would do differently from day one.
The problem that hid in plain sight
What was the first sign something was wrong?
Month-end reports looked fine individually. But when I tried to consolidate them, the category definitions were inconsistent across stores. One location coded staff overtime under operations, another under HR. We were comparing numbers that meant different things. The variance reports were technically accurate and practically useless.
The monitoring gap
How long did it take to identify the root cause?
About six weeks. We brought in an external analyst who mapped every cost category across all fourteen locations. The finding was straightforward: we had no shared chart of accounts enforced at the point of entry. Managers were coding expenses based on habit, not policy.
What the fix actually looked like
What changed operationally?
We standardised the chart of accounts in our ERP system and locked category selection at input. We also introduced weekly budget-versus-actual snapshots rather than monthly reviews. Catching a drift after four weeks is manageable. Catching it after one week means you can still act within the same period.
The discipline of weekly review sounds heavy, but it takes under thirty minutes when the data is clean. That was the real lesson: monitoring frequency only works if the underlying data is consistent.