The renewal radar: expiring and expired certs

What the renewal radar is

Every certification on file, whether it belongs to a team member, the firm itself, or a subcontractor, has one date that matters more than any other: when it expires. Verinode reads that date off every team, firm, and subcontractor certification record and projects it forward into a status, a color, and, where it matters, a call to action. That whole mechanism, the countdown from today to a cert's expiry date and everything it triggers along the way, is what this article calls the renewal radar.

Verinode does not renew anything for you and does not decide when a class gets booked. It reads the expiry dates you have on file, applies the same day-count math used across the platform, and surfaces what needs attention before it becomes a problem. You decide what to renew, when, and with which training vendor.

Where to find it

Open Certifications from the sidebar at iq.verinode.ai/certifications. The renewal radar isn't a single tab, it's a set of related numbers and controls that show up in four places on that page:

• The Expiring and Expired secondary metrics in the hero panel at the top of the page.
• The Expiring in 30d tile in the Explore row.
• The status label, colored dot, and due badge on every certification tile in Most Recent and in the All Certifications tab.
• The stance pill, subtitle, and Renew CTA on an individual certification's detail view.

For the hero panel's Active Certifications headline and program-coverage pill, see reading the certifications home screen. For the three underlying tables and how a raw row becomes a certification record in the first place, see team, firm, and subcontractor certifications. This article is about what happens once that record exists and has an expiry date on it.

Three separate clocks, not one

It helps to know up front that "expiring soon" is not computed one single way everywhere on the page. Three different pieces of logic look at the same expiry date and answer three different questions:

1. Is this cert inside the next 30 days? A flat, kind-agnostic cutoff that feeds the Expiring count in the hero and the Expiring in 30d Explore tile.
2. What color dot and status label does this record's tile show? A two-tier cutoff (60 days, then 14 days) applied the same way to team, firm, and sub certs, that decides whether a tile reads "Current," "Expires in Nd," or "Expired Nd ago," and whether its dot is green, amber, or red.
3. What stance is this record in, and what should I do about it? A per-kind set of cutoffs (they are not the same for team certs, firm certs, and sub certs) that drives the colored pill on the detail view, the one-sentence recommendation, and the Renew CTA.

The 90, 60, 30, and 14-day numbers you'll see referenced below all come from these three systems layered on top of each other, not from one universal countdown.

1. The 30-day count: Expiring and Expiring in 30d

The hero panel's Expiring metric and the Explore row's Expiring in 30d tile both count the same thing: every certification across team, firm, and subcontractor records whose expiry date falls within the next 30 days and hasn't passed yet. A cert expiring today counts. A cert that expired yesterday does not, it moves into Expired instead. This 30-day window doesn't distinguish between kinds and doesn't care whether the underlying stance treats that kind's renewal window as 30, 60, or 90 days, it's a flat, simple "is this due inside a month" tripwire meant to be glanced at, not analyzed.

What you see on the Expiring in 30d tile:

• The count itself as the headline value.
• Underneath, either "+N already expired" when there's at least one expired cert on file, or "Renewals on the radar" when nothing has lapsed yet.
• A row of dots previewing the split between certs needing attention and certs that are fine, colored red when any certs have already expired, amber when certs are approaching but none have lapsed.
• Clicking the tile opens the All Certifications tab already scrolled to the renewal-focused view.

When there is nothing expiring and nothing expired, the tile's accent switches from copper to green and the sub-line reads "Renewals on the radar," a calm state, not an empty one, since it can still show a nonzero Active Certifications count.

2. Status label and severity dot: the 60/14 display bands

Independent of the 30-day count above, every certification record (team, firm, or sub, the logic is identical across all three) carries a status label and a severity level computed straight from days-until-expiry:

• More than 60 days out: status reads "Current", severity is informational, dot renders green.
• 15 to 60 days out: status reads "Expires in Nd", severity is a warning, dot renders amber.
• 14 days or fewer, or already past expiry: status reads "Expires in Nd" (or "Expired Nd ago" once the date has passed), severity is critical, dot renders red.
• No expiry date on file at all: status reads "Active" with no severity flag, since there's nothing to count down from yet.

