Report Builder turns the findings sitting in a workspace into an audit report. You assemble the findings you want to include, and it produces a structured document organized by severity — the deliverable a client or stakeholder actually reads, built from the analysis you already ran rather than retyped by hand.
Why it exists
Analysis that never leaves the tool doesn’t help the person who has to act on it. The last mile of an audit is packaging: collecting the findings that matter, ordering them so the critical issues come first, and presenting them consistently. Report Builder does that packaging step so the report reflects the same findings the engine produced, with no transcription drift between what was found and what was written up.
Who uses it
- Auditor — assembles the review’s findings into the report that goes to the client.
- Team lead — produces a consistent, severity-ordered summary of a workspace’s results for stakeholders.
How to open it
- Sidebar → Report Builder.
- Direct URL —
/report-builder.
Assembling a report
- Assemble the report from the workspace’s findings; they are grouped and ordered by severity so the highest-impact issues lead.
- Use Load demo data to see a fully populated example before building your own.
Limits
- Report Builder packages findings that already exist in the workspace — it presents analysis, it does not perform it. Run the analysis first, then assemble.
- The report reflects the findings included at assembly time; regenerate it after new analysis to keep it current.
Related pages
- Evidence Graph — the case structure the findings connect into.
- EVM Contract Overview — where the findings a report collects are produced.