# Reports

> Configure, preview, and export CORE Reports for an AI system

Canonical URL: http://modelmonster.ai/docs/reporting-and-artifacts/reports/

## Article Metadata

- Reading time: 5 min

The CORE Report turns information from an existing system into a configurable document for governance and review. Use the report builder to choose content, inspect the preview, and download the full report or an individual section as a PDF.

## What the CORE Report reflects

A CORE Report is grounded in the system information documented in Model Monster. Its content can reflect the System Blueprint, use-case context, findings of record, policies evaluated, licensing information, and version-review details. This gives legal, compliance, governance, and technical stakeholders a shared document for discussing the system and its governance record.

A CORE Report reflects the information available in the system record when you generate it. Update the system first when its design, use case, findings, or review state has changed.

> **Note:** The report supports governance, review, and compliance work, but it does not certify compliance or independently verify facts outside Model Monster. Review the underlying system information before generating a report that others will rely on.

## Open the report builder

1. Open the system you want to report on.
2. Select **Reports** from the system navigation.

![Reports builder with the CORE Report preview visible](/media/original_images/visual-1-reports-builder.png)

The builder and report preview share the page. Select **Preview** when you want to hide or show the preview while configuring the report.

## Choose a report template

Open **Templates**, then choose the option that best matches the intended review.

![Templates menu showing Executive Summary, Full Audit Report, and Compliance Review](/media/original_images/visual-2-templates-menu.png)

- **Executive Summary** provides a concise system overview for leadership or an initial review. It includes the report header, System Blueprint, scope and methodology, and system overview.
- **Full Audit Report** provides the broadest record for a detailed governance or audit review. It adds use-case information, findings of record, policies evaluated, and licensing information with full license text.
- **Compliance Review** focuses on policy coverage and governance findings. It includes the report header, System Blueprint, scope and methodology, system overview, findings of record, and policies evaluated.

> **Tip:** Choose the closest template, then tailor its sections and presentation options to the people who will read the report.

## Configure the report

To build a report manually or refine a template, choose the content and presentation options that fit the review.

The checked sections under **Standard sections** are marked **Always** and remain in every report. Select the content you need under **Additional sections**.

![Additional sections with findings of record and Signoffs Attestation selected, showing their nested options plus Component display and Other options](/media/original_images/visual-3-additional-sections.png)

Some sections reveal another choice when selected:

- **Findings of record** adds **Exclude flows marked as not relevant**.
- **Licensing Information** lets you choose **License expressions only** or **Full license text**.
- **Signoffs Attestation** adds **Include reviewer comments**.

Use **Component display** to control component naming and notes. **Don't use display names** uses canonical component and resource labels instead of system-specific display names. **Include notes** adds system-only notes to report sections.

Under **Other options**, **Confidential badge** adds **CONFIDENTIAL** to each report-page footer. **Full-Page System Blueprint** adds a landscape blueprint section to the report.

### Include Signoffs Attestation

Select **Signoffs Attestation** when the report should include system-review information. When review data is available, the section can show submission details and reviewer decisions. Select **Include reviewer comments** when those comments should appear in the report.

You can include the section before a version has review data. In that case, the report displays **No version review record is available for this version.**

## Review the live preview

Use **Previous page** and **Next page** to inspect the report. Select **Open in fullscreen** when you want more room to read, then select **Exit fullscreen** to return to the builder.

![Fullscreen CORE Report preview with page controls and the fullscreen exit icon visible](/media/original_images/visual-4-fullscreen-preview.png)

Confirm that the report includes the sections and options you selected. The page count may change while Model Monster updates the preview, so allow it to settle before checking the final length.

## Download the full report or one section

To download the complete report, use either full-report action:

1. Select **Generate Report**; or
2. Open **Export**, then select **PDF**.

![Export menu open with PDF as the available format](/media/original_images/visual-5-export-pdf.png)

To download one report section, select the download icon for that section on the report builder. Its label is **Export this section**.

Open the downloaded PDF and confirm that it reflects the content and presentation choices shown in the preview.

## Report options reference

Use these tables when you need to check what a particular report choice includes.

### Standard sections

| Section | What it adds |
|---|---|
| **Report Header** | CORE cover, report metadata, and responsible party |
| **System Blueprint** | A visual architecture diagram of the system |
| **System Overview** | Components, resources, and operations |

### Additional sections

| Section | What it adds | Related choice |
|---|---|---|
| **Scope and Methodology** | Report scope, basis, limitations, and methodology | Selected by default |
| **Use Case Information** | Full use-case details and context | None |
| **findings of record** | Policy outputs and risk indicators | **Exclude flows marked as not relevant** |
| **Policies Evaluated** | Policies run against the system | None |
| **Licensing Information** | Component licenses, terms, and acceptable use | **License expressions only** or **Full license text** |
| **Signoffs Attestation** | Review signoffs for the relevant release | **Include reviewer comments** |

### Display and document options

| Option | Effect |
|---|---|
| **Don't use display names** | Uses canonical component and resource labels instead of system-specific display names |
| **Include notes** | Shows system-only notes in report sections |
| **Confidential badge** | Shows **CONFIDENTIAL** in each report-page footer |
| **Full-Page System Blueprint** | Adds a full-page landscape view of the System Blueprint |

## Add organization branding

An organization admin can manage the logo used in the CORE Report header. Open **Settings**, stay on **General**, then find **Branding**.

![Branding setting showing This logo appears in the CORE Report header and the organization logo control](/media/original_images/visual-6-settings-branding.png)

## Reports and released records

A CORE Report presents selected system and governance information in a readable document. A released version preserves system state at a point in time. They support related governance work, but they are not interchangeable artifacts.

Signoffs Attestation can present review information associated with a relevant release. Use the version workflow when you need to preserve or retrieve a release record.

## Next steps

Before distributing a final report, review the System Blueprint, use-case information, findings, policies, and other source data included in it. Review and approve a system version when you need to create review information for Signoffs Attestation. Work with released versions and exports when you need preserved release records.