Quick answer
Associations update candidate handbooks, exam guides, eligibility policies, renewal forms, standards and continuing-education documents on a cycle — and many of those files have almost identical names while belonging to completely different credentials.
That is exactly what a batch with a review step is for.
Replace the pages that mean “the current one”. Publish new items when an edition of a standard or handbook needs to stay available in its own right. And leave the member access rules alone.
What certification programs publish
Candidate handbooks, application packs, exam guides, eligibility criteria, renewal handbooks, continuing-education policy, codes of ethics, standards documents, specialty requirements, recertification forms.
One association often runs several credential programs, each with its own version of all of those.
The program is what identifies the file
Consider:
- Candidate Handbook — Credential A
- Candidate Handbook — Credential B
- Candidate Handbook — Advanced Level
- Candidate Handbook — Specialty Track
A file called candidate-handbook-final.pdf tells you nothing about which of those it is. The credential has to be part of the match, or you will publish the Advanced handbook to Credential B and nobody will notice for a month.
Current, or an edition?
Current. The certification page says “Current Candidate Handbook”. Once the new version is approved, replace the file.
Edition-specific. A standards library lists the 2024, 2025 and 2026 Standards separately. Those stay separate — the year is the identity, not filename clutter.
How the annual cycle runs
The exam cycle changes, candidate materials are revised, application forms change, renewal requirements change, the program pages need the new files, and the previous standards stay archived.
A batch handles the mechanical part. The editorial rules stay yours.
Member-only and public
Some certification resources are public. Others are only for members, candidates, certificants or committees.
WP Bulk Replace does not decide any of that. Because the document stays where it is, whatever does decide carries on working.
Example: a four-credential refresh
An association receives:
- 4 candidate handbooks
- 4 application packs
- 4 renewal guides
- 2 revised standards
- 3 new specialty documents.
A safe run: upload the 17, map each to its credential, check the ambiguous acronyms, decide whether the standards replace or become new editions, mark the 3 new ones as new, replace the current documents, publish the new editions separately, and check candidate and member access.
The shorthand everyone uses
Associations have their own abbreviations: CPC for Certified Program Coordinator, CE for continuing education, Recert for recertification.
Teaching those once takes most of the guesswork out of next cycle. They stay specific to your association, because the same three letters mean something else at the one down the road.
What this does not decide
Certification policy, exam eligibility, standards approval, effective dates, retention requirements.
The plugin puts approved files in the right place after all of that is settled.
Exam windows
Certification documents often take effect for a specific exam cycle.
Publishing the right handbook for the wrong cycle confuses candidates even though the file mapping was technically perfect. Where timing matters, the cycle needs to be recorded alongside the document rather than inferred.
Policies shared across programs
One ethics policy or renewal policy may cover several credentials.
That shared use is usually deliberate. Before replacing it, confirm every program using it is moving to the new version at the same time — because all of them will.
Links in candidate communications
Handbook and application links are embedded in confirmation emails, candidate portals and prep-course materials.
Keeping those links stable means far less communication content to rewrite each cycle.
Check the version inside the file
Certification documents usually carry their own cycle information.
After replacing, open one and confirm the exam year, the handbook version, the effective date and the program name.
That catches the case where the filename matched perfectly and the document inside is the wrong approved edition.
Forms and standards behave differently
Application forms are usually rolling current documents.
Standards are usually versioned publications.
That is a good default expectation to start from, though your association’s own policy is what decides.
When it goes wrong, it goes wrong loudly
A wrong certification document produces support tickets within hours.
A clear batch result and a working undo let staff fix it in minutes rather than restoring unrelated parts of the website.
Summary
Certification content suits a batch because the files recur, look alike, and belong to specific programs.
The order that matters: which credential, which document, current or a specific edition, and which page it belongs on.
That keeps candidate resources current without erasing the standards history.
Related: Association document updates · Policy documents · Employee handbook updates