7.3 Requirement record

For each requirement, the organisation shall record:

UID;

requirement class and jurisdictional or procedural name;

purpose;

geographic extent and CRS;

stratum or vertical extent, where relevant;

start, end or duration, where known;

status, including proposed, approved, superseded, implemented or withdrawn;

design or decision basis;

originating authority or responsible function;

source documents and evidence;

dependencies on other requirements;

version and approval information; and

known limitations or assumptions.

The requirement status shall not imply that a legal power or agreement exists unless that status is separately evidenced.