Xcelerate
Menu
Get in touch
All articles on council finance and operations

Council finance and operations

A council contract register that catches renewal decisions

Build notice periods, exit choices and ownership into a council contract register. Test renewal reminders with a variation, a departing manager and an export.

Staff check a contract file against renewal dates on a tablet.
AI-generated editorial image.

A calendar reminder on the last day of a software contract can arrive months after the buyer needed to act. A useful council contract register works back from the notice clause and the time needed for a decision. Give suppliers a real decision to model, such as whether to extend a library system agreement, transfer to another provider or run a procurement.

Which dates drive a renewal?

Start with the signed agreement and its variations. Capture the end of the current term, any extension option, the notice window, the permitted method of notice and who checks those details. Clauses can describe calendar months, working days or an exact date. Ask the commercial owner to confirm the calculated deadline against the wording and record that check.

Count back again for internal decisions. If a replacement system requires a data export, procurement work and staff training, the library manager needs time to investigate before the notice window closes. A useful register shows both the contractual deadline and the earlier internal decision date. The earlier date can change as the replacement plan becomes clearer.

How does an alert turn into a decision?

Assign the agreement to an accountable role with a current named owner and cover. Give the owner a task that can be acknowledged, transferred or escalated. Sending an email is weak evidence that someone has actually started the review. Look for the named decision maker, the due date for their recommendation and the date the governing group will consider it.

NZ Government Procurement provides a register template and encourages contract management plans proportionate to value, complexity, duration and risk. A council can draw on that guidance and its own policy to decide which agreements need a short review and which merit a detailed exit plan.

What should go in the review pack?

For the library example, gather recent service issues, costs of exercising the option, expected export format and outstanding commitments. Link back to the evidence and record its date. Keep the commercial decision separate from the mechanical reminder. A manager opening the pack should be able to tell which questions still need supplier input.

Retain the signed notice and delivery evidence once a decision is made. If the parties sign a variation, record its effect on renewal dates alongside the old terms. The record should still explain what staff believed the deadline to be before the variation took effect.

Rehearse an awkward handover

In the supplier demonstration assign the library agreement to a manager, change the term through a variation and move that manager to another role. Ask their successor to find the revised decision date, the reason for the change and all open tasks. Export those records and their document references. The procurement team should be able to take ownership of the register even if it later changes software providers.

Set alerts on the review tasks themselves. A closed reminder should never hide an unresolved question about the right to extend the agreement.

Sources and further reading