Scenario overview

What this part of the draft does

The contents list names a scenario overview. The draft body is not public, so this page states the step the heading names and the method in ISO 37004:2023 clause 6.5: fix the entities, the controller, the group purpose and the reason the evaluation was commissioned. That is the boundary map and the intent statement in one place.

What it means when you apply it

A scenario overview is not decoration. It fixes the scope, the period and the audience, and it lets a reader see whether the ratings that follow are plausible for that group.

The overview is also the place to record what the example leaves out: an entity acquired during the period, a joint venture with reserved matters, or a board that changed chair. Those omissions are the first questions a real group should ask of its own overview.

The clause reference is the draft's public contents heading. From clause 4 onwards the body is not in the free preview, so this page states the public heading, the model it draws on and our own reading, and does not present the draft's text.

What to keep beside the evaluation

A one-page group profile: entities, controller, group purpose, evaluation period and audience.

• The clause reference and the edition you read, so a later reader can check it.
• The decision it supports, with an owner and a date.
• The link to the requirement rows it frames, so the clause is not an orphan page in the file.

The annex body is not in the public preview. This page describes the step the draft's contents list names and the method in ISO 37004:2023 clause 6.5, and labels it as such.

Where this clause is used

• All 35 requirements
• The 21 terms
• The three aspects
• The publication record
• The method