Start with the decision
Define readable or displayed area, quality, duration, locations and deployments. Record exposure, handling and supports needed for that service. An area-based comparison alone can conceal differences in replacement or equipment life.
Build the record
Describe both complete routes with retained and changing components. Record when graphics are refreshed and which equipment returns. Keep the expected service assumptions separate from confirmed deployment records.
Check before acting
Confirm both options can deliver the agreed function and use comparable assessment boundaries. If one cannot meet a mandatory requirement, do not rank it suitable because it has a smaller material figure. Preserve priorities and unknown dimensions instead of compressing them into one green score.
Worked example — illustrative
A fictional programme needs graphics at four successive events. One route retains a support and changes faces; another supplies complete units each time. The analyst defines the programme service and includes every required component. The comparison starts from that service rather than only the first printed area.
Keep a useful handover
Close the “Define a functional outcome for comparing display programmes” decision with a named owner and a dated evidence version. The next working record is “Build a lifecycle record”. Record whether that step is planned or confirmed; retain the prior decision if new information changes the instruction.
- Define service and quality.
- Record repeat deployments.
- Include required supports.
- Align assessment scope.
- Separate expected and actual use.
