← BackSee all toolsPartner and Vendor SLA PlaybookWorking demo · sample data · shows a method I used, not a real event
Partner SLAs · cascade and scorecard

Partner and Vendor SLA Playbook

A tiered allocation cascade, a remedy ladder, a scorecard and six commercial terms that prevent most disputes.

I built playbooks like this for partner networks and for hardware vendors. Every number and tier is illustrative.

Allocation

A cascade with a clock on every tier.

Orders go to the first tier. Each tier has a fixed window to accept all, accept part or decline. Declined work cascades; if no partner accepts, it falls to the internal team. Pick where it lands.

Where does an order get accepted?

96Hours to allocation, worst case
Tier 2Accepted by
PartnerFulfilled by

Remedies

A ladder, so nobody improvises.

The response to a late delivery should be decided before it happens. Drag the days late to see which step applies.

  1. On time Nothing to do. Record it.
  2. Nudge Same-day message from the owner: new date, one question, no blame.
  3. Written notice Written notice. Root-cause analysis due in two business days.
  4. Credit and hold Credit or hold terms apply. Weekly review with the vendor's lead.
  5. Second source Split the volume. Qualify a second source before the next order.

Measurement

The scorecard, and what the SLA is set to.

Set the SLA and watch which partner types meet it. A target nobody meets is a signal to fix the process or the contract.

Partner typeAvg daysOn timeStatus
Hardware distributor4.888%
Watch
Installer network7.363%
Fix
Repair and returns9.038%
Fix
Software vendor support3.4100%
Meets

Eight sample orders per partner type. Illustrative.

Terms

Six commercial terms that prevent most disputes.

Orders

One purchase order per batch, ship date and address.

Mixing destinations in one order is how the wrong thing goes to the wrong place. Split them at the source.

Stock

An inventory buffer and written hold terms.

Agree how long the vendor holds stock for you and what happens at expiry, before the first order.

Install

A site survey before the install.

A small survey fee protects against rework and change orders across a large rollout. It is also the lever that gets the customer to send the photos.

Rework

A flat fee for a second visit.

If the first visit failed for customer-side reasons, the second is chargeable and agreed in advance.

Referral

Refer, or contract directly, and keep a percentage.

When a partner is better placed to contract with the customer, a referral share keeps incentives clean.

Onboarding

Pilot one site, then five, then the rollout.

Each stage has an exit test. A failed test stops the rollout, not the relationship.

Onboarding paths

Three ways a partner joins.

PathWhenTypical clock
Standard agreement, as isMost partners1 to 14 days for small, 7 to 30 for large
RedlinePartner needs changesLegal review; case by case
Hybrid billingPartner wants to keep its own billingNeeds a written value case and sponsor approval

Also on this page

Related tools folded into this page. Each opens in place; tap Close when done.

When a Vendor Relationship Is FailingA short executive brief that turns a vendor complaint into a support-model decision, with options compared by impact, cost and risk.Open section

More in Partner Ecosystems & Performance

See all tools