Before hiring an IT outsourcing provider, verify more than its service list and sales presentation. This reusable IT outsourcing vendor due diligence checklist helps procurement, operations, and technology teams examine financial stability, technical capability, security controls, data handling, subcontractors, references, insurance, service levels, escalation paths, and contract ownership before a provider reaches the final shortlist.
Overview
Due diligence is the process of testing whether a provider can deliver the proposed service safely, consistently, and under clearly defined commercial terms. It is different from comparing logos, hourly rates, platform badges, or general outsourcing provider reviews. A provider may be a strong fit in one area and unsuitable in another, depending on your data, operating model, regulatory obligations, internal skills, and tolerance for dependency.
Use this checklist after defining the scope of work and before signing a statement of work or master services agreement. Ask each shortlisted provider for evidence in a consistent format, record unanswered questions, and distinguish between evidence that has been verified and information that has only been asserted. A simple red, amber, or green status can make gaps visible without creating a false sense of precision.
For a broader procurement workflow, pair this checklist with the Cloud Migration and MSP RFP Template and Vendor Evaluation Scorecard. If the proposed work involves migration, managed services, development, or DevOps, adjust the evidence requested to match the actual risk.
Core evidence categories
- Company: legal entity, ownership, operating history, financial resilience, and relevant locations.
- People: named delivery leaders, staff qualifications, availability, retention, and background-check practices where relevant.
- Technology: architecture, tooling, delivery methods, access controls, monitoring, documentation, and support coverage.
- Security and privacy: policies, independent assessments or certifications where applicable, incident procedures, data locations, and access management.
- Commercial and legal: insurance, liability, intellectual property, confidentiality, subcontracting, termination assistance, and exit terms.
- Performance: references, service levels, reporting, escalation routes, remedies, and ownership of corrective actions.
Checklist by scenario
Not every engagement requires the same depth of review. Use the relevant checks below, then apply the full checklist to providers handling sensitive data, production systems, regulated processes, or business-critical operations.
For a software development provider
- Request examples of comparable projects and ask what the provider personally delivered.
- Confirm who owns source code, documentation, designs, test assets, build pipelines, and other work product.
- Identify the proposed team by role, location, seniority, and expected allocation. Ask how substitutions are approved.
- Review the development workflow, code review practice, testing responsibilities, release process, and defect-handling procedure.
- Confirm repository access, credential management, environment separation, and the process for returning assets at the end of the engagement.
- Clarify whether any open-source or third-party components require approval, disclosure, or separate licensing review.
For cloud migration or consulting work
- Ask for a representative migration plan showing discovery, dependency mapping, testing, cutover, rollback, and post-migration support.
- Verify relevant experience with the cloud platform, workload type, operating model, and integration constraints in your scope.
- Define who owns architecture decisions, landing-zone configuration, identity design, network changes, security findings, and documentation.
- Request assumptions behind the proposed timeline and identify conditions that would create change requests.
- Confirm how access is granted, reviewed, removed, and logged during the project.
For a structured comparison, see Cloud Migration Services Comparison: How to Match a Provider to Your Project and the guide to verifying AWS, Azure, and Google Cloud partner credentials.
For managed cloud or infrastructure services
- Define supported systems, service hours, monitoring responsibilities, maintenance windows, and included versus excluded work.
- Review the service-level objectives, measurement method, reporting frequency, exclusions, and remedies for missed commitments.
- Ask for the escalation matrix, on-call structure, incident communications process, and named service owner.
- Confirm backup, recovery, vulnerability management, patching, logging, and privileged-access procedures.
- Understand how cloud consumption charges, provider fees, third-party licenses, and project work are separated on invoices.
- Establish how changes to tooling, staffing, scope, or cloud architecture are proposed, approved, and documented.
The Cloud Outsourcing Disaster Recovery Assessment Checklist can help extend this review into recovery planning. For ongoing financial oversight, use the Cloud Managed Services Cost Review Template.
Evidence-request table
| Area | Request | What to verify |
|---|---|---|
| Company stability | Legal entity details, ownership information, and relevant financial or operating disclosures | The contracting entity is clear and can support the proposed commitment. |
| Technical staff | Proposed team profiles, role descriptions, certifications where relevant, and availability | The people presented during evaluation match the delivery plan. |
| Security | Security policies, assessment reports, certifications, or control summaries where applicable | Controls address your data, access, infrastructure, and incident risks. |
| Subcontractors | Current and planned subcontractor list, locations, responsibilities, and approval process | You know who may access systems or data and who remains accountable. |
| References | Comparable customer references and a short description of the delivered scope | References can discuss reliability, communication, transitions, and problems resolved. |
| Insurance | Relevant coverage types and evidence of current coverage | Coverage aligns with the service risk and contract requirements. |
| Service levels | Draft service levels, reporting examples, exclusions, and escalation matrix | Performance can be measured and unresolved issues have an agreed route. |
| Data handling | Data locations, retention, deletion, access, transfer, and incident procedures | Handling practices match your privacy, security, and contractual requirements. |
| Exit and ownership | Transition plan, asset-return process, documentation obligations, and termination assistance | You can recover systems, knowledge, credentials, and work product without avoidable dependency. |
What to double-check
Evidence is useful only when it matches the proposed scope. A certification, partner designation, policy document, or favorable reference does not automatically validate every service. Check the coverage period, legal entity, locations, business unit, and control boundaries. Ask whether the evidence applies to the team and systems that would actually support your account.
Double-check the difference between the sales team and the delivery team. Request an initial organization chart, named account owner, technical lead, escalation contacts, and expected staffing model. Ask what happens when a key person leaves or becomes unavailable. If the provider will use nearshore or offshore teams, confirm working hours, handoffs, language expectations, access restrictions, and support coverage rather than treating location as a quality proxy.
Review subcontracting carefully. Require notification of material changes, define your approval rights where needed, and identify whether subcontractors can access production environments or confidential information. Responsibility should remain clear even when work is distributed across multiple entities.
Test the contract against realistic failure scenarios. What happens after a serious incident, missed service level, disputed invoice, security event, prolonged outage, or termination? Confirm who owns investigation, communications, remediation, records, and costs. If exit requirements are vague, dependency can increase over time.
Finally, compare the proposal with the operating model your team can actually manage. A detailed service may still fail if your organization cannot supply timely approvals, product decisions, access, subject-matter expertise, or internal ownership. Include these client-side dependencies in the evaluation record.
Common mistakes
- Choosing on price alone: A lower rate may exclude monitoring, documentation, security work, management time, or transition support. Compare total scope and operating effort.
- Accepting generic evidence: Ask how a policy or control applies to your exact service, data, location, and access model.
- Skipping customer references: Speak with references about incidents, missed expectations, staff changes, billing disputes, and the end of the engagement—not only the initial sale.
- Leaving ownership until the end: Define ownership of code, configurations, credentials, documentation, data, and intellectual property before work begins.
- Ignoring subcontractors: A provider may coordinate the service while another party performs important work. Map the delivery chain.
- Writing vague service levels: Terms such as “prompt response” or “high availability” need a measurable definition, reporting method, and escalation path.
- Failing to record exceptions: If a provider cannot supply evidence, document the gap, risk owner, compensating control, and deadline for resolution.
When to revisit
Run this due-diligence review before every new shortlist and repeat the relevant checks at renewal, after a material scope change, or when the provider proposes a new subcontractor, location, platform, or delivery model. Revisit it after a security incident, serious service failure, ownership change, major staffing change, or shift in the sensitivity of the data being processed.
At least annually, review whether your evidence is still current: insurance, certifications or independent assessments, security policies, contact lists, subcontractor records, recovery arrangements, and service reports. Also update the checklist when your workflows, tools, cloud architecture, privacy obligations, or internal approval process changes. Regulatory and compliance expectations can change, so confirm current requirements with your legal, privacy, and security advisers rather than relying on an old template.
To put the checklist into practice, create a vendor evidence folder, assign an owner to each open item, and set a decision date. Mark every item as verified, partially verified, not applicable, or unresolved. Escalate unresolved high-impact risks before contract signature; do not hide them inside general evaluation notes. After appointment, retain the checklist as the baseline for quarterly reviews and renewal decisions. The quarterly provider performance review workflow can help turn initial due diligence into an ongoing control.
For the next shortlist, start with the IT Outsourcing Vendor Vetting Checklist and RFP Template, tailor the evidence requests to your scope, and have procurement, technology, security, finance, and the business owner review the final risk record together.