Released time is not a rates saving

The Local Government (Rates Capping) Amendment Bill passed its first reading on 1 September 2026. As introduced, it would require councils to consider a target range of 2 to 4 percent for annual rates increases when preparing long term plans from 1 July 2027. A maximum cap of 4 percent would take full effect from 1 July 2029, with exemptions for exceptional circumstances and oversight by an independent regulator. The select committee reports back in February 2027 and the settings may change. Councils preparing the 2027 to 2037 long term plan are already modelling what the proposed settings could mean for them.

Hutt City Council has published the scale it is working with. Its draft annual plan material for 2026/27 says a target operating model review identified a need to save about $24 million a year by 2034 to meet the proposed 4 percent cap, and that savings of that size could not be achieved without fundamental changes to services and a reduction in the assets the council owns. Process improvement alone is unlikely to close a gap of that size. This article is about the part of the response that process and workflow improvement can supply, and about a habit that matters more under a cap than it did before: not using a process benefit to close a rates gap until finance has shown that it reduces the rates requirement.

Time and money are different

Removing a step from a process releases staff time. Released time is a capacity benefit until the council can show how it changes service, throughput, risk or future cost. It becomes a rates saving only when it removes or avoids a cost that is funded from rates and sits in the council's agreed financial baseline, and the council-wide model shows the rates requirement falling as a result. Four questions are a useful first screen.

The screen is not the validation. A benefit that passes it still goes to finance, which tests it in the council-wide financial model against the stated counterfactual, including revenue effects, implementation cost, any redeployment of the released time and any double counting with other initiatives. Only then does it carry a named budget owner, the cost line it changes, the year and a delivery risk, and only then does it support a rates scenario. Benefits that do not pass are recorded separately as service or capacity benefits, reported, and kept out of the rates calculation.

What a published case does and does not show

LSI Consulting's published work with a rapidly growing urban council's consent processing reports an 87 percent increase in applications processed on time, a 50 percent reduction in processing sent to outside contractors, and 10 percent more technical staff time available for specialist work. The published case does not include a dollar value and does not establish a rates saving. The on time improvement and the specialist time are capacity benefits. The reduction in outsourced processing has the clearest direct link to expenditure, and a council counting it toward a cap would trace it to the supplier budget line, confirm that spend fell against the baseline, and check that nothing else rose, before claiming it. A good operational result and a validated saving are different things, and the case shows the gap between them.

Working alongside the percentage

Councils modelling percentage scenarios for the long term plan will keep doing so, and process work sits alongside that modelling. A percentage target used as a planning constraint is a reasonable tool. Uniform application of it can produce blunt decisions unless each service identifies the work, the expenditure, the risk and the service consequence behind its share of the reduction, because rework, duplicated checks and repeat contact from residents have no budget lines of their own to be cut from. Validated process savings can be included in the financial scenario. Unvalidated opportunities are shown separately, with their delivery costs, timing and a confidence range, and are not used to close the gap.

Some changes will sit within management delegations. Changes outside those delegations, or changes that are significant or alter adopted service levels or policy, need elected member approval, and the work should say which is which so that the long term plan does not carry a management change that turns out to need a governance decision.

Where to look, and what is enough to look with

Start with rates funded operating costs that are controllable within the planning period. Test each candidate against contract constraints, service impacts, statutory obligations, implementation cost and who has to approve the change. That filter is more useful than volume or complaint data on their own, since a high volume service may already be cheap to run, and a complaint may point at a legal timeframe the council cannot change.

Within a shortlisted service, four places are worth examining first: handovers, where a request queues between people and the same information is re-entered; rework, where applications are returned for information that could reasonably have been asked for earlier; approvals that may have outlived the risk they were created for; and demand the process creates for itself, such as calls asking where a request is up to. Some waiting cannot be avoided. Statutory clocks, applicant delays, hearings and specialist input can add necessary time to a process, and measurement should separate that from avoidable queuing.

Samples and ranges can show whether detailed design is justified. Councils should not change a long term plan budget on that basis alone. Any saving entered into the plan needs a finance approved baseline and implementation assumptions, and until then it should be recorded as an opportunity.

When a process changes, delegations and skills often need to change with it, and the cost of that training belongs in the net figure. If decisions are meant to move closer to the front of a process and the people there do not have the authority or skills to make them, escalation continues and the released time is smaller than the design assumed.

What to do this quarter

Agree the four question screen and the finance validation step with your finance team, and apply them to every process benefit already being proposed for the long term plan. Enter only the validated ones, net of implementation cost, with an owner, a cost line, a year and a delivery risk. Show the rest separately, as opportunities with their delivery costs, timing and a confidence range, so that elected members can see what is validated and what is still a possibility.