Exporting Results & PDF Reports
Learn how to export check run results to CSV or Excel, including column details, formatting, and links for reviewing files and register check summaries.
CSV Export
Click the CSV button on a check run's action bar. The download includes:
| Column | Description |
|---|---|
| Result Type | File Check for per-file results, or Register Check for run-level Register Cross-Reference results |
| File Name | File name (no clickable link in CSV). For register check rows this contains [Register Check] {rule name} |
| File Path | Folder path in the CDE (empty for register check rows) |
| Status | Passed, Failed, Warning, or Skipped |
| File Type | File extension |
| Version | Version number extracted from the URN |
| Rule Set | Which rule set was applied (only in per-folder mode) |
| Zone columns | One column per zone field (e.g. "Drawing Number", "Date") |
| Violations | Violation messages. For register check rows this contains a completeness summary like 94.0% complete: 232/247 found, 12 missing, 3 unexpected |
| Rule Names | Names of the rules that fired |
| Severities | Error, Warning, or Info |
| Expected | Expected value(s). For register check rows this is Missing: DWG-001, DWG-002, ... |
| Actual | Actual value(s). For register check rows this is Unexpected: STRAY-FILE.pdf, ... |
| Forma Link | Direct URL to the file in Autodesk Forma (empty for register check rows since they are not file-bound) |
Both passed and failed files are included with full details. Register Cross-Reference rules add one row per rule with a Register Check result type — these rows aggregate the missing/unexpected counts across all checked files.
Excel Export
Click the Excel button. The XLSX file includes the same columns as CSV plus:
- Clickable file names that link to Forma (skipped for register check rows since they are not file-bound).
- Colour-coded status cells (green/red/amber/grey).
- Purple bold "Result Type" cells for
Register Checkrows so they stand out from regular file rows. - Clickable "Open in Forma" column with hyperlinks (also skipped for register check rows).
- Auto-filter enabled on all columns — use this to quickly filter to only Register Check rows or only File Check rows.
- Header row styling with slate background and bold text.
The file is named QA-{RuleSetName}-{date}.xlsx.
PDF Report
Click the PDF Report button to open the report configuration dialog.
Configuring the Report
| Setting | Description |
|---|---|
| Title | Custom report title (defaults to project name) |
| Prepared by | Your name or team name |
| Notes | Free-text notes included at the bottom of the report |
| Logo | Upload your company logo (shown on cover page and footer) |
| File filter | All files, failed only, or failed + warnings |
Configurable Sections
Toggle each section on or off:
| Section | Content |
|---|---|
| Cover page | Logo, title, project name, rule set(s) used, health score, date, prepared by |
| Executive summary | Table with total/passed/failed/warning/skipped counts, pass rate, duration, rule sets used |
| Health trend | Pass rate trend across recent check runs (requires 2+ completed runs). Includes a Rule Set(s) column showing which rule set was used for each run. For per-folder runs, this shows "X rule sets (per-folder)". The date column includes the time for better differentiation between runs on the same day. |
| Violations by rule | Table of violations grouped by rule name with counts and severity |
| Violations by folder | Breakdown of failed files by folder path (register check entries are excluded — they have their own section) |
| File type breakdown | Count of files by extension |
| Register completeness | NEW — Per Register Cross-Reference rule, a card with a colour-coded completeness percentage, found / missing / unexpected / total stat boxes, and a list of every missing register entry and every unexpected file. Only shown when at least one register cross-reference rule produced data. |
| Detailed results | Per-file results with status, violations, rule set name, and clickable Forma links. Register check entries are excluded from this section since they appear in the dedicated Register Completeness section above. |
| Extracted content | Zone values extracted from PDFs, grouped by file. Register check entries are excluded. |
| Rule set details | Full list of rules in the rule set with their type, severity, and configuration |
| Notes | Your custom notes |
Register Completeness Section (Detail)
When your check run includes a Register Cross-Reference rule, the PDF reserves a dedicated section that surfaces the deliverables completeness picture in a way that's easy to share with stakeholders.
For each Register Cross-Reference rule, the section renders a card with:
- Header — rule name on the left, completeness percentage on the right (green ≥95%, amber ≥80%, red <80%)
- Stat row — four boxes: Found / Missing / Unexpected / In Register (totals)
- Missing files list — every register entry that has no matching file in the checked folders. Top 30 entries shown inline; if there are more, an overflow count is added (e.g.
… +12 more) - Unexpected files list — every file in the checked folders whose value isn't in the register. Same top 30 + overflow pattern.
- All-clear message — when both lists are empty, the card shows "All register entries matched. No unexpected files."
This section is the most useful page of the report at milestone reviews — it answers "are we delivering everything we said we would?" in a single glance.
Multi-Rule Set Reports
In per-folder mode, the report automatically:
- Lists all rule sets on the cover page ("Rule Sets: Arch Standards, Struct Standards").
- Shows a "Rule Sets" row in the executive summary.
- Displays the rule set name under each file in the detailed results section.
Branding
- Upload a logo (PNG or JPG, max 2 MB). The logo appears on the cover page next to the "FOREMAN" text and in the footer.
- If no logo is uploaded, the default Foreman logo is used.
- The report uses the Montserrat font for the "FOREMAN" brand text.
- All filenames in the detailed results section are clickable links to the file in Forma (region-aware: acc.autodesk.com, acc.autodesk.eu, etc.).
The file is named QA-Report-{ProjectName}-{date}.pdf.
Your report settings (sections, title, logo) are saved to your account and persist across sessions. You do not need to reconfigure them each time.
Combined Reports — multi-run exports
Sometimes one run isn't the right unit. You may want a single CSV / Excel / PDF that covers a milestone (last 5 runs across the past month), a stage gate (every run since the last freeze), or a discipline group (one run per discipline pulled together).
In the Check History tab, tick the checkbox at the start of any completed run row. As soon as two or more runs are selected, a sticky dark action bar appears at the bottom of the page:
N runs selected [ Combined CSV ] [ Combined Excel ] [ Combined PDF ] Clear selection
| Format | What you get |
|---|---|
| Combined CSV | One CSV file containing every result row from every selected run. A new Run column identifies which run each row came from (run id + date). All other columns mirror the single-run CSV schema. |
| Combined Excel | Same as Combined CSV in column shape, plus the colour-coded styling and clickable Forma links from the single-run XLSX. Auto-filter is enabled — use it to slice by run, status, rule set, or folder. |
| Combined PDF | Opens the same PDF Report Settings dialog. The header reads Combined PDF Report (N runs) — confirming you're configuring a multi-run output. |
Configuring a Combined PDF
The dialog mirrors the single-run PDF flow with two differences:
- The Health trend section automatically uses the selected runs as its trend points, even when fewer than the usual lookback window applies.
- The Detailed results and Extracted content sections list rows from every selected run, prefixed by run date / project so you can tell where each row came from.
All other sections (Cover page, Executive summary, Violations by rule, Violations by folder, File type breakdown, Register completeness, Rule set details, Notes) aggregate across the selected runs. Register completeness is computed against the union of register cross-reference rules in any selected run — useful when each run validates a slice of the deliverables register.
When to use combined exports
| Pattern | What it looks like |
|---|---|
| Stage gate handover | Tick every run since the last issue date, generate a Combined PDF with cover + executive summary + register completeness. One file goes to the auditor. |
| Cross-discipline review | Tick the latest run from each discipline rule set (Arch / Structures / MEP) — the Combined Excel gives a single sheet to filter by discipline. |
| Trend analysis | Tick monthly check runs across a quarter, generate a Combined CSV, drop it into your BI tool to track quality over time. |
Selection is run-scoped, not file-scoped. Combined exports always include all results from each selected run. To filter file-by-file across runs, use Combined CSV / Excel and apply column filters in your spreadsheet tool.
Next Steps
- QA Dashboard & Trends -- view aggregate metrics without exporting
- Understanding Check Results -- drill into violations before exporting