Transparency

Reverification Queue

Verified facts age. This page surfaces every source that should be re-checked before a value moves to a new surface or a procurement decision. The queue is informational — there is no automatic scraping, no auto-mutation of values, and no claim that a stale row is wrong.

At a glance

Queue summary

Counts derived from the typed local data layer. Cards link to the corresponding queue section below.

Total items
11
Critical
0
High
6
Pricing review due
0
Hosted pricing review due
0
Blocked vendor docs
6
Stale citations
0
Build date
2026-05-24

Queue

Review queue (0)

Ordered by priority (critical → high → medium → low). Every row points at a source URL and a suggested manual action. The catalogue does not change any verified value until a reviewer confirms the source.

No items match this filter.

Suggested review workflow

Pick a queue item (highest priority first).
Open the linked source URL in a browser. Confirm the value on the vendor's own page.
Compare the on-page value against the current catalogue record (linked in Affected routes).
Update the relevant record in data/ — pricing in data/pricing.ts or data/hosted-pricing.ts; citations in data/citations.ts; verification attempts in data/verification-attempts.ts. Only update the verified field if the vendor source confirms the new value; otherwise update the citation timestamp alone.
Stamp the new retrievedAt or lastCheckedAt with the date of the manual review. Do not back-date.
Re-run npm run check:production and npm run build before pushing. The queue refreshes on the next build.

Need a printable checklist? /api/reverification/checklist returns Markdown (or JSON with ?format=json).