# Moves, additions, changes, and retirement closeout sheet

> Account for old and final states, object IDs, migration waves, physical labels, evidence, and closure in the editable change and retirement sheet.

Canonical page: https://datacenterlabeling.com/templates/moves-and-retirement-closeout

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

Workbook tab: 29 Change closeout. 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. Collect the approved work reference and establish the stable identities of all affected objects and relevant media.
2. Capture planned, current, and historical locations or connections separately, including actual completion evidence already available.
3. List physical legends and system fields affected by the transition, including unchanged connection ends and temporary tags.
4. Select the applicable change/move, migration, or retirement path and identify its closeout, custody, and records owners.

## Complete the register

1. Enter Work reference and Path for each object or bounded related group, linking multiple paths when the project contains them.
2. Record Object/media ID and Old state from established evidence rather than reassigning identity to match a destination.
3. Enter intended Final state separately from actual observed events, preserving partial completion or rollback when they occur.
4. For migration, record Wave/manifest and individual dispatch, receipt, deferment, diversion, and final-installation references.
5. Complete Label accounting for retained, replaced, superseded, and temporary faces, including both ends of changed connections.
6. Link path-specific Evidence to Closeout state, Owner, and the actual final Verification date or explicit pending obligation.

## Walk through the example

The fictional migration row concerns AST-008422, starting at DC01 / H1, R014/U24 and targeting DC02, R031/U12 under change CH-029. Record Migration as the path and W3 / manifest M3 as the tracking reference. Preserve the stable asset ID while recording departure, receipt, and final installation as separate observed events. The target location remains intended until the relevant completion evidence supports its actual installation. Link EX-M3 receipt and installation review, and account for temporary destination tags and superseded operational legends. Compare the asset's current location and the affected occupancy records through their authorized owners. The example row can close only when that identification scope is verified. If receipt occurs but installation is deferred, record received awaiting installation and retain the next owner rather than marking the migration complete. AST-008421 remains the separate recurring example asset at R014/U23; do not substitute its identity merely because it occupies a nearby source position.

## Handle common exceptions

### An asset is deferred from one migration wave into another.

Retain its original manifest row, record the approved transfer reference, and track the same stable ID through the later wave.

### A move is rolled back to the original location.

Record the return event, verify the actual final state, and account for destination and temporary labels created during the attempt.

### A removed chassis has media awaiting separate disposition review.

Keep chassis removal, media identities, custody, and disposition evidence distinct, with final lifecycle status pending the responsible decision.

## Review and close

1. Compare individual object identities through the transition rather than accepting matching manifest totals alone.
2. Verify current location and connection records together with their affected physical legends and old-position occupancy where applicable.
3. Keep deferred or transferred migration items attached to their original wave and documented subsequent disposition.
4. For retirement, preserve required media identity and custody/disposition links without treating removal or label cleanup as sanitization proof.
5. Retain history, rollback events, and open partial work so completed checks do not imply unverified lifecycle outcomes.

## Fields and fictional filled example

| Field | What to record | Fictional example |
| --- | --- | --- |
| Work reference | Approved change or project. | CH-029 |
| Path | Change/move, migration, or retirement. | Migration |
| Object/media ID | Stable identifier; media IDs when relevant. | AST-008422 |
| Old state | Previous location, endpoints, or status. | DC01/R014/U24 |
| Final state | Approved destination or lifecycle status. | DC02/R031/U12 |
| Wave/manifest | Migration tracking; not-applicable otherwise. | W3 / manifest M3 |
| Label accounting | Current, superseded, and temporary legends. | Destination tags reconciled |
| Evidence | Receipt, removal, custody, or disposition references. | EX-M3 receipt and install review |
| Closeout state | Verified outcome or remaining exception. | Example migration closed |
| Owner | Person responsible for closeout. | Example migration lead |
| Verification date | Final identification-check date. | 2026-09-12 |

## Sources

- [IBM: Server cable management and labeling](https://www.ibm.com/support/pages/cable-management-and-labeling-servers): Replacement labels and documented deviations; migration workflow is editorial.
- [NIST: SP 800-88 Revision 2](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r2.pdf): September 2025; device/media identity in disposition evidence. No sanitization procedure reproduced.
- [Cloudflare: Dashboard and API outage on April 15, 2020](https://blog.cloudflare.com/cloudflare-dashboard-and-api-outage-on-april-15-2020/): Primary operator incident report published April 16, 2020. Scope limited to the reported event; retirement-register lesson is explicitly editorial.