Clear labelling makes a consumer unit easier to understand, inspect and maintain.
This guide is written for practical use: it focuses on information that should remain understandable after installation, handover, maintenance or staff changes. The objective is not to collect the maximum possible data, but to keep the right data structured, traceable and easy to use at the physical object.
What good labels should do
A useful consumer unit label identifies the circuit in plain language and helps another person understand what the protective device controls. Keep wording short, consistent and specific enough to distinguish similar circuits.
Build a repeatable structure
Use the same naming pattern across the board, keep ratings and device information separate from the circuit name, and avoid abbreviations that only the original installer understands.
Keep the record with the installation
A printed schedule is useful at the board, while a digital record can carry photos, revisions and supporting documents. The two work best together.
Practical focus
For consumer-unit labels, the most useful test is simple: can a competent person standing at the board understand each circuit quickly without guessing what an abbreviation meant years ago? Keep permanent wording concise and move revision history and supporting evidence into the associated digital record.
Keep the panel record structured
A useful panel record separates circuit purpose, position, protective-device information, notes and evidence instead of compressing everything into one label. Structured fields are easier to review, print and update when the installation changes.
- Use plain-language circuit names that another person can understand.
- Keep device ratings and technical attributes separate from the circuit description.
- Record the board identity and location so exported schedules cannot be confused with another panel.
Treat labels and the digital record as one system
The physical schedule is the fast local reference; the digital record is where revisions, photographs and supporting documents can live. They should describe the same installation and be reviewed together after changes.
- Update the printed schedule when circuit use changes.
- Keep dated evidence of significant revisions.
- Avoid using a photograph as the only source of structured circuit data.
Design for maintenance and handover
Documentation is most valuable when the original installer is no longer present. Use names, positions and notes that help a competent person understand what exists without relying on undocumented local knowledge.
How to put this into practice
Start with a small, consistent structure and test it on real objects before scaling. Define the naming rules, required fields, ownership of updates and what should happen after a change. A short documented process is more sustainable than relying on memory.
- Pilot the structure on a handful of real examples.
- Use the same field names and identifiers across labels, exports and digital records.
- Review the process after the first handover or maintenance cycle.
What good implementation looks like
The finished workflow should be understandable by someone who did not create it. A person should be able to identify the object, see the current state, find relevant evidence and understand significant changes without reconstructing the story from filenames or messages.
A practical implementation workflow
Treat the first version as an operational baseline rather than a one-off document. Start with a small representative sample, check that another person can understand the identifiers and fields without verbal explanation, then apply the same structure consistently. The workflow should be simple enough to repeat during installation, handover and later maintenance, because a technically perfect record that nobody keeps updated quickly loses value.
- Pilot the structure on a few real objects before rolling it out in bulk.
- Define which fields are mandatory and which are optional before importing or printing labels.
- Test links, QR codes and exported files on the actual devices and materials used in the field.
- Record who owns the data quality and who is expected to update the record after a change.
Review the record as part of the lifecycle
Good documentation is not finished when the first record is created. Review it whenever the physical object changes, when responsibility is handed over, or when an inspection or maintenance event reveals new information. A short periodic review is usually more reliable than trying to reconstruct several years of undocumented changes later. The aim is to keep the current view accurate while preserving enough history to understand important decisions.
- Update the current state after material changes instead of adding contradictory notes.
- Keep dated evidence for changes that may matter during troubleshooting, audit or handover.
- Retire obsolete information deliberately rather than leaving several competing versions in circulation.
Common mistakes to avoid
Avoid undocumented abbreviations, duplicated circuit names, screenshots used as the only source of truth and physical labels that are not updated after changes. Do not publish sensitive installation details simply because a QR page is convenient.
A sensible next step
Create or review the panel schedule using a consistent naming structure, then keep the printable schedule and the digital object record aligned whenever circuits change.
Electrical work and compliance decisions must follow the rules that apply to the installation and should be carried out or verified by a suitably competent person. This article is about documentation and identification, not a substitute for electrical design or inspection.