# Check arc flash and electrical safety labels against their source

> Confirm a hazard label names the right equipment, carries every required element, and is still current, without transcribing or inventing a value.

Canonical page: https://datacenterlabeling.com/guides/arc-flash-and-electrical-safety-labels

Source review: 2026-09-12. This is a source-review date, not a claim of standards certification.

Rackstamp provides editorial field guidance. IDs, cases, and worksheet entries are fictional examples unless identified otherwise. Distinguish local conventions from adopted standards. Source notes describe the evidence scope; a linked overview is not the full standard or a project approval.

## The practical answer

Check hazard labels by confirming that each one names the equipment in front of you, carries every element the adopted edition requires, and traces to a dated analysis whose currency you can assess. Record presence, legibility, and condition separately, and route anything missing or doubtful to the named technical owner. A labeling review never transcribes, converts, or infers a protective value, and it does not authorize work.

## What this check covers, and what it does not

An identification review can confirm that a hazard label exists, that it is legible, that it names the equipment in front of you, and that it agrees with the document that produced it. It cannot establish incident energy, select protective equipment, or authorize work on energized equipment. Those outputs belong to the electrical engineering analysis and to the employer's electrical safety program.

OSHA places the selection of safe work practices and the training of qualified persons on the employer rather than on the person reading the label. [OSHA 29 CFR 1910.333](https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.333) describes those work-practice obligations, and [OSHA 29 CFR 1910.303](https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.303) covers general electrical installation requirements including field marking. Neither makes a labeling survey a substitute for the analysis behind the label.

Use this guide to produce an exception list for the responsible technical owner. When the review finds a missing, unreadable, or doubtful label, the output is a dated record and a referral. It is not a replacement sticker.

## Identify who owns the label content before touching anything

Every hazard label should trace to a controlled document: an arc flash risk assessment or incident energy analysis, a drawing revision, or an equipment submittal. Record the document name, revision, date, and accountable owner before evaluating the label itself. If the review cannot name that document, the finding is a records gap, and it is more important than any wording on the sticker.

Ask who is permitted to issue a replacement. In most organizations that authority sits with the electrical engineer of record, the facilities engineering group, or a contracted study provider, not with the team that owns the printer. Write that name into the review record so the exception has somewhere to go.

In a colocation or shared facility, ownership follows the equipment boundary rather than the room. Equipment owned and maintained by the provider carries labels the provider controls. Confirm the boundary in writing before recording an exception against something another organization maintains.

## Confirm the label belongs to the equipment in front of you

A hazard label describes one piece of equipment at one point in a distribution system. Confirm that the equipment identifier printed on the label matches the identifier in your approved records for the physical unit you are standing at. This is the same crosswalk problem that appears between facility equipment names and operational names, and it fails the same way: two naming systems, one surface, and nobody reconciling them.

Where the label carries no equipment identifier at all, record that as a distinct finding. A correct set of values attached to an unidentifiable panel cannot be verified later, cannot be re-issued after a study update, and cannot be matched to a change record.

## Check the label against the content list its own source requires

