Static field route #468

What do I do when no record of field conflict/RFI answer?

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

Document the condition before it disappears. Get the room/grid, system, close-up, wide photo, and what question needs an answer.

Open in Field Rescue Open category

Field checklist

Take a wide photo showing location/context.
Take a close photo showing the actual issue.
Include room, grid, equipment/system tag, or drawing reference.
Tell the foreman what is blocked or questionable.
Save the note/photo before the area gets covered.

Ask foreman

What photos or notes do you want before this gets covered or changed?

Do not

Do not take random photos with no location, system, or reason.

Why it matters

Documentation only helps if someone can understand where the issue is and why it matters.

Search words: quality punchlist turnover RFI record documentation QA QC punchlist turnover documentation what do I do when no record of field conflict/RFI answer #468 documentation QA QC punchlist turnover documentation what do I do when no record of field conflict/RFI answer #468 qaqc apprentice workflow