RCD and RCBO test result workflow
How to prepare RCD, RCBO and safety switch test records before using the AUWiring entered-criteria test checker.
Test record purpose
RCD and RCBO test records are only useful when the device, test point, multiplier, instrument and criterion are traceable. The calculator compares entered values; it does not publish a universal legal threshold.
The guide keeps the measured result connected to the actual device and source record.
Workflow
- Identify the RCD, RCBO or safety switch device.
- Record the board, circuit and test point.
- Record the test instrument and test condition.
- Enter measured trip time and test multiplier.
- Enter the reviewer criterion used for comparison.
- Store the result with the verification record.
RCD record fields
| Field | Record | Why it matters |
|---|---|---|
| Device reference | Board and device label | Ties result to one device |
| Test point | Location where the test was performed | Avoids mixing records |
| Test multiplier | Entered test condition | Changes interpretation |
| Measured result | Trip time or no-trip result | Primary measured value |
| Instrument record | Instrument ID and date context | Supports traceability |
| Criterion | Reviewer-entered comparison value | Avoids hidden pass language |
Boundaries
- Do not publish universal RCD pass/fail values in the public guide.
- Do not separate a result from its instrument record.
- Do not mix RCD, RCBO and safety switch labels casually.
- Do not treat an entered-criteria comparison as full verification.
RCD and RCBO test result workflow in Australian work
Show how to keep RCD test point, device and instrument data traceable before comparing measured results against entered criteria. The useful record is not just the final number or definition; it is the combination of the entered value, the supply arrangement, the equipment or circuit reference and the decision that still needs project review.
RCD and RCBO test result workflow for Australian entered-criteria verification records Keep the wording in Australian English, use metric units, and treat 230/400 V a.c. at 50 Hz as the ordinary low-voltage context unless the project information states a different value.
Checks that belong beside this page
- Regional scopeAustralia; Australian English; project, instrument, device, local authority and current standards source documents can override worksheet assumptions.
- Standards contextAS/NZS 3000 and AS/NZS 3017 context noted for project review; current standards, device data, test instrument records and site conditions remain controlling inputs.
- Review timingReview cadence: Annual or when RCD checker fields, testing record fields or Australian verification wording changes.. Update trigger: Calculator field change, testing table change, standards context update, instrument practice update or project feedback.
Practical use sequence
For RCD and RCBO test result workflow, begin with the circuit, board, load, cable route, equipment item or measurement record named by this topic. Record the value basis, such as current, voltage, kW, kVA, route length, test value, product rating, tariff value or worksheet field, then note the review boundary so another person can see what this page explained and what still needs a project decision.
The strongest RCD and RCBO test result workflow record is specific enough to be reviewed later. It names the Australian context, keeps the entered assumptions visible, separates calculation support from compliance decisions and shows where a calculator, table, chart or term definition should be opened next.
Record detail to capture
Keep the RCD and RCBO test result workflow note attached to Australia; Australian English; project, instrument, device, local authority and current standards source documents can override worksheet assumptions.. When the page is used during design, estimating, testing, review or study work, write the entered assumption, the source that supplied it, the circuit or equipment label and the person or role that must review the following action.
For RCD and RCBO test result workflow, the review cadence is Annual or when RCD checker fields, testing record fields or Australian verification wording changes. and the update trigger is Calculator field change, testing table change, standards context update, instrument practice update or project feedback.. If the topic connects to RCD test checker, open that page after the current definition, input basis or boundary has been recorded, so the next calculation inherits the right Australian context.
A complete RCD and RCBO test result workflow record leaves four facts visible: why the page was opened, which Australian supply or equipment context applies, which value remains user-entered and what later change would alter the result. That makes the page useful as a working note instead of a loose reference copied away from the project evidence.
- InputsWrite down the entered values and their units before comparing results across calculators or reference pages.
- LocationKeep the value tied to the board, circuit, cable run, equipment terminal, supply point or worksheet row it describes.
- Authority checkCompare the record with current Australian requirements, DNSP or local authority conditions and product information.
- Review trailRetain the date, edition context and reason for the calculation so later changes can be traced.
Connected AUWiring pages
Use the related pages for RCD and RCBO test result workflow when the topic needs a calculator input, lookup table, formula chart or supporting term before the project record is complete. Open RCD test checker first when that page owns the next value or definition.
- RCD test checkerCompare entered measured values with reviewer-entered criteria.
- Fault-loop impedanceKeep circuit and device context aligned.
- Short-circuit currentReview source current context where needed.
- Testing record fieldsRecord instrument, test point and measured result fields.