A career shaped by the winter operating calendar

Mandate

Make pre-season obligations and investment alternatives clear enough for timely funding decisions.

Outcomes

• Excluded unresolved collection assumptions from a critical supplier-payment plan
• Supported a staged extension alongside priority renewal work
• Kept the controls rollout conditional on stronger technical evidence

Decisions in context

I lead the financial recommendation before the company commits its funding to a heating season. That requires an account of supplier payments, customer receipts and network works that operating colleagues can recognise. I have introduced a pre-season review focused on unresolved conditions rather than another general performance presentation. The general manager retains executive authority, and the board approves matters reserved to it. I present the alternatives and explain the financial consequences, including the cost of choosing greater certainty. My current remit includes financial reporting and treasury, but it does not extend to engineering acceptance or service standards. The three recent cases show different boundaries: borrowing against a realistic receipt date, sequencing expansion around existing obligations, and refusing to turn a promising trial into a universal saving. Each decision left work to be done after approval.

Reason for the move

Continuing in the executive appointment; exploring a bounded external oversight contribution.

Mandate

Connect operating explanations with financial results and preserve the basis of significant estimates.

Outcomes

• Separated price, weather and network factors in management cost reviews
• Introduced a consistent record of unresolved customer-balance assumptions
• Reconciled programme forecasts with approved work and contractor claims

Decisions in context

As controller, I was responsible for the financial explanation that accompanied the monthly result. A favourable movement was not complete until the people closest to the operation could explain its likely causes and limits. I worked with technical management on heat-cost comparisons and with customer operations on the state of unresolved balances. The challenge was to retain enough detail for a decision without sending the board every account record. I also supervised the reporting team through changes in the network's scale and kept forecast revisions connected to approved work. External advisers supported specialist reporting judgements. I learnt to distinguish an estimate that had become better informed from an error that should have been prevented. Both required correction, but the management response should reflect why the number changed rather than treat every revision as evidence of the same control failure.

Reason for the move

Promoted to CFO as the board sought earlier visibility of seasonal commitments.

Mandate

Prepare reliable payment plans across the gap between summer works and winter collections.

Outcomes

• Mapped major supplier and contractor payments by required date
• Separated confirmed receipts from unresolved customer-account assumptions
• Documented facility conditions before including funding in forecasts

Decisions in context

Treasury made the timing of a financial promise concrete. I could not pay a contractor with a full-year revenue forecast, and a facility amount was not useful until its conditions and draw process were understood. I prepared cash forecasts under the controller's supervision and worked with operational teams on the dates behind their requests. The seasonal pattern meant that apparently small timing changes could accumulate around the same period. I learnt to ask for evidence without assuming that a colleague's estimate was careless. Sometimes the missing fact belonged to a customer or a contractor outside our immediate control. My response was to show the uncertainty and the alternative funding action, not to conceal it in a more precise-looking date. The role prepared me to discuss liquidity as an operating responsibility shared across functions.

Reason for the move

Moved into the controller role to take responsibility for the wider financial account.

Mandate

Explain contractor claims and job-cost variations against authorised work scopes.

Outcomes

• Distinguished urgent repairs from planned asset renewal
• Recorded approved scope changes alongside contractor claims
• Prepared cost comparisons for the next summer works programme

Decisions in context

I followed the financial record of work performed during the summer window. Each job had a purpose, an authorised scope and a sequence that technical managers understood. My task was to compare the cost record with that account and investigate differences with the responsible colleagues. I learnt that an unchanged budget was not necessarily evidence of a well-managed job if essential work had merely been postponed. Equally, a higher contractor claim needed support rather than a sympathetic explanation alone. I documented changes and prepared the review for managers who held approval authority. The work gave me a practical understanding of why renewal and extension expenditure could compete for the same time and resources. It also taught me to distinguish the value of maintaining an existing service from the visibility of adding a new connection.

Reason for the move

Appointed treasury manager after developing an understanding of the network's expenditure cycle.

Mandate

Maintain supporting records that explained the purpose and approval of operating expenditure.

Outcomes

• Matched contractor invoices to authorised job records
• Reconciled assigned accounts with customer-service colleagues
• Prepared repair-cost schedules for the chief accountant

Decisions in context

My first responsibilities required care with ordinary records. I checked whether an invoice referred to the authorised job, whether the amount agreed with supporting documents and who could explain a difference. The chief accountant reviewed my schedules before they entered the wider financial report. I was initially more comfortable with the ledger than with the operating language, so I spent time learning what different repairs and connections involved. That did not make me an engineer. It made me a better accountant because I could recognise when two similar descriptions referred to different activities. I also worked on selected customer reconciliations and saw how an incomplete address or account history could complicate an otherwise straightforward balance. These experiences gave me a lasting preference for resolving the underlying record before choosing a confident financial explanation.

Reason for the move

Moved into network cost accounting to work more closely with the annual works programme.