This is the same 60-day and 14-day split you'll see on any certification tile, in Most Recent, in the All Certifications list, and on the small colored dot next to a record's status text. A due badge rides alongside it on tiles: "Nd" when a cert is 60 days or fewer from expiry, or "Nd overdue" once it's past. Certs more than 60 days out show no due badge at all, there's nothing urgent enough to call out yet.

3. The stance engine: different lead times by kind

The detail view of a single certification goes further than a status label, it computes a stance, one of five postures that drives the colored pill at the top of the record, the one-line recommendation under the title, and whether a Renew CTA appears at all. This is where the 90 and 30-day numbers come from, and it's the one place the renewal radar's math genuinely differs by kind.

Team certs (IICRC disciplines, OSHA cards, and similar, held by a person on your crew):

• More than 60 days out: Current. No action needed, next renewal window opens automatically.
• 60 down to 15 days out: Expiring, "Renewal soon." Verinode's reasoning: renewal classes typically fill four to six weeks out, so a 60-day lead gives you a seat before the good dates go.
• 14 days or fewer, or the cert is the only one covering an active service line on your crew (see Single Point of Failure below), even if it's not yet inside 14 days: Exposed. Below 14 days the message is to book now because classes fill fast; when it's flagged purely for being the only holder, the message is to get a second person qualified.
• Already past expiry: Expired. The consequence line differs depending on whether the cert gates a service line you actively run: if it does, that service line is blocked until renewed; if it doesn't, the exposure is a carrier audit flag rather than a stopped crew.
• No expiry date recorded: Expiring with the label "No expiry set," a nudge to log the date so the 60/14-day reminders can start working at all.

Firm certs (IICRC Firm designations, state contractor licenses, and other business-level credentials):

