# Label audit and exception register

> Define the audit scope and criteria, log observed findings, and retain corrections, evidence, reviewers, and closure in the label-audit register.

Canonical page: https://datacenterlabeling.com/templates/label-audit-evidence

Download: https://datacenterlabeling.com/assets/downloads/rackstamp-worksheets.xlsx

Workbook tab: 30 Audit evidence. The workbook includes all 30 registers.

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.

## Before you start

1. Define the intended inspection claim, relevant criteria, policy revisions, and whether counts represent objects, faces, or criterion checks.
2. Retain the population reference, sample-selection method and list, exclusions, and any known inventory limitation.
3. Gather previous findings and separate a closure recheck from a new population inspection when both occur during one visit.
4. Agree permitted observation methods, evidence access, correction ownership, and the site's actual closure or exception authority.

## Complete the register

1. Enter Audit/scope and Object ID with the physical face and counting unit, retaining not-inspected items in the scope accounting.
2. Assign Finding ID and Criterion/revision to each specific departure or explicitly bounded group of affected faces.
3. Record Observed condition as actually seen, separating incomplete text from the independently established expected identity.
4. Enter Decision/correction after reviewing the evidence, distinguishing a proposed remedy, completed physical correction, and authorized exception.
5. Link original and final Evidence with the Owner and any due point or exception review trigger under the site's process.
6. Record Verifier, actual Verification date, and Closure status only for the criterion checked, leaving other unresolved findings visible.

## Walk through the example

In fictional DC01 / H1, audit AU-030 selects twelve labels from a population of one hundred twenty. Preserve the actual selection list and readability criterion under policy revision 3. Finding A-301 concerns the unreadable label on AST-008421, the recurring asset at R014/U23. Record the damaged observed condition separately from the independently established asset ID, and link the original EX-301 evidence. Replacement under CH-030 is a correction reference, so it does not close the finding until the installed face is checked. The verifier reads the complete correct ID, confirms its association with the asset, and records the actual final evidence and date. A-301 can then be marked corrected while A-302 and A-303 remain open in the fictional audit. Reconcile the twelve inspected labels and the three original findings, keeping the remaining one hundred eight uninspected labels outside the pass claim. Report any approved exception separately from a physically corrected label.

## Handle common exceptions

### A selected face is inaccessible under the permitted observation method.

Record not inspected for the relevant criterion, retain the reason, and preserve any approved selection change or follow-up assignment.

### A label is readable but its destination disagrees with the record.

Record the favorable readability observation and separate correspondence finding; do not report overall conformity while the mismatch remains.

### An authorized exception closes the decision but leaves the physical departure.

Report approved exception distinctly, retaining its authority, scope, and review conditions instead of counting it as corrected.

## Review and close

1. Reconcile population, selection, inspected, excluded, and not-inspected counts using the declared unit throughout the report.
2. Count affected objects and findings separately, explaining multiple criteria or grouped findings without double-counting.
3. Verify each claimed correction against the original criterion rather than accepting a requested or completed work order alone.
4. Keep corrected findings, approved exceptions, and open findings distinct, retaining the authority and any future review conditions.
5. Test evidence retrieval and report the actual reviewed scope without implying that unselected or inaccessible labels passed.

## Fields and fictional filled example

| Field | What to record | Fictional example |
| --- | --- | --- |
| Audit/scope | Audit reference and included population/sample. | AU-030; 12 of 120 |
| Finding ID | Reference for one observed issue. | A-301 |
| Object ID | Object being assessed. | AST-008421 |
| Criterion/revision | Expected condition and governing version. | Readable ID; policy r3 |
| Observed condition | Original finding, retained after correction. | Unreadable |
| Decision/correction | Remedy or approved exception reference. | Replacement under CH-030 |
| Evidence | Observation and final-check references. | EX-301 before/after |
| Owner | Person accountable for correction. | Example label lead |
| Verifier | Person who checked closure evidence. | Example audit reviewer |
| Verification date | Date final check was completed. | 2026-09-12 |
| Closure status | Open, corrected, or approved exception. | Corrected; example only |

## Sources

- [Sunbird: Asset audit application note](https://www.sunbirddcim.com/sites/default/files/AN011_Sunbird_Application_Note_Asset_Audit_0.pdf): Manufacturer audit-log example; frequency, sampling, and closure workflow here are editorial.