# Move, add, change, and retirement ticket insert

> Carry old and new identifiers, label actions, record corrections, and evidence into the change ticket.

Canonical page: https://datacenterlabeling.com/planning-templates/change-ticket-labeling-closeout

## Change identity

Ticket: ______ | Approved scope: ______ | Work window: ______

Implementation owner: ______ | Record owner: ______ | Closeout reviewer: ______

Choose the event: move / add / connection change / alias correction / retirement / rollback. Describe the actual affected objects. A tag reading 'retire' does not authorize removal or establish completion of data sanitization.

## Affected objects and relationships

| Stable object key | Before location/endpoints | Intended after value | Labels affected | Records affected | Evidence reference |
|---|---|---|---|---|---|
| ______ | ______ | ______ | ______ | ______ | ______ |

List identities separately from locations and relationships. For a device move, the asset key may stay the same while the location and attached cable relationships change. For a replaced cable, preserve the old cable's history and identify the new object explicitly.

## Pre-work record

- [ ] Before values and relevant revisions are captured.
- [ ] Proposed identifiers are reserved and checked for collisions.
- [ ] The exact label batch and intended placements are reviewable.
- [ ] Record changes have named owners.
- [ ] Exceptions and rollback conditions are known.

## Post-work observation

Actual outcome: completed / partial / deferred / rolled back. Describe deviations from the intended after state: ______.

Record what was observed, by whom, from which viewpoint, and when. Link any required test result through the actual object identifier. Do not infer that a change succeeded solely because its scheduled end time passed.

## Reconcile the result

- [ ] Active labels show the approved identifiers and relationships.
- [ ] Superseded operational labels have the correct disposition.
- [ ] DCIM, schedules, and other in-scope records show the observed result.
- [ ] Exports no longer recreate the old values.
- [ ] A rollback restored both physical and record relationships where required.
- [ ] Partial work has a bounded remaining scope and accountable owner.

For retirement, record separate references for removal, inventory disposition, data handling, and any other required controls. A wiped flag, empty rack position, or deleted CMDB entry does not prove the other steps occurred.

## Closure record

Accepted scope and evidence: ______. Remaining exceptions: ______.

Reviewer and review date: ______. Follow-up trigger: ______.

Keep historical before values attached to the ticket even after the current register changes. This preserves the ability to explain an old photograph, test report, or incident record without making the retired identifier current again.