Choosing Managed IT in Michigan: A Municipality’s Practical Checklist

Start with the work your community depends on

A township does not buy IT support because it wants more technology. It needs staff to take payments, prepare board packets, answer residents, issue permits, and finish the day without a computer problem becoming everyone’s problem. Choosing managed IT in Michigan starts by describing that work clearly. The right conversation connects technical tasks to the services your municipality needs to keep available.

Before contacting providers, gather a short list of your important applications, office locations, staff roles, and recurring frustrations. Include the workstation at the public counter and the laptop used for meetings. Ask department leaders which interruptions cause the most trouble. This gives each prospective provider the same starting point and makes proposals easier to compare.

Make day-to-day support specific

Ask how a clerk reports an urgent problem, what happens when the normal contact is unavailable, and when an issue moves from remote support to an onsite visit. A local address is helpful, but your practical question is whether the support arrangement fits your buildings and working hours. An evening board meeting may need a different plan from an ordinary password reset.

Get the distinction between response and resolution in writing. A response means someone acknowledges and begins handling the request; it does not necessarily mean the underlying fault is fixed. Ask for the escalation process, the information staff should provide, and how the municipality receives updates. Clear expectations make it easier to judge service fairly.

Find out who owns each responsibility

A municipality may have separate vendors for accounting software, internet service, phones, and its website. When an application cannot connect, those boundaries matter. Ask your IT provider to describe how it coordinates with other vendors and who remains responsible for communicating with your staff. Otherwise, a small fault can become a series of calls in which everyone asks you to contact someone else.

Request a responsibility list covering account administration, updates, backups, security alerts, hardware purchasing, and project work. NIST’s Cybersecurity Framework offers a useful way to discuss responsibilities across governance, protection, detection, response, and recovery. You do not need to turn the procurement process into a technical exam; you need to know who does the work and who makes decisions.

Compare the scope behind the monthly number

Two proposals can have similar totals and very different boundaries. One might include routine onsite support while another treats each visit as a separate charge. Another may include backup software without a defined restoration test. Compare the work included, the exclusions, and the assumptions about staff and devices before comparing price alone.

Ask how fees change when you add an employee, open a building, or replace a server. Identify licensing, hardware, project labor, and any transition costs separately. A board should be able to understand what the recurring payment covers and which decisions will require a future appropriation. A readable scope makes that explanation much easier.

• Which users, devices, buildings, and applications are included?
• Who verifies backups and documents recovery tests?
• Which onsite visits and projects are charged separately?
• How are service concerns escalated and reviewed?

Ask for a first 90 days you can understand

The transition should begin with discovery and controlled access, followed by an agreed list of priorities. Ask how the provider will collect existing documentation, coordinate with the outgoing vendor, and confirm ownership of domains and cloud accounts. Schedule changes around your office calendar rather than assuming every system can be changed immediately.

A useful first review should explain what was found, what has been corrected, and what still needs a decision. Ask for plain-language reporting on recurring support issues and significant risks. Black Rock Technologies serves more than 50 Michigan municipalities; our starting point is the same practical question your team should ask any provider: what will make the staff’s everyday work more reliable?