Static field route #425

What do I do when installer takes blame for design conflict because no documentation?

Coordination, Clashes, Sequencing & ReworkCoordination starter — document before changing work

If you are already being blamed for an undocumented design conflict, reconstruct the timeline and bring evidence to your foreman/PM before accepting blame or touching rework.

Open in Field Rescue Open category

Field checklist

Pull photos, texts, notes, and drawing revisions from the time of install.
Write a simple timeline: date, location, direction, who gave it, what changed.
Identify what was installed and what was based on verbal direction/design conflict.
Bring the package to your foreman first.
Do not remove work until scope and responsibility are clarified.

Ask foreman

I’m being asked about this rework. I have photos/texts and the drawing history from when it was installed. Can we review the timeline before I start removing anything?

Do not

Do not argue, delete messages, or start rework before the scope/responsibility is clear.

Why it matters

When design conflicts are not documented, the last installer often gets blamed. A clean timeline gives the crew a factual starting point.

Search words: coordination clashes rework documentation design conflict documentation installer blame RFI field report design conflict documentation installer blame RFI field report coordination rework What do I do when installer takes blame for design conflict because no documentation? If you are already being blamed for an undocumented design conflict, reconstruct the timeline and bring evidence to your foreman/PM before accepting blame or touching rework. coordination clashes rework documentation design conflict documentation installer blame RFI field report