Engineering Delivery

Compliance and Standards Matrix Generator

Build a standards compliance matrix that traces your design against the standards it must meet — pick the standards you are assessing against (AS/NZS 3000, AS/NZS 1768, ARPANSA RPS S-1, ISO/IEC 11801, IEC 60529, AS/CA S009) and their key requirements are generated with the clause reference and a verification method already written, then map a design provision against each requirement, record a compliance status, raise non-conformances for the gaps, and export the matrix, the gap register or a printable statement of compliance.

Free ● Live 6 standards

Use it free → Sign in

Free to use, no sign-up needed.

Overview

What the Compliance and Standards Matrix Generator does

A compliance and standards matrix — the requirements-traceability register that pairs each requirement of a standard with how the design or installation meets it and whether it complies — is a core engineering-delivery deliverable on any project held to a code or specification. The hard part is not the table; it is knowing what the standard actually requires, clause by clause, and keeping the assessment traceable. This tool puts that requirement set in a catalogue.

Read the full overview

Pick the standards you are assessing against and their key requirements are generated with the clause reference, the requirement category and a verification method already written. Six standards ship: AS/NZS 3000 (the Wiring Rules), AS/NZS 1768 (lightning protection), ARPANSA RPS S-1 / ICNIRP (RF EME exposure), ISO/IEC 11801 (generic structured cabling), IEC 60529 (the IP enclosure code) and AS/CA S009 (customer telecommunications cabling). A project can hold several at once, so a multi-standard assessment becomes one compliance pack.

You then work like a spreadsheet you assess into: against each standard requirement, record the design provision that meets it, set the compliance status (Compliant / Partial / Non-Compliant / N/A; blank is Not Assessed), and reference the evidence. Compliance Refs number themselves from the standard and category. Setting a requirement Non-Compliant raises a non-conformance on a corrective-action register. The Summary tracks the assessment progress and a conformance rate, and you export the matrix, the open gaps or the non-conformance register as CSV, a JSON project file, or a formatted statement of compliance for print or PDF. Catalogue requirements are paraphrased working summaries to confirm against the published standard, and design provisions and statuses are always blank, so the tool records your assessment and never fabricates a compliance claim.

Capabilities 6

A catalogue, not a blank matrix

Pick the standards you are assessing against and their key requirements are generated with the clause reference, the requirement category and a verification method written for every item. Six standards ship — AS/NZS 3000 (Wiring Rules), AS/NZS 1768 (lightning protection), ARPANSA RPS S-1 / ICNIRP (RF EME exposure), ISO/IEC 11801 (structured cabling), IEC 60529 (IP enclosure rating) and AS/CA S009 (customer cabling) — each laid out across the relevant requirement categories.

Design provision against standard requirement

The matrix pairs each standard requirement with the design provision that meets it — what in your design or installation satisfies the clause — and a compliance status (Compliant / Partial / Non-Compliant / N/A; blank is Not Assessed), with an evidence reference and a verification method. That is the traceability a compliance matrix exists to provide.

One project, many standards

A project is a compliance pack. Add several standards at once — the electrical, lightning-protection, RF-exposure and cabling standards a comms site is held to — and every row carries the standard it belongs to. The grid filters by standard and category, and the Summary rolls a conformance rate up per standard and per category.

Non-conformances and corrective actions

Setting a requirement to Non-Compliant raises a non-conformance on a corrective-action register, where you set severity, owner, target and close-out. “Raise from non-compliances” pulls every gap in at once, the tick verifies and closes a non-conformance and flips its requirement to Compliant, and the register exports as a CSV gap / corrective-action deliverable.

Honest requirements, never a fabricated claim

Catalogue requirement text and clause references are paraphrased working summaries of the published standards (whose text is copyright) — a defensible starting point to confirm against the actual published edition, never a substitute for it. Design-provision and status cells always start blank, so the tool records exactly the compliance assessment you make and never invents a compliance claim.

Tailored to the client, and the export

Every column is customisable, the compliance-Ref pattern is built from tokens ({std}, {cat}, {seq:n}), and the layout saves as a named client template. Export the matrix or the open gaps to CSV (project-headed, formula-injection safe), copy to the clipboard for an Excel template, export the non-conformance register, save the project to JSON, or print a formatted statement of compliance with a declaration block straight to PDF. Everything auto-saves to the browser.

Inputs and outputs

What goes in, what comes out

Inputs 6

