Monitoring plans

Before buying monitoring

Monitoring is the recurring check path for a project that already has accepted scope and a completed baseline live audit. Billing can show plan and subscription state, but scheduled monitoring cannot produce useful comparisons until the first audit exists. Use this page when you need to decide whether to buy Monitor Plan, use included monitoring from Fix Plan or Agency Plan, wait for provider confirmation or return to the project first.

Confirm baseline and scope

Follow the path `Projects → Project detail → Monitoring → Billing`.

1. Open /projects and choose the project you want monitored. Result: the project detail page shows accepted scope, latest scan/report state and Monitoring controls.
2. Confirm the project has an accepted scan scope for the public pages you want checked again. Result: recurring scans stay inside the same approved boundary.
3. Confirm a baseline live audit has completed and produced a report. Result: monitoring can compare future findings against a known starting point.
4. Open /billing while switched to the same account. Result: Billing shows the account subscription state, payment provider readiness and monitoring plan cards.
5. Read the plan ladder and choose Monitor Plan only when checkout is available, or use Fix Plan or Agency Plan when they already include monitoring. Result: the cadence, `/checkout/monitor_plan` route and limits match the project before payment.
6. If baseline or scope is missing, return to the project and finish that step before checkout. Result: payment does not create a monitoring subscription that cannot run.

Choose Monitor Plan

Choose the smallest plan that matches the project cadence and page limit. Public checkout paths are useful only when the plan is enabled and the project already meets the baseline and scope requirements.

• Scan Plan is enough when a monthly evidence refresh is all the project needs.
• Monitor Plan is the first recurring path for weekly checks, alerts and larger scan allowance.
• Fix Plan keeps monitoring on and adds generated remediation tasks and retests.
• Agency Plan applies monitoring across eligible client-site slots inside agency boundaries.
• Unsupported scope does not become monitorable through payment; reduce or re-accept scope before checkout.
• Monitoring compares current findings against the baseline; it does not replace a new full audit when the public journey changes materially.

Wait for subscription readiness

After checkout, return to Billing and wait for provider-confirmed subscription state before expecting scheduled runs. WebRiskOps uses stored provider webhook records, not the browser return page alone, as the source of truth.

• Active allows scheduled checks within the plan cadence and page limits.
• Pending means provider confirmation has not updated product entitlement yet.
• Past due can block new monitoring runs until provider state recovers.
• Cancellation scheduled means access may continue until the current term ends.
• Cancelled means new scheduled monitoring needs another available plan.

Continue to scheduled scans

When Billing is active and the project monitoring setup is saved, open [Scheduled scans](/docs/monitoring-retests/scheduled-scans) to review recurring runs and [Monthly summaries](/docs/monitoring-retests/monthly-summaries) for the monitoring evidence rollup.

• Monitoring plan required means choose Monitor Plan or a stronger included plan and wait for subscription readiness.
• Baseline scan required means complete a live audit first.
• Subscription past due means resolve provider state before new scheduled runs continue.
• Accepted scope missing means return to the project and accept a scan scope.
• Plan deferred means choose the available plan named in the disabled reason.