Asks awaiting your response

What this section is

Your data feeds Verinode's benchmarks anonymously by default. Nobody at your franchisor, network, or association sees your name next to a number unless you say yes. Consent Requests is the inbox where those asks land: every time your network HQ wants to show your data by name, whether that's a leaderboard, a specific metric view, a case study, a deep drill-down, or a franchise disclosure cohort, it shows up here first, and nothing changes until you respond.

This article covers the Asks awaiting your response row, the tile-by-tile view of every request still open. For what happens once you click into one and approve, decline, or revoke, see the companion article on that flow.

Where to find it

Open Consent Requests from the sidebar at iq.verinode.ai/consent-requests. The page has three rows, top to bottom:

1. Hero, a count of what's pending right now and a 30-day resolution summary.
2. Asks awaiting your response, one tile per open request. This is the row this article covers.
3. Recently resolved, read-only history of what you approved or declined in the last 30 days.

The hero row, above the tiles

Before the pending tiles, a hero panel gives you the headline numbers:

• The eyebrow reads "From your network HQ," a reminder that every request in this inbox originates from your franchisor or network, never from Verinode itself.
• The big number is your current pending count, with a pill next to it: "Nothing pending" when it's zero, or "N pending" otherwise.
• The subtext does one of three things. With nothing pending and nothing resolved recently, it explains the whole feature: "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." With nothing pending but resolved history in the last 30 days, it reports how many: "N resolved in the last 30 days." With requests pending, it names how long the oldest one has been waiting ("Oldest pending asked N days ago") and repeats the default-visibility reminder.
• Three secondary figures underneath: Approved 30d (requests you said yes to in the last 30 days, subtext "You shared by name"), Declined 30d (requests you turned down, subtext "You declined"), and Pending kinds (how many distinct request types, like a leaderboard ask and a case-study ask, are sitting in your pending queue right now, subtext "Distinct request types").

Reading a pending tile

Each tile in Asks awaiting your response packs five pieces of information. Here is what each one is and where it comes from.

Kind and HQ group (the label line). The top line of every tile reads {request kind} · {group name}. The request kind is one of five, always shown in plain language, never as a raw code:

• Named leaderboard, HQ wants your name to appear next to your numbers on a leaderboard that is anonymous by default.
• Named view, HQ wants a specific metric tied to your name for a defined window, rather than anonymized.
• Case study, HQ wants to feature your data in a research publication or case study.
• Deep data, HQ wants drill-down access to underlying detail (for example, job-level records) for a defined scope.
• Item 19 cohort, HQ is assembling the Item 19 Financial Performance Representation for their Franchise Disclosure Document. This one works differently from the other four: approving adds your anonymized financial-period and jobs facts into the cohort's distribution. Your individual numbers are never disclosed on their own, only network-wide percentile bands (the same P10/P25/P50/P75/P90 percentile approach used across Verinode's benchmarks) get computed and published.

The group name is whichever HQ, franchise network, or association actually sent the ask. It always says which network is asking, so if you belong to more than one, you can tell them apart at a glance.

Metrics requested (the headline). The tile's headline line lists the metric keys attached to the request, up to two by name, with "+N more" appended if there are additional ones ("Net margin, Cash conversion, +2 more"). If the request didn't specify any particular metric, the headline reads "No metrics specified", which is normal for asks like a case study or a broader cohort invitation that aren't scoped to a single number.

Rationale (the sub line). Underneath the headline sits HQ's stated reason for the ask, whatever they entered when they sent it. If they didn't provide one, the tile reads "No rationale provided." This is HQ's own explanation, Verinode does not add or infer a reason on their behalf.

Asked and expires timing (the meta line). The bottom line of the tile reads Asked {relative time} · {expiry status}.

• The "Asked" side counts up from when the request was created: "today," "1 day ago," "N days ago" under 30 days, then "1 month ago" or "N months ago" beyond that.
• The expiry side counts down to the request's expiration, if it has one: "expires today," "expires tomorrow," "expires in N days" under 30 days, or "expires in N months" beyond that. A request with no expiry date reads "no expiry".

Every pending tile carries the same accent color (the Hard Hat Yellow "maintain" signal tone), since a pending ask is, by definition, something waiting on a decision rather than something urgent or already resolved.

Opening a tile to respond

Click anywhere on a pending tile to open the response window for that request. Inside, you'll see the full ask laid out: the group name and status at the top, a one-line plain description of what that request kind means (the same wording used in this article), then a detail list with whichever of these apply, cohort name and methodology version for an Item 19 ask, the metrics requested, the time window (start and end, or "any" and "open" where unbounded), when it was asked, and its expiry date. If HQ attached a rationale, it appears in its own labeled block, "HQ's rationale," below the details.

From there you have two buttons: Decline, with an optional text field to tell HQ why (sent back to them), and Approve, which flips the request to shared-by-name for the scope requested. Both actions close the window and refresh the page once they complete. If something goes wrong submitting your response, an error message appears in the window and nothing changes until you retry.

Once a request is approved, reopening its tile (now in Recently resolved) shows a Revoke approval button instead, with its own optional reason field. Revoking flips the request back to a closed, non-shared state immediately, HQ stops seeing your name from that point on. Declined, withdrawn, and expired requests are read-only when reopened: the window just confirms "This request is closed. No further action needed," along with your decline reason if you gave one.

The empty state

When there is nothing waiting on you, the Asks awaiting your response row shows this line in place of tiles:

"Nothing waiting on you. New asks land here when HQ wants to surface your data by name."

This is not a broken page. It means your franchisor or network hasn't sent any outstanding named-data requests. New tiles appear here automatically the moment HQ sends one, you don't need to check anything else or take any setup step to receive them.

Best-practice example

Say two tiles are sitting in Asks awaiting your response. The first reads "Named leaderboard · Northeast Restoration Group," headline "Net margin, Cash conversion," sub "We want to spotlight top-performing locations at the fall ownership meeting," meta "Asked 3 days ago · expires in 11 days." The second reads "Item 19 cohort · Northeast Restoration Group," headline "No metrics specified," sub "Preparing FY2026 FDD Item 19 filing," meta "Asked 1 month ago · expires in 2 months." The leaderboard ask is time-boxed and closer to expiry, so it's worth opening first: read the rationale, decide whether you want your net margin and cash conversion numbers named at the ownership meeting, and approve or decline with a reason. The Item 19 ask has more runway, but it only ever discloses anonymized, percentile-banded figures across the whole cohort, never your individual numbers, so it carries a different kind of decision than being named on a leaderboard.

Related reading

• Reading a benchmark
• Benchmarks overview
• How benchmarks work
• The decision workspace

Data sources