The certification nobody noticed expired

A membership card does not stop working when a certification expires. No alarm sounds, no screen turns red, and the member who let it lapse is usually the last person to know. The gap between "expired" and "discovered" is where organizations get hurt.

Nothing happens on the expiry date

That is the whole problem. A lapsed certification is not an event. It is the absence of an event — a renewal that did not happen, on a date nobody was watching. The member keeps showing up. The schedule keeps assigning them. The roster still lists them under the role they have always held.

Then something makes it matter. An insurance audit. A mutual-aid request that asks who on your roster holds what. An incident review that works backwards through the duty roster. Suddenly the question is not "is this person qualified?" but "for how long have they not been, and who should have known?"

That second question is the expensive one. An expired credential is a renewal problem. An expired credential nobody tracked is a governance problem.

Why the spreadsheet always rots

Most organizations start with a list of certifications and expiry dates in a spreadsheet, maintained by whoever cared enough to start it. It works for about a year. Then:

• The maintainer changes. The person who built it moves, steps down, or simply stops. The file survives; the updating does not.
• Renewals arrive out of band. A member renews their card, mentions it at a meeting, and the spreadsheet is three screens away from that conversation. The fact exists and the record does not.
• Nobody reads a list of dates. A column of expiry dates is not a warning. It is raw material for a warning that someone has to remember to produce.
• The rules live somewhere else. The bylaws say a Full member holds a current certification. The spreadsheet says a date. Connecting the two is a judgment call made by a person, from memory, under time pressure.

The pattern is the same one that defeats volunteer hour tracking: the record depends on somebody doing extra work at exactly the wrong moment.

What a working system actually does

Four things, and they are less about reminders than about where the rules live.

Record the credential, not just the date. A certification is a thing with a number, an issuer, and an expiry — and a person holds several of them over the years, not one that gets overwritten. Keeping the history means you can answer "was this person certified last March?", which is the question an incident review actually asks. Overwriting means you can only answer "are they certified now?"

Let the membership type carry the requirement. The organization's rules already say which memberships require which credentials. Put that where the rule is enforced rather than in a document that describes it. Then "is this member in good standing?" is computed the same way for everyone, every time, instead of being decided by whoever is in the room.

Compute standing on a schedule, not on demand. If a certification lapsing should affect standing, it should affect standing on the day it lapses — not on the day somebody checks. Scheduled evaluation turns a silent gap into a dated, visible fact.

Warn before, not after. An expiry notice on the day of expiry is a report, not a warning. Thirty and sixty days out, to the member and to whoever manages the roster, is the difference between a renewal and a lapse.

One trap worth naming

There is a specific failure that looks like diligence: a requirement that names a credential the organization never actually defined. The bylaws say "current CPR certification", so somebody types a requirement called CPR — but no certification by that name exists in the system, so nobody holds it, so nothing satisfies it.

Every member of that type is now permanently out of standing, for a reason that reads like a bug, with nothing on any screen to fix. We have seen this one both ways round: a requirement typed before the certification existed, and a certification removed while a requirement still pointed at it. A system that lets you create either state will eventually produce a roster where everybody is failing and nobody knows why.

The fix is unglamorous: refuse the dangling requirement at the point someone tries to create it, and say which membership types are in the way before letting anyone remove a certification. Governance rules should be impossible to half-configure.

Track what the rules need, and nothing else

A last caution, the same one that applies to hours. A certification record exists to meet the organization's obligations — qualification, standing, insurance, mutual aid. It is not a personnel file. Record the credential, its number, its issuer, and its dates. Show members their own. Resist the urge to collect the scan of the card "just in case", because a filing cabinet of other people's identity documents is a liability you have volunteered for.