Monthly monitoring summaries

Before sharing a summary

Use this page after scheduled monitoring scans have completed for the month and issue change states are available. A monthly summary is a customer-facing digest of evidence-backed changes, not a replacement for report evidence. Do not share or export a monthly summary while scheduled scans are still running, evidence is inconclusive or monitoring is inactive.

Review monthly summary draft

Follow the path `Scheduled scans → Issue change states → Monthly summary draft → Evidence review → Share or follow-up action`.

1. Open /projects/{project}/monitoring after scheduled scans for the summary period have completed. Result: summary_period and monthly_summary_status are visible before a summary is shared.
2. Choose the monthly summary draft for the account and project. Result: the draft is tied to the same Monitor Plan, accepted scope and report_id.
3. Review new, recurring, resolved and inconclusive issue counts. Result: the summary separates evidence-backed changes from limitations.
4. Open linked evidence for changed or high-risk findings before sharing. Result: screenshots, HTML, console, network or missing_artifact_reason details support the summary language.
5. Resolve blocked states before sending the summary. Result: summary not ready, inconclusive evidence or inactive monitoring does not become a false monthly claim.
6. Choose the next action from the draft. Result: safe summaries can be shared or exported, recurring findings can become fix tasks, and inconclusive findings keep their limitation notes.

Summary sections

Review each section before the summary leaves the private workspace.

• Summary period identifies the month, project and accepted scope covered by the digest.
• New issues list fingerprints that appeared during the period and should be evidence-reviewed before alerts.
• Recurring issues list fingerprints that still require remediation, ticket export or monitoring follow-up.
• Resolved issues list fingerprints that disappeared with enough evidence to support the claim.
• Inconclusive evidence lists missing artifacts, skipped pages or changed scope so limitations stay visible.
• Report links point back to report_id or issue evidence before any public report, PDF or client share.

Blocked or unsafe summary states

Do not share a draft in these states.

• Summary not ready means the scheduled scan, comparison or issue state aggregation has not completed.
• Inconclusive evidence means the summary can mention the limitation but must not claim resolution.
• No active monitoring means return to plan or billing state before expecting a current monthly digest.
• Accepted scope changed means the period may not compare the same site surface.
• Sensitive evidence means use privacy redaction before sharing outside the private workspace.
• No report_id means evidence links are not ready for export or public report handoff.

Continue after summary review

Use Public reports when the monthly summary is safe to share externally. Use Report evidence when a stakeholder needs proof behind a count. Use Fix tasks when recurring issues need follow-up work. Keep inconclusive findings linked to Inconclusive evidence so the monthly summary does not overstate what WebRiskOps observed.