Partner certification is a personal qualification: the vendor certifies a named individual at a partner company after that person demonstrates a defined skill, usually by passing a test or an assessed practical. You certify a person; you accredit a company. A partner company's accreditation or partner program status rests on having certified individuals on staff, so when a certified person leaves the partner, the certification leaves with them, and the partner must certify someone else to retain any status that depends on it.
Certify the Person, Accredit the Company
The two words get used interchangeably, and they describe different mechanics. A certification attaches to an individual: this person passed this assessment on this product version on this date. An accreditation attaches to a company, and it is defined in terms of certified people: "employs at least two certified engineers", "keeps one certified seller per region".
The consequence shows up the day someone resigns. The certification travels with the person to their next employer. The partner's count of certified staff drops by one, and if that drops them below the accreditation threshold, the company status lapses until they certify a replacement. The partner never owned the certification; it only ever held people who did. This is the same logic the Preferred Partner Program applies: status sits with named, certified, active people at the partner, not with the logo on a contract.
What Certifications Gate
In a working program, individual certifications are the raw material that company-level entitlements are built from. Tier status typically requires a stated headcount of certified people per role, and the margin or discount attached to that tier moves with it. Co-sell eligibility can require a certified seller on the deal. Delivery rights are the strictest gate: only partners with certified delivery staff may implement the product, because a failed implementation lands on the vendor's brand, not the partner's.
Designing Certification That Means Something
Three properties separate a real certification from a completion badge. First, it tests an observable skill with a pass/fail outcome: configure the product, run the demo, scope the implementation. Watching videos is enablement, not certification. Second, it expires. Certify against a product version or a renewal window, so the credential stays a claim about current skill rather than past attendance. Third, track named individuals per partner. The roster of who is certified, at which partner, until when, is the dataset that tells you the moment a leaver puts a partner's accreditation at risk.
Related Guides
- Preferred Partner Program: How certified individuals underpin the earned Preferred tier and its annual recertification
- Partner Tiering: Setting certification headcounts as tier requirements per partner motion
- Partner Enablement: Building the training that gets people to the certification bar