The Vault: your HQ document library

What the Vault is

The Vault is HQ's read-only library of the generated reports your network has produced: Discovery Day Packs, quarterly reviews, compliance audits, and member cohort reports. Every document in it is a finished PDF (with a matching XLSX export where one exists), stamped with the period it covers and a link back to the network data it was built from.

The Vault does not create anything itself. It is an index and archive of reports that have already been generated elsewhere (most commonly from the Discovery Day builder). Think of it as the filing cabinet, not the printer.

Because it sits inside Verinode HQ, everything in the Vault is built from aggregates across your network, cohort counts, rollups, and compliance summaries. It is never a window into one member's private day-to-day business data. Members own their own data; HQ sees the network-level picture.

Where to find it

• HQ sidebar: look for "Vault."
• Direct URL: hq.verinode.ai/vault

Anyone with HQ access can open the Vault and read what's in it. The "Generate report" action in the top right is admin-only; non-admin HQ users see the same library without that button.

Layout, top to bottom

The page has three parts, stacked in this order:

1. A summary panel at the top showing how many documents exist in total and what's been added recently.
2. A set of horizontal rows, "Recent" first, then one row per document type.
3. An "Access trail" list below the rows, showing who has opened which document and when.

The summary panel

At the top of the page you'll see a large count of Generated documents, the total number of reports in your library.

Next to it is a status pill:

• "X new 30d" if any documents were generated in the last 30 days.
• "Library current" if you have documents but none in the last 30 days.
• "Nothing yet" if the library is empty.

Below the count, a line of text summarizes the mix, for example: "3 Discovery Day Packs · 2 quarterly reviews · last generated 4 days ago." If the library is empty, the text instead explains what will show up here: "Generated reports land here as Discovery Day Packs, quarterly reviews, compliance audits, and member cohorts ship. PDFs are stored with their period and a link back to the network data they cite."

Three smaller figures sit alongside the main count:

| Figure | What it counts | |---|---| | Discovery Day Packs | Item-19-style outputs | | Quarterly reviews | Board-ready snapshots | | Compliance audits | Audit + cohort artifacts |

The rows

Below the summary panel, documents are organized into horizontal scrolling rows. Each row is a different slice of the same library, not a different data source, so a document only ever appears once across the rows it belongs to (once in "Recent" if it's new enough, and once in its type row).

Recent. The 12 most recently generated documents across every type, newest first. If nothing has been generated yet, this row reads: "No documents generated yet. Use the Generate button to run a Discovery Day Pack or open the Discovery Day surface for the full builder."

Discovery Day Packs. Item-19-style outputs used for prospective-franchisee discovery meetings. Empty state: "No Discovery Day Packs generated yet. Item-19-style outputs land here once Discovery Day generation runs."

Quarterly reviews. Board-ready performance snapshots for the period. Empty state: "No quarterly reviews yet."

Compliance audits. Audit and cohort artifacts tied to compliance review cycles. Empty state: "No compliance audits yet."

Member cohort reports. Reports built around a defined cohort of members (for example, a comparison group used in a review). Empty state: "No member-cohort reports yet."

Reading a document tile

Each tile in every row shows the same four pieces of information:

• Type label: Discovery Day Pack, Quarterly review, Compliance audit, or Member cohort, color-accented by type.
• Period: the reporting period, shown as a from/to range (year and month) when the report covers a defined period, or the generation date when it doesn't.
• Availability line: "PDF + XLSX available" when both exports are ready, or "Generation incomplete" if the PDF hasn't finished generating yet.
• Generated timestamp: a relative label such as "today," "1 day ago," "6 days ago," or "2 months ago."

Click any tile to open its document. If a PDF export exists it opens that; if only the XLSX export exists, that opens instead. Documents open in a new tab so you don't lose your place in the Vault.

Generating a new report

If you're an HQ admin, a "Generate report →" button sits at the top right of the page. It takes you to the Discovery Day builder, where reports are actually produced. The Vault itself is a library and index; it doesn't have a report-creation flow of its own.

1. 1From the Vault, click Generate report → (admin only).
2. 2Build and run the report from the Discovery Day builder.
3. 3Once generation finishes, return to the Vault. The new document appears in Recent and in its type row, and the summary panel's count and "new 30d" pill update to reflect it.

Access trail

Below the document rows, a separate section titled Access trail lists recent pulls from every HQ document route, not just the Vault. Its purpose is compliance: a defensible record of who opened which document and when, without exposing any member's private business data.

Each row shows:

• What was pulled: labeled by kind: Item 19 pack, Discovery Day pack, Recruitment deck, Board slide, or Counsel-review link (signed).
• Who pulled it: the HQ colleague's name, or "Outside counsel" for a signed counsel-review link opened outside of a logged-in HQ session. Depending on how your network is set up, some pulls are attributed by name and others show a neutral label instead.
• A reference line describing which document: for example a section name, a cohort reference, a fiscal-year and quarter combination, a franchisee count, or a methodology version, whichever applies to that document. If none of those apply, this shows a dash.
• A timestamp for when it was accessed.

The access trail shows the most recent pulls (up to the last 30). If nothing has been pulled yet, it reads: "No document pulls recorded yet. The first download from any HQ document route lands here." Directly under the section heading, the Vault explains its purpose in plain terms: "Every HQ document pull lands here. Defensible for compliance review without crossing the operator-data boundary."

The privacy posture

That boundary shapes what you'll find in every document type:

• Discovery Day Packs present network-level performance for prospective-franchisee discovery, not any one member's day-to-day figures.
• Quarterly reviews and compliance audits summarize the network as a whole or a defined cohort within it, using counts, rates, and rollups.
• Member cohort reports compare groups of members against each other in aggregate; they don't expose one member's numbers to another.

If you need to review something at the level of an individual member's account, that's a conversation to have directly with that member. The Vault, and Verinode HQ generally, is built to keep it that way by design, not by convention.

Empty states, at a glance

| Section | What you'll see with nothing in it | |---|---| | Summary panel | Pill reads "Nothing yet"; explanatory text about what will land here | | Recent | Prompt to use Generate or open the Discovery Day builder | | Discovery Day Packs | "No Discovery Day Packs generated yet…" | | Quarterly reviews | "No quarterly reviews yet." | | Compliance audits | "No compliance audits yet." | | Member cohort reports | "No member-cohort reports yet." | | Access trail | "No document pulls recorded yet…" |

An empty Vault is normal for a network that hasn't run its first Discovery Day generation or quarterly cycle yet. Nothing here needs to be "set up," documents simply appear as your network generates them.

Related help

• Reading the generated-documents summary
• Recent documents and opening a report
• Quarterly network reviews
• Compliance audit documents
• Member cohort reports
• The document access trail
• What HQ sees: the network privacy boundary