Reports & Exports

Exports are how you turn Modulos work into auditor-consumable artifacts: point-in-time snapshots of scope, status, Evidence, and decisions.

For the full traceability model, see Governance Operating Model.

What this is

Exports are intentionally conservative: they reflect what is currently recorded in the platform and can be shared externally.

In practice, you export:

• The project PDF to share a full scope snapshot
• Evidence files to provide proof artifacts to auditors or internal assurance teams
• Asset files to share living documentation as portable documents

Where in Modulos

• Project → Dashboard → Export for the project snapshot PDF
• Project → Evidence to download Evidence files
• Project → Assets → select an asset → Download File to download asset content

12

Use Project → Dashboard → Export to generate a point-in-time snapshot PDF for audits and stakeholders. UI shown in light mode.

1. 1
   Export

   Generates a project snapshot PDF that captures scope, status, and key rollups.
2. 2
   Project context

   Confirm you are in the correct project before exporting.

Who can do what

Permissions

• Most users can view exports and download Evidence within the projects they have access to.
• Export actions are typically restricted to Project Owners to avoid uncontrolled sharing.
• Viewers can often access exports as read-only artifacts when granted access to the project.

How it works

Exports are generated server-side and should be treated as point-in-time snapshots:

• exports reflect the current state of the project at the time you generate them
• PDFs include an export date (and are generated with a timezone parameter)

Building an audit pack

If you need to assemble an audit pack today, a practical starting point is:

• the project export PDF (scope + rollups)
• Evidence files referenced by the most critical Controls
• key assets (system description, policies, procedures) downloaded from their asset pages

The diagram below shows a practical audit pack bundle built from exports, Evidence files, and key assets.

Audit pack

How three export surfaces collapse into one shippable bundle.

Inputs

Project PDF export

Evidence files (per-file download)

Asset files (Download File)

Audit pack

Single shippable bundle

All three inputs, versioned together, ready for the auditor.

Snapshot

Exports are snapshots. Keep scope stable before exporting — the bundle freezes whatever was in place at export time.

How to use it

1

Stabilize scope

Confirm frameworks, roles, and project scope statement are correct

2

Ensure decisions are recorded

Finish Control statuses and Requirement reviews so the record is auditable

3

Export the project

Generate the project PDF snapshot as the primary audit artifact

4

Bundle Evidence

Download the Evidence files referenced by the most critical Controls

Important considerations

• Exports are not the audit trail. They are views of the audit trail at a moment in time.
• Freeze framework updates when approaching audit completion so exported scope remains stable.
• Prefer bundling the Evidence for a smaller set of high-impact Controls over downloading everything.

Related pages

Governance Operating Model

How exports relate to reviews, logs, and Evidence

Controls

Where implementation, Evidence, and status-change comments live

Evidence

Evidence files are the proof artifacts included in audit packs

Assets & Documents

Export living documentation as Markdown when needed