Choose work that follows from evidence
Open Actions and Opportunities after reviewing the underlying answers and website findings. A useful action identifies a problem, its evidence, the affected page and the intended customer decision. Do not treat a long list as a requirement to rewrite everything. Prioritise the few changes your team can implement and verify.
A missing explanation on a buying page, an outdated factual claim and a crawler access failure need different owners. Assign the work to the person who can change the relevant material. The value of the action brief is that the next person can understand the reason without repeating your research.
Write a complete action brief
- State the buyer question and the observed finding, with the original sample and date.
- Link the exact answer, passage, page or crawl evidence. Separate observed claims from facts you independently verified.
- Specify the change: which section, statement, source, table, link or technical rule should change.
- Name an owner and a practical completion date. Record dependencies such as product review or engineering access.
- Define acceptance: the public page contains the corrected evidence; the link works; the declared rule matches the intended policy.
- Define a later measurement separately, using the same question and source scope if you want a comparison.
Use Content to prepare a useful deliverable
Content work should retain the question, intended audience, factual sources and limitations from the brief. Review a generated or prepared draft as an editor would: check accuracy, originality, product claims, dates and whether the answer is useful to a real buyer. A draft is not a verified claim merely because software produced it.
Export the appropriate publishing bundle for the responsible team. IndexHalo does not turn a bundle export into an automatic CMS deployment. Once the page is live, record its URL and verify that the intended change is actually visible. Keep a distinction between drafted, published and verified work.
Read Impact as an observation comparison
Impact can organise saved tasks and recorded before-and-after observations. Preserve the baseline and match the later scope: question wording, brand, market, language, sources and inclusion rules. If any of those changed, explain the difference rather than presenting a clean improvement arrow.
An answer can change for reasons outside your website: source availability, model behaviour, competitor changes or timing. A later citation is an observation, not automatic causal proof. For a stronger test, define the intervention, baseline, comparison group where feasible, period and success measure before doing the work.
Close tasks with evidence
Attach the live verification and follow-up result to the task. If the page fix passed but the later answer did not change, report both facts. The fix may still improve clarity or accessibility; it simply did not demonstrate the proposed answer outcome in that sample. If data is missing, keep the outcome unmeasured.
A monthly report should distinguish completed work, observed outcomes and next experiments. This gives stakeholders a defensible reason to continue the programme: a clear record of what was learned and what should happen next.
Your next step
Complete one brief with an owner, acceptance test and repeat-measurement scope.
Continue to the next guide → · All Academy lessons