Skills Currency vs. Skills Completion: Why "Trained" and "Current" Aren't the Same Word

A commercial pilot can hold a 737 type rating and not be legally allowed to fly a 737 today. Type rating says she's trained on the aircraft. Currency says she's flown three takeoffs and landings in the last 90 days. The first is permanent. The second decays. Aviation built its safety architecture around the difference fifty years ago and would never confuse the two.

Medicine has the same distinction. Board certification proves the surgeon was once qualified. Active practice — case volume, procedural recency, hospital privileges renewal — proves they're currently competent. The cardiac surgeon who hasn't operated in two years isn't "trained but rusty." She's specifically not current. Hospitals enforce the distinction in credentialing committees. Insurance carriers enforce it in coverage decisions. Patients enforce it the moment they ask "how many of these have you done in the last year."

Engineering, nuclear operations, defense, regulated chemistry — every domain where the cost of mistaking trained for current is paid in incidents has built around the difference for decades.

HR, until recently, hasn't.

Where the Conflation Comes From

The default HR architecture treats training as a one-time event. The LMS records completion. The HRIS stores certifications. The skills field, when it exists, gets populated at the moment training finishes and then never updates. Six months later, the system still says the employee can do the thing, and there's nothing inside the system that knows otherwise.

This is fine when the underlying skill is genuinely stable — basic literacy, compliance training people are going to forget but won't need to act on for years. It's not fine when the skill is operational and decays. A welder qualified on a specific weld type six years ago and hasn't done it since is treated by the system the same as one who welded a hundred joints last month. The audit signs off on both because the system can't tell them apart.

The cost shows up in three places.

Workforce visibility lies upward. Leadership pulls a report on "how many people are qualified to do X" and gets a number that includes everyone trained at any point. The actual operational depth — the number of people currently performing or capable of performing X today — is some unknown fraction of that. Workforce planning runs on the inflated number.

Compliance findings persist. ISO, FDA, FAA, NRC — every regulated framework that touches workforce competency draws the distinction between qualification and current competence. Auditors find it in the same place every cycle: the company has trained records but can't prove currency. The finding gets a CAPA. The CAPA promises a process. The process doesn't fix the data architecture. The finding recurs next cycle.

Strategic capability gets mismeasured. When a CHRO sits in a board meeting and reports on workforce capability, the numbers are functionally inflated by everyone who was trained on something they haven't done since. The capability that actually exists is a smaller, more honest number — and the leaders who learn to operate from that number make better workforce bets than the ones who learn to operate from the optimistic version.

What Currency Means as a Skills Primitive

Currency isn't a binary. It's a structured property of a skill that captures three dimensions:

• Recency. When was this skill last assessed, performed, or refreshed? A skill last assessed three years ago has a different operational meaning than one assessed last quarter.
• Decay rate. How fast does this specific skill lose currency in the absence of practice? Compliance knowledge decays slowly. Specialized procedural skills decay fast. Tool-specific software skills decay in proportion to how much the tool itself has changed.
• Re-currency conditions. What does it take to restore currency? Sometimes assessment alone. Sometimes practice plus assessment. Sometimes a structured retraining and a supervised session.

A skills system that treats currency as a first-class property — with decay rates configured per skill, recency tracking attached to every qualification, and re-currency conditions defined for each one — produces a different operational picture than the default LMS-plus-HRIS architecture. The workforce-capability report stops being "everyone who's ever been trained on this." It becomes "everyone who is currently qualified, plus the ones approaching expiry, plus the ones who've lapsed and would need to re-cert."

That's a different number. It's also the number the operation actually runs on.

How Currency Changes the Decisions

A few decisions shift when the system can tell trained from current.

Staffing. Resource managers staffing a project don't pull from "everyone trained on X." They pull from "everyone currently qualified on X, in the right time zone, available 50%+ next month." The shortlist is smaller and more accurate. The match is operational, not theoretical.

