Records by location: linking different records to one place
The office asks for everything concerning the west wall on level three. Photographs say 'west side', the inspection record uses a room number and the ticket names a grid. The records exist, but their locations do not connect.
Agree a simple location key from the project's drawings and use it across record types. Include the level, zone or grid and room or area needed to identify the subject. Keep the key accessible and preserve links when names change. Consistent location references make retrieval easier; they do not guarantee that one search returns every relevant record.
Connect different records to one place
- Choose stable references. Use the current drawing conventions and agree how far each record needs to locate its subject. A wall may need a level, elevation and grid range, while a delivery may serve the whole job. Avoid inventing room names that only one crew understands.
- Apply the code consistently. Add it to relevant daily-report lines, photo captions, inspection entries, RFIs, tickets and deficiency items. Show a worked example to the writers and receivers. Keep the original document unchanged where appropriate and add the location in its index or approved record field.
- Handle changes and multiple places. Retain a dated alias key when a temporary room name becomes a final number. Link a record affecting several locations to each relevant place, or define its range. Use a general-project reference for genuinely unlocated matters; do not attach a random room just to fill the field.
- Test across record types. Pick an actual location and retrieve its records from the different systems. Search old names, dates and subject terms as well as the code. Record missing links, ambiguous labels and inaccessible files, then assign corrections without silently altering the original observation.
Keep the key under an identified updater, and tell trades when a reference changes. Test a new trade's first set of records while its foreman can still explain the location. A chosen monthly spot-check may suit your project, but change that routine when repeated errors or a revised layout need earlier attention. Retrieval speed is useful only if the returned set is relevant and its gaps are understood.
Common mistakes
- Using a different nickname in each trade's records.
- Losing the old room name when the final schedule changes.
- Treating a code search's result count as proof of completeness or cause.
Checklist
Check the location key
- Drawing-based level, zone, grid or room convention.
- Worked examples across record types.
- Aliases, ranges and general-job records defined.
- Updater and change communication assigned.
- Retrieval sample, missing links and corrections recorded.
Check your understanding
A room was renamed halfway through the job. Should you replace every old reference?
