Scoutmark help

From captured evidence to a reviewed output

Start with a captured baseline, then prepare guidance or a report with clear evidence and sharing controls.

On this page

Capture your first sources

Workspace setup walks through a short sequence: discover pages, choose sources, start monitoring. Each source’s first successful capture is its starting point, and it appears in Market baseline. You do not need to wait for a detected change before preparing useful work.

For product marketing: add your business context, capture a competitor page, confirm what Scoutmark captured, then create and approve sales guidance from that baseline. A detected change is not required.

For research advisors: create a client account, select that client in the sidebar, add its private brief, and confirm the first sources. Create a report draft, choose its evidence, review the exact recipient preview, and publish it to your client portal. Invite a client response to close the loop.

Confirm what each source captures

Open a source in Sources and inspect its retained comparison text. Search the full text, check its status and selected section, and preview noise filters on that same capture. Confirm the intended content for every active source. A new source or a changed capture configuration needs confirmation before setup is complete.

Capture and drafting can continue while confirmation is pending. A partial or failed capture is shown separately from a successful verification and should not be read as evidence that a company removed content. To use a source for another client, duplicate it into that client account; its earlier evidence stays in its original scope.

Keep client context separate from evidence

The sidebar selector carries your chosen portfolio or client between work areas. Business & client context stores a versioned private brief for that exact scope. All portfolios uses your explicitly saved workspace brief. Client briefs do not silently inherit your own company brief; a client without a brief uses only its evidence.

Context helps interpret evidence; it is not proof of a market fact. Generated outputs keep the context version used at creation. Updating a brief does not rewrite previous work. Private brief fields are excluded from public reports; review any narrative you choose to write for recipients.

Review changes and ask Analyst

When a later capture differs from the retained version, the difference appears in Changes and in Briefings. Analyst answers questions from retained changes within the selected scope and period, with citations and limitations visible; it is not open web research.

Review sales guidance before sharing

Sales guidance lives under Actions. Start from a retained baseline capture or change, write your response, and approve a revision before distribution. Creating a draft does not publish a public link.

Approval and source currency are separate. When newer retained evidence affects guidance, existing links show a warning. Review the new evidence in a new revision before distributing again, even if the response wording still applies.

Choose reviewed or automatic reports

Reports live under Reports & sharing. A report draft can include baseline evidence and changes you have already actioned, alongside your narrative, recommended actions, questions, and coverage limitations. The public preview shows the exact content and branding being reviewed. If someone edits the draft, review the new version before publishing.

Reviewed is the default schedule mode. A due weekly or monthly edition prepares a draft and notifies its author; it does not send that draft to clients. Automatic delivery is an explicit option and its editions are labeled unreviewed. Existing automatic schedules keep an explicit legacy automatic label.

Schedules run in UTC. Monthly dates beyond the end of a month use its last day. Provider acceptance means the provider accepted a send request; it does not prove delivery to an inbox or that a person read the report. Sharing & delivery and Alert settings show pending, failed, accepted, or uncertain attempts as appropriate.

Understand AI allowances

Market readouts have a separate allowance from Analyst questions: three successful readouts in total during the trial, then 20, 100, or 500 per UTC month on Starter, Growth, or Scale. Paid readout allowances reset on the first of the month at 00:00 UTC. Reusing a cached result, a failed generation, or a labeled standard evidence summary does not consume a successful readout.

At the readout limit, an active workspace can still capture evidence, review it, write guidance, and use a standard evidence summary. Operating safeguards may also temporarily prevent AI generation. There are no automatic overage charges. Evidence references identify what an answer used; review whether its claims actually follow from those excerpts.

Trial sharing and retained work

Your trial includes one live client portal with preview, responses, and revocation. At trial expiry, monitoring, new AI work, and new sharing pause. Trial portal and report access ends at request time, including copied report links and reply paths. Your private work is retained under the retention policy.

Upgrading before the trial ends keeps existing sharing continuous, subject to each link’s normal expiry and revocation. After an expired trial, upgrade and explicitly resume sharing from the owner controls. The resume control explains its workspace scope. Revoked or individually expired links stay closed. Separate baseline, guidance, and client value review links retain their stated lifetimes.

Use Results to review outcomes

Results brings together review evidence, delivery activity, and recorded outcomes. Checks, opens, and responses show activity; they do not establish revenue impact. Record an outcome with its evidence and review date, and distinguish a measured result from an estimate or a stakeholder’s statement.