Rackstamp, data center labeling field guide

WORKSHEET 29 / Records & lifecycle

Moves, additions, changes, and retirement closeout sheet

Choose a change, migration, or retirement path and close physical identification and records together.

Download workbook ↓Read the guide

The download includes all 30 worksheets. Open the 29 Change closeout tab.

Use it with your own records.

  1. Download the workbook and open 29 Change closeout.
  2. Enter your site and room scope and the project or policy reference.
  3. Use the blank amber table for actual records. The fictional example below it is a reference.
  4. Insert table rows when needed. Keep identifiers as text, including leading zeros.
  5. Follow guide 29 to complete the checks and record unresolved items.

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 filled example

Fictional values only. Scope: DC01 / H1 unless another location is shown. The downloadable register is blank for your actual observations.

FieldWhat to recordFictional example
Work referenceApproved change or project.CH-029
PathChange/move, migration, or retirement.Migration
Object/media IDStable identifier; media IDs when relevant.AST-008422
Old statePrevious location, endpoints, or status.DC01/R014/U24
Final stateApproved destination or lifecycle status.DC02/R031/U12
Wave/manifestMigration tracking; not-applicable otherwise.W3 / manifest M3
Label accountingCurrent, superseded, and temporary legends.Destination tags reconciled
EvidenceReceipt, removal, custody, or disposition references.EX-M3 receipt and install review
Closeout stateVerified outcome or remaining exception.Example migration closed
OwnerPerson responsible for closeout.Example migration lead
Verification dateFinal identification-check date.2026-09-12
29 Change closeout workbook preview
29 Change closeout workbook preview. View full size ↗

Sources and scope