Co-Branding CPD Certificates: Training Delivered Under Someone Else's Banner

A co-branded CPD certificate carries two names: yours as the issuing provider, and the client's or partner's as the organisation the training was delivered for or under. It exists because training relationships are rarely simple, and a certificate that names only one party often misdescribes what actually happened.

When co-branding is the right answer

Delivering under a client's banner. You are a freelance trainer or a small training business contracted to run a programme for a larger organisation. The client wants their name on the certificate, because it is their programme and their learners. You designed and delivered it, and the credential is issued by you.

Joint programmes. Two organisations run a course together, both having contributed to the content and both with a stake in the credential. A single-branded certificate would give one of them the whole of the credit.

White-label training. You develop a course that another organisation delivers as its own. Learners know it as their programme, so the certificate carries their brand, while the credentialing infrastructure remains yours.

Charitable and funded training. A charity delivers training on behalf of a funder, a grant body or a commissioning organisation. Naming the funder reflects the real relationship and often satisfies a reporting requirement at the same time.

What a co-branded certificate shows

It carries your name as the issuing Open CPD provider, since you are the party who signed the declaration and holds the membership, alongside the client's or partner's name and branding. Both are visible. The verification link points to your provider profile, because you are the legitimate issuing authority.

That makes the credential chain readable at a glance: who delivered the training, who the partner was, and how to check the certificate. It also removes an awkward conversation about whose logo takes priority, because both names are there and the issuing relationship is stated rather than implied.

How it works in practice

Co-branding is part of the ordinary certificate workflow rather than a separate feature to switch on. When you set up a course that will be delivered in partnership or under a client's name, you include the co-branding details in the course configuration. Certificates issued against that course carry both names automatically.

You remain the issuing provider throughout. Your OCPD Provider ID, your declaration and your membership are the accountability layer behind every certificate, co-branded or not. The co-branding describes the training relationship. The verification describes who is answerable for it.

What it means for the learner

The certificate reflects what the learner actually experienced. If they attended a programme run by one organisation and delivered by another, the certificate says so. That context is useful to the learner describing the training later, to an employer checking it, and to a professional body reviewer working out what the training was and who stood behind it.

Verification is unaffected. The achievement page shows the full credential detail including the co-branding context, the digital badge carries the same information, and anyone can check it without an account. Nothing about co-branding weakens the credential.

Available on every plan

Co-branded certificates are available on all Open CPD plans, with no tier that restricts them. Whether you issue occasionally for a single client arrangement or run several co-branded programmes at once, the option is there. Plans and current prices are on the pricing page, and the wider structure is set out in how it works.