Municipal Software Renewals: A License Review Checklist

Start with one upcoming renewal

A software renewal lands in the clerk’s inbox. The invoice looks familiar, but the office has changed: one employee retired, another works part time, and a department added a separate document tool. Approving last year’s quantities takes minutes. Understanding what the municipality needs takes a conversation between finance, department staff, and IT.

Start with one subscription approaching renewal. Gather the current invoice, purchase agreement, product and plan names, purchasing account, and vendor contact. Name the staff member responsible for the service. This focused review complements your broader municipal IT budget by turning one recurring expense into a documented decision.

Separate the payment schedule from the commitment

Record the renewal date, commitment length, billing frequency, and current automatic renewal setting separately. A monthly payment does not necessarily mean a monthly commitment. Microsoft’s Cloud Solution Provider billing documentation distinguishes payment frequency from subscription term; your supplier should confirm the arrangement that applies to your municipality.

Ask when a proposed quantity or plan change can take effect and what action your purchasing channel requires. Microsoft’s license reduction rules vary by billing arrangement, so an available seat does not automatically mean an immediate refund. Set an internal review date that leaves time for a quote, department input, and your normal approval process. Confirm any supplier notice requirements from the actual agreement.

Reconcile purchased, assigned, and needed licenses

Ask the authorized administrator for the purchased quantity, current assignments, and available licenses for each plan. Microsoft 365’s Licenses page can combine quantities from multiple subscriptions for the same product. Match those totals back to the individual subscriptions being renewed, rather than assuming every seat shares one renewal date.

Next, compare assignments with the people and work that need them. In a hypothetical village, 20 purchased licenses and 16 assigned licenses leave four unassigned. That is a question to investigate: perhaps an approved hire needs one, or an upcoming staffing change explains the reserve. Ask department owners to confirm the need before changing the order.

An assigned license also does not prove that a service is being used effectively. Review the actual task, seasonal needs, and upcoming work. Keep a short explanation for any spare capacity the municipality chooses to retain.

Check the work behind overlapping tools

Two products may both edit PDFs or host meetings while supporting different workflows. Before consolidating, have the person doing the work demonstrate a representative task. Can the proposed replacement handle the required forms, signatures, file formats, and outside participants? Does the existing tool connect to another municipal application?

Ask IT to identify the features included in each exact plan and whether changing plans affects configured security or device management. A similar product name is not enough evidence. Record what was tested, who accepted the result, and any remaining dependency. If replacing the tool requires staff training or data migration, include that work in the decision.

Plan changes before touching accounts

Separate access changes from purchasing changes. In Microsoft 365, unassigning a user’s license and reducing the subscription’s purchased quantity are separate actions. Removing an assignment alone does not complete a billing reduction. Have the administrator and supplier confirm the sequence and effective date for an approved change.

Before removing or switching licenses, identify affected mail, files, applications, and any services relying on the account. Follow the municipality’s established records and account handling process, with the responsible staff involved. Schedule the change around the work it affects, then test the required tasks. Record the new quantity and check the supplier’s confirmation and subsequent invoice against the approved order.

Bring this checklist to your renewal review

Use one shared review sheet so finance, the department owner, and IT are working from the same information.

• Identify the exact subscription, purchasing channel, service owner, and invoice being reviewed.
• Confirm the renewal date, commitment term, payment frequency, and supplier change process.
• Reconcile purchased and assigned licenses with current staff needs and approved upcoming changes.
• Test replacement tools against real tasks and document any application or security dependencies.
• Approve the quantities, costs, implementation work, and effective date before making changes.
• Save the supplier confirmation, check the resulting invoice, and assign the next review date.

Give the board a decision it can understand

Summarize the current arrangement, proposed renewal, reason for the recommendation, and expected recurring cost. Identify one-time transition costs separately. Where a price or quantity is awaiting confirmation, label it clearly. Describe potential savings as an estimate until the supplier confirms the change and its timing.

For a Michigan township, village, or city, a useful next step is to choose the next renewal and book a review with finance, its department owner, and your IT provider. If you use managed IT in Michigan, ask your provider to help connect license counts to daily work. Bring the resulting decision sheet into the approval process, then retain it so next year’s review starts with the reasons behind the purchase.