CodeMark Australia building product certification and certificate verification
Prepare the product scope, National Construction Code evidence and quality plan for certification. Check a live certificate against the actual product and installation before relying on it.
Australian Building Codes Board and JASANZ-accredited CodeMark certification bodies
Timing
Ask the certification body to quote evaluation, audit and surveillance. Under the scheme rules a certificate is valid for three years unless suspended or withdrawn. Initial surveillance is within 12 months of issue and routine intervals are no longer than 12 months.
Reviewed
Inside this guide
4 steps · 4 templates
Who it applies to
Manufacturers, importers and other applicants seeking a Certificate of Conformity for a building product or system, and project teams specifying or accepting it under the National Construction Code (NCC).
What you’ll produce
A certificate covering defined products, uses and NCC provisions if granted, a current register entry and a record of how a project meets the conditions.
For each project, verify the adopted NCC edition and state or territory provisions. Use the complete certificate and referenced instructions. Match the product configuration, listed clauses, permitted construction and installation conditions to the project.
Confirm the applicable edition, sites, products or service boundary and the certification route. Budget for assessment, changes needed to pass, and maintaining certification.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
What to review each week
Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
CodeMark Australia kickoff brief
Business reason and required outcome [Contract, obligation or approval]
Scope and exclusions [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones [Date, source and owner]
Executive sponsor and authorized signer [Names]
Project lead and backup [Names]
First workstream Define the product and intended uses · Product owner + building code specialist [Name and due date]
People, effort and external costs [Estimate, owner and contingency]
Evidence folder and reviewer access [Location, access owner and review date]
Decisions and blockers [Item, options, owner and decision date]
First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START
How this works in practice
Two questions to check scope
Does the proposed use fit every relevant certificate limitation and referenced drawing?
Who can stop a substitution or design change before a certificate scope gap reaches site?
Worked scenario
A facade supplier proposes a panel system for Australian projects. The certifier agrees which assembly and NCC provisions will be evaluated. On a later project, the buyer checks the register and the building surveyor reviews a proposed substrate change against the current certificate.
Review electrical equipment evidence separately for any in-scope products in the project.
FROM THE SOURCE
Cases and numbers
NSW notice · 2019 withdrawals
9Cladding certificates listed as withdrawn by NSW
Register status can change after a product is specified
The NSW notice identifies nine withdrawn CodeMark certificates and explains that practitioners would need other evidence of suitability to support a compliant use of those products. It lists the certificate numbers and associated products.
What to check Save a dated register check at approval and recheck before a substitution or installation. Keep the certificate number searchable in project records.
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Define the product and intended uses
Who Product owner + building code specialistWhen Before requesting a certifier proposal
List variants, components, production sites and intended installation conditions. Map proposed claims to the applicable NCC Performance Requirements or Deemed-to-Satisfy provisions. Check the certification body’s accreditation and get a quote with evaluation, surveillance and renewal costs.
What to produce
CodeMark scope and NCC evidence matrixSpreadsheet
Gather first
Product drawings
Manufacturing locations
Proposed claims
Applicable NCC edition and state variations
JASANZ accreditation scope
How to prepare it
Give each assembly and variant a unique row. Record product, components, substrate, fixing system, installation limits and factory. Mark any options that will remain outside the proposed scope.
Link each performance claim to the applicable NCC provision and evidence. Record the report revision, tested configuration, lab and any gap. Have the building code specialist and certification body agree the assessment boundary.
Obtain a written proposal showing expected evidence, evaluation and surveillance scope, price and which findings could require retesting.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional assembly
Marshline FP-12 rainscreen assembly. Engineering lists the specific panel, supporting rail and substrate represented by its drawings.
Open scope item
A second substrate appears in the marketing draft. No evidence has yet been reviewed for that configuration. The Product owner removes it from the proposed claim pending assessment.
Sign-off
Product owns the claim, Engineering owns the evidence, and the building code specialist checks the edition and project assumptions.
Check before handing it over
Every claim has a verified NCC reference, a matching configuration and an evidence owner or named gap.
Give the signed matrix and complete referenced records to the certification body.
Assemble test evidence and the Product Quality Plan
Who Engineering + factory quality + certification bodyWhen Before evaluation and factory review
Reconcile tested samples and reports to controlled drawings. Agree where new tests or technical assessments are needed. Build the Appendix 1 Product Quality Plan around agreed procedures, owners, manufacturing and traceability checks, complaints and recall. Track findings and obtain written closeout.
What to produce
CodeMark evaluation and Product Quality PlanMemo
Gather first
Agreed scope matrix
Full lab reports
Controlled drawings and specifications
Factory process map
Appendix 1 requirements
How to prepare it
Map the bill of materials, installed configuration and production process to the tested sample and report. Get written decisions on variations and evidence gaps.
For each Appendix 1 requirement, name the procedure, person, frequency and evidence. Include incoming checks, manufacturing inspections, release, traceability, corrective action, complaints and recall.
Review records from one trial lot before submitting. Track each evaluation finding with the requested action, owner, due date and certifier confirmation.
Worked example
Fictional details. Use the same fields with evidence from your work.
Incoming check
For fictional FP-12, receiving verifies the specified panel core against the approved bill of materials. The recorded lot links to its supplier evidence.
Trace exercise
Quality starts with a dispatched serial or lot and retrieves the factory inspection, approved component batch and customer shipment.
Finding example
Work instruction revision differs from the approved drawing. Engineering reconciles the revisions, trains the line lead and submits the new production record for closeout.
Check before handing it over
A reviewer can link the tested configuration to production controls and verify open and closed findings.
Give the certifier a dated copy. Keep the approved version accessible to production and field quality staff.
Who Procurement + designer + building surveyorWhen Before specifying, purchasing or substituting
Search the certificate number and retrieve the current complete certificate. Compare the model, version, conditions, code edition, installation and underlying assembly to the design and order. Refer differences in scope to the designer and appropriate authority before relying on the certificate.
What to produce
CodeMark project acceptance recordChecklist
Gather first
Current complete certificate and register entry
Project drawings and specifications
NCC edition and local variations
Purchase order and installation instructions
How to prepare it
Search the advertised certificate number in the JASANZ CodeMark register. Save the verification date, status, issuer and complete certificate version with any referenced instructions.
Compare the specified product, application and installation with each certificate condition. Check model, site use, construction and components against the actual order and design.
Assign the project designer and appropriate approval authority any scope gaps. Record their decision, additional evidence and site checks before accepting a substitution.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional substitution
FP-12’s installation drawing specifies one substrate. A contractor proposes a different substrate. Procurement pauses acceptance while the designer checks the certificate and confirms how the new design will be substantiated.
Retained evidence
Current certificate and public register status, project drawing revision, marked comparison, approval decision and inspection evidence.
Check before handing it over
The acceptance decision identifies what the certificate covers and what evidence supports every difference.
Attach the approval to the procurement and construction records, then give Site Quality the conditions to verify.
Who Certificate holder + Quality + certifierWhen After issue and before approved product changes
Schedule surveillance and review any product, process or code change with the certifier. Keep the Product Quality Plan and traceability current. If suspended or withdrawn, notify existing customers and cease using the certificate, mark and number as required by Rule 35. Track renewal against actual expiry.
What to produce
CodeMark surveillance and change registerSpreadsheet
Gather first
Certificate and expiry
Product Quality Plan
Surveillance reports
Product change requests
Complaints, dispatch records and recall procedures
How to prepare it
Record issue, first surveillance, routine surveillance, supply-chain review and expiry as distinct rows or fields. Confirm dates with the certification body.
Before changing specifications, processes or factories, record what changes, affected batches and evidence. Send the required notice and retain the certifier’s decision and any amended certificate.
If the listing is suspended or withdrawn, notify existing customers and cease use of the certificate and mark as required. Where a product fails to meet the BCA or certificate claims, activate the Rule 35 recall and reporting process.
Worked example
Fictional details. Use the same fields with evidence from your work.
Fictional dates
Certificate issued 18 November 2026. Initial surveillance due by 18 November 2027. Confirm the exact expiry and subsequent dates with the certifier.
Change ticket
Proposed adhesive substitution. Quality identifies affected parts, keeps the existing design in production and asks the certifier to confirm the evidence and approval needed.
Check before handing it over
The owner can show the current certified scope, next review date, decisions on changes and who receives status alerts.
Keep the register with Quality and send revised approved claims to Sales and the installation team.