How certifications land: uploads, photos, and email forwards

What this article covers

Certifications never get typed into a form one at a time. They land the same way every other data type lands in Verinode: you send a document (a PDF, a photo, or a forwarded email) and Verinode reads it, files it, and starts thinking about it. This article walks through the three practical paths a cert can take into Verinode, what happens in the seconds after you send one, and the credential "tips" Verinode writes the moment a new cert is recognized, before you've asked it a single question.

Where to find it

Open Certifications from the sidebar at iq.verinode.ai/certifications. Every page in Verinode has the same Add Data button in the top right of the header, this is the one entry point for getting a cert (or anything else) into the system. On Certifications specifically, it opens a modal titled "Send data to Certifications" so the file lands in the right bucket without you needing to say what it is.

The page itself is built from three rows: Take Action (decisions and tips), Explore (the metric tiles), and Most recent (every cert record as an individual tile). The rest of this article is about the pipe that feeds all three, not the rows themselves, but a few numbers from Explore are worth knowing since they come straight from the certs you send:

• All Certifications shows the total record count, split as "N team · N firm · N sub."
• Expiring in 30d counts certs whose expiry date falls within the next 30 days from today, and separately calls out how many are "already expired." Both counts are computed straight off each record's expiry date, not off any status label.
• Training Compliance is the share of your team certs that are active or expiring soon, out of all team certs on file. If you have zero team certs, this reads 100%.

The three ways a cert lands

Click Add Data anywhere on the Certifications page and a modal opens with a row of tabs: Drop files, Snap a photo, Paste it, Tell me, and Forward (that last one only appears once your operator has an intelligence email address configured). All five write to the same pipeline. For certifications specifically, three of them do almost all the work:

1. Upload a PDF ("Drop files")

Drag a file onto the dashed drop zone, or click it to browse, and choose a certificate PDF (IICRC WRT, ASD, AMRT, FSRT, an OSHA 10/30 card, an EPA RRP certificate, whatever your team or your subs hold). Verinode accepts PDF, images, CSV, Excel, Word, video, and audio through this same drop zone, so there's no separate "cert upload" screen to hunt for. There's also a "Send multiple at once" link below the drop zone for bulk cert dumps, useful right after onboarding a new hire or catching up a backlog of expiring credentials in one pass.

2. Photograph a cert card ("Snap a photo")

Switch to the Snap a photo tab (on a phone, this is the tab Verinode opens by default) and it prompts: "Snap a photo. Receipts, invoices, certs, equipment tags." This is the path for a physical wallet card, a laminated cert, or anything that only exists on paper. It works the same as a PDF upload underneath, the photo goes through the same document reader.

3. Forward the renewal or CEC email ("Forward")

Every operator has a dedicated intelligence email address. Open the Forward tab to copy it, or set up organization-wide auto-forwarding from the /connect page so IICRC renewal notices, CEC-completion certificates, and carrier cert-requirement emails route to Verinode automatically without anyone having to remember to forward anything. This is the path with the least friction: once forwarding is set up, a training provider's completion email lands, gets read, and files itself.

Two smaller paths exist too, in case a cert only exists as a description rather than a document: Paste it, for pasting the text of a renewal notice, and Tell me, for talking through a cert verbally (Verinode records, transcribes, and reads the transcript the same way it reads a document). Both are far less common for certifications than for other data types, but they run through the identical extraction and confidence logic described below.

What happens in the seconds after you send one

Once a document is recognized as a certification, Verinode works through a short pipeline before the record appears on your Certifications page:

1. 1Match the certification itself. Verinode reads the cert name off the document and matches it to Verinode's certification catalog (the reference list of IICRC, OSHA, EPA, and carrier-program credentials). A close name match is enough, it doesn't need to be an exact string.
2. 2Match the holder, if it's a team cert. For a credential that belongs to a person, Verinode tries to match the name on the document to someone already on your team roster. A confident name match assigns the cert straight to that person.
3. 3Decide who holds it. Every cert is filed under one of three buckets: a team member, your firm itself (a company-level credential like an IICRC Firm certification), or a subcontractor. The document tells Verinode which bucket it belongs in.
4. 4Check the expiry date. If the certificate's expiration date has already passed by the time it's ingested, the record is saved as expired no matter how confidently it was read.
5. 5Save it, and keep the source. The record is saved to your certification list, and the original file stays attached to it. If you forward the same renewal notice twice, or forward a training-completion email for a cert that's already on file, Verinode updates the existing record instead of creating a duplicate, so a re-sent document never inflates your cert count.
6. 6Log continuing-education credits, if any. If the document mentions CEC credits earned (a training-completion certificate, typically), those credits are logged against that person and that certification, and the running credit total on the cert record updates immediately. The same duplicate protection applies here: forwarding the same completion notice twice won't double-count the credits.

