This article explains how EasyITGuys handles covered and non-covered projects under managed IT services. Our goal is to make project expectations clear before work begins. Some IT projects are included because they are part of normal IT lifecycle management. Other projects require a separate quote, vendor professional services, or a specialized partner because they fall outside standard managed IT coverage.
This article also explains how we use Change Management Requests, also called CMRs, to plan, approve, communicate, and safely complete projects. A project does not happen just because someone asks for it. A project happens when the plan is clear, the scope is understood, the right people are involved, the risks are reviewed, and the required approvals are in place.
You can review these resources for more detail:
Managed IT services are designed to support a stable, secure, and maintainable technology environment. To do that well, we need clear boundaries around what is included and what requires a separate scope. Without clear boundaries, projects can become confusing, delayed, risky, or unfair to both the client and the support team.
Project boundaries help us:
Coverage boundaries are not meant to create friction. They are meant to prevent confusion. The earlier we define what is covered, what is not covered, and who owns each part of the project, the better the project usually goes.
Projects create change. Change can affect users, systems, security, downtime, workflows, vendors, applications, and business operations. Because of that, EasyITGuys uses a Change Management Request process for projects and important IT changes. A Change Management Request, also called a CMR, is the written plan for an important IT change.
A CMR helps answer important questions before the work begins:
This process is based on IT Service Management and ITIL-style change management principles. The goal is simple: important changes should be reviewed, planned, communicated, approved, and completed in a controlled way.
A successful project requires shared responsibility. EasyITGuys is responsible for planning and executing the covered IT portions of the project. The client is responsible for business decisions, approvals, vendor coordination where required, user testing, access to required systems, and timely communication. Vendors are responsible for their own software, systems, tools, databases, licensing, and professional services work.
That means a project may require agreement from:
Everyone does not need to do the same work. Everyone does need to agree on the plan. If the plan is not clear, approved, and ready, the project should not move forward.
We all agree on the project plan, or the project does not happen. This protects the client, the users, the business, and the project team. It is much better to pause before the project than to rush into a change that creates downtime, confusion, data loss, vendor issues, missed expectations, or unexpected costs.
A covered lifecycle IT project is a standard IT infrastructure project that is part of keeping the managed technology environment healthy, current, and supportable.
These projects are usually tied to a normal lifecycle event, such as:
Covered lifecycle projects generally involve standard IT infrastructure that EasyITGuys manages and supports as part of the client’s managed IT plan. Covered does not mean unplanned. Even covered lifecycle projects may still require a Change Management Request when they affect users, systems, downtime, security, vendors, or business operations.
The following are common examples of covered lifecycle IT projects when they are part of the managed environment and fit the service plan.
Examples:
Common covered Windows Server roles may include:
Examples:
Examples:
A simple way to think about this is: covered infrastructure hardware is usually core IT equipment that supports the business network, servers, storage, security, or connectivity.
Examples:
A project is generally not covered as a lifecycle IT project when it requires specialized work outside standard IT infrastructure support. These projects may still be very important. They may still be work we help coordinate. They may also be available through EasyITGuys, a vendor, or an approved partner under a separate quote. However, they are not automatically included as covered lifecycle IT projects.
The following are examples of projects that usually require a separate quote, vendor professional services, or a specialized partner.
Examples:
Why this is not fully covered: EasyITGuys supports the IT infrastructure around the application. We are not a replacement for the software vendor’s professional services team. Many line-of-business applications require vendor-specific tools, licensing checks, database conversion, application validation, or certified migration steps. A simple file-based move, such as moving a QuickBooks Desktop company file from one supported server share to another, may be handled as standard IT infrastructure work when no application upgrade, database conversion, vendor tools, repair, licensing issue, or specialized validation is required.
Examples:
Why this is not covered: Database work often requires specialized vendor or database engineering expertise. Incorrect database changes can create data loss, downtime, performance issues, or application corruption.
Examples:
Why this is not covered: Custom work is not standard managed IT support. It requires a separate scope because it depends on business requirements, testing, change control, security review, and long-term maintenance.
Examples:
Why this is not covered: Integrations can be complex and may involve multiple vendors, data ownership concerns, security risks, testing requirements, and ongoing maintenance.
Examples:
Why this is not covered: Compliance services require a separate scope because they are advisory, documentation-heavy, and often tied to legal, regulatory, contractual, or audit requirements.
Examples:
Why this is not covered: Website and marketing services are different from managed IT infrastructure services. They may be available under a separate website, marketing, or business growth service plan.
Examples:
Why this is not covered: Physical work may require onsite labor, tools, building access, licensed trades, safety planning, construction coordination, or third-party vendors.
Examples:
Why this is not covered: Unsupported technology creates security, reliability, compliance, and support risks. We may provide limited best-effort assistance, but the normal recommendation is to upgrade, replace, or standardize the system.
Here is a common example.
A client needs to migrate or update a line-of-business application to a new version on a new server.
Examples may include:
The old server may be running an unsupported operating system, such as Windows Server 2012 R2. The old server may also be failing, unstable, or no longer aligned with the client’s technology standards.
EasyITGuys can manage the standard IT lifecycle portion of the project.
This may include:
This is the part that falls under standard IT lifecycle management.
The software vendor or vendor-certified professional services team is responsible for the application-specific migration.
This may include:
This work belongs with the vendor because they know their software, database structure, upgrade path, and support requirements.
This split protects the client. EasyITGuys manages the IT infrastructure. The application vendor manages the specialized application and database work. That gives the project the best chance of being completed safely, correctly, and with the right experts involved.
Not every line-of-business application move is the same. Some applications are simple file-based systems. Others are more complex and may require vendor tools, database work, professional services, licensing changes, software upgrades, data conversion, or specialized validation. Because of this, EasyITGuys reviews each line-of-business application move based on risk and complexity.
The goal is simple: we want the right people responsible for the right parts of the project.
Line-of-business application moves should not be a frequent or regular activity. In a healthy environment, most server-based line-of-business application moves should happen during a planned lifecycle event. A common example is a Windows Server replacement cycle. Microsoft’s Fixed Lifecycle Policy commonly includes a minimum of five years of Mainstream Support and an additional period of Extended Support for some products. Windows Server Long-Term Servicing Channel releases are designed for longer-term server use, with defined mainstream and extended support dates. Because of this, many server-based application moves should normally align with planned server lifecycle replacement cycles instead of happening repeatedly without a clear reason. If the same application needs to be moved repeatedly, EasyITGuys may recommend a root cause review before approving another move as a normal project.
Common root causes may include:
Repeated movement of a business application is not normal. It may indicate a larger stability, design, vendor, lifecycle, or business process issue.
A Tier 1 line-of-business file move can usually be handled as part of a covered lifecycle project when it is truly a simple file-based move. This type of work is usually standard IT work because we are moving or reconnecting files on supported infrastructure.
Examples may include:
A Tier 1 move usually has these characteristics:
The client is still responsible for application-level testing. This includes confirming that the correct users can open the application, access the file, and complete their normal business workflows.
If we are moving a file, share, shortcut, permission, or mapped drive on supported infrastructure, it may be covered as standard lifecycle IT work.
A Tier 2 line-of-business application move may be covered in part, but it may also require vendor involvement, additional approval, or a separate billable project scope depending on what is discovered. This type of move is more involved than a simple file move, but it may not rise to the level of a full vendor-led migration.
Examples may include:
In these cases, EasyITGuys may assist with the infrastructure and basic application connectivity portions of the project. However, vendor support may be required if the software requires specialized configuration, licensing, upgrade, repair, conversion, or troubleshooting.
If we are helping connect the application to supported infrastructure, we may be able to assist. If the work becomes application-specific, vendor-specific, or requires specialized knowledge of the software, vendor support or a separate scope may be required.
A Tier 3 line-of-business application migration is not considered a standard covered lifecycle IT project unless it is specifically included in writing. This type of project requires the software vendor, certified application provider, database specialist, or professional services team to lead the application-specific portion of the work.
Examples may include:
EasyITGuys can still help manage the IT infrastructure portion of the project.
This may include:
EasyITGuys is not a replacement for the vendor’s professional services team. The application vendor is responsible for the specialized application, database, licensing, conversion, and validation work.
If we are moving, upgrading, converting, repairing, validating, or reconfiguring the application or database, the project needs review and may require vendor support or a separate scope.
EasyITGuys uses the following questions to determine whether a line-of-business application move is Tier 1, Tier 2, or Tier 3:
If the answer is mostly no, the work may be handled as a Tier 1 basic file-based move. If the answer is yes to one or more application-specific items, the work may be Tier 2 or Tier 3. If the application is being moved repeatedly, EasyITGuys may recommend a root cause review before approving another move. Repeated movement of a business application is not normal and may indicate a larger stability, design, vendor, lifecycle, or business process issue. The goal is not to avoid helping. The goal is to make sure the business is solving the real problem.
Many projects are mixed-scope projects. That means part of the project may be covered, while another part may require a vendor, partner, separate quote, or separate professional services agreement.
For example, a line-of-business application server migration may include:
1. Covered lifecycle IT work:
2. Non-covered vendor or specialized work:
In this type of project, the CMR helps define:
This avoids the common problem where everyone assumes someone else is handling an important part of the project.
A CMR is generally required when a project or change could affect:
A CMR may also be required when a project has a meaningful risk of confusion, downtime, cost changes, vendor dependencies, or business disruption.
Not every small task requires a full CMR. Routine, low-risk, well-understood support tasks may follow the normal ticket process.
Examples may include:
EasyITGuys will determine when a request should remain a normal support ticket and when it should become a CMR.
A project cannot move forward until the required CMR details are reviewed and approved.
The approval process may include:
If required approvals are not received by the deadline, the project may be postponed. This is not unnecessary red tape. It protects the business from rushed work, incomplete planning, missed communication, avoidable downtime, and unclear responsibility.
A strong CMR should include the following details:
A short explanation of what is changing and why.
The reason the project is needed.
Examples:
A clear explanation of what is included. This should define what EasyITGuys is doing, what the client is doing, and what vendors or partners are doing.
A clear explanation of what is not included. This is especially important for projects involving applications, databases, vendors, compliance, cabling, construction, custom development, or unsupported technology.
The CMR should clarify which portions are covered under the managed IT plan and which portions require a separate quote, vendor agreement, or approval.
The CMR should list the systems, users, departments, locations, and services that may be affected.
The CMR should identify project risks.
Examples:
The CMR should define who needs to know about the project and when they need to be informed.
The CMR should define when the work will happen. This may include after-hours work, business-hours work, phased work, or a scheduled maintenance window.
The CMR should explain what happens if the change fails or cannot be completed as expected. Not every project can be rolled back easily. If rollback is limited or not possible, that should be clearly stated before the project begins.
The CMR should define how success will be confirmed.
Testing may involve:
The CMR should define who must approve the project before work starts.
To keep projects moving smoothly, clients are responsible for helping with reasonable project needs.
This may include:
A project can be delayed when client approvals, vendor responses, licensing details, access, testing, or business decisions are not provided in time.
When a vendor is involved, the vendor is responsible for the specialized work related to their product or service.
This may include:
EasyITGuys can help coordinate with the vendor, but we are not a replacement for the vendor’s professional services team.
EasyITGuys is responsible for the approved IT portion of the project.
This may include:
Use these simple rules to understand project coverage:
Use the following guide to understand how a project will usually be handled.
| Project Type | Usually Covered? | CMR Required? | Notes |
|---|---|---|---|
| Replace supported firewall | Yes | Yes | Covered when part of normal infrastructure lifecycle and service scope. Hardware cost is separate unless included in writing. |
| Replace supported switch | Yes | Yes | Required when it affects phones, Wi-Fi, users, production systems, or downtime. |
| Replace supported wireless access point | Yes | Yes | Required when it affects business Wi-Fi coverage, downtime, or multiple users. |
| Replace supported server hardware | Yes | Yes | Covered when part of normal infrastructure lifecycle and service scope. Hardware cost is separate unless included in writing. |
| Upgrade supported Windows Server operating system | Yes | Yes | Covered when it is a standard OS lifecycle project. |
| Migrate standard Windows Server roles | Yes | Yes | Examples may include Active Directory, DHCP, DNS, and file services. |
| Update managed workstations to connect to a new server | Yes | Yes | Covered when part of the approved lifecycle project. Smaller single-user or single-device requests may be handled as normal tickets instead of project work. |
| Tier 1: Line of business (LOB) application File Move | Yes | Yes | Covered when it is a simple file, share, permission, shortcut, or workstation connectivity move without database conversion, vendor upgrade, licensing issues, repair, or specialized application work. |
| Tier 2: Assisted Line of business (LOB) Application Move | Yes (partial) | Yes | May be covered in part when EasyITGuys is handling infrastructure and basic connectivity. Vendor support or separate scope may be required if application-specific configuration, Database Server Manager work, licensing, repair, upgrade, or troubleshooting is needed. |
| Tier 3: Specialized ERP, SQL, or database-backed migration | No | Yes | Requires vendor professional services, database specialist, or certified application support when migration, conversion, upgrade, validation, custom integration, or specialized application work is required. |
| Custom scripts or software changes | No | Yes | Requires separate scope. |
| Application integrations | No | Yes | Requires separate scope and possible vendor involvement. |
| Cabling or electrical work | No | Yes | Requires separate onsite, cabling, or electrical scope. |
| Remediate unsupported or nonstandard technology | No | Yes | Applies to technology that is end-of-life, not vendor-supported, outside the managed scope, not aligned with our Technology Standards Map, or not reasonably supportable. Cleanup, replacement, onboarding, or standardization work is separate unless included in writing. |
| Compliance documentation or audit evidence | No | No | Requires compliance or vCISO service scope. A CMR may still be required if the work includes production system changes. |
| Website, SEO, or marketing work | No | No | Requires separate website or marketing service scope. A CMR may still be required if the work affects DNS, email, security, hosting, production systems, or business operations. |
Even when the labor for a lifecycle IT project is covered, hardware, software, licensing, subscriptions, renewals, upgrades, shipping, vendor fees, and third-party costs are not included unless specifically stated in writing.
Examples of separate costs may include:
EasyITGuys may provide limited best-effort support for non-supported software as an accommodation. Best-effort support does not mean the software is fully covered. It also does not guarantee resolution. For line-of-business applications, we strongly recommend that clients maintain an active vendor support contract. This gives the client access to the software vendor when application-specific help is needed.
Vendor support contracts are important for specialized software.
They help with:
Without vendor support, application issues can take longer to resolve and may require additional billable work.
When a project request is submitted, EasyITGuys will review the request and determine how it should be handled.
We first confirm what the client is trying to accomplish.
Examples:
We review the systems involved.
Examples:
We separate the standard IT lifecycle work from specialized or excluded work. For line-of-business application moves, EasyITGuys classifies the project work as Tier 1, Tier 2, or Tier 3. Tier 1 is a basic file-based move. Tier 2 is an assisted application move. Tier 3 is a specialized vendor migration. This helps everyone understand what is covered, what may be partially covered, and what requires vendor support or separate approval.
This helps define:
If the project affects users, systems, security, downtime, business operations, vendors, or risk, a CMR is required. The CMR becomes the written plan for the project.
If a vendor, application provider, database specialist, cabling provider, compliance consultant, or other partner is needed, we will identify that early. Vendor involvement is especially important for Tier 2 and Tier 3 line-of-business application moves. If the application requires vendor tools, licensing support, database work, conversion, repair, upgrade, or specialized validation, the vendor or certified professional services team may need to be involved before the project can move forward.
If the project includes non-covered work, we will provide or recommend a separate quote, statement of work, or vendor scope before that portion begins.
The required stakeholders review the plan. The project does not proceed until the required approvals are in place.
Once approved, the project is scheduled.
This may include:
The work is completed according to the approved plan. If new information changes the plan, the project may need to pause, be updated, or be re-approved.
The project is tested and reviewed.
Closure may require:
No. Managed IT services include support and certain lifecycle IT projects based on the service plan. Projects outside that scope require a separate written agreement, quote, or vendor scope.
Sometimes, yes. Coverage answers the question, “Is this included?” A CMR answers the question, “How will this be planned, approved, communicated, and completed safely?” A project can be covered and still require a CMR.
Because the server and the application are different layers. EasyITGuys can manage the server infrastructure. The software vendor should manage the specialized application and database migration.
No. A simple QuickBooks Desktop company file move from one supported server share to another may be handled as standard IT infrastructure work when no application upgrade, database conversion, vendor tools, repair, licensing issue, or specialized validation is required. However, if the work involves QuickBooks Database Server Manager, application repair, licensing, activation, version upgrades, database services, data conversion, vendor-specific errors, or specialized validation, vendor support or a separate project scope may be required. The difference is whether we are moving a business file on supported infrastructure or performing specialized application work.
No. Line-of-business application moves should not be a frequent or routine activity. In a healthy environment, many server-based application moves should align with planned lifecycle events, such as Windows Server replacement cycles. If the same application needs to be moved repeatedly, EasyITGuys may recommend a root cause review. Repeated moves can be a sign of unstable servers, unsupported software, poor vendor planning, incomplete prior migrations, storage issues, performance issues, technical debt, or a larger business process problem. The goal is to solve the real issue instead of repeatedly moving the same problem from one system to another.
Yes. In many cases, we can help coordinate, advise, or participate in the project. The work may require a separate quote or a vendor professional services agreement.
Not unless they are specifically included in writing. Hardware, software, subscriptions, renewals, license true-ups, vendor support fees, and third-party costs are typically separate.
If the work is required to bring the environment up to minimum standards, replace unsupported systems, fix pre-existing issues, clean up technical debt, or remediate security gaps, it may require a separate scope unless specifically included in writing.
Unsupported systems may continue to function, but they create risk. They may be harder to secure, harder to support, and more likely to cause downtime. EasyITGuys may recommend replacement or may limit support until the system is brought back to standard.
The project may be delayed. This protects the business from rushed work, unclear expectations, missed communication, downtime, and incomplete planning.
EasyITGuys reviews the request against the applicable quote, service plan, Service Guide, Terms of Service, Technology Standards Map, and written recommendations. If there is a conflict, the client-specific quote or written agreement controls.
EasyITGuys determines whether a CMR is required based on the project risk, business impact, user impact, system impact, security impact, vendor involvement, and complexity of the change.
The project decision is shared. EasyITGuys owns the IT planning and execution within the approved scope. The client owns business approval, timing approval, user testing, and required business decisions. Vendors own their specialized products and professional services work. If the required parties do not approve the plan, the project should not move forward.
EasyITGuys includes standard lifecycle IT project work because modern, supported infrastructure is essential to a healthy business technology environment. Specialized projects require a separate scope because they often involve vendor-specific software, databases, compliance requirements, custom work, physical work, unsupported technology, or third-party costs. Change Management Requests help make projects safer, clearer, and more successful.
The goal is not to slow projects down. The goal is to make sure the right work happens the right way, with the right people, at the right time, under the right plan. We all agree on the plan, or the plan does not happen.
