Brand-protection audit trail

What it is

The brand-protection audit trail is the panel at the bottom of the Compliance page that answers one question in a form you can hand to a lawyer: for this franchisee, what compliance actions happened, and when. It is a per-franchisee timeline of certification events, audits, training completions, and incidents, built specifically to hold up if a brand-liability dispute ever lands on your desk.

The scenario it exists for: a franchisee causes a brand incident, and the franchisor needs the defensive narrative. "This location was certified on this date, completed this training on that date, passed its last audit at this score, and network-wide compliance stood at this rate." That narrative only holds up if the underlying record was captured continuously and cannot be edited after the fact. The audit trail is built that way: the events feeding it are appended, never edited or deleted from the application layer. If a past event needs correcting, a new event is filed to record the correction rather than the original row being changed, so the history stays intact.

The privacy boundary is the other half of what makes this trustworthy. HQ does not read a franchisee's job files, invoices, or customer records to build this timeline. It reads a nightly rollup of compliance-relevant events only, meaning certification issued or expired, an audit scheduled or completed, training finished or gone overdue, an incident or policy violation recorded. Nothing about a specific job, a specific customer, or a specific team member's file crosses into this view. That is the same privacy boundary that governs the rest of Verinode HQ: franchisees own their operating data, HQ sees compliance status and aggregates, never the underlying records.

Where to find it

Open Compliance from the HQ sidebar at hq.verinode.ai/brand-compliance. The audit trail is not one of the tile rows near the top of the page, it is a flat panel that flows below the entire row stack. Scroll past, in order: the Brand health composite hero, Standards & Audits, Safety Incidents, Cert Coverage, Critical Gaps, Compliance (the per-franchisee worst-cert row), Reputation Watch, and Top Reputation. The audit trail is the last thing on the page.

It has no card frame around it. In keeping with the rest of the platform's visual language, it flows directly on the page background with a plain heading, a one-paragraph explainer, and a list of events separated by hairline dividers, the same way every non-tile surface in Verinode reads.

A shorter version of the same data also appears on mobile HQ, at mhq.verinode.ai/brand-compliance (or the Verinode HQ mobile app), as the Audit log section near the bottom of the Brand Compliance rollup screen, described below.

What the header line tells you

At the top of the panel, the heading reads Brand-protection audit trail. Below it, a fixed explainer:

"Per-franchisee compliance timeline: cert events, audits, training, incidents. Defensible for litigation. Aggregated nightly from the operator-side audit log. HQ never reads per-job records, only compliance events."

When at least one franchisee has events in the current pull, a sentence is appended: "Covering N franchisees" (singular "franchisee" when N is 1). This count is not your network's total franchisee count, it is the number of distinct franchisees represented in the current window of recent events, described below. A franchisee with no recent compliance activity, even one who is fully compliant, may simply not appear if their most recent event has aged out of the window.

How the timeline is organized

Events are grouped into one block per franchisee. Within a block, events are sorted with the most recent first. Across blocks, the franchisee whose most recent event is itself the most recent sits at the top of the panel, so the freshest activity in the whole network reads first.

Each franchisee block shows:

• The franchisee's name, in uppercase small text, as the block's headline.
• An event count beside it, in the form "· N events" (or "· 1 event").
• A list of events, each row showing:

- A small copper dot marker. - The event label as the main line, a plain-language description of what happened (for example a certification renewal, a passed audit with its score, a completed training). This is written by the nightly aggregation job from the underlying action, not typed by hand. - A second line in small capitalized text showing the event's raw category code, taken directly from the compliance event's type (for example values like CERT.RENEWED, AUDIT.COMPLETED, TRAINING.OVERDUE, or INCIDENT.RECORDED). This is the compliance category the event was filed under, it is not a separate description, treat it as a tag rather than a headline. - The date the event occurred, right-aligned, in month, day, year format.

Up to 12 franchisee blocks are shown, and each block shows up to 8 of its most recent events. If a franchisee has more events in the pulled window than that, a line appears under their list reading "+N earlier events retained in the log" (with "event" or "events" matched to the count). That phrasing is deliberate: those events are not deleted or hidden from the record, they are simply not rendered on this page. Nothing in the audit trail is ever discarded by scrolling it off the visible list.

