IT for Townships: A Cleaner Process for Staff and Elected Official Transitions

Make transitions an office process

Staff changes affect more than a desk and a name on the door. A departing employee may own a spreadsheet, receive vendor invoices, administer a website, or hold a key to a meeting-room cabinet. An incoming official may need access to shared calendars and board material before their first meeting. IT for townships works better when these transitions follow a predictable office process.

Create one request that starts the work: the person’s role, start or departure date, approving manager, required applications, and assigned equipment. Identify a municipal contact who can answer questions about access. Ask departments to request accounts through that process rather than independently asking different vendors. This creates a record of what was requested and who authorized it.

Give access for the role and the task

An employee should receive the resources their job requires, with additional permissions approved when needed. Use a role checklist as a starting point rather than copying every permission from a predecessor. A long-serving employee may have accumulated access that no longer reflects the job. Review sensitive folders and administrator privileges separately from ordinary office accounts.

For a deputy clerk, the checklist might include the shared clerk mailbox, meeting documents, office printers, and the relevant application. For a board member, it may be a different set of documents and communication tools. Record which access is ongoing and which is temporary. Clear role definitions make future reviews easier and reduce the number of unexplained exceptions.

Prepare before the first day

Assign an individual account, prepare the device, and schedule a short orientation. Staff should know where shared work belongs, how to contact support, and how to report a suspicious message. Complete authentication enrollment with appropriate assistance rather than leaving the employee to improvise. Confirm access by walking through a real task such as opening a meeting packet or using the correct printer.

Include the practical details that slow down a new employee: dock connections, scan-to-email settings, phone sign-in, shared calendars, and application contacts. Give the person a concise reference they can use later. A well-prepared first day is also a chance to establish good habits before staff develop workarounds that are difficult to unwind.

Separate access removal from data preservation

Microsoft’s guidance for removing former employees treats blocking sign-in, preserving mailbox and OneDrive information, transferring access, and managing licenses as separate steps. The sequence matters. Agree on the departure timing and data needs before deleting accounts or removing services. In environments with synchronized identities, the technical procedure also depends on where those accounts are managed.

Municipal records and retention decisions belong with the responsible officials and advisers. Ask them what must be preserved and who should take over active work; have IT implement the approved plan. A useful handover names an owner for ongoing correspondence and shared documents. Do not assume that collecting a laptop also removes access to every cloud application or vendor portal.

• Confirm the approved access cutoff and responsible contact.
• Preserve required information before account or license changes.
• Reassign active work, mailbox handling, and document ownership.
• Collect equipment and review separate vendor and building access.

Close the loop and check the overlooked accounts

Use a completion record that covers email, business applications, phones, website access, remote connections, and physical credentials where applicable. Check municipal subscriptions and portals that may sit outside the main directory. The person handling access control can confirm badge changes while IT confirms account changes. Give the approving manager a clear result rather than an informal assurance that everything is handled.

Review your checklist after each transition. If staff discover a folder nobody can manage or a vendor sending mail to an abandoned account, update the process. Good IT support for municipalities turns those discoveries into a better next handover. The result is straightforward: incoming people can work, outgoing access is handled deliberately, and the office retains ownership of its information.