How Do You Get RCM Certification for a New Electronic Product in Australia?

Detailed Explanation

RCM (Regulatory Compliance Mark) certification is the process by which a supplier demonstrates that their electronic product meets Australian and New Zealand requirements for electrical safety, electromagnetic compatibility (EMC), and — for products containing intentional radio transmitters — radio spectrum compliance. Applying the RCM mark is a legal requirement before placing most consumer and commercial electronic products on the Australian or New Zealand market.

The Three Compliance Domains

Three regulatory domains govern RCM compliance. Most products must address two of the three; products with radio transmitters must address all three.

Electrical safety — governed primarily by AS/NZS 3820:1998 Essential requirements for electrical equipment and product-specific standards. Applies to mains-connected products and equipment operating above the extra-low-voltage threshold (typically 50 V AC / 120 V DC). Battery-powered low-voltage products may have reduced electrical safety obligations but are not exempt from EMC requirements.

Electromagnetic compatibility (EMC) — administered by the ACMA under the Radiocommunications (Electromagnetic Compatibility) Standard 2017, which references CISPR and IEC test standards. The applicable standard depends on your product's category:

For most embedded commercial electronics products, CISPR 32 is the starting point. Confirm the applicable standard by checking ACMA's product category guidance before committing to a test program — selecting the wrong standard wastes testing time and may require retesting. For a detailed walkthrough of the product category decision — including Class A vs Class B within CISPR 32, what qualifies as industrial equipment under IEC 61000-6-4, and what happens when the wrong standard is selected — see which Australian EMC standard applies to your product.

Radio (telecommunications) — governed by the Radiocommunications Act 1992 for any product containing an intentional radio transmitter (BLE, Wi-Fi, LoRa, Zigbee, LTE-M, NB-IoT, or any other radio). For products using a pre-certified radio module, the module's own radio certification covers its intentional transmitter emissions. The host product still requires CISPR EMC testing for non-intentional emissions from its own circuitry — see what a pre-certified radio module's ACMA certification covers and what the host board must still test for the full breakdown. For custom radio designs, full radio certification under the Radiocommunications Act is required separately.

Supplier Self-Declaration vs Government Approval

Australia's RCM scheme operates on a responsible supplier self-declaration model for most product categories. The entity placing the product on the Australian market (the "responsible supplier") declares conformity by preparing a Declaration of Conformity (DoC) supported by accredited laboratory test evidence, then applies the RCM mark — without prior government approval or review. There is no ACMA pre-market approval step for most categories.

For radio-transmitting equipment, an additional requirement applies: the responsible supplier must register the device in the ACMA's compliance labelling database before supplying the product. This registration is still based on self-declaration and accredited test evidence — it is not a separate approval — but it makes the device's compliance record publicly searchable via the ACMA's register.

The RCM Certification Process — Step by Step

Step 1: Determine which standards apply

From the product category table above, identify the applicable CISPR or IEC standard for your product. Also determine whether the product contains intentional radio transmitters requiring Radiocommunications Act compliance, and whether it is mains-connected (electrical safety).

Step 2: Design with compliance in mind

The most cost-effective compliance work happens at the design stage. Minimise switching loop area on the PCB, maintain a solid ground plane, filter common-mode noise on cables, and keep high-speed signal traces short. Waiting until after prototyping to consider EMC typically results in board respins after a failed formal test. How to reduce EMI in PCB design covers the specific PCB layout strategies that have the largest impact on emissions.

Step 3: Pre-compliance testing (internal)

Before engaging a formal test laboratory, conduct EMC pre-compliance testing using a near-field probe set and a spectrum analyser. This is informal, non-accredited testing — it cannot support a Declaration of Conformity — but it reliably identifies dominant emission sources before the formal test, where fixing them is far less expensive than after a failure. Pre-compliance testing typically reduces total certification cost significantly.

Step 4: Formal NATA-accredited lab testing

Engage a NATA (National Association of Testing Authorities)-accredited laboratory to conduct the formal compliance test. NATA is the Australian body that accredits laboratories for specific test methods; only a NATA-accredited lab's test report constitutes recognised evidence supporting a Declaration of Conformity under the ACMA framework.

The formal test covers the conducted and radiated emissions paths defined by the applicable standard, plus immunity tests where the standard requires them. Lab scheduling lead time is typically 1–4 weeks; testing duration is typically 1–3 days for a single-standard product. The test report typically follows 1–2 weeks after testing.

Step 5: Prepare the Declaration of Conformity

With the test report in hand, the responsible supplier prepares the Declaration of Conformity — a legal document asserting that the product meets the applicable standards. It must identify the responsible supplier, the product (name, model number), the standards declared against (by number and edition), and the signatory's name and title. The DoC references and summarises the test report; it does not replace it. For the complete content requirements — what each field must contain, who qualifies as responsible supplier, and when a DoC must be updated — see Declaration of Conformity requirements for RCM.

