Compliance & Standards Forms
The 25 forms that connect and validate the evidence created everywhere else in the AGL Engineering Documentation System — mapping every ICAO, FAA, IEC, BIS/IS, DGCA, project-specification, and tender requirement through design, procurement, installation, testing, inspection, and maintenance, to a documented final acceptance. This is the layer that turns "ICAO compliant" from a slogan into a traceable, evidenced fact.
Where this fits — every other division in this library creates evidence — a design calculation, a delivery record, an installation checklist, a test report. Division 21 doesn't duplicate any of that. It's the layer that asks, for every requirement in every applicable standard: which clause, does it apply here, how was it designed for, which product satisfies it, how was installation verified, which test proves it, and what's the final evidence — with the Requirement Traceability Matrix (CMP-18) as the master record tying it all together.
A · Compliance & Requirement Control
6 of 6 formsCMP-01 Technical Compliance Matrix Matrix
Purpose
Master matrix for verifying the technical compliance of an AGL system, equipment item, or project against every applicable requirement in one controlled record.
Key Fields
- Compliance Matrix ID and project
- Equipment / system
- Requirement number and description
- Applicable standard and clause reference
- Project requirement
- Proposed solution
- Compliance status
- Supporting document / evidence reference
- Remarks
CMP-02 ICAO Compliance Checklist Checklist
Purpose
Systematically reviews the ICAO Annex 14 provisions affecting the project — runway, taxiway and approach lighting, PAPI/APAPI, signs, stop bars — against a specific document and edition rather than a generic “ICAO compliant” claim.
Key Fields
- ICAO document / reference and edition
- Applicable provision
- Project applicability
- Requirement
- Project implementation
- Evidence
- Compliance status
- Reviewer and remarks
CMP-03 FAA Compliance Checklist Checklist
Purpose
Verifies applicable FAA Advisory Circular requirements where FAA standards are contractually, technically, or project-wise applicable — CCR, isolation transformers, connectors, cables, photometry, and equipment qualification.
Key Fields
- FAA document / AC number
- Applicable section
- Requirement
- Design response
- Product compliance
- Test evidence
- Status and remarks
CMP-04 IEC Compliance Checklist Checklist
Purpose
Verifies applicable IEC requirements for electrical equipment, control systems, protection, earthing, testing, and instrumentation associated with the AGL installation.
Key Fields
- IEC standard and edition
- Clause
- Requirement
- Applicable equipment
- Design response
- Evidence
- Compliance status
CMP-05 BIS/IS Compliance Checklist Checklist
Purpose
Controls compliance with applicable Indian Standards / BIS requirements for cables, transformers, earthing, connectors, and electrical installation and testing.
Key Fields
- IS / BIS standard number and edition or amendment
- Clause
- Requirement
- Product / system
- Compliance evidence
- Certificate
- Test report
- Status
CMP-06 DGCA Requirement Checklist Checklist
Purpose
Documents compliance with applicable Indian civil aviation regulatory requirements — aerodrome visual aids, markings, signs, lighting, and inspection or maintenance obligations.
Key Fields
- DGCA reference
- Requirement
- Applicability
- Project implementation
- Evidence
- Status
- Remarks
B · Project & Tender Compliance
4 of 4 formsCMP-07 Project Specification Compliance Matrix
Purpose
Verifies compliance against the actual project specification, tracing each clause through the design, equipment, installation, and testing response all the way to field evidence.
Key Fields
- Specification section and clause number
- Requirement
- Design response
- Equipment response
- Installation response
- Testing response
- Evidence
- Status
CMP-08 Tender Compliance Matrix Matrix
Purpose
Establishes compliance against the tender / BOQ / technical specification before and during project execution, flagging deviations and alternative proposals for review.
Key Fields
- Tender clause
- BOQ item
- Technical requirement
- Offered solution
- Manufacturer and model
- Deviation
- Supporting document
- Compliance / remarks
CMP-09 Product Compliance Certificate Certificate
Purpose
Formally documents that a proposed product satisfies the applicable standards, project specification, and technical requirements before it is approved for use.
Key Fields
- Product, manufacturer, model, part number
- Application
- Applicable standards and project specification
- Tests, certificates, datasheets
- Declaration (compliant / partially / non-compliant)
- Approval — vendor, contractor, reviewer, client
CMP-10 Material Compliance Certificate Certificate
Purpose
Verifies that supplied materials conform to approved technical requirements before they're accepted onto site.
Key Fields
- Material description, manufacturer, model, batch / lot, quantity, PO
- Approved submittal
- Datasheet and certificate of conformity
- Test certificate and inspection record
- Final status — accepted / rejected / conditional
C · Design, Installation & Testing Compliance
5 of 5 formsCMP-11 Design Compliance Review Review
Purpose
Verifies the engineering design satisfies all applicable requirements before it's released for procurement or construction.
Key Fields
- Design criteria and lighting layout
- Series circuits, CCR, transformer, cable, fixture selection
- PAPI, signs, approach lighting, ALCMS
- Earthing, protection, photometry
- Evidence — drawings, calculations, submittals
- Result — compliant / comments / non-compliant
CMP-12 Installation Compliance Review Review
Purpose
Verifies that installed systems match the approved design and applicable requirements — equipment location, identification, cabling, fixtures, earthing, workmanship, and as-built condition.
Key Fields
- Equipment location and identification
- Cable, fixture, transformer, connector installation
- Earthing, signs, PAPI, ALCMS
- Workmanship and as-built condition
- Evidence — installation records, inspection reports, photographs
CMP-13 Testing Compliance Review Review
Purpose
Confirms testing has been performed according to applicable requirements — insulation resistance, continuity, earth resistance, series circuit, CCR, transformer, fixture, PAPI, sign, ALCMS, photometry, FAT/SAT.
Key Fields
- Requirement and required test
- Test report and test date
- Test equipment and calibration status
- Result and compliance status
CMP-14 Maintenance Compliance Review Review
Purpose
Verifies that AGL maintenance practices — preventive maintenance, inspection frequency, equipment and photometric testing — satisfy applicable requirements.
Key Fields
- Preventive maintenance and inspection frequency
- Equipment and photometry testing
- CCR, transformer, fixture, PAPI, sign, ALCMS maintenance
- Evidence — PM records, inspection records, test reports, work orders, failure records
CMP-15 Inspection Compliance Review Review
Purpose
Verifies that inspection activities — daily through annual, day and night, airside — are being performed against applicable requirements.
Key Fields
- Inspection type — daily, weekly, monthly, quarterly, annual, day / night, airside
- Requirement and inspection checklist
- Actual result and defect
- Corrective action and closure
D · Standards Management
2 of 2 formsCMP-16 Standards Reference Register Register
Purpose
Maintains the controlled list of standards referenced by the project across ICAO, FAA, IEC, BIS/IS, DGCA, and any other contractually applicable body.
Key Fields
- Standard ID and organization
- Standard number, title, edition, amendment
- Publication date
- Applicable discipline and applicability
- Controlled copy / reference
- Review date
CMP-17 Applicable Standards Register Register
Purpose
Distinguishes standards that merely exist from standards that are actually applicable to the project — a project should not claim compliance with every standard in the library.
Key Fields
- Standard and edition
- Project applicability
- Equipment / system
- Contractual, regulatory, design, testing, maintenance applicability
- Approval and status — applicable / partially applicable / not applicable
E · Requirement Traceability & Deviation Control
3 of 3 formsCMP-18 Requirement Traceability Matrix Matrix
Purpose
The master link between every significant requirement and the evidence proving compliance — requirement through design, procurement, installation, testing, and inspection, to final acceptance. One of the most important forms in the division.
Key Fields
- Requirement ID, source and clause
- Requirement text / summary
- Design response and equipment
- Installation, test and inspection evidence
- Final evidence — acceptance / handover
- Compliance status
CMP-19 Deviation Request Request Form
Purpose
Formally requests approval for a deviation from an applicable requirement, with technical justification, risk, and impact assessed before work proceeds.
Key Fields
- Deviation ID and requirement / standard / clause
- Existing requirement and proposed deviation
- Reason and technical justification
- Risk and impact
- Supporting drawing, calculation, datasheet, test evidence
- Approval and status
CMP-20 Technical Deviation Register Register
Purpose
Maintains the master register of approved, rejected, and pending deviations across design, material, installation, testing, and operational categories.
Key Fields
- Deviation ID, requirement and description
- Reason and risk
- Proposed solution
- Approval status, authority and date
- Expiry / review date
- Closure status
F · Compliance Gap & Audit
4 of 4 formsCMP-21 Compliance Gap Analysis Analysis
Purpose
Identifies where current project conditions don't fully satisfy applicable requirements, across design, material, installation, testing, documentation, maintenance, regulatory, and operational categories.
Key Fields
- Requirement
- Current condition and required condition
- Gap and risk
- Corrective action and responsible person
- Target date and closure evidence
- Priority — critical / high / medium / low
CMP-22 Compliance Review Record Record
Purpose
Formally records a periodic or project-stage compliance review — design, procurement, installation, pre-commissioning, commissioning, final acceptance, or periodic operational review.
Key Fields
- Review date, team and scope
- Standards reviewed
- Findings and gaps
- Deviations
- Corrective actions
- Final status
CMP-23 Standards Revision Tracker Tracker
Purpose
Monitors revisions to referenced standards and assesses whether a new edition is actually applicable to an existing project before treating it as a requirement.
Key Fields
- Standard, previous edition, new edition, revision date
- Change identified
- Applicable to project?
- Impact assessment
- Required action and responsible engineer
- Implementation status
CMP-24 Compliance Audit Checklist Checklist
Purpose
Performs a systematic audit of AGL compliance across standards, design, procurement, installation, testing, inspection, maintenance, and documentation.
Key Fields
- Applicable standards identified and editions verified
- Design requirements, calculations, drawings
- Approved products, compliance certificates, submittals
- Installation vs. approved design; materials and workmanship
- Required tests completed; calibration status
- Inspections completed and defects closed
- PM records available
- As-built drawings, O&M manuals, certificates, asset records
- Result — compliant / observation / non-conformance
G · Final Compliance
1 of 1 formsCMP-25 Final Compliance Certificate Certificate
Purpose
The formal final declaration that the completed AGL system has been reviewed against every applicable requirement, standard, specification, and approved deviation.
Key Fields
- Project, airport, system, contract
- Compliance review period
- Applicable standards, specifications, approved deviations
- Final verification — design, material, installation, testing, inspection, photometric, safety, documentation, asset
- Outstanding NCRs and deviations
- Final status — fully compliant / compliant with approved deviations / not compliant
- Certification — prepared by, technical reviewer, QA/QC, PM, client, authority
How Division 21 Connects
These 25 forms don't stand alone — each one draws evidence from another division and feeds it back into the master compliance record.
Compliance Traceability Flow
The seven categories in this division follow the compliance chain from source requirement to closed-out acceptance:
Related Divisions
- Division 02 — Design & Engineering Forms (design evidence)
- Division 03 — Procurement & Material Approval Forms (product / material evidence)
- Division 04 — Installation Forms (installation evidence)
- Division 06 — Testing Forms (test evidence)
- Division 15 — Photometry Forms (photometric evidence)
- Division 19 — ALCMS Forms (control-system compliance)
The Control Principle
A statement such as "ICAO compliant," "FAA compliant," or "IEC compliant" is not by itself treated as sufficient evidence. The compliance system is built to answer, for every requirement: which clause? does it apply to this project? how was it addressed in the design? which product or material satisfies it? how was installation verified? which test proves compliance? which inspection confirms the installed condition? was any deviation approved? and what is the final evidence? That chain — not the label — is what CMP-18, the Requirement Traceability Matrix, exists to hold together.
Frequently Asked Questions
Quick answers about the 25 Division 21 compliance and standards forms, how they are grouped, and how they build a traceable compliance record.
Q1What is Division 21 — Compliance & Standards Forms in the AGL Engineering Forms & Templates library?
Division 21 is a set of 25 compliance and standards forms (CMP-01 to CMP-25) that connect and validate the evidence created across the AGL Engineering Documentation System. They map ICAO, FAA, IEC, BIS/IS, DGCA, project-specification and tender requirements through design, procurement, installation, testing, inspection and maintenance to a documented final acceptance. The forms are grouped into seven categories.
Q2Why is a statement such as “ICAO compliant” not treated as enough evidence?
The division treats a label such as “ICAO compliant”, “FAA compliant” or “IEC compliant” as a claim, not as proof. For every requirement the forms ask which clause applies, whether it applies to this project, how it was addressed in design, which product or material satisfies it, how installation was verified, which test proves it, which inspection confirms the installed condition, whether any deviation was approved, and what the final evidence is. The Requirement Traceability Matrix (CMP-18) holds that chain together.
Q3Which checklists cover ICAO, FAA, IEC, BIS/IS and DGCA requirements?
The Compliance & Requirement Control category has six forms: Technical Compliance Matrix (CMP-01), ICAO Compliance Checklist (CMP-02), FAA Compliance Checklist (CMP-03), IEC Compliance Checklist (CMP-04), BIS/IS Compliance Checklist (CMP-05) and DGCA Requirement Checklist (CMP-06). The ICAO checklist reviews the Annex 14 provisions affecting the project against a specific document and edition rather than a generic “ICAO compliant” claim.
Q4How do the project, tender, product and material compliance forms differ?
Project Specification Compliance (CMP-07) traces each specification clause through the design, equipment, installation and testing response to field evidence. Tender Compliance Matrix (CMP-08) checks compliance against the tender, BOQ and technical specification, flagging deviations and alternative proposals. Product Compliance Certificate (CMP-09) documents that a proposed product satisfies the applicable standards before it is approved for use, and Material Compliance Certificate (CMP-10) verifies that supplied materials conform to approved technical requirements before they are accepted onto site.
Q5What is the Requirement Traceability Matrix (CMP-18) used for?
The Requirement Traceability Matrix is the master link between every significant requirement and the evidence proving compliance, running from the requirement through design, procurement, installation, testing and inspection to final acceptance. Its key fields include the requirement ID, source and clause, design response and equipment, installation, test and inspection evidence, final evidence and compliance status. It is one of the most important forms in the division.
Q6How are technical deviations requested and tracked?
A Deviation Request (CMP-19) formally asks for approval to deviate from an applicable requirement, with technical justification, risk and impact assessed before work proceeds. The Technical Deviation Register (CMP-20) is the master register of approved, rejected and pending deviations across design, material, installation, testing and operational categories, including approval authority, expiry or review date and closure status.
Q7What is the difference between the Standards Reference Register, the Applicable Standards Register and the Standards Revision Tracker?
The Standards Reference Register (CMP-16) is the controlled list of standards referenced by the project, with edition and amendment. The Applicable Standards Register (CMP-17) separates standards that merely exist from those actually applicable to the project, because a project should not claim compliance with every standard in the library. The Standards Revision Tracker (CMP-23) monitors revisions and assesses whether a new edition is applicable to an existing project before it is treated as a requirement.
Q8Which forms handle compliance reviews, gap analysis, audit and final certification?
Stage reviews are covered by the Design, Installation, Testing, Maintenance and Inspection Compliance Reviews (CMP-11 to CMP-15). Compliance Gap Analysis (CMP-21) identifies where current conditions do not satisfy requirements, Compliance Review Record (CMP-22) records periodic or stage reviews, and Compliance Audit Checklist (CMP-24) performs a systematic audit. The Final Compliance Certificate (CMP-25) is the formal declaration that the completed system was reviewed against every applicable requirement, standard, specification and approved deviation, with a final status of fully compliant, compliant with approved deviations, or not compliant.
Q9Can the Division 21 forms be downloaded, and how does this division connect to the others?
Yes. Each entry has a Download as Word button that produces an uncontrolled sample Word template with letterhead, a document-control block, ruled entry fields and a three-tier approval table (Prepared By, Reviewed By, Approved By) as layout only, to be adapted under your own document-control system before use. Division 21 does not duplicate evidence created elsewhere: it draws design evidence from Division 02, product and material evidence from Division 03, installation evidence from Division 04, test evidence from Division 06, photometric evidence from Division 15 and control-system compliance from Division 19, and ties them together in the master compliance record.
MEET THE STANDARD. UNDERSTAND WHY IT EXISTS.
A compliance form confirms a requirement was met — but real standards competence means understanding what ICAO Annex 14, FAA Advisory Circulars and IS 12290/IS 7785 are actually protecting against, not just citing the clause number.
Take your knowledge further with Precision AGL Academy.
Build Complete AGL Project Capability
Learn how technical AGL work connects with:
Develop the knowledge to not only record the work, but understand the engineering and project-management principles behind it.
Plan the project. Understand the engineering. Deliver with confidence.
Follow the Academy
Important Notice, Disclaimer & Limitation of Liability
Please read before relying on any content on this page or on any template downloaded from it.
- Purpose and intended users. This page is an independent educational and informational reference for competent, suitably trained and authorised airfield ground lighting (AGL), aerodrome electrical and project personnel. It is not professional engineering, legal or regulatory advice, and using it does not create any professional or client relationship.
- Sample templates, not controlled documents. Forms, checklists, registers, reports, certificate layouts and Word downloads are generic samples. They are uncontrolled copies and are not approved work instructions, procedures, permits, certificates, test or calibration records, or regulatory records. Letterheads, form numbers, revision labels, dates, document-control blocks and approval tables are layout only. Review and adapt a template under your own document-control system before any use; signatures on it carry no authority unless made under your own approved system. Precision AGL Academy does not issue, approve, certify or take responsibility for any record completed using a template, and does not receive or store such records.
- Safety. Work on series circuits, constant current regulators (CCRs), isolating transformers, cables, connectors and control equipment can be fatal. Always apply the aerodrome’s permit-to-work and isolation/LOTO procedures, prove dead, use correctly rated instruments and PPE, and follow the manufacturer’s instructions. Nothing here authorises work on live equipment or the bypassing of any safety device or interlock.
- Certificates, approvals and compliance. A completed template is not a certificate, approval, acceptance, release, permit or evidence of compliance, and listing a certificate, approval or sign-off field does not make the document valid. Reading this material or completing a template confers no certification, accreditation, competency assessment or authorisation to work on any aerodrome.
- Aviation operations. Nothing here authorises return to service, a change of operating category (CAT I/II/III), a NOTAM, a flight-inspection outcome or any aerodrome certification decision. These rest with the aerodrome operator, the air navigation service provider and the competent regulator.
- Standards, regulations and contracts. References to ICAO, FAA, IEC, IEEE, ISO, BIS, DGCA and other standards are for orientation only. They are summarised, may be incomplete or out of date, and standards are revised from time to time. Consult the current official editions. Following this content does not guarantee compliance with any law, standard, contract or regulatory approval. Contract, specification and official requirements always prevail, and nothing here is a contract document or legal advice.
- Personal and confidential data. Some templates have fields for names, signatures, training or competency records, and incident or injury details. If you record personal or confidential information on a template, you are responsible for handling it lawfully, including under India’s Digital Personal Data Protection Act, 2023 and your contracts. Word files are generated in your browser; the content you enter is not sent to us.
- Generic content; no warranty. Field lists, sequences, categories and example values are generic and indicative; real projects, installations and contracts differ. Content is provided “as is” and “as available”, without warranty of any kind, express or implied, including accuracy, completeness, currency or fitness for a particular purpose.
- Limitation of liability. To the fullest extent permitted by applicable law, Precision AGL Academy and its owners, authors and contributors are not liable for any injury, death, loss, damage, downtime, penalty, contractual dispute or regulatory consequence, whether direct or indirect, arising from the use of, reliance on, or inability to use this content or any template downloaded from it. Nothing in this notice excludes or limits any liability that cannot lawfully be excluded or limited.
- Independence and trademarks. This is an independent publication, not affiliated with or endorsed by ICAO, the FAA, the IEC, BIS, DGCA, any airport, regulator, certification body or equipment manufacturer. Third-party names, standard designations and trademarks, including Microsoft Word and Excel, belong to their respective owners and are used for identification only.
- Copyright and use. © 2026 Precision AGL Academy. All rights reserved. You may view this page and use downloaded templates for personal reference, internal training and, once adapted under your own document-control system, your own internal project records, keeping this notice attached to unadapted copies. You may not present them as approved or controlled documents, or copy, republish, redistribute, scrape or commercially use the library without our prior written permission.
- Corrections. Content is reviewed periodically, with no obligation to update. To report an error, safety concern or rights issue, write to precisionaglsolutions@gmail.com.