Operations vs Projects (Simple Definitions That Stop Scope Arguments)

Keep Control of Your IT Access

Prevent vendor lock-in and make renewals and support easier. Book a Fit Check to verify your license ownership, admin access, and recovery controls, then get a clear list of any gaps.

Book a Fit Check
_{15-Minute Discovery Call}

‍Last updated

May 13, 2026

Reviewed by

IT Service Delivery Lead

Speakable Summary

Monthly support covers routine operations that keep your current systems running. Projects are not included because projects are one-time change work.

Opening

Most scope arguments happen when the words are vague. One side thinks a change is “support” and the other side treats it as “project work.”

This page removes that ambiguity. It explains what monthly support includes, what it does not include, and how we handle anything that falls outside the monthly scope.

If you ever want different boundaries, that is fine. We revisit the contract and update scope in writing.

Direct Answer

Monthly support covers routine operations that keep your current environment running within scope. Projects are not included because projects change the environment and must be scoped and approvedseparately.

‍

Monthly support and project definitions

Monthly support definition
Monthly support means recurring operations work that keeps your current systems running within the agreed scope.

Project definition
A project is one-time work that changes, upgrades, migrates, rebuilds, or expands your environment.

‍

What monthly support includes

Included in monthly support	Not included because it is a project
Help desk support through tickets	Migrations and platform moves
Routine user onboarding and offboarding	Office moves and buildouts
Monitoring and alert handling	Network redesigns and major changes
Patch cadence and routine maintenance	New system implementations
Vendor coordination during incidents	Large cleanup and remediation work

‍

The boundary between support and project work

If the work changes the environment, it is a project.
If the work restores normal operation inside the current scope, it is monthly support.

Change means things like new systems, migrations, rebuilds, major redesign, or anything that alters how your environment is set up.

Restore means fixing what is already in place soit works normally again.

‍

Examples of monthly support and project work

These are monthly support

● User issues and troubleshooting handled through tickets

● Routine access changes inside existing systems

● Monitoring follow-through and resolving alerts

● Routine patching and maintenance within the current setup

● Vendor escalation during outages and service interruptions

These are projects

● Moving email, files, or tenants from one platform to another

● Implementing a new backup tool, VoIP system, firewall, or security platform

● Redesigning networks, Wi-Fi coverage, segmentation, or core configurations

● Office moves, new locations,buildouts, cabling, and coordinated go-lives

● Large cleanup work across many systems to rebuild standards or fix technical debt

‍

How we handle anything outside monthly scope

1. We label it as a project request.

2. We write a short scope summary.

3. We provide an approval path before work starts.

This keeps monthly support predictable. It also prevents surprise invoices.

If you want different boundaries later, we update scope in the agreement.

‍

Common Questions

Are projects included in monthly support

No projects are not included. Projects are separate because they are one-time change work.

Why are projects separate

Projects change systems and create risk that must be planned and approved. Monthly support is designed for predictable recurring operations.

What if something feels like a small change

If it changes the environment, it is a project. If it restores normal operation inside scope, it is monthly support.

What if we want more included in monthly support

That is fine. We revisit the contract and update scope in writing so expectations stay clear.

What if an emergency forces project work

We still treat it as project work. We document what is needed and get approval before expanding scope.

What if we are switching providers and need cleanup

Cleanup that changes the environment is a project. It should be scoped so the transition is controlled and predictable.

How do we avoid surprise invoices

We do not start project work under monthly scope. Anything outside scope is written and approved first.

Can you support both Microsoft 365 and Google Workspace

Yes within defined scope. Migrations between platforms are projects.

What should be written in the agreement

An included list, a not-included project list, and an approval rule. Clear writing is what stops arguments.

What is a Fit Check

A Fit Check maps your environment to clear scope boundaries. It clarifies what is monthly support and what becomes a project.

‍

Key terms in plain English

Monthly support: Recurring operations work that keeps your current systems running.
Project: One-time change work that modifies or expands the environment.
Scope: The written boundary of what is included.
Approval: A yes in writing before project work begins.
Change: Work that alters systems, design, or platform.
Restore: Work that returns existing systems to normal operation.
Cutover: A planned switch from old to new.
Closeout notes: A short record of what was done and why it worked.

‍

Copy/paste boundary statement

Monthly support includes recurring operations work that keeps the current environment running within scope. Projects are not included and are any one-time work that changes, migrates, rebuilds, upgrades, or expands the environment and must be scoped and approved separately.

‍

Call to action

If you want clean boundaries and predictable approvals, book a Fit Check. We will map your current environment to monthly scope and identify upcoming project needs before they become emergencies.

‍