Build the location register

The skill and its purpose

A multi-site programme needs an identity for each real location rather than a list of names that can be confused or overwritten. The location record connects measurements, variants, quantities, access and acceptance. Stable identifiers also make an import or exception understandable when two branches have similar names. An address change or new contact should update the location’s facts without discarding its project history.

Work through the decision

Create a unique site reference and record the confirmed location name, delivery information, responsible contact and relevant fixture references. Keep contact details limited to the people who need them. Validate imported rows before applying them, rejecting duplicate references and missing required identifiers. Preserve unknown geometry or access as assigned questions rather than filling gaps with a different branch’s values.

Practical exercise — fictional

A fictional CSV contains two rows named High Street, with references S-01 and S-01 but different delivery towns. Run a dry check and explain why the import must pause. Draft the question that resolves whether this is one changed location or two distinct sites. Retain both source rows for review without silently adding their quantities.

Take it to the next job

• Assign unique stable location references.
• Keep fixture and site identities separate.
• Dry-check imports for duplicates and gaps.
• Resolve identity questions before allocation.