Findings & actions

Overview

Findings & actions (Insights › Findings & actions) is the page that answers what did the last cycle change, and what should we do about it?

A finding is a standing condition the intelligence pass measured against your own captured answers — "3 of 12 non-brand transactional questions had nobody named", "your site was cited in 25% of 160 answers without being named". It stays open while it is true and closes on its own test. Findings are computed over each project's own capture cycle, so this page does not follow a date range: a finding re-sliced by a picker would show a number that was never measured.

The findings feed

The page leads with the feed. A filter row narrows it:

• Status — Open (the default: new and seen), Seen, Actioned, Dismissed, Closed.
• Type — the finding types (Nobody Named, Cited Not Named, Rival In Your Answer, Fact Stated Wrongly, …).
• Question type — one of the four question types. This is the same control as the question-type chip in the filter bar; a finding carries its question type but no reference to the individual questions behind it, so the other chips (segment, intent, journey, topic, tag, group) cannot be applied here — when one is on, the feed says so instead of showing an unfiltered list.
• Stage — where in answer assembly it fails (Stage 1 shortlist, Stage 2 filtered out, Stage 3 name dropped or described wrongly).
• Kind of work — gate problem or content problem.

Every filter is applied by the database, so the count shown is the whole population, not the page in front of you.

Above the list, one tile per question type shows how many findings are standing there and, where one has already become an action, the single next action for that question type.

Each finding is one card:

• the strip — question type › stage › kind of work · the n it rests on, banded (low confidence under 10, below target at 10–29, at target from 30) · how it is known (measured directly, a rule of the method, a pattern not yet separable from coincidence, a forecast)
• the title and the measure sentence exactly as written when it was measured
• the test that closes it, in your own capture rhythm ("Closes when this falls to 12% or below within the next fortnight")
• the action it has already been raised as, linking to that action

When nothing is standing, the page says so: "Nothing is standing. New findings are raised after each capture cycle."

Problem diagnosis — the four stages

The Problem diagnosis page (Insights › Problem diagnosis) reads every view down to one named problem per question type. An answer is built in three stages — the engine assembles a shortlist, filters it, then writes the answer — and each symptom points at one stage and one kind of work:

The failing stage for a question type compares two shares over the same contested questions — not named at all (Stage 1) against named but not in the first three (Stage 3); when the two are within the six-point noise floor of each other, both apply. Figures counted in runs, such as answers that cited your page without naming you, are printed beside the verdict with their own denominators and never enter it. Stage 2 is reported in words as not yet distinguishable from Stage 1 until your page's search rank for the same question (Search Console) can separate them.

Every count is printed with its population ("N of M contested questions"), question types are never added together, and the page composes figures the Performance review, Citation sources, Content coverage gaps, Website readiness check and Fact check already compute — it computes nothing new. The gate-or-content card at the bottom sorts the open gaps by the budget that closes them: a gate problem is binary and closes on two or three credible independent domains; a content problem is continuous and routes to the content plan.

Actions

The actions themselves live on the Action list. This page shows one line — how many are open, in progress and completed — and the door to the list. That line counts the whole project and carries an "All prompts" badge when a filter chip is active.

Verified impact and what works best

Two cards under the actions line:

• Verified impact — completed actions with a verification verdict. Today's verification is a project-wide before/after on the retired blended score; the change in points on the action's own question type arrives when the per-pool verification ships.
• What works best — success rate per kind of action, from the actions that were verified. It fills as you verify more; treat it as directional until each kind has a handful of verified rows.

Model changes

Shown only when there are any: brand-mention shifts around the dates a new model was first seen on an engine. The delta printed beside each date is an observation, not a claim that the model change moved the number.

Actions lifecycle

1. Detect — the intelligence pass raises a finding with its measure and its stop condition.
2. Raise — a finding becomes an action (automatically for the finding types that map to one; by hand for the rest), and lands on the Action list.
3. Assign — open the action from the list (one hop) and set its owner and due date on the action's record page.
4. Execute — work the checklist; mark it In progress, then Completed.
5. Verify — after completion the platform compares a project-wide figure before and after — today a check on the retired blended score, kept until the measurement on the action's own question type ships. Verified and Failed verification are set by that check, never by changing a status.
6. Learn — verified outcomes feed the "What works best" table.

How findings are generated

Findings are written by the intelligence pass that runs after each capture cycle, over the project's own captured answers. There is no setup: the more cycles a project has, the more its findings can say. Each finding closes when its own test is met, and a closed finding is kept under the Closed filter so you can see what stopped being true and when.