What is a compliance matrix in AGL?
One table that shows, requirement by requirement, what was asked, how it was proved and whether it was met.
A compliance matrix is a table with one row per requirement. Each row holds the source, the verification method, the evidence and a status. It is where the outcome of requirement mapping is recorded, so reviewers can see at a glance what is done and what is not.
The status must come from evidence on file, not assumption. An agreed deviation is recorded as its own status with an approval reference, never counted as a pass, and any open or not-met item is resolved before acceptance.
- Start from the mapping. Each mapped requirement becomes a row.
- Define the statuses. Agree a short set, such as met, deviation agreed, open and not met.
- Fill from evidence. Set each status only when the record is on file.
- Log deviations. Note the reason and who approved it.
- Review before acceptance. Clear or formally accept every open and not-met item.
The tracing work: requirement to source, specification clause, test and record.
The result: for each requirement, the evidence and whether it is met.
Frequently Asked Questions
Q1What is a compliance matrix?
A compliance matrix is a table that lists each requirement with its source, how it is verified, the evidence, and a status showing whether it is met. It gives a single view of how well a design, product or installation meets its specification.
Q2What statuses should a matrix use?
Keep a short, defined set, for example met, deviation agreed, open (evidence still to come) and not met. Define each one in the document so everyone reads them the same way, and do not use a status that is not defined.
Q3Can a deviation be marked as compliant?
No. A deviation is a departure from the requirement that someone with authority has agreed to accept. Record it as its own status with a reference to the approval, so it stays visible rather than being counted as a pass.
Q4When is the matrix filled in?
It is started when the specification is written, updated as tests and inspections are completed, and reviewed before acceptance. A status should come from evidence on file, never from assumption.
Q5How does it relate to requirement mapping?
Requirement mapping traces each requirement to its source, specification clause, test and record. The compliance matrix is where the outcome of that tracing is recorded, so a good matrix is built on a complete mapping.
See It. Understand It. Then Learn How to Engineer It.
Recognising an AGL system visually is the first step. The next step is knowing how to design, install, test, commission and maintain them correctly.
Build Practical AGL Engineering Skills
Go deeper with structured training from Precision AGL Academy, covering:
Learn how each light, sign and circuit works as part of a complete airport lighting system, not just as an isolated diagram.