What is excluded from the quoted cost of outsourced IT services?
The quoted cost of outsourced IT services typically excludes work outside the agreed support scope, such as major projects, hardware, software licences, third-party charges and specialist consultancy. The proposal should identify these exclusions clearly, including how additional work will be approved and charged.
The quoted cost of outsourced IT services is limited to the activities, users, systems and service levels expressly defined in the proposal. Anything dependent on assumptions that later change, or requiring a separate decision, resource or charge, may fall outside that price. An exclusion is not necessarily work the provider cannot undertake; it means the work is not covered by the agreed recurring fee unless it is separately authorised.
Common exclusions relate to the boundaries of the service model rather than to a particular technical task. For example, a proposal may assume a stated number of users, sites, devices or supported systems. If the organisation expands, acquires another business, adds a site or introduces a new platform, the original fee may no longer cover the changed environment. The contract should explain whether this leads to a revised monthly charge, a separate quotation or a formal review of the service scope.
Quotes can also exclude environments that do not meet the provider’s support requirements. Unsupported operating systems, obsolete equipment, undocumented networks, non-standard configurations or systems altered without approval may need assessment before they can be managed under the normal service. The cost of bringing those systems into a supportable condition should be identified separately, rather than assumed to be part of the ongoing fee.
Some work is excluded because it is remedial or investigative in nature. Examples may include tracing the cause of a recurring fault, restoring a system after an unauthorised change, reconstructing missing documentation, or correcting configuration issues inherited from another arrangement. These activities can take considerably more effort than routine maintenance. A clear proposal should distinguish between ordinary support and the additional work needed to establish a stable, supportable environment.
Travel and site-related expenses may also sit outside the quoted service, particularly where the agreement is primarily delivered remotely or covers specific locations only. The wording should state whether site visits are included, whether travel is charged separately, and how related expenses are handled. This is important for organisations with several premises or staff working from locations that were not included in the original assessment.
Security-related exclusions need especially careful reading. Routine monitoring and support may be covered, while investigation and recovery following a serious security event may be governed by a separate incident process. A contract should clarify what happens if an incident requires evidence preservation, specialist investigation, extensive restoration or coordination with external parties. It should also identify the point at which ordinary support becomes chargeable response or recovery work.
There may be exclusions connected with the responsibilities retained by the customer. These can include maintaining accurate user information, authorising changes, providing access to premises or systems, approving purchases, and ensuring that staff follow agreed procedures. If the provider cannot complete work because a required customer decision or access permission is unavailable, the associated delay and any further effort should be addressed in the contract.
The charging method for excluded work is as important as the exclusion itself. A proposal may use an hourly or daily rate, a fixed quotation, a pre-approved block of consultancy time, or a separate statement of work. It should explain how the provider estimates the work, whether investigation is chargeable before a final scope is known, how time is recorded, and whether a minimum billing period applies. Without these details, a business may understand that something is excluded but still be unable to predict the resulting cost.
Approval controls should be documented before the service begins. Good arrangements normally specify who can authorise additional work, the form that approval takes, whether a spending limit applies, and what happens when urgent action is needed to protect systems or restore service. Verbal requests and informal instructions can create disputes if it is unclear whether they changed the agreed scope.
Before accepting a quote, compare its exclusions with the operational assumptions behind it. Check the covered users, sites and systems; the distinction between routine support and remedial work; the treatment of visits and customer dependencies; the process for security incidents; and the rates or quotation method for additional work. Ask for ambiguous terms such as “reasonable use”, “standard support” or “non-standard system” to be defined. The more precisely these boundaries are recorded, the easier it is to distinguish a genuinely unexpected requirement from a cost that should have been included in the original agreement.
Compliance and governance work is often excluded from the recurring outsourced IT fee unless it is specifically listed in the proposal. Routine technical support does not necessarily include preparing policies, completing supplier questionnaires, producing audit evidence, carrying out formal risk assessments or supporting a compliance review.
These activities should be identified separately because their scope depends on the organisation’s obligations, existing documentation and the level of evidence required. Before accepting a quote, check whether compliance-related advice and documentation are included, limited to a stated amount, or charged as additional consultancy. The proposal should also explain how any follow-up actions, remediation work or audit requests will be assessed and approved.
