Reports

What a report is

A report is an organized output that helps the user understand what happened and what needs attention.

It may arrive by email, be downloaded as a file, or remain available inside QAC.

What it should answer

A good report should answer:

• What was processed.
• What changed.
• What requires action.
• What had no updates.
• What could not be validated.
• When the check happened.

Recommended structure

Reports should prioritize attention:

1. Errors or review items.
2. Relevant changes.
3. Completed or arrived operations.
4. Operations without changes.
5. Summary and next steps.

Language and recipients

Language should follow the user or organization configuration. Recipients should be configurable without a developer.

When a report is used for daily operations, clarity and consistency matter more than excessive detail.