# Bulk-label data preparation and batch checklist

> Compare source and preview IDs, endpoint fields, original copies, reprints, and release decisions in the editable bulk-label batch checklist.

Canonical page: https://datacenterlabeling.com/templates/bulk-label-import

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

Workbook tab: 24 Bulk label import. 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. Retain the received source with its owner, revision, scope, and receipt reference, then create a distinct preparation copy.
2. Define the row unit, uniqueness scope, endpoint-face roles, original copy rules, and authorized additional copy purposes.
3. Gather the active label template, field definitions, selection population, and approved text-transformation rules.
4. Choose challenging preview records and a physical-proof plan that covers the actual content and copy roles.

## Complete the register

1. Assign a Batch ID and Source revision to the selected population, retaining per-record provenance when sources are combined.
2. Record Source ID as exact approved text and compare the actual Preview ID, including significant zeros, spaces, punctuation, and case.
3. Enter Endpoint fields as complete related values and verify local/remote roles against the retained source, not just column counts.
4. Record Original copies by object and face purpose, distinguishing paired labels from duplicate object identities.
5. Enter Approved reprints with the exact replaced face, current revision, reason, and prior-copy disposition where known.
6. Link mapping, preview, physical proof, and count Evidence to the Batch decision, Owner, and actual Verification date.

## Walk through the example

In fictional DC01 / H1, batch B-024 uses Cable-register revision 6. Enter source ID 000042 as its complete approved text and compare the actual imported preview value, which must remain 000042. Record the endpoint relationship R014/07 to R021/19 with its intended face roles, then record two original physical labels for that cable. The example has no approved reprints. Compare another challenging record such as 000043; if the preview shows 43, hold it and restore the intended value from the retained source rather than guessing. For the broader fictional run, twenty-four cables require forty-eight original end labels, and two authorized replacements bring total printed output to fifty. Keep replacement reasons and spoiled-copy dispositions in the evidence. Review a physical proof before release, then link EX-B024, the selected source population, and the actual reviewer. The object inventory remains twenty-four cables even though the physical print count is fifty.

## Handle common exceptions

### Repeated IDs are intentional cable-end faces.

Retain them under explicit end roles and copy rules; uniqueness checks must distinguish object identity from physical label purpose.

### A column-only sort attaches correct IDs to wrong destinations.

Restore from the retained source, rebuild whole-record relationships, and compare every affected endpoint pair before reproofing.

### Some source rows remain incomplete while others are ready.

Issue only an explicitly approved bounded scope and retain held rows with reasons, owners, and later batch references.

## Review and close

1. Compare complete affected records after sorting or transformation so IDs remain attached to their correct endpoint relationships.
2. Resolve required blanks, unexpected headers, selection-boundary errors, and collisions or retain them in an explicitly held scope.
3. Reconcile original output and replacements with spoiled, retained, issued, and other defined physical-copy dispositions.
4. Confirm that the approved preparation version, mapping, template, and printer proof can be retrieved and reproduced together.
5. Hand off an explicit object-and-face issue list, keeping excluded source rows and later revision changes visible.

## Fields and fictional filled example

| Field | What to record | Fictional example |
| --- | --- | --- |
| Batch ID | Print-run reference. | B-024 |
| Source revision | Approved input file/version. | Cable-register r6 |
| Source ID | Exact original identifier text. | 000042 |
| Preview ID | Text observed after import. | 000042 |
| Endpoint fields | Mapped local and remote references. | R014/07 -> R021/19 |
| Original copies | Planned physical labels for this record. | 2 |
| Approved reprints | Additional copies and reason. | 0; none |
| Batch decision | Release or unresolved exception. | Example proof accepted |
| Evidence | Mapping/proof/count references. | EX-B024 |
| Owner | Person releasing the batch. | Example batch reviewer |
| Verification date | Date of the batch review. | 2026-09-12 |

## Sources

- [Brady: Spreadsheet import preparation](https://support.bradyid.com/articles/en_US/Knowledge/How-to-format-Excel-files-for-importing-into-Brady-software): Brady import behavior and text preparation; the batch accounting workflow is editorial.
- [Brother: Cut options in iPrint&Label](https://help.brother-usa.com/app/answers/detail/a_id/183293/~/cut-options---iprint%26label): Primary manufacturer support page checked for named cut/feed options and model-dependent half-cut availability. No device recommendation, universal margin or cutter setting is adopted.