What CPD is and why it matters
Continuing professional development, or CPD, is the ongoing, deliberate process of maintaining and extending the knowledge, skills and judgment needed to practice competently in computing. It is not limited to formal training courses. CPD covers any activity that builds capability relevant to your role, from reading a technical standard to leading a project retrospective, provided the learning is identified, undertaken and reflected upon with intent rather than absorbed incidentally.
Technology changes faster than most professional fields. Programming languages, security threats, cloud platforms and regulatory obligations shift within a few years, sometimes months. A credential earned a decade ago says little about a practitioner's current capability unless it is backed by evidence of sustained learning. CPD is the discipline that keeps a qualification meaningful over time, and it is a hallmark of professions that hold themselves accountable to the public they serve.
For ACS members, CPD is also a matter of trust. Employers, clients and the public rely on ACS registration as a signal that a member's skills are current, not just historically certified. A structured CPD habit protects that signal, protects the member's own employability, and protects the profession's standing as a whole.
Why ACS requires CPD for registered members
ACS registration categories, including the Certified Computing Professional (CCP) and the senior grades of membership, carry an ongoing obligation to maintain competence rather than a one-time test to pass. This mirrors the approach taken by established American professions such as engineering, where state boards set continuing education requirements for PE licensure, and accounting, where CPAs must complete continuing professional education to retain their license.
Requiring CPD protects three groups at once. It protects members, whose market value depends on staying current in a field where skills decay quickly. It protects employers and clients, who need assurance that an ACS-registered professional can be trusted with systems that affect safety, privacy and financial integrity. And it protects the profession collectively, since a single high-profile failure by an under-skilled practitioner damages the credibility of every member who holds the same designation.
ACS does not prescribe a single syllabus, because computing roles are too varied for one curriculum to fit a network engineer, a data scientist and a software architect equally well. Instead the requirement is procedural: identify a development need, undertake a relevant activity, and record what changed as a result.
The 30-hour annual guideline
ACS asks registered members to complete a minimum of 30 hours of CPD activity each membership year, in line with the norms used by comparable computing bodies internationally. This is a floor, not a target to hit exactly and stop. Members whose roles are changing rapidly, who are moving into management, or who are pursuing a new certification will typically exceed it substantially.
The 30 hours need not come from a single source. A realistic annual mix might include a short certification course, attendance at two or three conference sessions or webinars, structured reading of a new standard or framework, mentoring a junior colleague, and self-study following a project post-mortem. What counts is that each activity is logged with a date, a stated purpose and a note on the outcome.
Plan hours across the year rather than compressing them into a pre-audit scramble. A quarterly review — roughly seven to eight hours per quarter — produces better-quality learning and a more credible record, and gives time to adjust the plan if a role changes mid-year.
Planning, doing and recording
Effective CPD follows a simple cycle: plan, act, record, reflect. Planning starts with an honest skills gap analysis, ideally benchmarked against a recognized framework such as SFIA or the NIST NICE Workforce Framework for Cybersecurity, so that development effort targets an actual deficit rather than the most convenient course on offer. A one-page annual development plan keeps this focused.
Recording should happen as activities are completed, not reconstructed from memory later. Each entry should note the date, the activity, the time spent, the learning objective it addressed and, critically, a short reflection on what changed in your practice as a result. A course attended but never applied is weak evidence of development; a course followed by a specific change in how you approach your work is strong evidence.
Members can maintain this record in any format that is consistent and retrievable — a spreadsheet, a learning platform export, or the ACS CPD log template. What matters at audit is that the record is contemporaneous, specific and tied to demonstrable outcomes rather than generic statements such as 'attended training'.
Types of activity that count
ACS recognizes a broad range of CPD activity because competence is built in many ways, not only in classrooms. The common thread is that the activity is purposeful and produces a traceable improvement in knowledge, skill or judgment relevant to your professional practice.
- Formal training and certification study — vendor courses (AWS, Microsoft, Google Cloud), ACS certification preparation, or accredited university modules
- Conferences and webinars — technical sessions, standards-body briefings, and ACS chapter or specialist group events
- Structured reading — new standards, RFCs, whitepapers and peer-reviewed research applied directly to current work
- On-the-job learning — leading a new type of project, adopting an unfamiliar toolchain, or working through a significant incident post-mortem
- Teaching and mentoring — preparing training material, mentoring junior staff or supervising interns, which reinforces your own understanding
- Professional contribution — writing technical articles, reviewing conference papers, contributing to open source, or serving on a standards committee
- Committee and volunteer work — serving on an ACS chapter board or working group, building governance and leadership skills alongside technical ones
Audit and evidence
ACS operates a sample-based CPD audit of registered members each year rather than reviewing every record annually. Members selected for audit submit their CPD log along with supporting evidence for a subset of listed activities. This balances member workload against the credibility of the scheme.
Acceptable evidence varies by activity but should be independently verifiable where possible: certificates of completion, conference registrations, minutes showing committee attendance, published articles or commit histories, or a short statement from a supervisor or mentee for informal learning. Retain evidence for at least the current and prior membership year.
Members who fall short of the guideline are not treated punitively on a first occurrence; ACS requires a remediation plan and a follow-up review within a defined period. Repeated failure to engage with CPD can affect registration status, since it undermines the basis on which the credential is granted. The intent of audit is to keep the scheme honest, not to catch members out.