• More than 90 days out: Current.
• 90 down to 31 days out: Expiring, "Renewal due." The longer lead time here (90 days versus a team cert's 60) reflects that most issuing bodies process a firm-level renewal in 30 to 45 days, and a firm cert often gates carrier-program eligibility for the whole business, not just one service line, so the stakes justify starting earlier.
• 30 days or fewer: Exposed, "Expiring imminent." If the cert gates a carrier program you're actively enrolled in, the recommendation names which program suspends the day it lapses.
• Already past expiry: Expired. Any carrier program this cert gates is already off-limits.
• No expiry date recorded: Expiring, "No expiry set."

Subcontractor certs (a sub's own credentials or insurance-style documents, verified or self-reported):

• More than 60 days out: Current.
• 60 down to 31 days out: Expiring, "Renewal due," queued so you can ask the sub without urgency.
• 30 days or fewer: Exposed, "Expiring imminent," a direct prompt to send the sub a renewal request.
• Already past expiry: Expired, a prompt to request an updated document, worded differently depending on whether the lapsed cert was ever verified in the first place.
• No expiry date recorded: Expiring, "No expiry set," a nudge to ask the sub for their current expiry date.

A fifth stance, Missing, is reserved in the model for a gate-required certification the operator doesn't hold at all (today scoped to firm certs, for example being enrolled in a carrier program that requires IICRC Firm without that credential on file anywhere). Because there's no underlying record to open when a cert is genuinely missing, this state doesn't yet render as a per-record pill, a missing required cert instead surfaces through the program-coverage pill on the hero and through Take Action findings, both covered in reading the certifications home screen.

Single point of failure (team certs only)

Team certs carry one more check that has nothing to do with the calendar: how many people on your active crew currently hold the same credential. If exactly one person holds a cert that gates an active service line you run (for instance, only one technician holds the WRT that unlocks your water-restoration work), that record jumps straight to Exposed even if its expiry is still months away, because the exposure isn't about the date, it's about having zero backup. The recommendation in that case is to get a second team member qualified, not to renew anything. Once a third holder is added anywhere on the team, the record's detail view notes "Deep bench. Rotation won't break coverage."

Reading the stance pill

On a certification's detail view, the pill next to the kind label (Team Cert, Firm Cert, Sub Cert) shows the current stance in plain language and in color:

| Pill | Meaning | Color | |---|---|---| | Current | Nothing needs attention | Deere green | | Expiring | Inside the renewal-planning window, not urgent yet | Hard Hat Yellow | | Exposed | Inside the tightest window, or single point of failure | Ember Red | | Expired | Past the expiry date | Ember Red (deeper) | | Missing | Gate-required cert not held (reserved, not yet surfacing per record) | Ember Red (dashed) |

These signal colors describe the certification's urgency, not the Verinode brand palette, the same Ember Red, Hard Hat Yellow, and Deere Green convention used across every section of the platform for Analyse, Maintain, and Expand-style postures.

The Renew-with-vendor CTA

On a team cert's detail view, once its days-to-expiry drops to 60 or fewer (the same window Expiring starts in), a Renewal CTA appears directly under the certification overview:

• If a training vendor is already set on that cert, the box reads "Renewal due" (or "Expired" if it's already past its date) and the button reads "Renew [cert name] with [vendor name]". Clicking it takes you to that vendor's page on Vendors so you can open the renewal conversation with the provider you already use.
• If no training vendor is set, the box explains that no vendor is on file yet for that member's cert and the button instead reads "Pick a training vendor for [cert name]", which opens Vendors filtered to training providers so you can choose one. Once you do, it's wired in for the next renewal automatically.

The box itself is colored rose when the cert is already overdue and amber when it's inside the window but not yet expired, matching the same severity logic used everywhere else on the page. This CTA only appears on team certs today; firm and subcontractor cert detail views don't carry the same vendor-linked button (a firm cert's renewal is closer to a firm-directly-with-issuer transaction, and a subcontractor cert's equivalent action is the Verification section's send-a-request flow, covered below).

On a subcontractor cert, the equivalent action isn't a vendor CTA, it's the Verification section: a button to send the sub a one-click upload link by email. Before anything is sent, it reads "Send verification request"; once sent, the confirmation reads "Sent, they'll get a one-click upload link by email." If the sub has already verified once, the button becomes "Re-send verification link", and sending it again confirms "Re-sent, they can replace the existing cert from the same link." Without an email address on the record, you're told to add one first.

How to use the renewal radar

1. 1Start at the hero panel. If Expired shows anything above zero, those certifications have already lapsed, work them first.
2. 2Check the Expiring in 30d tile next. Anything counted there is inside a flat 30-day window regardless of kind, click it to jump straight to the affected records in All Certifications.
3. 3Open a record whose dot is amber or red. Read the stance pill and the one-line recommendation under the title before doing anything else, it tells you exactly what's driving the urgency (calendar proximity, single point of failure, or a program-eligibility gate).
4. 4On a team cert inside 60 days, use the Renew CTA. If a vendor is already set, one click takes you to that renewal conversation. If not, pick one, it'll be remembered for next time.
5. 5On a subcontractor cert inside its window, send a verification request instead of chasing the sub by phone, the link does the collecting for you.

Empty states

• With no certifications on file at all, the hero's Expiring and Expired metrics both read 0, with sub-labels "Nothing Expiring Soon" and "All Certs Current". The Explore row's Expiring in 30d tile still renders, reading 0 with "Renewals on the radar" underneath.
• The Most Recent row, before any certifications exist, reads: "Certifications will appear as you forward cert PDFs or capture credential photos."
• The All Certifications tab, with nothing on file, reads: "No certifications on file yet. Upload a cert PDF via Add Data."

Certifications land through Add Data (forwarding a renewal notice or CEC-completion email, or uploading a photo of a cert card or a training-portal screenshot), see forwarding documents and connecting your data for the ingestion paths that feed every date the renewal radar reads.

Related reading

• Reading the certifications home screen for the Active Certifications headline and program-coverage pill that sit above the metrics covered here.
• Team, firm, and subcontractor certifications for the underlying data model, all three record types, and the full detail-view layout.
• Vendors overview for what the Renew CTA hands off to once you click through to a training vendor's page.
• Clients and carriers for how a firm cert's expiry connects to carrier and TPA program eligibility.
• The decision workspace for how a renewal or exposure surfaces as a Finding in Take Action.