Reading the consent hero: pending, approved, declined

What Consent Requests is

Verinode's benchmarks work because every operator's data is anonymized by default. Your numbers feed the network's peer medians and percentiles, but no one outside Verinode sees your business tied to your name. Your network HQ (your franchisor or association) sometimes wants more than an anonymous data point: naming you on a leaderboard, featuring your numbers in a case study, or including you by name in a specific view. Verinode never grants that on HQ's behalf. Every one of those asks becomes a consent request that lands in your Consent Requests inbox, and nothing changes about how your data is shown until you approve it.

Consent Requests is a queue you manage, not a settings toggle buried in account preferences. It has its own hero panel, its own pending list, and its own history, because a decision to be named in front of your peer network deserves the same visibility as any other decision on the platform.

Where to find it

Open Consent Requests from the sidebar. The route is iq.verinode.ai/consent-requests. The page opens directly on the hero panel described below, with two rows underneath it: asks awaiting your response, and recently resolved requests.

The hero panel

The hero panel is the first thing you see on the page. It has three parts: an eyebrow, a headline number with a pill, and a supporting line, plus three secondary stats laid out to the right.

Eyebrow: "From your network HQ"

This small uppercase label sits above the headline number. It is a reminder of where every request on this page originates: your network HQ, never Verinode itself and never a carrier. Verinode is the independent data trust that holds your data; it does not initiate these asks.

Headline: the pending count

The large number in the hero is your pending count, the number of consent requests currently awaiting your response. It counts every request from your network with a status of pending, nothing else. Approved, declined, withdrawn, and expired requests are not part of this number.

The pill and its tone

Beside the headline sits a pill that mirrors the count and shifts color depending on how many requests are waiting:

• 0 pending: the pill reads "Nothing pending" and renders in the green Expand tone.
• 1 pending: the pill reads "1 pending" and renders in the yellow Maintain tone.
• 2 or more pending: the pill reads "N pending" and renders in the red Analyse tone.

The tone is not a judgment about the requests themselves. It is a simple visual cue that more waiting asks means more attention needed, the same escalation logic Verinode uses on signal tiles elsewhere on the platform.

The oldest-pending line

Directly under the headline, the supporting line tells you how long the longest-waiting request has been sitting in your queue. When you have at least one pending request, it reads:

"Oldest pending asked [X] ago. Default visibility stays anonymous-aggregate until you respond."

The "[X] ago" phrasing is relative: "today," "1 day ago," a day count under a month ("14 days ago"), or a month count once it passes 30 days ("2 months ago"). Verinode finds the oldest pending request by created date, not by expiry date, so this line always points you at the ask that has been waiting longest, not the one closest to lapsing.

The second sentence is a standing reminder: nothing about your visibility changes by default. Your data stays anonymous-aggregate in every benchmark and every leaderboard until you explicitly approve a specific ask.

When nothing is pending

If your pending count is zero, the supporting line changes to reflect what has happened recently instead of what's waiting:

• If you also have no resolved requests in the last 30 days, it reads: "Your franchisor will ask here when they want to surface your data by name on a leaderboard, deep-dive into a metric, or feature you in a case study. Default visibility stays anonymous-aggregate until you approve."
• If you have resolved requests in the last 30 days but nothing currently pending, it reads: "N resolved in the last 30 days," where N is your 30-day resolved count.

The three 30-day stats

To the right of the headline, three secondary numbers give you a 30-day rearview on how the queue has been moving:

• Approved 30d: how many requests you approved in the last 30 days. The sub-label under it reads "You shared by name."
• Declined 30d: how many requests you declined in the last 30 days. The sub-label reads "You declined."
• Pending kinds: not a 30-day figure, this counts the number of distinct request kinds currently sitting in your pending queue right now (for example, if you have two pending named-leaderboard asks and one case-study ask, this reads 2, not 3). The sub-label reads "Distinct request types."

All three counts are simple integers with a count-up animation on load. None of them expose which HQ member sent the request or reference any specific peer-operator counts, only your own response history and your own pending queue.

The request kinds you may see

Every consent request on Verinode falls into one of five kinds. You'll see these as labels on the tiles in both rows below the hero:

| Kind | What it means | |---|---| | Named leaderboard | HQ wants to show your name next to your ranking on a leaderboard, instead of an anonymous position. | | Named view | HQ wants to reference your business by name in a specific view or report. | | Case study | HQ wants to feature your results in a written case study. | | Deep data | HQ is asking for a deeper look into specific metrics than the standard anonymized aggregate provides. | | Item 19 cohort | HQ wants to include you, by name, in a franchise disclosure document (FDD) Item 19 financial performance cohort. |

The two rows under the hero

Asks awaiting your response

This row lists every pending request as a tile. Each tile shows the request kind and the requesting group's name, the specific metrics involved (up to two, with a "+N more" count if there are others), the rationale HQ gave for the ask (or "No rationale provided" if none was given), and when it was asked plus when it expires (or "no expiry" if none was set). Clicking a tile opens a response window where you can approve or decline; approving may let you narrow the scope of what you're sharing rather than agreeing to the full ask as written.

Empty state, verbatim: "Nothing waiting on you. New asks land here when HQ wants to surface your data by name."

Recently resolved

This row lists your last 12 resolved requests (approved, declined, withdrawn, or expired) from the trailing 30 days, each tile showing the kind, the resolved status, the requesting group, the rationale (truncated), and when it was approved or declined.

Empty state, verbatim: "No resolved requests in the last 30 days."

How to use this page

1. 1Check the hero pill first. If it's red (2 or more pending) or yellow (1 pending), something is waiting on you.
2. 2Read the oldest-pending line to see how long the longest-waiting ask has sat, then open the "Asks awaiting your response" row.
3. 3Click any pending tile to read the full rationale and metrics, then approve (with or without narrowing scope) or decline from the response window.
4. 4Use the Approved 30d and Declined 30d stats as a quick gut-check on how often you've been saying yes versus no. If Declined 30d is climbing, it may be worth a direct conversation with HQ about why a given kind of ask doesn't fit your business.

Related reading: Reading a benchmark, Benchmarks overview, How benchmarks work, The decision workspace.

Data sources