Issuing Non-Overlapping Tag Ranges to Concurrent Field Teams
Prevent duplicate asset tags when several teams work at once by controlling range allocation, offline use, spoiled labels and end-of-day reconciliation.
How can several field teams issue tags without creating duplicate numbers?
Allocate exclusive tag ranges or centrally reserved identifiers before fieldwork, record who holds them, and reconcile their use each day. Keep applied, unused, spoiled and cancelled labels distinguishable. If teams work offline, prevent reassignment of their reserved numbers until the completed field records have been received and checked.
Two teams may visit different municipal sites with labels printed from separate spreadsheets. If both print the next available sequence, duplicate identifiers can appear on unrelated assets. The failure is especially difficult to detect while devices are offline. A simple issue-and-return process makes label custody as clear as asset custody.
Reserve identifiers before printing begins
Use one controlled register of tag allocations with team, site, range, quantity and issue date. Check each proposed range against existing asset identifiers and other reservations. Keep a named coordinator responsible for conflicts. Teams should receive an approved allocation rather than generating their own numbers from the last row visible in a local file.
Choose a numbering format that the software preserves exactly. Avoid embedding details such as room or custodian that may change. If the organisation adopts a formal external identification scheme, follow that scheme's allocation rules. GS1, for example, distinguishes individual asset identifiers from other identification keys; an internal sequence should not be described as GS1-compliant without the required basis.
Track what happens to every issued label
Record a label as applied only when its identifier is linked to a specific observation and asset decision. Keep spoiled labels physically controlled and mark them unusable in the allocation record. Labels lost in the field need a separate incident entry so they are not later accepted as legitimate assignments merely because their numbers fall in an issued range.
For offline teams, treat the entire allocation as reserved until synchronisation and reconciliation finish. A number not yet visible in the central application may already be attached to an item. Do not release apparently unused numbers based on a mid-day system query. Use an explicit team return statement supported by the field records and remaining label stock.
Reconcile before the next allocation
At day end, compare issued quantity with applied, unused, spoiled and missing labels. Check for the same tag assigned to different observations and for observations without an issued tag. Resolve gaps with the team while the visit is still recent. Physical label stock and uploaded data should tell the same story.
Before issuing replacement stock, review whether the team needs a fresh range or can continue its existing reservation. Keep closed allocations searchable. A later duplicate investigation should reveal which team received the number and where it was recorded, without reconstructing events from photographs of half-used label sheets.
Practical Example
Illustrative example: two verification teams receive separate ranges of one hundred tags. One team applies eighty-two, returns fifteen and reports three spoiled labels. The coordinator reconciles those quantities with uploaded observations before closing the allocation. The second team's unuploaded range remains reserved overnight, preventing another team from using numbers that are already attached in the field.
Action Checklist
- 1.Reserve each team's identifiers centrally before any label sheets are printed.
- 2.Check allocations against existing records and other active reservations.
- 3.Record applied, unused, spoiled and missing labels as separate outcomes.
- 4.Keep offline allocations reserved until field data and physical stock reconcile.
- 5.Investigate duplicate assignments before distributing the next batch of tags.
Coordinate tag allocations across concurrent field teams through Asset Verification Services.