Vendor Ecosystem Examination Checklist

The vendor ecosystem examination checklist is the set of questions a workforce or operations leader asks about an outsourced service supply base on arrival at any company, before any restructuring decision is taken. It is deliberately short. Each question maps to a lever on Vendor Ecosystem Restructuring Agenda, which carries the reasoning, the dependencies and the evidence; this page is the list to walk through.

Purpose

• Why does each vendor seat exist: variance absorption, market access, or rate arbitrage?
• Which work is front office (judgment) and which is back office (specified), and are they sourced on different logic?
• Is the back office on a standardize, consolidate, automate track, or is it treated like the front office?

Portfolio

• How many vendors serve each body of work, and could it consolidate to a pair for the front office and a pair for the back office?
• What is the selection logic for each pair: substitutability for the front office, automation path for the back office?
• Is any work delivered off-network, on vendor telephony or tooling the company cannot see, or placed outside a framework agreement?
• What exits does the answer imply, and is there a transition plan: notice, parallel run, hypercare, knowledge transfer?

Comparability

• Is there one quality instrument, meaning one rubric, one sampling design and one calibration cadence, across all vendors and captive centers?
• Does the sampling volume resolve the differences that decisions are made on?
• Are targets set by work tier, or differentiated by location or supply type?
• Is there one taxonomy of work types, or does each vendor define the same work differently?
• Have the contracts been read from the signed documents: term, notice, minimums, attrition and tenure terms, at-risk fees, facility approvals, data and automation clauses?

Pricing unit

• What is paid for: full-time equivalent, clock hour, productive hour, transaction, or outcome?
• If productive hours, is the denominator standardized before it ranks anything?
• Where could transaction pricing be piloted on one back-office transaction type?
• Is outcome pricing feasible given attribution and baseline disputes?

Contract terms

• Tenure by team: is there an attrition ceiling on the named account, a tenure-mix floor, and named-team continuity?
• Is fee at risk on the same scorecard that governs allocation, settled monthly and framed as earnable?
• Commitment horizon: is the planning function in the room, and is there a lock ladder of tolerances set against forecast error?
• Relief valve: is committed flex distinguished from contingent flex, is it metered, is the ramp-down protected, and is cross-vendor overflow tested?
• Dedicated, designated or pooled: which seats are genuinely dedicated and priced as such, and is the rest pooled?
• Is renegotiation designed at signing, with flexibility provisions and termination for convenience?

Automation

• Is there a gain-share on the efficiency component, or is the vendor paid to suppress contact reduction?
• Are data isolation, no-training, model ownership, volume decline against minimums and productivity-dividend sharing addressed?
• Are those clauses drafted ahead of the next renewal or platform migration?

Governance

• Is the commercial pen (contracts, billing, penalties, the measurement instrument) split from the daily performance conversation?
• Does operations own daily performance for all but highly specified work? See Specification and the Placement of Vendor Oversight.
• Does the party that owns the measurement instrument also own the verdict? It should not. See Vendor Governance Placement.
• Is there a tiered review cadence with a cross-vendor calibration forum?

Destination

• Is there a placement function that computes where work goes, or is placement decided by relationship? See Placement Engine Architecture.
• Is flexibility a measured objective, or an invisible contract term?

The order the answers can be acted on

1. Purpose per seat.
2. Consolidate; this is not gated on anything else.
3. One instrument, one taxonomy and the contract inventory, in parallel.
4. Pricing unit, tenure terms and the at-risk fee.
5. Transaction pilot, gain-share and relief-valve test, after the suppliers are comparable.
6. Automation and model clauses drafted now, signed at the counterparty's renewal or migration.
7. The placement function, built alongside all of the above.

How to use it

Walk the list once in the first weeks, recording for each question one of four answers: settled, in flight, gated (and on what), or not started. The gated answers show the dependency chain; the not-started answers in the Comparability section are usually the ones that block everything above them. The reasoning behind each question, and the research that bears on it, is on Vendor Ecosystem Restructuring Agenda.

See Also

• Vendor Ecosystem Restructuring Agenda — the levers, dependencies and evidence behind each question
• Vendor Portfolio Design by Body of Work — consolidation and the pair per body
• Placement Rules and the Tenure Contract — tenure terms
• Sample Size and Detectable Difference in Quality Measurement — whether the sampling resolves anything
• The Vendor as Relief Valve — the flex terms