Learn the concept.
A report should help its reader make a decision. A long list of completed tasks can hide unresolved risk.
Choose meaningful measures
Explain what is counted and the reporting period. Separate completed fixes from open or overdue work.
Keep claims supported
Show evidence and limitations. A sample result does not automatically represent the full population.
Ask for a decision
Highlight what needs ownership, resources, or approval, and when. Keep technical detail available for follow-up.
Field example08 / A
Put it in context
Your weekly summary reports three verified fixes and two overdue high-impact gaps. It asks the designated owner to decide the next treatment, rather than calling the program green.
Show progress and remaining exposure
A fictional weekly update, not site-wide performance data.
- 3 verified fixes
Changes have supporting verification. State the relevant scope and reporting period.
- 2 overdue high-impact gaps
Name the owners, blockers, and decision needed. These remain visible alongside the fixes.
Read the visualWhich follow-up makes the overdue count useful?
Identify the accountable owner, next action, and date or decision needed.
Make a decision.
Use what you just learned. A correct answer lets you save this lesson to your progress.
Take this with you.
Report remaining risk and decisions needed, alongside progress.
Next lesson: Test a security control