How to Track Professional Development Credits

Somewhere in a three-year renewal cycle, most certified professionals hit the same moment: the portal says 31 credits reported, your memory says you have done far more than that, and you cannot say where the difference went. Tracking — not earning — is where renewal cycles quietly go wrong. A webinar attended in month four of a 36-month cycle is easy to complete and easy to forget.

The fix is a small system with three parts: a single log you own, the provider's official portal, and an evidence folder that backs both. Set it up once and updating it costs about two minutes per activity.

This guide covers the record-keeping only. What credits are and how cycles, categories and caps work is explained in How Continuing Education Credits Work; ideas for actually accumulating units, including free options, live in How to Earn Continuing Education Units.

Know the number you are tracking toward

A tracker is only useful against a target, so anchor yours to your programme's requirement. As of 2026, the headline figures for the major bodies: PMI certifications such as the Project Management Professional (PMP) require 60 Professional Development Units (PDUs) per three-year cycle (the Certified Associate in Project Management, CAPM, needs 15); ISC2's Certified Information Systems Security Professional (CISSP) requires 120 Continuing Professional Education (CPE) credits per three-year cycle; ISACA's Certified Information Systems Auditor (CISA) requires 120 CPE hours per cycle with a minimum of 20 per year, reported annually by 31 December; CompTIA lists 20 Continuing Education Units (CEUs) for A+ and 50 for Security+ over three years; Cisco accepts 30 CE credits for CCNA-level renewal and 80 at CCNP level. Requirements change, so confirm your own count on your provider's maintenance page.

Two of those details matter specifically for tracking. ISACA's annual minimum means a CISA tracker needs a per-year subtotal, not just a cycle total. And PMI caps some categories (Giving Back PDUs) while setting minimums for others (Education PDUs across the Talent Triangle), so a PMP tracker should record category, not just quantity — otherwise you can hit 60 on paper and still fall short. The naming differences themselves — CEU, CPE, PDU — are just branding, as CEUs vs PDUs vs CPEs explains.

The three-layer tracking system

Layer 1: your own log

Own your master record; treat the provider's portal as a copy. A spreadsheet is entirely sufficient. Give it these columns:

1. Date completed
2. Activity — course title, event name, book, volunteering role
3. Provider/organiser
4. Credits claimed and category (Education vs Giving Back for PMI; the relevant group or domain for ISC2/ISACA)
5. Evidence — a link or filename pointing at the certificate, confirmation email or attendance record
6. Reported? — the date you entered it in the provider's portal
7. Running total (plus a per-year subtotal where an annual minimum applies)

Column 6 is the one most people omit and most people need. The gap between "done" and "reported" is exactly where credits evaporate.

If you hold multiple credentials, add a column per credential rather than a sheet per credential — many activities count toward several programmes at once, and a single row with two credit columns captures that without double-entry. Coordinating deadlines across several certifications is its own discipline, covered in How to Keep Your Professional Certifications Current.

Layer 2: the provider's portal

Every major programme has an official reporting system — PMI's Continuing Certification Requirements System (CCRS) is the best-known example; CompTIA, ISC2 and ISACA each have their own submission process on their sites. Report activities as you complete them rather than batching at cycle end: portals occasionally reject or query an entry, and you want that conversation in month six, not the week before expiry.

The portal is authoritative for one thing only: what the certification body believes you have reported. It is not your evidence store, and a submitted entry is not proof the activity happened. Which brings us to layer three.

Layer 3: the evidence folder

For every row in the log, a file in a backed-up personal cloud folder: the completion certificate, registration confirmation, or attendance email, saved the day the activity finishes. Name files so they sort and match the log — 2026-03-14_risk-webinar_2PDU.pdf beats certificate(7).pdf. Keep evidence for at least a full cycle after you use it, since renewal submissions can be audited retrospectively. Why that matters, and the wider habit of audit-proofing every claim you make to a certification body, is the subject of How to Prepare for a Certification Audit — here it is enough to say: no evidence file, no logged credit.

The two-minute habit that makes it work

Systems fail at the capture step, not the design step. The workable habit is a single rule: an activity is not finished until it is logged. Close the webinar tab, then — before anything else — add the row, drop the certificate into the folder, and report it in the portal if you have five minutes. Done immediately, the whole chain takes two or three minutes. Done in December for a year's worth of activities, it takes an evening of detective work through old emails.

Support the habit with two calendar entries: a recurring quarterly reminder to reconcile log against portal (totals should match; investigate any gap), and a milestone check at each third of your cycle. For a 60-PDU PMP cycle, that means roughly 20 banked per year — if the twelve-month check shows eight, you have found the problem with two years to fix it rather than two weeks.