Build the content check from the edition your program has adopted rather than from a remembered field list. NFPA 70E is the consensus document usually named for arc flash labeling in the United States, and the [2024 edition](https://link.nfpa.org/all-publications/70E/2024) is the current published edition; installation marking requirements sit in the adopted electrical code, published as [NFPA 70, the National Electrical Code](https://www.nfpa.org/product/nfpa-70-standard/p0070code). Record which edition and clause your check used, because that reference is what makes the result reproducible next year.

Structure the review so each element is confirmed separately rather than judged as one impression:

| Element to confirm | What the reviewer records | Why it is checked separately |
|---|---|---|
| Equipment identity | Identifier on the label and the matching record | A correct value on an unidentified panel cannot be re-issued or audited |
| Nominal system voltage | Value present and legible | Drives almost every downstream decision on the label |
| Arc flash boundary | Value present with its unit | An approach distance is a different quantity from a protective level |
| Protective level expression | Which form the label uses | Incident energy with working distance, a category, and a site-specific level are not interchangeable |
| Source analysis reference | Study name, revision, or date | Without it, currency cannot be assessed at all |
| Signal word and format | Wording and layout as issued | Format belongs to the issuing document, not to the reviewer |

Do not transcribe values between labels, translate a category into an energy figure, or infer a missing field from a similar panel. Each of those actions creates a new engineering statement that the reviewer is not authorized to make. Record the gap and stop.

## Assess whether the label is still current

A label can carry correct content and still be out of date. Treat currency as a separate question with its own evidence. The common triggers are a change to the upstream protective device, a change in available fault current, a transformer or service alteration, equipment replacement, and the elapsed review interval defined by the adopted edition and your own program.

Ask for the analysis date rather than assuming the label's age. Where the label shows no date and the study cannot be located, the correct outcome is an exception stating that currency could not be established, not a judgement that the label is wrong. Those are different findings and they route to different people.

Changes made by your own team are the easiest to miss, because they rarely feel like electrical modifications. A breaker swap, a feeder re-termination, or a panel schedule correction can all invalidate an existing analysis. Link the labeling exception to the change record that caused it wherever one exists.

## Treat durability and legibility as their own finding

A label whose content is correct and whose print has failed is still a failed label. Field-applied markings are expected to be permanent, legible, and suited to the environment where they are installed; the requirement belongs to the adopted electrical code, and the material evidence belongs to the manufacturer of the label stock.

Record the observed condition rather than a verdict: fading, lifting at an edge, surface contamination, a label applied over a previous label, or a position that has been covered by later equipment. Pass those observations to the material selection decision rather than solving them with whatever stock is loaded in the printer. Agency evidence such as UL recognition applies to the specific construction and surface the manufacturer identifies, not to a category of label.

## Worked fictional case: the label outlived the equipment it described

In fictional DC01 / H1, remote power panel RPP-2 carries a hazard label referencing study ARC-2021-04. The panel identifier on the label reads RPP-02 while the approved facility record and the door stencil read RPP-2. A change record from earlier in the year shows the main protective device was replaced during a capacity upgrade.

The review records three separate findings. First, an identifier mismatch between the label and the approved record, which is a crosswalk exception. Second, a currency exception, because a protective device change is a recognized trigger for re-evaluation and the label still references the earlier study revision. Third, no durability exception, because the print is intact and legible.

The reviewer issues no new label. The record goes to the named engineering owner with the panel identifier, the study reference, the change record number, and the date of observation. The identifier mismatch is fixed in the records and the door marking through the normal identification process, because that part is an identification problem. The protective-level content waits for the engineering owner. Every value in this example is fictional.

## Record the exception rather than repairing the label

Write the finding so that someone who was not present can act on it: equipment identifier, location, observed label content by element, what could not be confirmed, the document reference if one exists, the trigger that raised the currency question, photographs, reviewer, and date. Keep the physical label in place unless the responsible owner directs otherwise, because removing it destroys the evidence and leaves the equipment with no warning at all.

Track the exception to closure in the same system that holds other identification work, and record who accepted the closure. A labeling program can legitimately report that a hazard label is missing or unverifiable. It cannot report that the hazard has been assessed.

## Acceptance checklist

- [ ] The controlled document behind each label is named, with revision, date, and accountable owner.
- [ ] Equipment identifiers on labels reconcile with approved records and physical markings.
- [ ] Each required content element is confirmed separately against the adopted edition, which is recorded.
- [ ] Currency triggers are checked against change records rather than assumed from label age.
- [ ] Durability and legibility observations are recorded as their own findings with photographs.
- [ ] No value was transcribed, converted, or inferred by the reviewer.
- [ ] Open exceptions are routed to the named owner and tracked to an accepted closure.

## Frequently asked questions

### Can we print a replacement arc flash label ourselves?
Only when the responsible technical owner supplies the content and authorizes the re-issue. Producing the physical label is a printing task; deciding what it says is an engineering output. Keep the two roles visible in the record so a re-issued label can be traced to the analysis revision it came from, not to the person who happened to run the printer.

### The label has no date. Is it still valid?
Record that currency could not be established, which is different from recording that the label is wrong. The content may be entirely correct. Without a study reference or date, neither the review interval nor the effect of later equipment changes can be assessed, so the finding is an evidence gap for the owner to close.

### Who sets the review interval?
The adopted edition of the consensus standard sets an outer limit, and your electrical safety program may set a shorter one. Record which document and interval the review applied. Equipment changes can require re-evaluation well before any interval elapses, so treat the interval as a maximum rather than a schedule.

### What if the equipment identifier on the label does not exist in our records?
Treat it as an identification exception first. Resolve the name through the normal crosswalk between facility records, operational records, and physical marking before anyone considers reprinting hazard content. A hazard label attached to an object your records cannot name is unverifiable regardless of the values it carries.

### In a colocation space, whose label is it?
Follow the equipment ownership and maintenance boundary stated in your agreement, not the physical room. Record the boundary in the review so exceptions are raised against the organization that can actually act. Where the boundary is unclear, that ambiguity is itself the finding worth escalating.

### Does a labeling audit demonstrate electrical safety compliance?
No. It demonstrates that labels were checked against a stated document on a stated date. Compliance with an electrical safety program involves analysis, training, work practices, and equipment condition that a label review does not observe. Report the checked scope precisely so the evidence is not read as more than it is.

## Sources and applicability

- [NFPA: NFPA 70E, 2024 official publication](https://link.nfpa.org/all-publications/70E/2024): Publisher page establishes the current published edition and scope of the electrical safety document usually adopted for arc flash labeling. The clause-level content list is in the document itself and is not reproduced here.
- [NFPA: NFPA 70, National Electrical Code](https://www.nfpa.org/product/nfpa-70-standard/p0070code): Publisher page for the installation code that carries field marking requirements. Adoption, edition, and amendments vary by jurisdiction; confirm locally rather than assuming the latest edition applies.
- [OSHA: 29 CFR 1910.333](https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.333): Regulatory text placing selection of safe work practices on the employer. Cited to establish that a labeling survey does not authorize work, not as a labeling content specification.
- [OSHA: 29 CFR 1910.303](https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.303): General electrical installation requirements including field marking of equipment. Used for scope context only.
- [OSHA: 29 CFR 1910.145](https://www.osha.gov/laws-regs/regulations/standardnumber/1910/1910.145): Specifications for accident prevention signs and tags. Supports the separation of signal-word format questions from technical content questions.

## Related guidance

- https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking
- https://datacenterlabeling.com/problems/operational-versus-safety-labels
- https://datacenterlabeling.com/problems/a-b-power-feed-identification
- https://datacenterlabeling.com/problems/grounding-bonding-identification
- https://datacenterlabeling.com/problems/facility-equipment-name-crosswalk
- https://datacenterlabeling.com/problems/label-audit-evidence