A CPD ledger you can trust.

cpd.so gives your regulator a real-time, identity-bound record of every CPD hour earned by the professionals you license. No more pdf shoeboxes at renewal. No more re-typing hours into your registry.

What we record

• Who — the professional, bound to your registry identifier via a Connect flow they initiate.
• What— the course title, provider, accredited hours, and the regulator scheme it's mapped to.
• When — issue date, with the underlying activity dates and assessment score.
• Proof — every certificate has a public verification code, so any third party can confirm it in seconds.

How the integration works

cpd.so ships with an adapter framework. Each regulator gets a named adapter that maps cpd hours into your scheme's terminology and pushes them on a cadence you choose — daily, weekly, or on demand. Two integration shapes are supported:

• Push API — cpd.so calls a secure endpoint you publish; we send identity-bound ledger entries; you persist them in your registry. Standard JSON; HMAC signed.
• Read-only dashboard— if you don't want to host an endpoint, your staff log in to a regulator dashboard on cpd.so and see hours filtered to your registry.

What you get

• An auditable record of every accredited course your professionals attended.
• Identity-bound entries — no name collisions, no impostor hours.
• Audit log of every event: enrolment, completion, cert issued, sync attempt.
• Hours scoped by your scheme — required hours, cycle length, mapping rules — all configurable per regulator.

What we don't do

We don't set your licensing rules, decide who passes renewal, or store your registry data. Your registry is the source of truth; cpd.so is the verified inflow of hours.