Managed IT Services for Local Government: What to Require Before You Sign
In a local-government buy, the shortlist is decided at the procurement gate, before anyone compares response times. That is the first thing to understand about managed IT services for local government: the credentials that matter attach to the cloud products a provider runs and to the agreements it signs, not to the provider itself. Turn each one into a written question or a contract clause, and disqualify any provider that claims a credential that does not exist.
This guide is for the IT Director or CIO at a city, county or special district with 100 to 2,500 employees, preparing to put managed IT out for a multi-year contract. You already know what CJIS and FedRAMP are, so it skips the definitions. It covers how the buy happens, the frameworks that decide the shortlist, the five buyer signals, the red flags, and the questions to put in the meeting and the solicitation. The guidance is the same for IT support for municipalities, managed IT services for counties, and special districts. What changes is which frameworks apply.
How managed IT services for local government get bought
A private company can shortlist three providers over lunch. You publish a solicitation, score responses against stated criteria, and defend the award in public. Pass/fail requirements come first: insurance minimums, required contract terms, and any security program the solicitation names. A provider that misses one is out before anyone scores its price or its response times. So the work of choosing an MSP starts with writing the solicitation, not with the sales meeting.
Not every buy needs a full solicitation. Cooperative contract vehicles let an agency buy from a contract another public body has already competed. GSA's Cooperative Purchasing program lets eligible state and local governments buy eligible IT products and services through the GSA Multiple Award Schedule, GSA MAS (IT category). Sourcewell, NASPO ValuePoint, OMNIA Partners and TIPS run cooperative contracts as well. Whether you can use one depends on your state's procurement law and your own purchasing rules, so confirm with your purchasing office first. A cooperative contract settles how you buy. It does not settle whether the tools a provider brings meet your security requirements, so every question in this guide still applies.
Three more filters shape the field before scoring starts:
- Insurance and bonding. A solicitation may set minimums for general liability, professional liability and cyber liability coverage, and may require a performance bond. Ask for the certificates with the proposal, not after award.
- Set-asides and local preference. A small-business set-aside or a local-preference rule narrows the field before any scoring. Know which ones apply before you write the evaluation criteria.
- Public records. Under state public records laws, your contract and much of the winning proposal can become public records, and so can the ticket history and incident reports behind them. A provider has to accept that, and it has to be able to export the records you need to answer a request on your deadline.
Which frameworks decide the shortlist
Which frameworks apply depends on what the provider will touch, not on what its website says. Four come up in local-government buys:
- GovRAMP (formerly StateRAMP), when your state participates or your solicitation names it. It applies to the cloud products the provider runs.
- The CJIS Security Policy, when police, sheriff, court or dispatch systems are in scope. It applies to anyone who can reach Criminal Justice Information.
- FedRAMP, as a question about the provider's cloud tools.
- CMMC, only if your organization also holds Department of Defense contracts.
None of them certifies a managed service provider as a company. GovRAMP and FedRAMP authorize specific cloud products. CJIS compliance belongs to the agency. CMMC results belong to the contractor being assessed. That is why the useful questions are about products and agreements, and why a provider page that calls itself an MSP for government tells you nothing your solicitation can score. Our guide to MSP compliance with HIPAA, PCI and SOC 2 shows the same split between your obligations and the provider's work in other frameworks.
GovRAMP (formerly StateRAMP) is a procurement gate for cloud tools
If your solicitation names GovRAMP, treat it as a procurement gate, not a nice-to-have. GovRAMP authorizes cloud products, not managed service providers, so the question is never whether the MSP is GovRAMP anything. It is whether each cloud product the provider will run on your data holds the status your solicitation requires.
Start with the provider's own tool stack, because that is where your data and your network access live: the remote monitoring and management (RMM) platform, the PSA or ticketing system, backup, remote access, the endpoint protection console, and the documentation or password vault. Each one is a cloud product, and each one either holds your data or opens a path into your network.
Then check the status, not just the listing. GovRAMP's product list shows each listed offering with a security status: Core, Ready, Provisionally Authorized or Authorized. Listed is not Authorized. Match the status your solicitation requires, product by product.
Two more distinctions catch buyers out. First, FedRAMP is not GovRAMP. They are separate authorizations, and a cloud product can hold one without the other, so "we run on FedRAMP cloud" does not answer a solicitation that names GovRAMP. Second, Texas state agencies use a different program: TX-RAMP, run by the Texas Department of Information Resources under its Program Manual 4.0, effective February 12, 2026. TX-RAMP can accept a GovRAMP or FedRAMP authorization through a review, but not automatically. Different list, different process.
Participation varies too. GovRAMP keeps a list of participating government organizations, grouped by state. A participating state uses GovRAMP in its own cloud purchasing; that does not mean every solicitation in the state, or yours, requires it. Your solicitation decides. The sentence to put in it: "List every cloud product that will touch our data, including RMM, PSA and backup, with its current GovRAMP status." Then get each product's status in writing before you shortlist.
CJIS: when police, courts or dispatch are in scope
If your network carries Criminal Justice Information (CJI) for a police department, sheriff's office, court or 911 dispatch center, the CJIS Security Policy v6.1 (June 25, 2026) applies to that information and to anyone who can reach it. Since v6.0 the policy has been organized around NIST SP 800-53 control families, so a proposal that still cites the old 5.x area numbers is working from a retired version. There is no FBI "CJIS certification" for vendors. Your agency, through its CJIS Systems Agency (CSA), is responsible for compliance, and the CSA audits it.
What that means for the provider is concrete. An MSP whose technicians can access CJI must sign the CJIS Security Addendum, and its people go through the same fingerprint-based background checks as agency staff. Two control families come up first in the provider conversation: Personnel Security (PS), which covers that screening, and Identification and Authentication (IA), which covers multi-factor authentication (MFA) for privileged and non-privileged accounts. Ask whether every technician who could reach CJI has completed fingerprint-based screening, and how the provider enforces MFA on its own remote-support tools. A SOC 2 report does not satisfy CJIS, which is a separate policy with its own requirements. Bring your CSA into the conversation before award, because it audits you, not the MSP.
FedRAMP: a question about the provider's cloud tools
FedRAMP authorizations attach to a specific cloud service offering, not to a managed service provider. A federal agency grants an Authority to Operate (ATO) to use a particular cloud product, and the FedRAMP Marketplace is searchable by cloud service provider. If your solicitation or your own security policy points to FedRAMP, the check is the same as for GovRAMP: list the cloud tools the provider plans to use and look each one up. An MSP that calls itself "FedRAMP authorized" is using a credential that does not apply to a company.
CMMC: only if you also hold defense contracts
CMMC applies through Department of Defense contracts, not to a local government as such. This section is for the federal contractor IT manager, or the public entity that also handles Controlled Unclassified Information (CUI) under a DoD contract. When a solicitation includes CMMC, it names the level and assessment type. Phase 1 self-assessments apply today. In July 2026 the DoD suspended the move to required third-party (C3PAO) assessments pending a program review, and told contracting officers to remove or revise CMMC requirements (DoD CIO; DFARS class deviation 2026-O0025, checked November 2026).
There is no "CMMC compliant" status. A CMMC result is a level plus an assessment type: a self-assessment or a C3PAO certification. If your MSP will touch your CUI, or the tools that protect it, its services are part of what your assessment looks at. Ask how its responsibilities will be documented in your System Security Plan (SSP), and which of the 110 NIST SP 800-171 Rev. 2 requirements it operates for you and which stay with you. For cloud tools, DFARS 252.204-7012 requires that any external cloud service provider used to store, process or transmit covered defense information meet security requirements equivalent to the FedRAMP Moderate baseline. Ask which cloud services will hold your CUI and what evidence backs that.
The five buyer signals, applied to public-sector IT
Once a provider clears the gates, compare it on the same five signals you would use anywhere, adjusted for how government runs. Write each one into the solicitation as something the provider must show, not describe.
| Signal | What to require in writing |
|---|---|
| Response time | Priority tiers in the SLA that name your critical systems (dispatch interfaces, permitting, utility billing, payroll), a first response for a P1 outage within one hour, and the response on nights, weekends and during an emergency operations center activation. |
| Ticket tracking | A named owner on every ticket, timestamps on every change, and an audit trail you can export for an audit or a public-records request. |
| Proactive monitoring | What is monitored (endpoints, servers, network, identity, backup jobs), who gets alerted, and a documented incident response runbook that names who can isolate a system and how the provider works with your emergency management staff. |
| Past performance | At least two public-sector references of comparable size that you can call, with the scope of work for each. |
| Security evidence | MFA coverage, EDR deployment, backup restore test results, log retention, and the date of the last tabletop exercise, mapped to the framework that applies to you. |
Response time deserves a second look in local government, because your worst hours may fall outside business hours. A storm, an election night or a water main break does not wait for Monday. If the SLA defines response only during business hours, the provider is pricing a different job than the one you have. The IT support SLA guide covers how to get priority definitions into the contract instead of the proposal.
Past performance needs the same care. A provider that supports 40-person offices is not automatically ready for a 900-employee county with a records office, a police department and a public meeting schedule. Call the references, and ask them what happened the last time something broke on a weekend.
Red flags that disqualify a provider
Look for these in the proposal and the first meeting. Any one of them is enough to stop:
- A credential that does not exist. An MSP that calls itself CMMC compliant or CJIS certified is using a credential that does not exist. The same goes for an MSP that calls itself GovRAMP authorized or FedRAMP authorized: those authorizations belong to products.
- No public-sector past performance of comparable size. "We support government clients" without references you can call is a sentence, not past performance.
- Refusing the terms your framework requires. If CJI is in scope and the provider will not sign the CJIS Security Addendum or put its technicians through fingerprint-based screening, it cannot do the job.
- No records on request. A provider that cannot export ticket history, change records and incident reports when you need them leaves you unable to answer a public-records request or an audit.
- Cloud tools without the status your solicitation names. If the provider plans to run its RMM, PSA or backup on a product that does not hold the GovRAMP (or TX-RAMP) status you require, the proposal fails your own gate.
- Retired vocabulary. A proposal that cites CJIS 5.x area numbers, treats StateRAMP and GovRAMP as two programs, or offers "GSA Schedule 70" is working from out-of-date material. Ask what else is out of date.
The point under all of these: in a public-sector buy, the credential that matters sits on the cloud product and in the agreement your provider signs, never on the provider's homepage. Ask for the product list and the signed addendum, not the badge. For the contract terms that go wrong in any sector, see our guide to MSP contract red flags.
What to ask in the meeting
Seven questions, each one answerable in writing. Put the same questions in the solicitation so every proposal answers them the same way.
- "List every cloud product that will touch our data, including RMM, PSA and backup, with its current GovRAMP or TX-RAMP status, whichever our solicitation names."
- "Which of your technicians could reach CJI, and has each one completed fingerprint-based screening? Will you sign the CJIS Security Addendum?"
- "How do you enforce MFA on your own remote-support and administration tools?"
- "Show us your incident response runbook and walk us through your last tabletop exercise."
- "Give us two public-sector references of comparable size, with the scope of work for each."
- "If we receive a public-records request about your work, what can you export, in what format, and how fast?"
- "When the contract ends, who holds our documentation, admin credentials and backups, and how do they come back to us?"
The last question matters more than it looks. For example, at the end of a contract, documentation, passwords and backup ownership may never have been clearly assigned, and the next provider can spend its first months finding them. Ask how to leave before you ask how to sign.
Compare providers, then put these questions in your solicitation
Compare managed IT providers in your state, then put these questions in your solicitation and score the answers, not the adjectives. If you are earlier in the process, the MSP buyer's guide walks through the full evaluation, from shortlist to signed contract.
Frequently asked questions
Does an MSP need to be CJIS certified?
No, because there is no FBI CJIS certification for vendors. The agency, through its CJIS Systems Agency, is responsible for compliance and audits it. What an MSP with access to Criminal Justice Information must do is sign the CJIS Security Addendum, put every technician who could reach that information through fingerprint-based background checks, and follow the policy's controls, including multi-factor authentication. A provider that calls itself CJIS certified is using a credential that does not exist.
Is GovRAMP the same as FedRAMP?
No. They are separate authorizations for cloud products, and a product can hold one without the other. FedRAMP covers cloud services used by federal agencies. GovRAMP, which was called StateRAMP until February 2025, serves state, local, tribal and education buyers. Neither one applies to a managed service provider as a company, so ask for the status of each cloud product the provider will use.
Can a city buy managed IT without a full solicitation?
Possibly, through a cooperative contract vehicle: a contract another public body has already competed. Examples include GSA's Cooperative Purchasing program, which opens eligible parts of GSA MAS (IT category) to state and local buyers, Sourcewell, NASPO ValuePoint, OMNIA Partners and TIPS. Whether you can use one depends on your state's procurement law and your local purchasing rules, so check with your purchasing office first. The vehicle settles how you buy, not whether the provider's cloud tools meet your security requirements.
What is TX-RAMP?
TX-RAMP, the Texas Risk and Authorization Management Program, is the program Texas state agencies use for the cloud computing services they buy. The Texas Department of Information Resources runs it, and Program Manual 4.0 took effect on February 12, 2026. TX-RAMP can accept a GovRAMP or FedRAMP authorization through a review, but not automatically, so a GovRAMP status alone does not settle a Texas state agency purchase.
Can an MSP be FedRAMP authorized?
Not as a company. FedRAMP authorizations attach to a specific cloud service offering, and the FedRAMP Marketplace lists them by cloud service provider. What you can check is whether each cloud product the MSP plans to use holds an authorization, one product at a time. When a provider describes itself as FedRAMP authorized, ask which product it means and look that product up.
What should a local government MSP contract include?
At minimum: an SLA that names your critical systems, with response times for nights, weekends and emergencies; the list of cloud products the provider will use, with each one's GovRAMP or other required status; the CJIS Security Addendum if Criminal Justice Information is in scope; your insurance minimums; the provider's duty to produce records for audits and public-records requests; and exit terms that return documentation, admin credentials and backups to you.
Related Articles
Free Buyer's Guide
The complete guide to finding and hiring the right MSP for your business.
Download Free Guide