What's Included in a Managed Network Services Contract?
What a managed network services contract should include, common exclusions, SLA terms and red flags, plus a 14-point checklist to review before you sign.
It's renewal time, and your managed network provider just sent over a 14-page contract. The cover letter says "comprehensive network management," the price went up a little, and your owner wants to know if you're getting your money's worth. You skim it, see words like "proactive" and "best effort," and realize you can't actually say what's in a managed network services contract and what isn't.
That's a common spot to be in. Network contracts are written by the people selling them, and the important parts are usually in the scope table and the exclusions, not the marketing language up front.
I'm a network engineer, and I've been on both sides of these agreements for about 15 years. This guide breaks down what a solid contract should include, what's usually left out, and the questions I'd ask before signing one, whether it's with us or anyone else.
In this guide
- What managed network services actually cover
- What a managed network services contract should include
- SLAs: response times, uptime and what "24/7" really means
- Hardware, licensing and who owns what
- What's usually not included
- Red flags to watch for before you sign
- A contract review checklist you can use this week
What managed network services actually cover
Managed network services means an outside team takes ongoing responsibility for your network: the firewall, switches, wireless, internet circuits and remote access. They watch it, maintain it, fix it when it breaks and keep records of how it's built.
That's different from break-fix, where you call someone after something fails and pay by the hour. It's also different from full managed IT, which usually adds desktop support, user accounts, Microsoft 365 and servers. Some providers bundle all of it. Others split network management and desktop support so you only pay for what you need.
If you're still deciding whether outsourcing makes sense at all, I covered the math in MSP vs. hiring a full-time IT person. This post assumes you're already looking at a contract.
What a managed network services contract should include
A good contract names each service, the devices it covers and how often the work happens. If a line item doesn't say how often or how fast, it's hard to hold anyone to it.
1. Monitoring and alerting
The provider should monitor every covered device for up/down status, and ideally for bandwidth, CPU, interface errors and WAN latency. The contract should say which hours are monitored and what happens when an alert fires.
Ask: "If our main internet circuit drops at 2 a.m. on a Saturday, who sees it, and what do they do?"
2. Firmware and patch management
Firewalls, switches and access points need firmware updates, especially for security fixes. The contract should state how often updates are reviewed, who approves them and when they're applied.
For manufacturers, this matters even more. You don't want a switch rebooting mid-shift, so look for language about scheduled maintenance windows you agree to in advance.
3. Configuration backups
Every covered device should have its configuration backed up automatically, stored off the device and kept for a set period. If a firewall dies, a current config backup is the difference between a few hours of downtime and a few days of rebuilding.
Ask how often backups run and whether they've ever tested a restore.
4. Change management
Every rule change, VLAN addition or new VPN user should be logged: who asked, who made it, when and why. This protects you during audits and makes troubleshooting much faster.
The contract should say whether small changes (often called moves, adds and changes) are included, and if so, how many per month.
5. Security services
Many contracts now include security functions on the network edge. Typical examples:
- Firewall rule reviews on a set schedule (quarterly is common)
- Intrusion prevention, web filtering and threat subscriptions kept active
- VPN and remote access management, including MFA
- Log retention and review of firewall events
Be clear on whether the provider is just keeping these features turned on or actually reviewing what they report. Those are very different services.
6. Vendor and ISP management
When the internet goes down, someone has to call the ISP, sit on hold and push the ticket. A good contract says the provider will handle carrier tickets on your behalf, which usually requires a letter of agency you sign once.
7. Documentation
You should get, and keep, current network diagrams, an IP address plan, a device inventory with serial numbers and support dates, and a list of admin accounts. This is your property, not theirs.
8. Reporting and reviews
Look for a monthly or quarterly report covering uptime, tickets, changes made and devices nearing end of support. A short quarterly review meeting is a good sign the provider plans to stay accountable.
SLAs: response times, uptime and what "24/7" really means
The service level agreement is the part of a managed network services contract that tells you how fast things happen. It's also where vague language does the most damage.
Response time vs. resolution time
Most SLAs promise a response time, meaning how fast someone acknowledges the ticket and starts work. Very few promise a resolution time, because fixes depend on hardware, carriers and parts.
That's fair, but you should know which one you're getting. "15-minute response" can mean an automated email confirming your ticket was received.
Priority levels
A useful SLA defines priority levels with examples. Something like:
- Critical: the whole site is down or production is stopped
- High: a major system or many users affected
- Medium: one user or a workaround exists
- Low: requests and scheduled changes
Each level should have a response target and say whether it applies during business hours only or around the clock.
What "24/7" covers
"24/7 monitoring" and "24/7 support" are not the same thing. Plenty of providers monitor around the clock but only act on alerts during business hours, unless you pay for after-hours coverage.
If you run second or third shift, get the after-hours terms in writing, including any extra hourly rates.
Uptime guarantees and credits
Some contracts promise a network uptime percentage with service credits if they miss it. Read how uptime is measured and what's excluded. ISP outages, power failures and scheduled maintenance are often carved out, which can make the guarantee mean less than it sounds.
Hardware, licensing and who owns what
This is where a lot of disputes start, usually when a business tries to leave.
Who owns the hardware?
There are two common models:
- You buy the equipment. You own it outright, and the provider manages it.
- Hardware as a service. The provider supplies the equipment as part of the monthly fee and keeps ownership.
The second model can lower upfront costs. But if you leave, you may need to return or buy out the equipment, so find out what that costs before you sign.
Who holds the licenses?
Firewall security subscriptions, cloud management licenses and support contracts (like Cisco SmartNet) should ideally be registered to your company, with the provider listed as a partner. If they're registered under the provider's account, moving them later can be slow.
Who has the admin passwords?
You should always have break-glass admin access to your own network devices, stored somewhere you control. A provider who refuses to share credentials with the business that owns the equipment is a provider I'd be cautious about.
What's usually not included
Every managed network services contract has exclusions. That's normal. The problem is finding out about them on the invoice.
Common exclusions include:
- Projects: new office build-outs, firewall replacements, Wi-Fi redesigns and site moves are usually quoted separately
- Hardware costs: replacement switches, access points and licenses are typically billed on top
- Cabling: running new cable or fixing physical drops is often subcontracted
- On-site visits: some contracts include remote support only, with on-site time billed hourly or with a trip charge
- Uncovered devices: anything not listed on the device schedule, including equipment you add later
- Shop-floor and OT equipment: PLCs, HMIs and machine networks are often excluded or need special handling
That last one deserves attention if you're a manufacturer. If your machine networks touch the office network at all, decide who is responsible for that boundary. I wrote more about that in how to secure shop-floor (OT) networks without stopping production.
Red flags to watch for before you sign
Most providers are trying to do good work. Still, these terms are worth slowing down for:
- Auto-renewal with a long notice window. A three-year term that auto-renews unless you cancel 90 days before the end date is easy to miss.
- Steep early termination fees. Ask what it costs to leave if service is poor, not just if you change your mind.
- No offboarding clause. The contract should say the provider will hand over credentials, configs and documentation within a set number of days if you leave.
- "Best effort" everywhere. A little is fine. If every service is best effort, there's nothing to measure.
- Device counts that drift. Check whether adding one access point bumps you into a higher pricing tier.
- No security responsibility defined. If a breach starts through the firewall, the contract should make clear what the provider was supposed to be doing.
None of these are automatic deal breakers. They're points to negotiate or clarify in writing.
A contract review checklist you can use this week
Print this out and go through your current or proposed contract line by line. If you can't answer a question from the document, ask the provider to put the answer in writing.
- Is every covered device listed by type, location and count?
- Are monitoring hours and alert actions stated clearly?
- How often are firmware updates reviewed and applied, and in what maintenance window?
- Are configuration backups automatic, stored off-device and tested?
- Are small changes included, and is there a monthly limit?
- What are the response targets by priority, and do they apply after hours?
- Is after-hours support included, or billed separately?
- Who owns the hardware, and what happens to it if we leave?
- Are licenses and support contracts registered to our company?
- Do we have our own admin credentials, stored where we control them?
- Do we receive network diagrams, an IP plan and a device inventory?
- What's the term length, renewal notice and early termination cost?
- Is there an offboarding clause with a handover deadline?
- What reporting do we get, and how often do we review it together?
If you're also comparing providers more broadly, my post on what Roanoke businesses should expect from managed IT services covers the bigger picture beyond the network.
Frequently asked questions
What is included in a managed network services contract?
Most contracts include network monitoring, firmware and patch management, configuration backups, change management, firewall and security subscription management, ISP ticket handling, documentation and regular reporting. The exact scope depends on the provider, so always check the device list and the exclusions section.
How much do managed network services cost?
Pricing is commonly based on the number of devices, sites or users, and it varies a lot by region and scope. Hardware, projects and after-hours work are often billed separately. The best way to compare is to get quotes that list the same devices and services side by side.
What's the difference between managed network services and managed IT services?
Managed network services focus on infrastructure: firewalls, switches, Wi-Fi, internet circuits and remote access. Managed IT services usually add desktop support, user accounts, email, servers and cloud apps. Many providers offer both together or separately.
How long are managed network services contracts usually?
One to three year terms are common, often with automatic renewal. Shorter terms give you more flexibility, while longer terms sometimes come with better pricing or included hardware. Read the renewal notice period and early termination terms carefully either way.
Can I switch managed network providers in the middle of a contract?
Usually yes, but it may cost you an early termination fee, and hardware-as-a-service equipment may need to be returned or bought out. Before switching, confirm you have admin credentials, current configs and documentation so the new provider isn't starting blind.
Not sure what your current contract really covers?
That's a good question to answer before your next renewal. During our free cybersecurity assessment, my partner Mukesh and I look at your firewall, switching, wireless and remote access, and we can walk through how that compares with what your contract says you're getting. You'll come away with a plain-English list of gaps.
There's no obligation to switch providers. Sometimes the right answer is to keep your current MSP and tighten a few contract terms. If you'd like a second set of eyes, request a free cybersecurity assessment and we'll set up a time that works around your production schedule.
Related reading
- MSP vs. Hiring a Full-Time IT Person: A Real Cost Breakdown
- Managed IT Services in Roanoke, VA: What Local Businesses Should Expect
- Cybersecurity for Roanoke Small Businesses: 10 Steps to Protect Your Company
Harsha is a co-founder of SoftwarePac Technologies in Roanoke, VA, and a network engineer with 15 years of experience.




