Vendor management: controlling contracted service providers

Build one register or manage nothing

The first constraint is usually knowledge. Contracts sit in personal inboxes, renew automatically and are noticed only when the invoice changes. A central register holding each agreement's owner, term, notice date, price basis and service commitments is the precondition for every other control. Until it exists, negotiation happens after auto-renewal has already removed the leverage.

Service commitments have to be measurable by you

A commitment the vendor measures and self-reports is weaker than one you can observe from your own records. Where that is impractical, agree the measurement method and the data source in the contract itself, along with what happens when the two parties disagree. Vague obligations to use reasonable endeavours give you nothing to hold in a review beyond dissatisfaction.

Remedies that change behaviour

Service credits are the common mechanism, and on their own they rarely alter conduct because the amounts are small relative to the vendor's revenue. More effective structures pair them with escalation obligations, a remediation plan on repeated breach, a right to withhold a portion of fees, and termination rights that trigger on a pattern rather than a single event. The purpose is to make sustained underperformance more expensive than fixing it.

Renewals, term creep and lock-in

Vendors accumulate leverage through embedded processes, held data and integrations. Managing that means diarising notice dates well before they fall, keeping exit and data-return provisions current, and periodically testing the market even where no change is intended. Where the relationship covers services also handled by material suppliers, keep the governance separate so a commercial dispute in one does not contaminate supply in the other.

Frequently asked questions

How does vendor management differ from supplier management?

In practice by what is bought. Supplier management governs the sources of goods that feed the product and the plan; vendor management governs contracted services and indirect provision, where the risks are contractual and financial rather than production stoppage.

Who should own a vendor relationship?

The business function that consumes the service should own the outcome, with procurement owning the commercial terms and a central register owning visibility. Splitting it this way avoids both the purchasing team judging service quality it never experiences and departments signing terms nobody reviewed.

What is the most common source of avoidable indirect spend?

Contracts that renewed because nobody was tracking the notice date, and duplicated provision across departments buying the same capability separately. Both are register problems before they are negotiation problems.