What Verinode Is Tracking (Vault Hero)

What it is

The Vault hero is the status band at the top of your Vault: one large number for how many documents Verinode has captured, a color-coded completeness pill beside it, a line of context underneath, and two smaller tiles to the right for Signals Fed and Needs Review. A single trust line sits along the bottom.

It is a read-only status display, not a control. There is nothing to click inside the hero itself except the two secondary tiles, each of which opens the matching tab below. Everything it shows comes from documents already sitting in your account and from what those documents have already done: it does not estimate, forecast, or invent activity to make the panel look busier than your account actually is. An account with no documents shows zero everywhere and a prompt to connect a channel, not a placeholder number.

Where to find it

In the sidebar, open My Data, then Vault. The route is /data. Older bookmarks or links to /invoices or /documents redirect straight through to /data: invoices, uploads, and every other document type live together in the Vault now, not in a separate Invoices page.

At the top right of the page header is an Add Data button (keyboard shortcut Cmd+U on Mac, Ctrl+U on Windows). It opens the capture modal, which accepts an upload, a photo, a pasted export, a voice note, or a forwarded email. Every document that comes in through any of those paths, or through a connected inbox, is what the hero panel counts. See Forwarding documents and Connecting your data for the channels themselves.

The headline number: documents captured

What it is. The large number on the left is your total document count, animated with a brief count-up when the page loads. Beside it reads "document captured" (singular, only when the count is exactly 1) or "documents captured" (every other count, including zero).

What you see. This counts every document Verinode has recorded for your account: invoices, estimates, certificates, financial statements, job exports, team rosters, and everything else the capture modal or a connected channel can bring in.

The Extraction Completeness pill

What it is. A small colored pill that appears next to the headline number, reading something like "78% Extraction Completeness." It only shows once you have at least one document and Verinode has been able to compute an average.

What it measures. This is not the AI's confidence in what it read. It is a coverage score: for each document, Verinode knows which fields it is capable of extracting for that document type (an invoice has different extractable fields than a certificate, for example), and the completeness score is the share of those fields it actually populated. A document where every expected field came through reads high. One where several expected fields came back empty, because the document was low quality, partial, or an unusual layout, reads low. The pill is the average of that score across your documents.

Color bands. The percentage is color-coded against three tiers:

• 80% and above, shown in green: most of what could be extracted, was.
• 40% up to 80%, shown in amber: a meaningful share of expected fields did not come through.
• Under 40%, shown in red: extraction is thin, and Verinode is working with a partial picture of those documents.

What is left out of the average. Only documents that carry an extraction receipt count toward this average. Documents processed before receipts were tracked are quietly excluded rather than dragging your completeness average down for something that predates the feature. If no document yet has a receipt, the pill does not appear at all, even if your document count is well above zero.

What to do. A low or amber pill is a prompt to look at document quality, not a scorecard. Open the Uploads tab (via the Explore row beneath the hero) and check which document types are landing incomplete: often it is a scan quality issue, a document type Verinode has limited experience with, or a format that omits a field outright. Improving the source document, not the Vault, is usually what moves this number.

The status line

What it is. One sentence directly under the headline number, describing the state of your vault right now. It changes based on what your documents actually need, in this order of priority:

1. No documents yet: "Connect a channel, email, uploads, voice, or photo, and your vault starts filling."
2. Documents need review (checked first, even if some are also still processing): "N document(s) need a quick review to unlock more signals."
3. Nothing needs review, but some are still processing: "N document(s) still processing, signals fire as soon as they land."
4. Everything is processed and matched: "Feeds every section of your business, vendors, clients, jobs, equipment, team, certifications, and more."

What "processing" means. A document moves from processing to processed once Verinode finishes parsing it. Until then it is counted, but has not yet contributed anything else on this page.

Why review is called out first. A document waiting on review is a document that is not yet feeding signals elsewhere in the platform. The status line puts that ahead of "still processing" because it is the one state where the fix is on you, not on Verinode's pipeline.

Signals Fed tile

What it is. The first of the two secondary tiles, on the right. It counts how many of your documents have triggered at least one signal, meaning at least one entry elsewhere in the platform's intelligence layer traces back to that specific document.

What you see. The count, with the sub-label "documents that triggered platform intelligence." When the count is above zero, the number is shown in green to mark it as a healthy outcome. Signals a document contributes to are what populate the Feed and, where relevant, your margin picture: this tile is the count of documents doing that work, not a count of the signals themselves (one document can trigger more than one).

What to do. If this number is small relative to your total document count, it is worth checking the Uploads tab for documents stuck in review or still processing, since those cannot yet contribute a signal.

Needs Review tile

What it is. The second secondary tile. It counts documents flagged as needing review: a document Verinode has tagged as belonging to a carrier, TPA, or job, but could not confidently link to an existing record already in your account. It sits waiting for you to confirm which one it belongs to.

What you see. The count, with the sub-label "entities to assign" when the count is above zero, or "all matched" when it is zero. A non-zero count is shown in red to flag that it is waiting on you.

What to do. Click the tile to open the Uploads tab and resolve the flagged documents by assigning each to the correct carrier, TPA, or job. Until that assignment happens, a document sits captured but cannot feed the sections (see Clients and carriers) that depend on knowing whose document it is.

The trust line

What it is. A single sentence along the bottom of the hero, beside a small lock-and-vault icon: "Your data is yours. Encrypted under a key scoped to you, never sold, and only our audited systems ever touch it." It is the short version of Verinode's data-trust commitment, present on this surface specifically because the Vault is where your raw source documents live.

Why it matters here. Verinode is an independent data trust, not a tool owned or operated on behalf of any carrier. Your documents, and everything Verinode reads out of them, are never sold to a carrier, and every automated read of your data happens to do the work you asked for.

Best-practice example

Say your Vault reads 128 documents captured, with an amber "62% Extraction Completeness" pill and a status line reading "3 documents need a quick review to unlock more signals." Work top to bottom: open the Uploads tab, resolve the 3 flagged documents first (each is one click to assign the right carrier or job), then check which document types are pulling the completeness average down. Once those documents are matched and re-scored, the Signals Fed tile should climb, since matched documents are the ones eligible to trigger a signal in the first place.