A requirement register is a controlled record of requirements that a process or proposed change must satisfy, with traceability to their source and evidence of fulfilment. In a DMAIC project, it makes constraints explicit before the team changes how work moves through the process.
For a building-permit project, each statutory check has an entry identifying its legal authority and the conditions under which it applies. The entry names the responsible reviewer and specifies the evidence retained in the case file. Local administrative practices can have separate entries so their status remains clear during improvement discussions.
Suppose a team proposes removing a referral because it adds waiting time. The register provides the basis for a decision: the responsible regulatory officer determines whether the referral fulfils a mandatory requirement and whether an alternative route preserves that requirement. An unresolved interpretation remains open, with an assigned owner, before the routing change enters a pilot.
The project charter establishes scope and authority; the requirement register provides detail for evaluating individual changes. Value stream mapping can use its entries to identify required checks within the workflow. FMEA examines how those checks might fail, including missed referrals or reviews against superseded drawings. The control plan then specifies how completion evidence will be monitored. A register entry documents an obligation; case-level records establish whether that obligation was fulfilled for a particular permit.
