Operating ProcedureExecution layer

Weak Signal Triangulation Review (QA)

A checklist with 7 steps: Require three independent source types before a signal enters the client queue.

By InnovaAI ResearchPublished

What are the steps?

checklist

Weak Signal Triangulation Review (QA)

  1. 01

    Require three independent source types before a signal enters the client queue

    Pair a discovery feed (Exploding Topics for category growth curves), a change-detection layer (Visualping watching competitor pricing and policy pages), and a firsthand source (Recordal digests of named operators in the client's space). Two sources from the same family do not count as triangulation.

  2. 02

    Score each candidate signal on client relevance before volume

    Rate 1 to 5 on whether the shift touches the client's buyer, budget line, or category language. A 400 percent search spike in an adjacent vertical scores low; a quiet policy edit on a regulator page scores high if the client sells into that market.

  3. 03

    Deduplicate the feed so one event is not counted as three

    Cluster near-identical headlines into a single record before review, the way Scoopkit collapses duplicate AI coverage into one event with an article count. Three articles about the same funding round is one signal, not a trend.

  4. 04

    Set a freshness window and expire stale candidates

    Anything older than 30 days without a second confirming source gets archived, not carried forward. Stale candidates inflate the trend count and dilute the review meeting.

  5. 05

    Check the claim against outcomes where a prediction is involved

    When a signal rests on a vendor or analyst forecast, log the claim, the deadline, and the evidence. Feargate-style accountability tracking keeps a client from building a retainer deliverable on a prediction that already missed its date.

  6. 06

    Write a one-line action test for every signal that survives

    Each entry must answer: what would the agency do differently this month if this is real? Signals with no answer get parked in a watchlist rather than escalated to the client.

  7. 07

    Log the decision and the reviewer in a shared register

    Record who cleared the signal, the date, and the sources used. This register becomes the audit trail when a client asks why a campaign pivoted.