Record preparation

UST record import checklist.

Preserve the source. Check the identities. Confirm the relationships before you move the records.

Nine checks before import.

Check items here or print a copy. Checkboxes are not submitted or saved. Agree the supported format and import scope separately; this checklist does not promise automatic import of every file.

    • File or source name,
    • Source owner,
    • Last updated date,
    • Unchanged original copy

    Keep the original separate from the working file; mark information whose age or meaning is uncertain.

    • Customer identifier,
    • Business name,
    • Appropriate contact

    Confirm that similarly named companies are the same organization before combining them.

    • Site identifier,
    • Location,
    • Customer relationship

    Use the location and identifiers to distinguish separate sites with similar names.

    • Equipment identifier,
    • Equipment type,
    • Parent site,
    • Relevant attributes

    Confirm each equipment record belongs to the right site; keep missing identifiers visible.

    • Form name and version,
    • Field meanings,
    • Example finished report

    Use sample or redacted material; confirm which fields and output formats must be reproduced.

    • Source record key,
    • Related record key,
    • Relationship meaning

    Show how customer, site, equipment, and job records connect; test ambiguous links.

    • Duplicate candidates,
    • Conflicting values,
    • Missing keys,
    • Unsupported formats

    Do not fill gaps with guesses. Name who can resolve each exception and how it will be checked.

    • Normal records,
    • Missing-value case,
    • Duplicate-name case,
    • Unusual relationship

    Inspect a small, agreed sample before broad changes; include the cases most likely to break the mapping.

    • Reviewer,
    • Expected counts and links,
    • Open issues,
    • Accepted result

    Agree what a usable result looks like and keep the source copy until the outcome has been checked.

Check the links as well as the rows.

A repeated name or equipment label can describe different records.

Illustrative relationship checks
RelationshipSampleCheck
Customer to siteSampleC-01 → Sample Site 12CheckDoes the source establish that the location belongs to this customer?
Site to equipmentSampleSample Site 12 → TK-01CheckIs TK-01 the intended asset, even if its label repeats at another site?
Job to outputSampleUST job 104 → Inspection form → reportCheckAre the form version, source fields and expected output understood?

Keep uncertain values and their source. Name who will resolve each exception and who accepts the reviewed sample before broader changes.

Prepare a starting set your team can trust.