Recently resolved requests

What this section is

Every time your network HQ (your franchisor or association) wants to show your data by name instead of anonymously, whether that's a leaderboard, a case study, a specific metric view, a deep-data drill-down, or an Item 19 franchise disclosure cohort, the ask lands in your Consent Requests inbox first. Recently resolved is the third and last row on that page: a read-only record of every one of those asks that has already been settled, one way or another, in the last 30 days.

Nothing on this row is waiting on you. A request only appears here once it has an outcome, approved, declined, withdrawn, or expired, so this row exists to answer one question: what happened recently, not what's happening now. For the queue of requests still waiting on your decision, see Asks awaiting your response. For the headline numbers above both rows, see Reading the consent hero.

Where to find it

Open Consent Requests from the sidebar. The route is iq.verinode.ai/consent-requests. The page stacks three rows top to bottom: the hero panel, Asks awaiting your response, then Recently resolved at the bottom. Recently resolved is the row this article covers.

What counts as "recently resolved"

A request shows up in this row once its status is anything other than pending, meaning approved, declined, withdrawn, or expired, and it was last updated within the trailing 30 days. That window is measured from when the request's record was last touched, which in practice means the day it was resolved (approved, declined, or withdrawn) or the day it expired, not the day HQ originally sent it. A request asked two months ago that you approved yesterday still shows up here today; a request you approved six weeks ago has aged out, even though the approval itself still stands and still governs your visibility.

The row shows at most 12 tiles, your 12 most recently created resolved requests. If more than 12 have resolved in the last 30 days, the oldest of that batch simply don't get a tile, though the Approved 30d and Declined 30d counts in the hero panel still reflect the full 30-day totals, not just the 12 shown here.

Reading a resolved tile

Each tile packs the same four lines as a pending tile, but every field reflects an outcome instead of an open question.

Kind and outcome (the label line). The top line reads {request kind} · {outcome}, for example "Named leaderboard · Approved" or "Deep data · Declined." The request kind is always one of the five plain-language labels used throughout Consent Requests:

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

The outcome word is one of Approved, Declined, Withdrawn, or Expired, always capitalized, never the raw underlying status code.

Requesting group (the headline). The tile's headline is the name of the HQ, franchise network, or association that sent the ask. If you belong to more than one network, this is how you tell their requests apart at a glance.

Rationale (the sub line), truncated. Below the headline, the sub line shows the first 80 characters of whatever rationale HQ gave when they sent the request. If HQ didn't provide a rationale, this line is simply blank. Unlike the pending row, a resolved tile does not fill in a "No rationale provided" placeholder here, an empty sub line on a resolved tile just means none was given at the time.

When it resolved (the meta line). The bottom line tells you when the outcome happened, and the wording depends on the status:

• Approved, with an approval timestamp on record: "Approved [X] ago."
• Declined, with a decline timestamp on record: "Declined [X] ago."
• Withdrawn or Expired, or an approved/declined request missing its own timestamp: "Updated [X] ago," measured from when the request was originally created rather than from a dedicated withdrawal or expiry date, since neither of those has its own timestamp field. In practice this means a withdrawn or expired tile's "Updated" line points back to when HQ first asked, not the day it lapsed.

The "[X] ago" phrasing itself is relative: "today," "1 day ago," a day count under a month ("18 days ago"), then a month count once it passes 30 days ("1 month ago," "2 months ago").

Status accents, at a glance

Each tile carries a thin accent color tied to its outcome, so you can scan the row without reading every label:

• Approved tiles carry the green Expand signal accent, the same tone Verinode uses elsewhere for a favorable position.
• Declined tiles carry the red Analyse signal accent, the same tone used for something that needs attention elsewhere on the platform. Here it simply marks that you said no, not that anything is wrong.
• Withdrawn and Expired tiles both carry a neutral, muted accent, since neither reflects a decision you made, HQ pulled the ask back, or nobody acted before the deadline passed.

The accent is a fast visual sort, not a judgment. A row of mostly green tiles just means you've been saying yes more often; a neutral-accented expired tile usually means the ask simply wasn't a priority before its window closed.

Clicking into a resolved tile

Clicking a resolved tile opens the same detail window used everywhere in Consent Requests, but what you can do inside it depends on the outcome:

• Approved requests reopen with a Revoke approval button and an 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 reopen read-only. The window confirms "This request is closed. No further action needed," along with your decline reason if you gave one when you declined it.

Either way, opening a resolved tile is a safe way to double check exactly what you agreed to (or turned down) before it drops off this row in 30 days.

The empty state

When nothing has resolved in the last 30 days, the row shows this line in place of tiles, verbatim:

"No resolved requests in the last 30 days."

This is not a sign anything is broken. It means either your network HQ hasn't sent any consent requests recently, or every request you've received is still sitting in Asks awaiting your response. If you're new to a network, or your franchisor hasn't run a leaderboard, case study, or Item 19 cycle recently, an empty Recently resolved row is the normal state.

Best-practice example

Say Recently resolved shows three tiles: "Named leaderboard · Approved" for Northeast Restoration Group, meta "Approved 6 days ago"; "Deep data · Declined" for the same group, meta "Declined 19 days ago"; and "Case study · Expired" for a different network, meta "Updated 1 month ago." Reading left to right tells a quick story without opening anything: you agreed to be named on a leaderboard recently, you turned down a deep-data drill-down a few weeks back, and a case-study ask from a different network lapsed without anyone acting on it. If you want to revisit the leaderboard approval, click it and use Revoke approval. If you're curious why you declined the deep-data ask, click it to reread your reason. The expired case-study tile is read-only, since nobody, HQ included, acted before its window closed.

Related reading

• Asks awaiting your response
• Reading the consent hero
• Reading a benchmark
• Benchmarks overview
• How benchmarks work
• The decision workspace

Data sources