A trade partner says, “We’ll be back Thursday.” What should happen next?
A return commitment sounds simple, but it becomes a project problem when the date lives only in a phone call, text thread or superintendent’s memory.
Read the scenarioConstruction project scenario library
What should happen when everyday project activity turns into something the team still has to manage?
These scenarios use common field and office situations to show what should be documented, what should carry forward, who owns the next move and when the workflow needs to change.
Real project situations
The examples are intentionally practical. They are not rigid rules for every contractor; they show a clean way to keep the original activity connected to the responsibility and decision that follow it.
The owner asks for a field change during a walkthrough. Where should it go?
An owner request can start as a casual field conversation but quickly affect scope, price, schedule and responsibility. The path should preserve the original request without treating the conversation itself as approval.
Read the scenarioAn inspection fails. The result matters less than what the project does next.
A failed inspection is not just a completed calendar event. It creates a new project condition: something must be corrected, someone owns that correction and another inspection may be required before dependent work can proceed.
Read the scenarioA material delivery slips three days. What actually needs to change?
A late delivery matters only in relation to the work that depends on it. The delivery date, affected trade and downstream sequence should stay connected rather than living in separate calls and calendar notes.
Read the scenarioThe field condition does not match the drawings. Is it an issue, an RFI or both?
The field team often discovers the condition first. The project needs to preserve what was observed while moving the formal question to the person who can answer it.
Read the scenarioA trade partner was scheduled for today and never arrived. What should the project record show?
A no-show is different from ordinary absence. It means the project had a specific commitment that was not met, and that missed commitment may affect other work.
Read the scenarioThe owner asks three questions during a walkthrough. One conversation should not become one vague item.
Walkthrough conversations often mix several unrelated questions. The project team needs a clean way to preserve the conversation while allowing each item to move independently.
Read the scenarioA field change may cost money, but nobody has a number yet. What is the correct path?
The superintendent should be able to surface the condition without inventing a price or waiting until every cost detail is known. The project manager then owns the pricing path.
Read the scenarioThe delivery arrived, but part of it is damaged. Is the delivery complete?
Physical arrival does not always mean the project received usable material. The delivery event and the resulting issue are related but describe different project facts.
Read the scenarioOne trade says, “We can’t work until they finish.” How should that be tracked?
Blocked work is common in construction. The useful record is not simply that one crew stopped; it is which predecessor condition is incomplete, who owns it and what work is waiting behind it.
Read the scenario