Supporting reports
Source reports, batch status, and delivery readiness
Use this page to verify what evidence exists behind the current cycle, which reviewed pages have fresh source reports, and whether compare or export outputs are ready.
- Report batch
- No source reports yet
- Pages covered
- 0
- Confirmed findings
- 0
- Blocking findings
- 0
- Compare status
- Ready for compare
- Export status
- Export not ready
Run the first assessment to populate page-level source reports.
Coverage plan not defined
0 total reported findings in the current cycle.
Use this to gauge how much of the report set still needs remediation planning.
The current and baseline cycles cover compatible required website families.
Complete required coverage and findings work before relying on exports for delivery.
Report sources
Reviewed pages with current source inputs
Each row shows the page-level report set behind the current assessment so a customer can confirm coverage before opening compare or export outputs.
Batch and compare
Current batch status
The current workbench view keeps source freshness, coverage, and compare readiness together so the customer can tell whether this cycle is stable enough to reuse.
- Batch status
- No source reports yet
Run the first assessment to populate page-level source reports.
- Last report
- Jul 15, 4:00 PM
Fresh report timestamps matter because compare and export decisions should only use the latest cycle.
- Coverage
- Coverage plan not defined
All currently required website families are represented in the captured report set.
- Compare readiness
- Ready for compare
The current and baseline cycles cover compatible required website families.
Artifacts and export
What can be reused from this cycle
Artifacts stay summarized here. The goal is to tell the customer whether the current cycle is ready for evidence, backlog, or compare deliverables without mixing in internal operations.
- Evidence Pack
- Not ready yet
The current cycle still needs a completed assessment before evidence can be packaged.
- Backlog Export
- Grouping still needed
Confirm and group findings before relying on a backlog export.
- Diff Pack
- Available
The current and baseline cycles cover compatible required website families.
- Next step
- Choose representative pages
Formal delivery starts after setup defines the first representative public pages and assessment scope.
Delivery details
Supporting Reports stays at the summary layer. Open Deliverables when you need the actual evidence, backlog, or compare files.
Compare outputs only become trustworthy when the current and baseline cycles cover the same required website families.
Formal exports stay gated by current-cycle coverage and evidence quality, even when draft remediation material already exists.