Generate Reports and Review Coverage

Use Report Packages to preserve configuration evidence, then use the Coverage Matrix to document exactly what the release tracks and where limitations remain.

Generate an As-Built Report

1. Open Configuration Intelligence > Reports.
2. Select Create Package.
3. Choose As-built package.
4. Select the source snapshot.
5. Choose the available output format.
6. Generate the package and wait for its status to reach Complete.
7. Download the package from the report table.

The package records the captured cluster and snapshot context. Keep the source snapshot and report together when the package supports a formal review or audit.

Manage Report Delivery

The Reports page summarizes whether SFTP delivery is configured. Configure delivery in Configuration Intelligence Settings, then enable it only on schedules that need recurring evidence.

Delete obsolete packages according to your organization's retention policy. Deleting a report does not delete its source snapshot.

Review the Coverage Matrix

Open the Coverage tab to see the status of each configuration object type.

Interpret the status before making an evidence claim:

Status	Meaning
Supported	Configuration Intelligence captures and validates the object type.
Partial	Important fields are covered, but the notes identify known omissions.
Derived	Coverage is inferred from related configuration data.
Planned	The object type is visible in the roadmap but is not currently captured.
Gap	The current data source cannot provide complete evidence; read the stated reason.
Out of band	Another collection path supplies the evidence rather than the normal snapshot flow.

Search by object type or select a status chip to focus the matrix. The validation count shows how many records support the displayed coverage result when that count is available.

Download Coverage Proof

Select Download coverage proof when an auditor or reviewer needs the matrix as a retained artifact. Choose the format, generate the package, and store it with the related As-Built report.

Coverage proof describes what Configuration Intelligence can substantiate; it does not turn a Partial, Planned, or Gap object into supported evidence.

Complete the Review Cycle

At the end of a successful change window:

1. Resolve unexplained Timeline events.
2. Save the comparison or evidence bundle when required.
3. Generate the As-Built package.
4. Download the Coverage proof.
5. Approve and pin the new snapshot only after the resulting CUCM state is accepted.

Return to the Configuration Intelligence Overview →