Static field route #460

What do I do when as-built change not documented?

QA/QC, Punchlist, Documentation & TurnoverQA/QC starter — verify before calling it complete

Mark field changes while the work is still fresh. Redlines/as-builts are not a memory test at the end of the job.

Open in Field Rescue Open category

Field checklist

Mark what changed from the drawing.
Include room/grid/system and direction of change.
Attach photo/sketch if allowed.
Confirm whether foreman/PM wants formal RFI/as-built note.
Do not leave unclear notes for closeout.

Ask foreman

Does this field change need a redline/as-built note before we move on?

Do not

Do not wait until turnover to guess what changed weeks ago.

Why it matters

The person doing closeout may not be the person who saw the field change happen.

Search words: quality punchlist turnover as-built documentation QA QC punchlist turnover documentation what do I do when as-built change not documented #460 documentation QA QC punchlist turnover documentation what do I do when as-built change not documented #460 qaqc apprentice workflow