Who it is for
- Professionals recording continuing development
- Managers reviewing CPD evidence
- Firms with different professional-body models
Continuing professional development
SkillProof helps teams record CPD activity, upload supporting evidence, review status and connect development records to appraisals or professional requirements.
14-day trial. No card. Use test data first.
This workflow is included from Growth. Advanced controls vary by plan. Compare plans.

Real SkillProof product workflow shown with safe demo data.
Development records
SkillProof keeps each CPD activity against the staff member who completed it, with the title, category, provider, completion date, hours, learning type, evidence status, reflection and review status where those fields are used. Managers can then review the record alongside appraisals, development actions and professional registrations without treating a CPD total as proof of compliance.
Plain-English answer
SkillProof provides CPD tracking and management records for activity, hours or categories, reflections, evidence, review status and development follow-up.
Individual CPD logs become reviewable records connected to evidence, appraisals and professional registrations.
SkillProof records development completed through any provider; it does not host or sell the learning course itself.
Choose the right workflow
The same workflow, with the live record and the next action kept in front of the team.
Before SkillProof
With SkillProof
Development records
Record CPD, appraisals and development actions against the right person, then review what has been completed and what needs attention.
Record CPD activity, category, date and notes.
Attach or mark evidence status for CPD records.
Link CPD to staff records and development actions where relevant.
Review manager or employee actions that need follow-up.

A real SkillProof product view shown with safe demo data. The exact records and controls available depend on the workflow and plan.
CPD can become a loose collection of notes, certificates and declarations unless it is linked to staff records and review actions.
Record learning activity, category, dates and evidence status.
Track whether CPD evidence is missing, uploaded or approved where used.
Follow up actions that come from CPD reviews or appraisals.
Give managers a clear view of the records and actions they need.
Hours are recorded without the context behind them.
A total alone does not show the learning type, provider, reflection, evidence or review status.
Evidence sits outside the CPD log.
Certificates and supporting files are harder to check when they are stored away from the activity.
Review actions disappear after the conversation.
Development actions can be missed when CPD, appraisals and follow-up notes live in separate documents.
Record the activity
Capture the title, category, provider, completion date, hours and learning type.
Connect the evidence
Mark whether evidence is required and keep the supporting file linked to the CPD record.
Review the learning
Use reflection, evidence and review status to show more than a running hours total.
Follow up development
Keep agreed actions visible alongside appraisals, registrations and the wider staff record.
Straight answers about the record, workflow and product boundary.
Yes, for recording CPD activities, categories, hours, reflections, evidence, review status and development actions. SkillProof does not award CPD credits or decide whether an activity meets a professional body's rules.
No. SkillProof records CPD activity and evidence; it does not award CPD credits or replace professional body requirements.
CPD records can track evidence status and supporting evidence where your workflow uses it.
CPD sits in the Development area alongside appraisal records and development actions so teams can review them together.
Open the next product workflow or guide when you need more detail.
Next step
Start with test data or book a walkthrough to see how the record, evidence and follow-up work together.
No card required. 14-day trial. Start with test data first.