The standard(s) you are assessing against, chosen from the catalogue (AS/NZS 3000, AS/NZS 1768, ARPANSA RPS S-1, ISO/IEC 11801, IEC 60529, AS/CA S009)
Project details (name, client, project number, revision, date, compliance assessor, site)
A column layout per client (or a saved template) and a compliance-Ref pattern
A design provision recorded against each standard requirement — what in the design or installation meets it
A compliance status (Compliant / Partial / Non-Compliant / N/A / Not Assessed) and an evidence reference per requirement
Requirement text confirmed or edited against the published standard; optional ad-hoc requirements typed in or pasted from Excel

Outputs 7

A standards compliance / requirements-traceability matrix with the clause reference and verification method per requirement
Auto-generated compliance Refs from the standard and category (e.g. EL-ERTH01, LP-TEST02)
A per-standard and per-category conformance summary with progress bars and a compliance statement
A non-conformance / corrective-action register raised from the non-compliances
CSV matrix, CSV open-gaps and CSV non-conformance-register exports (project-headed, formula-injection safe)
Clipboard export (tab-separated for Excel) and a JSON project file, plus browser auto-save
A printable, declaration-ready statement of compliance (PDF via browser print)

Standards & methodology

AS/NZS 3000 (Electrical installations — the Wiring Rules)
AS/NZS 1768 (Lightning protection)
ARPANSA RPS S-1 / ICNIRP (RF electromagnetic energy exposure)
ISO/IEC 11801 (Information technology — generic cabling for customer premises)
IEC 60529 (Degrees of protection provided by enclosures — the IP Code)
AS/CA S009 (Installation requirements for customer cabling) — catalogue requirements are paraphrased working summaries to confirm against the published standard

Use cases

When to use this tool

01Producing a standards compliance / requirements-traceability matrix for a design or installation
02Demonstrating an electrical installation against AS/NZS 3000 (the Wiring Rules)
03Assessing a comms site against AS/NZS 1768 lightning protection and earthing requirements
04Showing RF EME exposure compliance against ARPANSA RPS S-1 / ICNIRP
05Tracing a structured-cabling installation against ISO/IEC 11801
06Confirming enclosure IP ratings against IEC 60529 and customer cabling against AS/CA S009
07Building a multi-standard compliance pack covering several standards on one project
08Mapping a design provision against each standard requirement with an evidence reference
09Raising and tracking non-conformances and corrective actions for the gaps
10Producing a printable, declaration-ready statement of compliance as a client deliverable

FAQ

Frequently asked questions

Not here? Ask us

What does the catalogue actually generate?

You pick the standards the design or installation is held to — AS/NZS 3000, AS/NZS 1768, ARPANSA RPS S-1, ISO/IEC 11801, IEC 60529 or AS/CA S009 — and the tool generates each standard’s key requirements. Every requirement ships with its clause reference, a requirement category and a default verification method (inspection, test, analysis, document review, demonstration). You then map a design provision against each one and record a compliance status.

Are the requirements the actual standard text?

No — and this matters. The requirement text and clause references are paraphrased working summaries of the published standards, whose text is copyright. They are a defensible starting point, not a substitute for the standard: confirm each against the actual published edition and edit any cell to suit. The tool never invents a compliance claim either — design-provision and status cells always start blank.

Can one matrix cover several standards?

Yes. A project is a multi-standard compliance pack. Add as many standards as the project is held to — the electrical, lightning-protection, RF-exposure and cabling standards a comms site needs — and every row carries the standard it belongs to. The grid filters by standard and category, and the Summary rolls a conformance rate up per standard and per category.

How do the compliance Refs work?

Each requirement is numbered from the standard code and the category using a pattern you control on the Setup tab: {std} for the standard code, {cat} for the category, and {seq:n} for a zero-padded sequence. The default {std}-{cat}{seq:2} gives EL-ERTH01, LP-TEST02. Auto-Ref fills blanks and Renumber-all re-sequences everything.

What happens to non-compliances?

Setting a requirement to Non-Compliant raises a non-conformance (NCR) on a corrective-action register, where you set severity, owner, target date and corrective action. “Raise from non-compliances” pulls every gap in at once. The tick verifies and closes a non-conformance and flips its requirement to Compliant. Export the register as your gap / corrective-action deliverable.

What can I export?

Export the full matrix or just the open gaps to CSV (project-headed and formula-injection safe), export the non-conformance register, copy the matrix to the clipboard as tab-separated text for an Excel template, or save the whole project to JSON. For a near-final client deliverable, print a formatted statement of compliance — grouped by standard and category with a compliance summary and a declaration / sign-off block — straight to PDF.

Free, no sign-up