Recurring services cover the responsibilities defined for covered users and systems. Work outside those responsibilities may require separate pricing, authorization, and scheduling before it begins.
When separate approval is needed
When a request falls outside purchased recurring responsibilities, Cloud Core MSP identifies the separate work, explains practical options and dependencies, provides the applicable pricing or estimate, and obtains the required authorization before scheduling or beginning it.
Projects and major changes
- Migrations, new deployments, major upgrades, and system rollouts.
- Site moves and onboarding or stabilization work beyond the purchased onboarding service.
- Tenant consolidation or major cloud and identity redesign.
- Firewall replacement, wireless redesign, network redesign, and server buildouts.
Physical and on-site work
- On-site troubleshooting and desk-side hardware work.
- Cabling, field installation, and office moves.
- Hardware swaps, rack work, and equipment installation.
- Printer or copier hardware repair and bench work.
After-hours work
- Routine night, weekend, or holiday work that does not meet the P1 emergency criteria.
- Planned after-hours change windows and weekend rollout work.
- Urgency alone does not make a request P1; P1 emergencies follow the published emergency process and selected emergency-response responsibilities.
Application, vendor, and third-party work
- Line-of-business application customization.
- Vendor project meetings.
- Database or reporting work.
- Software implementation consulting.
- Third-party professional services, licensing, supplier charges, hardware, and other external costs.
Major incident and recovery work
- Cybersecurity incident response beyond the initial containment and stabilization included in a selected service.
- Digital forensics, legal evidence preservation, and legal hold support.
- Large recovery events, major post-incident rebuilds, and ransomware recovery.
- Reconstruction, specialized data recovery, or application repair beyond standard restore operations.
Unsupported or uncovered systems
- Work on systems not covered by the purchased service.
- Systems lacking MSP access or tooling.
- Unsupported or end-of-life systems.
- Personal or BYOD devices not expressly included.
Pricing, approval, and scheduling
Depending on the work, Cloud Core MSP may provide a project proposal, Statement of Work, approved hourly estimate, supplier pricing, or another written authorization method. Work does not proceed until the required client approval is received.
Scheduling considers operational impact, system access, client availability, vendor commitments, parts, licensing, site access, and the approved work plan. Municipal approvals may also require a purchase order, available budget, board approval, finance preaudit, or another procurement step.
Why this matters
A clear distinction between recurring support and separate work gives leadership visibility into responsibility, options, cost, authorization, and timing before a project or major change begins.