The franchisee-name privacy gate

Whether a franchisee's real name appears in this trail, or an anonymized label instead, follows the same entity-model setting that governs every per-franchisee surface on the platform. Networks made up of independently owned franchise locations default to showing an anonymized label built from the franchisee's own account, never a name you'd have to look up. Networks that are same-entity, multi-location operations under one owner, see the real location name throughout, because there is no separate business to protect. This is a network-wide setting an HQ admin controls, not something you toggle per page or per article.

There is no separate franchisee-count threshold gating this specific panel the way some other per-franchisee rollups on the platform suppress rows in very small networks. The audit trail's only privacy control is the name-display setting above, applied consistently with the rest of the page.

Where the data comes from

Nothing in this panel is typed in directly. Every row traces back to a nightly aggregation job that runs across the whole platform (the same job that refreshes every other HQ rollup). Once a night, for every group, it:

1. Reads the operator-side action log for compliance-relevant activity, filtered to a fixed set of category prefixes: certification events, general compliance events, audits, training, incidents, and policy violations. Anything outside that list, meaning ordinary job, invoice, or customer activity, is never touched by this job and never reaches HQ.
2. Converts each qualifying action into one plain-language event label and files it under the franchisee it belongs to.
3. Writes the result into the compliance rollup table that this page (and the mobile Audit log) reads from. HQ pages never query the operator-side action log directly, they only ever read this rollup, which is the mechanism behind the "HQ never reads per-job records" line in the header, it is enforced by which table the page is allowed to query, not just a stated policy.
4. Skips any action it has already ingested on a prior run, so re-running the nightly job never duplicates an event that is already on file.

Because the feed refreshes once a night, a compliance action a franchisee takes today will typically show up in the audit trail the next day, not immediately.

On mobile

The mobile HQ Brand Compliance screen surfaces the same underlying feed under an Audit log section, with the caption "Recent compliance events." It is not grouped by franchisee, instead it is a single flat list of up to 10 of the network's most recent events, each row showing the event's plain-language label as the title and, on the line below, the franchisee's name and the date together. The category code shown on desktop (CERT.RENEWED and similar) is not displayed on mobile. A summary tile elsewhere on the same mobile screen reads "Audit Events" with the count of events in the current pull and how many franchisees ("offices") they span, the mobile equivalent of the "Covering N franchisees" line on desktop.

How to use it

1. 1Open Compliance from the sidebar and scroll to the bottom of the page, past the tile rows, to reach the audit trail panel.
2. 2Scan the franchisee blocks top to bottom. The freshest activity in the network sits at the top.
3. 3Read a franchisee's block as a chronological file: certifications, audits, training, and incidents in the order they happened, most recent first.
4. 4If you are pulling together the record for a specific dispute or a board update, treat the on-page view as a recent-activity check, not the full record, and ask an admin for the complete per-franchisee history when you need everything on file rather than just what fits on the page.
5. 5Cross-check anything concerning here against the Compliance row and Cert Coverage row further up the same page, which show current standing rather than a history of events.

Empty state

If no compliance events have been ingested yet for your network, the panel reads:

"No compliance events recorded yet. The audit trail populates as franchisees take compliance actions (cert renewals, training completions, audits), the daily cron pulls these from the operator-side audit log without crossing the per-job data boundary."

This is not a broken page. It means the nightly aggregation job has not yet had a qualifying compliance action to ingest for any franchisee in your network, either because the network is new or because no franchisee has logged a certification, audit, training, or incident event since onboarding. As franchisees take these actions on their side of the platform, the trail begins to populate automatically, with no HQ-side setup required.

Related reading

• Compliance overview: the full Compliance page this panel sits at the bottom of, including the brand health composite, Cert Coverage, and Safety Incidents.
• Compliance by franchisee (worst-cert view): the row above the audit trail that shows current certification standing per franchisee, rather than a history of events.
• Brand health composite: the hero score at the top of the Compliance page that blends compliance, safety, and reputation into one number.
• Standards & audits: the process standards, forms, and audit programs the network runs, which is where many of the audit events in this trail originate.
• Programs: how brand-standard and training programs are published to the network, feeding the training-completion events in this trail.
• Network health: the network-wide orientation view this page's compliance signal feeds into.