Reading confidence. Not every document reads perfectly, handwriting on a wallet card, a low-resolution photo, or a cert whose issuer isn't in the catalog can all lower how confident Verinode is in what it just extracted. A high-confidence read goes live right away, ready to show up across the credential radar the same way a clean PDF would. A lower-confidence read still saves (nothing is thrown away), but it also raises a flag asking you to double-check it, and if the confidence is quite low, Verinode adds a note explaining exactly what looked uncertain so you know what to verify rather than just being told "check this."

Unmatched holders. If Verinode can't confidently match a team cert to anyone on your roster (a nickname, a maiden name, someone not yet added as a team member), it still saves the cert rather than dropping it, and it raises a prompt asking you to assign it to the right person. Until you do, that credential doesn't count toward that person's coverage or your training compliance number.

The tips Verinode writes the moment a cert lands

This is the part that happens without you asking for anything. As soon as a new cert record is saved, Verinode looks at what just changed on your credential picture and, when there's something worth flagging, writes one or more tips straight into your Take Action row. You don't request these, they're generated at ingest time, the same moment the record is saved.

For a team member's cert, Verinode looks at three things: how many people on your team currently hold that same credential, which of your active service lines (water, mold, fire, biohazard) that credential is required for, and which carrier programs it unlocks. From that, it writes up to a few short, concrete tips, for example:

• A single-point-of-failure warning, when this person is the only one on your team holding a credential that's required for a service line you're actively running. The tip names the exposure plainly: if that one person is out, that line of work has no qualified coverage.
• A program-unlock note, when the credential you just added is one of the requirements for a carrier program (a name like Liberty Mutual Preferred or Travelers ASP), naming the program and what else, if anything, still needs to happen to use it.
• A peer-position note, when the credential is one that most operators at your scale already hold, so a fresh addition reads as catching up to table stakes rather than pulling ahead.

If a cert is already well-covered on your team and doesn't unlock anything new, Verinode doesn't manufacture a tip just to have one, nothing gets written.

For a firm-level cert (a credential your business holds rather than an individual), the tip is narrower and always about carrier-program eligibility: which programs this credential now unlocks, and whether a complementary cert you already hold multiplies that unlock (for example, holding both an IICRC Firm certification and an EPA RRP Firm certification together can open more programs than either alone). If the new firm cert doesn't unlock any program yet, no tip is written.

Where these tips show up. Look for them in the Take Action row on the Certifications home, and inside the cert's own record under the Open Tips section, which only appears when there's at least one open tip on that specific credential. Acting on a tip hands it to the specialist best suited to it: renewal timing and bench-depth tips route to a credentialing-focused conversation about training options and scheduling, while program-eligibility tips route to a conversation framed entirely around which carrier programs you now qualify for. Either way, Verinode surfaces the opportunity and the reasoning behind it, you decide whether and how to act.

Empty states

No certs on file yet. The hero at the top of the page reads "Add Data, certs land here as photos, screenshots, and uploads come in." The Take Action row shows a starter card, "Capture your team's credentials," with the prompt "Three quick moves and your first cert decisions surface within minutes," and three concrete steps:

• Upload IICRC + carrier-program cert PDFs, "WRT, ASD, AMRT, FSRT, any cert with a name + expiration date."
• Snap a photo of a cert card or training certificate, "Tap Add Data and pick Photo, works for OSHA 10/30, EPA RRP, BBP, anything."
• Forward IICRC renewal + CEC-completion emails, "Set up auto-forward so renewals never slip past the radar."

Underneath: "Renewal calendar, single-point-of-failure warnings, and carrier-program unlocks surface as certs land." The Most recent row, further down the page, reads simply: "Certifications will appear as you forward cert PDFs or capture credential photos."

Certs on file, but nothing currently open. Once you've worked through every open cert signal, the Take Action row switches to "All clear on your certifications," noting how many signals you've already resolved and that new renewals or program-gate changes will surface as the detector finds them.

Certs on file, detector still learning. If nothing has surfaced yet but you haven't resolved anything either, the row reads "Still learning your cert stack, as the detector analyzes renewals, team depth, and program-gate eligibility, top decisions will appear here."

Best-practice example

A crew lead completes a WRT renewal course and the training provider emails a completion certificate with CEC credits listed. If your inbox forwarding is set up, that email lands in Verinode automatically. Verinode reads it, matches "WRT" to the catalog, matches the crew lead's name to your roster, saves the renewed cert with the new expiry date, and logs the CEC credits against that person's running total, all without anyone touching Certifications that day. Because this crew lead was previously your only WRT holder covering water mitigation jobs, the single-point-of-failure tip that had been sitting in your Take Action row now clears on its own, since the renewal removed the immediate exposure, though it's worth checking whether a second holder is still worth training up for genuine redundancy.

Related articles

• Understanding your margin
• Benchmarks overview
• Reading a benchmark
• The decision workspace
• Clients and carriers
• Forwarding documents
• Connecting your data
• How benchmarks work

Data sources