What’s Not Included in Managed IT (What Becomes a Project)

Last updated

May 12, 2026

Reviewed by

Reviewed by: IT Service Delivery Lead

Speakable Summary

Managed IT covers ongoing operations and supportwithin a defined scope. Projects are one-time changes that modify systems oradd major new scope.

Opening

Most conflict with IT providers starts with onesentence. “I thought that was included.”

Managed IT should reduce surprises, but onlywhen boundaries are written in plain English. The goal is not to excludeeverything. The goal is to separate day-to-day operations from one-time changework so approvals and budgeting stay clean.

This page explains what managed IT usually doesnot include, what becomes a project, and how to prevent scope disputes beforethey turn into surprise invoices.

Direct Answer

Managed IT usually excludes one-time change workthat alters systems or adds major new scope. Projects should be quoted andapproved separately to prevent surprise charges.

LINK: IT Support page
LINK: Managed IT Services
LINK: Managed IT Pricing

What’s included vs what’s usually extra

Typically   included in managed IT

Usually   becomes a project

Ticket-based support and routine requests

Migrations and rebuilds

Monitoring and alert handling (RMM)

Office moves and new buildouts

Patch cadence and routine maintenance

Major network redesigns

Routine onboarding and offboarding

New system implementations

Vendor escalation during incidents

Large cleanup and remediation work

●    
Ask for excluded scope in writing before signing

●    Require an approval gate beforeproject work starts

●    Separate projects budget frommonthly operations budget

Included means recurring work that keeps systemsstable. Project work changes systems, adds new scope, or requires plannedexecution.

Primary Intent Block (DEFINITION)

If you only do one thing this week

●    Ask your provider to define“project” in one paragraph.

●    Ask what is excluded in plainEnglish.

●    Ask how approvals and quotes workbefore any extra work starts.

People

Managed IT typically includes day-to-day supportfor users and routine access changes. Projects usually start when the requestbecomes a larger rollout like a new department, a large hiring class, or achange that impacts many users at once.

Device

Managed IT typically includes routine devicesupport, patching cadence, monitoring, and standard setup. Projects usuallystart when you are refreshing many devices, changing device standards, ormigrating operating systems at scale.

Account/App

Managed IT typically includes routineadministration for in-scope tools and standard access requests. Projectsusually start when you are migrating platforms, changing domains, implementinga new major app, or redesigning permissions and structure.

Operations

Managed IT typically includes ticketing,documentation upkeep, vendor escalation, and consistent follow-through.Projects usually start when the work requires a planned design, coordinatedcutover, or a major environment change that needs approvals and rollback planning.

What usually becomes a project

Migrations and platform moves

Email moves, tenant-to-tenant migrations, fileserver to SharePoint moves, and cloud platform changes are projects. Theyinvolve planning, testing, cutovers, and rollback steps.

Office moves and buildouts

Moves involve cabling, equipment placement, newcircuits, and physical testing. Even if support can coordinate vendors, themove itself should be scoped as a project.

Major network redesigns

Replacing core network equipment, redesigningVLANs, rebuilding Wi-Fi coverage, or changing firewall architecture is projectwork. These changes can create downtime if rushed and should be planned.

New system implementations

New line-of-business applications, new VoIPplatforms, new backup platforms, or new security stacks are projects.Implementation requires onboarding, training, configuration, and validation.

Large remediation and cleanup

Inherited environments can have years of drift.If the work requires deep cleanup across many systems, it should be scoped as aproject rather than “quietly absorbed” into operations.

Compliance and audit preparation

Audit packaging and formal compliance programsare often projects. Ongoing baseline controls may be included, but auditpreparation is usually separate scope.