# Device-class label placement review

> Compare approved surfaces and real reading tasks across servers, switches, rack PDUs, and facility equipment.

Canonical page: https://datacenterlabeling.com/planning-templates/device-label-placement-review

## Review setup

Project: ______ | Reviewer: ______ | Date: ______ | Approved access scope: ______

List the actual device models being considered. A visually convenient surface may be a replaceable bezel, a moving handle, or a cover belonging to a different component. Establish which physical object the proposed label identifies before selecting its location.

## Placement matrix

| Device class/model | Stable object key | Proposed surface | Removable-part relationship | Viewpoint and access | Adjacent required markings | Evidence |
|---|---|---|---|---|---|---|
| Server | ______ | ______ | ______ | ______ | ______ | ______ |
| Switch | ______ | ______ | ______ | ______ | ______ | ______ |
| Rack PDU | ______ | ______ | ______ | ______ | ______ | ______ |
| Facility equipment | ______ | ______ | ______ | ______ | ______ | ______ |

Check the manufacturer's restrictions for the actual model. Keep vents, controls, latches, service information, and safety messages usable. If the preferred area is inaccessible under approved working conditions, record that limitation and propose a permitted alternative rather than moving equipment during the survey.

## Read and scan trial

Record the printed sample and template revision. Inspect it from the intended working view under the relevant lighting and cable arrangement. Test the longest anticipated ID. For a machine-readable symbol, record the actual scanner/profile and the decoded result, then confirm that the resulting record identifies the correct object.

| Sample | Human-readable result | Scan/decode result if used | Correct record resolved | Obstruction or ambiguity | Decision |
|---|---|---|---|---|---|
| ______ | ______ | ______ | ______ | ______ | ______ |

## Exception and approval

If duplicate front and rear representations are used, specify their common identity and location context. If a replaceable subcomponent needs its own identifier, give it a distinct record rather than reusing the chassis ID. An alternate lookup label must describe its role clearly enough that it is not mistaken for the adjacent object's identity.

- [ ] The physical identity-bearing component is unambiguous.
- [ ] The surface and placement have an approved basis.
- [ ] The installed view supports the intended reading task.
- [ ] Other required markings remain visible.
- [ ] A replacement or maintenance event has a defined relabeling owner.

Disposition and authorized reviewer: ______. Recheck triggers: model change, placement change, new reader, changed adjacent equipment, or repeated field failures.