Data completeness: what's missing and what each upload unlocks

Verinode can only surface intelligence from data it actually has. If you have never uploaded a job cost export, Verinode cannot show you true margin, it estimates instead. If you have never uploade…

6 min read·Updated July 13, 2026
On this page

What the completeness view shows

Verinode can only surface intelligence from data it actually has. If you have never uploaded a job cost export, Verinode cannot show you true margin, it estimates instead. If you have never uploaded a TPA scorecard, Verinode cannot benchmark your KPI standing against your own network history. The completeness view is where Verinode tells you this plainly: which categories of data it already has from you, which are partial, which are missing entirely, and, for each gap, the one thing you can upload and the intelligence that upload unlocks.

This is not a nag screen. It is a map. Six categories, each with a plain-language reason to close it.

Where to find it

Open Vault from the sidebar, under My Data (My Data → Vault, at iq.verinode.ai/data). Vault is where every document you upload or forward lands, gets read, and gets matched to a vendor, client, carrier, or job. The completeness view sits alongside Vault's other panels as the section that answers one question: out of everything Verinode could know about your business, what does it actually have yet?

If you have an old link to /documents, it still works, that route now redirects straight to /data. Documents was the section's original name; Vault is the current one.

Note

Vault also shows an Extraction Completeness pill on its hero panel, and a Completeness column on the Tracking tab. Those are a different number: they measure, document by document, how many of the fields on an already-uploaded document Verinode successfully read (its own internal extraction accuracy, not your data coverage). The completeness view this article covers measures something upstream of that: whether you have handed Verinode a given category of data at all. A document can score 95% on extraction and your Certifications category can still read Missing, because extraction quality and category coverage are two separate questions.

Reading the summary bar

At the top, Overall completeness shows a single percentage, bold and color-coded: green at 80% and above, amber from 50 to 79%, red below 50%. It is not a weighted or gated score, it is simply the share of the six categories below that currently read Complete. A thin progress bar underneath fills to match, in the same color. Below the bar, a caption spells out the math in words: "X of 6 categories complete."

That percentage moves only when a category's status changes, not when you add more documents to a category that is already Complete. Six green checks is 100%, five is 83%, and so on.

The six categories

Below the summary bar is a list, one row per category. Each row starts with a small colored badge: a green check (✓) for Complete, an amber exclamation mark (!) for Partial, and a red X (✗) for Missing. Next to the category name, a number shows your current count, either as "current/target" when Verinode has a specific target for that category, or as a plain count when it does not. Rows that are not yet Complete carry two more lines: the upload hint (what to bring) and, in bold copper, what that upload unlocks.

Here is what each of the six actually checks:

Jobs. Counts every job record in your Vault. Missing at zero, Complete as soon as you have one. There is no target and no partial state, this is the on/off switch for whether Verinode has any picture of your job book at all. Upload hint: "Import a CSV from your job management system or forward assignment emails." Unlocks: revenue tracking, payment velocity, job-level intelligence, the entire base layer everything else in Verinode is built on.

Job Costs. Counts your job cost records, separate from the jobs themselves. Also binary: Missing at zero, Complete the moment one cost record exists. Upload hint: "Upload a QuickBooks, Xero, or PowerBI cost export." Unlocks: true margin calculation. Until this category is Complete, the margin figures you see elsewhere in Verinode are estimated from industry patterns, not calculated from your own costs, which is exactly the gap this upload closes.

Scorecards. Counts TPA and carrier scorecard documents you have uploaded. Unlike Jobs and Job Costs, this one has a real target: one scorecard for every TPA client you currently have marked active (with a floor of one, so it still shows a sensible target even before you have added any active TPA clients). Fewer scorecards than active TPA clients reads Partial; zero reads Missing; matching or exceeding your active TPA count reads Complete. Upload hint: "Upload TPA scorecard PDFs (Contractor Connection, Alacrity, etc.)." Unlocks: KPI benchmarking, tier tracking, rank protection signals, the data Verinode needs to tell you where you stand inside a given TPA network and to flag when a slipping metric puts your tier at risk.

Certifications. Counts uploaded certification documents (IICRC, WRT, ASD, and similar). No visible target column, but the status logic underneath expects a small handful on file before it calls the category settled: zero reads Missing, a partial handful reads Partial, and a fuller set reads Complete. Upload hint: "Upload IICRC, WRT, ASD, or other certification documents." Unlocks: compliance monitoring, expiry alerts, TPA eligibility checks, so Verinode can warn you before a certification lapses and flag when a missing credential could cost you eligibility on a network.

Insurance COI. Counts uploaded certificates of insurance. Binary like Jobs and Job Costs: Missing at zero, Complete as soon as one is on file. Upload hint: "Upload your certificate of insurance." Unlocks: insurance expiry alerts and compliance risk signals, so a lapsing COI shows up as a warning instead of a surprise.

Vendor Invoices. Counts uploaded or forwarded vendor invoices. Zero reads Missing, a handful reads Partial, and a fuller run of invoices reads Complete, on the same logic as Scorecards and Certifications: Verinode wants enough invoices on file to see a real pattern, not just one data point. Upload hint: "Forward vendor invoices or upload invoice PDFs." Unlocks: vendor spend tracking, price benchmarking, renewal optimization, the data behind knowing whether a given vendor's pricing is in line with what your peers pay.

Tip

Notice the shape of the unlocks. Jobs and Job Costs unlock your own numbers (revenue, true margin). Scorecards, Certifications, and Vendor Invoices unlock comparative intelligence (benchmarking, eligibility, pricing). If your priority is closing the gap between estimated and true margin, start with Job Costs. If your priority is knowing where you stand against peers, Scorecards and Vendor Invoices matter more.

Uploading from the view

Any row that is not Complete carries an Upload → button on the right. Clicking it opens the upload flow for that specific category, so a click on the Certifications row takes you straight to certification upload rather than a generic drop zone you then have to sort through. Complete rows do not show the button, the hint, or the unlocks line, since there is nothing left to close for that category.

Verinode reads the count for every category directly from your Vault the moment you open this view. There is no separate sync step and no manual refresh: upload a certification, come back to the completeness view, and the Certifications row reflects it.

Empty states and edge cases

There is no dedicated "no data at all" screen for the completeness view itself, because a brand-new account is simply six red rows and a 0% summary bar. That is the intended first read: it tells a new operator, at a glance, exactly what to bring in first and what each thing is worth. As you upload, rows flip from red to amber to green one at a time, and the summary percentage climbs with them.

If Verinode cannot reach your Vault data for a moment (a transient fetch error), the view shows no categories rather than an error message. It resolves itself on the next successful read, no action needed on your part.

Was this helpful?