Tasks

Tasks turn PromptScout from passive monitoring into a weekly growth workflow. Each week, PromptScout can recommend focused work from monitored prompts, competitors, citations, sources, website gaps, and Traffic or Search context, then keep receipts and watch windows for later comparison.

TechFlow fixture workspace showing Weekly Tasks with priority reasons, prompt evidence, source context, completion receipts, and watch windows

Three actions, not a generic backlog

The buyer job is deciding what to complete this week. PromptScout Tasks are generated per brand from the latest evidence window and are meant to stay small: a focused set of recommended actions instead of a broad opportunity backlog.

  • Use the latest monitor run and insight batch as the evidence window
  • Keep content and comparison work from crowding out technical, directory, community, or positioning work
  • Treat Tasks as weekly execution, with Today and Morning brief providing daily context
TechFlow fixture workspace showing Weekly Tasks with priority reasons, prompt evidence, source context, completion receipts, and watch windows

Why now, Work, Evidence, Watch

Each Task explains the current reason it exists, the work to complete, the evidence that supports it, and what PromptScout will watch after completion. That structure keeps the recommendation specific enough for a user or agent to act on without inventing evidence.

  • Why now: the observed prompt, source, competitor, provider, or website signal
  • Work: the concrete page, directory, community, technical, or positioning action
  • Evidence: compact prompt, citation, source, competitor, provider, and run chips
  • Watch: the post-completion window and metrics to compare later

Receipts and watch windows keep it honest

Task completion is not the same as proven impact. PromptScout can store completion notes or artifact receipts, start a watch window, and later describe observed movement after completion without turning that movement into a causal claim.

  • Completion receipts can be a URL, note, updated page path, submission proof, or verification note
  • Watch windows compare the relevant evidence slice after enough time has passed
  • Result copy stays non-causal: observed after completion, not promised by completion
PromptScout weekly reports view summarizing AI visibility KPIs

Frequently asked questions

How many weekly Tasks does PromptScout generate?

The V1 contract is three recommended Tasks per brand when the weekly batch is eligible and the user has access to the Growth-tier workflow.

What is a watch window?

A watch window is the period after a Task is completed where PromptScout compares later evidence against the original scope and reports observed movement with non-causal language.

Complete weekly Tasks with receipts and watch windows

Set Up Your AI Visibility Check, complete the right Tasks, log completion receipts, and compare observed movement after the watch window.