The Technical Construction File (TCF) — comprising design schematics, test reports, risk assessment, and the DoC — must be maintained for at least 10 years from the date of last supply.

Step 6: Apply the RCM mark

Once the DoC is signed, the RCM mark is applied to the product and, where practical, its packaging. The RCM mark signals to regulators, customers, and distributors that the product has been assessed against the applicable Australian and New Zealand requirements.

Step 7: Register with ACMA (radio products)

For products containing intentional radio transmitters, the responsible supplier must register the device in the ACMA's compliance labelling database before supplying the product. Registration is submitted online via the ACMA's portal; the test report and DoC must exist before registration is submitted.

CE Marking vs RCM

CE (European Economic Area) and RCM (Australia/New Zealand) share many underlying test standards but operate under different legislative frameworks. Where test methods are identical — such as CISPR 32 and the EU's EN 55032 — test data from CE testing can typically support an RCM Declaration of Conformity. But a separate Australian DoC must be prepared, referencing the Australian standard designation, signed by an Australian or New Zealand responsible supplier. Products targeting both markets can often share test data but require separate compliance declarations and separate market-access marks.

Practical Examples

Consumer IoT sensor (BLE, battery-powered): A Brisbane company building a BLE environmental sensor uses an ACMA-registered nRF52 module. The module's radio certification covers the BLE transmitter. The company engages a NATA-accredited lab to conduct CISPR 32 testing on the complete device. After testing, a DoC is prepared, the RCM mark is applied to the device label, and the device is registered in the ACMA's compliance labelling database. Timeline from lab engagement to RCM marking: approximately 6 weeks.

Mains-powered industrial data logger (no radio): A Melbourne manufacturer building a mains-powered industrial data logger applies IEC 61000-6-4 (industrial emissions) and IEC 61000-6-2 (immunity). No radio transmitter is present, so Radiocommunications Act registration is not required. After NATA-accredited testing, a DoC is prepared and the RCM mark is applied. No ACMA registration step is needed.

Design Considerations

• Determine the applicable standard before PCB layout: The CISPR or IEC standard governs which emission limits apply, which frequencies are tested, and what test setups are required. Knowing this before the prototype board is designed avoids discovering that the test setup can't be replicated with the board as laid out.
• Pre-compliance testing as a development gate: Treating pre-compliance EMC scanning as a required milestone — rather than an optional step before the formal lab — systematically catches layout-driven emission problems at a stage where they cost little to fix. A single PCB revision found during pre-compliance testing costs far less than a failed formal test.
• Maintain records during development: The Technical Construction File requires design schematics, test reports, and a risk assessment assembled from project records. Building these records during development is dramatically easier than reconstructing them retrospectively after the product has shipped.
• Lead time for custom radio certification: If the product contains a custom-designed radio (not based on a pre-certified module), full Radiocommunications Act certification can take 4–12 weeks at a test laboratory. This must be built into the product schedule — treating radio certification as a last step frequently delays launch. For compliance strategy and test-readiness assessment across the full hardware stack, Zeus Design's engineering team has experience guiding Australian products through the RCM certification process.
• Sharing CE test data for RCM: Where the EU and Australian standards use identical test methods (common for CISPR 32 / EN 55032), ask your test lab at the outset whether a combined test report covering both markets is possible. This avoids running two separate test programs for the same measurements.

Common Mistakes

• Assuming a pre-certified radio module certifies the complete product: The module's certification covers its intentional transmitter emissions under the conditions defined at the module's own testing. The complete product — including MCU, switching regulator, digital logic, and cables — must still be tested for non-intentional emissions under the applicable CISPR standard. See what a pre-certified module's certification covers and what the host board must still address for a detailed breakdown of the certification boundary.
• Selecting the wrong standard for the product category: CISPR 32 (multimedia equipment), IEC 61000-6-4 (industrial equipment), and CISPR 11 (scientific/ISM equipment) each have different emission limits and test setups. Applying the wrong standard may mean passing a test that doesn't satisfy the actual regulatory requirement — which surfaces only when a regulator or customer's compliance team reviews the DoC.
• Not maintaining the Technical Construction File during development: The TCF is required to support the DoC. Assembling it retrospectively — tracking down schematics, pre-compliance scan records, and risk assessments from a shipped product — is significantly harder and more error-prone than maintaining it as a normal development output.
• Leaving compliance to the end of the project: EMC failures at formal testing typically require PCB layout changes, which require a new prototype spin. Finding the same issues during pre-compliance testing at the design stage costs a fraction of the post-failure iteration.
• Underestimating radio certification timeline for custom radio designs: Full radio certification under the Radiocommunications Act for a custom-designed radio typically takes 4–12 weeks at a test laboratory, depending on lab availability and design complexity. This timeline must be factored into the product launch schedule, not treated as a final formality that can be completed quickly.