Workforce planning. Capacity models stop being inflated by people who hold lapsed qualifications. Hiring decisions get sharper because the gap is real. Retention decisions get sharper because the cost of losing a currently-qualified employee is visible — that person is rare, not interchangeable with anyone who once attended the training module.

Compliance. The audit answer stops being a retrospective excavation and becomes a current-state query. "Show me everyone currently qualified against revision 4 of SOP-12, with assessment evidence in the last 12 months." The system either has it or it doesn't, and the answer is the same whether the auditor asks today or six months from now.

Career development. The conversation with the employee changes too. "You're trained on X but your currency has lapsed; here's the path to restore it" is a real growth conversation. "You're trained on X" with no currency framing is a record-keeping artifact that doesn't help anyone develop.

What This Requires Architecturally

Currency-aware skills tracking isn't a feature bolted on top of a completion-tracking system. It's a different data model. Each skill carries decay-rate metadata. Each assessment carries a timestamp the system can age. Each qualification carries expiry conditions configurable by the operation, not assumed by the vendor. The audit log tracks currency events — when someone moved from current to lapsed, when they re-acquired currency, when the underlying SOP revised and re-currency became required.

This is the architectural reason why a certification tracking system built on completion records will never produce the answers regulated industries actually need. The data model assumes the wrong primitive. Completion is a moment; currency is a state that has to be maintained.

Talent development decisions, frontline training decisions, and workforce strategy decisions all eventually run into the same wall: you can't manage what you can't currently see. Currency is what makes the visibility honest.

What the Bar Should Look Like

Aviation built its safety record on the discipline of distinguishing trained from current. Medicine built its credentialing systems on the same discipline. Engineering, nuclear, and defense the same.

HR has the chance to import a fifty-year-old idea from industries where the cost of getting it wrong is measured in lives. The companies that adopt currency as a first-class skills primitive will run their workforce off honest numbers. The ones that don't will keep reporting capability they can't actually operate on, and learning the gap the hard way every audit cycle.

The fix isn't more training. It's a system that knows when training has expired.

Frequently Asked Questions

What's the practical difference between a "trained" employee and a "current" employee?

A trained employee has, at some point, met the qualification standard for a skill or competency. A current employee meets the standard today, with recent enough assessment or practice to demonstrate continued capability. Aviation captures the difference in pilot certification and recency requirements; medicine captures it in board certification versus active practice. The same distinction matters in any operational context where skills decay between use — manufacturing operations, regulated chemistry, specialized engineering, software practice on changing tools.

Why does this matter more in 2026 than it did five years ago?

Two things shifted. First, regulators across multiple industries (FDA medical device, FAA, NRC, ISO 13485) have sharpened expectations around competence currency — auditors now ask the recency question explicitly rather than accepting historical completion records. Second, workforce planning has moved from headcount to capability, and capability is materially overstated when lapsed qualifications get counted as current. Both forces push toward systems that track currency natively.

Does this require running assessments more often?

Sometimes, but not always. Currency is configurable per skill — some skills decay slowly enough that annual assessment is sufficient; some require quarterly or monthly verification depending on regulatory framework or operational risk. The shift isn't "assess everyone, more often." It's "assess each skill on a cycle that matches its actual decay characteristics, and let the system maintain the currency state."

How does a certification tracking system handle currency differently than a training tracking system?

A training tracking system records completion: the employee went through the training, and the record stands forever. A currency-aware certification tracking system records the same completion but layers expiry rules, re-certification triggers, and decay-rate metadata on top. When the certification approaches expiry, the system flags it. When the underlying SOP revises, the system flags affected qualifications. The currency state — not just the completion record — is what the operation runs against.

What's the first step for a company that wants to adopt currency-based skills tracking?

Inventory the skills where decay actually matters. For most companies, this is a tractable subset of the full skills catalog — high-decay skills in regulated environments, tool-specific skills where the tool changes, procedural skills tied to revision-controlled documents. Define decay rates and re-currency conditions for that subset first; expand from there. Trying to retrofit currency across the entire skills catalog at once is what stalls the initiative. Starting with the 20% of skills where currency actually drives decisions delivers the operational value in a single cycle.