Are Projects Included in Monthly Support (Clear Boundaries)

Last updated

May 13, 2026

Reviewed by

Reviewed by: IT Service Delivery Lead

Speakable Summary

Projects are not included in monthly supportbecause they are one-time change work. Book a Fit Check to define what isincluded, what is excluded, and how approvals work.

Opening

Most frustration with IT providers comes fromone sentence. “I thought that was included.”

Monthly support is meant to keep day-to-dayoperations stable. Projects are meant to change systems, add capability, orclean up inherited issues in a planned way.

This page explains the boundary in plainEnglish. It helps you prevent surprise invoices and avoid the common trap whereeverything becomes a “project.”

Direct Answer

Projects are not included in monthly supportbecause they are one-time changes outside routine operations. Monthly supportshould include a clear project definition and an approval process so boundariesstay predictable.

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

What’s included vs what’s extra

Included   in monthly support

Not   included and becomes a project

Ticket-based help desk support

Migrations and platform moves

Routine onboarding and offboarding

Office moves and buildouts

Monitoring and alert handling

Major network redesigns

Patch cadence and routine maintenance

New system implementations

Vendor coordination during incidents

Large remediation and cleanup work

●    
Ask for included and excluded scope in writing

●    Require approval beforeout-of-scope work begins

●    Separate operations budget fromproject budget

Included means recurring work that keeps yourenvironment stable. Project work changes the environment and must be planned,scoped, and approved.

Primary Intent Block (DEFINITION)

If you only do one thing this week

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

●    Ask for an excluded scope list inplain English.

●    Ask how approvals work beforeextra work starts.

People

Monthly support covers day-to-day user help androutine access changes. Projects begin when the work affects many users at onceor requires planned rollout and coordination.

Device

Monthly support covers routine device issues,monitoring, and patching. Projects include large device refreshes,re-standardization, and major OS migrations.

Account/App

Monthly support covers routine administrationfor in-scope tools and normal access requests. Projects include migrations,major permission redesign, and new platform rollouts.

Operations

Monthly support includes ticketing,documentation upkeep, and vendor escalation during incidents. Projects includeplanned cutovers, large cleanup, and structured change work that requirestimeline and rollback planning.

Clear boundaries SMBs can use

Monthly support is for ongoing operations

Monthly support is recurring work that keepssystems stable. It is designed to reduce repeat issues through consistentmonitoring, patching, and standards.

It should include predictable support intake,closeout notes, and accountability. It should also include vendor coordinationwhen incidents happen.

Projects are for one-time change work

Projects are planned changes that modifysystems, add scope, or require coordination and testing. They often includedesign decisions, cutover planning, and rollback steps.

Projects must be quoted and approved before workbegins. This protects both the business and the provider.

What triggers a project

●    A migration or platform move

●    A new office buildout orrelocation

●    A major network redesign orfirewall replacement

●    Implementing a newline-of-business system

●    Large cleanup and remediationacross many systems

●    Major security redesign beyondbaseline controls

How to prevent surprise invoices

Require a written excluded scope list

If exclusions are not written, disputes happenduring emergencies. An excluded scope list is clarity, not negativity.

The excluded list should also state what becomesa project. That prevents “we thought it was included” arguments.

Use an approval gate for out-of-scope work

If a request is out of scope, work pauses untilapproved. Approval should include cost method, timeline, and what is changing.

An approval gate prevents the slow leak of“small extras” turning into a surprise bill.

Separate operations from projects in budgeting

Monthly support should be predictable operatingspend. Projects should be a separate line item so approvals are clean.

This also makes CFO planning easier. Spendvariance is reduced when projects are scoped early.

Use change control for risky project work

Projects often involve risky changes. Changecontrol keeps the business protected by requiring rollback steps andverification.

Change control does not have to be heavy. Itjust needs clarity before impact.

LINK: Help Desk
LINK: FAQ

‍

‍

‍

‍