# Power identification and safety labels

> Select the right identification guide for A/B feeds, circuits, PDU outlets, bonding, and safety labels. Record uncertainties for the responsible electrical owner.

Canonical page: https://datacenterlabeling.com/topics/power-safety-labels

## Identify the uncertain relationship

Power identification can involve several connected records: the source supplying a PDU, the outlet used by a cord, the device inlet at its other end, or the circuit and disconnect associated with equipment. A readable sticker answers only the question assigned to that sticker. It does not establish the condition of the electrical system.

Begin with the exact equipment and observed wording. Preserve the drawing, schedule, or record that appears to conflict with it, including its revision. State whether the uncertainty concerns an identity, an upstream relationship, a connection endpoint, or the function of a marking. Keep the issue with the owner responsible for that decision.

These guides organize identification and evidence. They do not authorize switching, unplugging, testing, or electrical work, and they do not establish an electrically safe work condition.

## Choose the relevant record

| The question in front of you | Start here | Evidence the guide helps organize |
|---|---|---|
| Which path is designated A or B? | [A/B power-feed identification](https://datacenterlabeling.com/problems/a-b-power-feed-identification) | Textual feed designation, PDU identity, upstream record, and applicable local legend. |
| Which circuit or disconnect supplies this equipment? | [Circuit and disconnect marking](https://datacenterlabeling.com/problems/panel-circuit-disconnect-marking) | Exact equipment, observed marking, conflicting reference, and the responsible electrical review. |
| Which PDU outlet connects to which device power supply? | [PDU outlet and PSU mapping](https://datacenterlabeling.com/problems/pdu-outlet-psu-map) | Cord identity and the particular marked outlet and device inlet. |
| Where does this grounding or bonding conductor terminate? | [Grounding and bonding identification](https://datacenterlabeling.com/problems/grounding-bonding-identification) | Conductor, equipment endpoint, busbar, termination reference, and drawing relationship. |
| Is this an asset sticker, manufacturer marking, or safety message? | [Operational versus safety labels](https://datacenterlabeling.com/problems/operational-versus-safety-labels) | Label function, approved source, visibility, condition, and reviewer. |

A PDU can have a clearly recorded A/B designation while one outlet-to-PSU relationship remains unresolved. Conversely, a correctly identified cord does not demonstrate that its two upstream supplies are independent. Choose the guide for the uncertain relationship instead of treating one completed label as proof of the entire path.

## Recognize what the evidence establishes

A useful closeout records the observed condition, accepted identity or relationship, source revision, reviewer, and affected physical and record references. If the discrepancy remains open, retain the missing evidence and next decision owner. Do not replace an unknown source with a plausible value simply because a print template requires text.

Keep identification conclusions separate from technical conclusions. Two colors do not prove redundancy. A bonding tag does not prove continuity or integrity. An asset barcode does not replace a required warning or manufacturer marking. Required safety information needs its own applicable source and review; visual consistency is not a reason to cover it.

## Bring in other topics at the right point

Use [label-to-record reconciliation](https://datacenterlabeling.com/problems/label-record-reconciliation) when several systems disagree about an equipment or circuit field. Use [material-failure review](https://datacenterlabeling.com/problems/label-material-failure) when an accepted message is deteriorating, preserving the marking's function and approved reference while the application is reviewed.

The [standards and project requirements planner](https://datacenterlabeling.com/guides/labeling-standards-and-project-requirements) separates identifier administration, equipment instructions, safety requirements, material evidence, and acceptance criteria. It also keeps publication, jurisdiction, and project applicability distinct. A US workplace reference should not become an assumed worldwide rule.

For a broader inherited-room program, the [legacy-room planner](https://datacenterlabeling.com/guides/legacy-room-relabeling) makes electrical-owner dependencies visible without folding them into a general printing crew's scope.