Update the expected delivery
Reschedule the delivery to the new committed date and retain the prior date in the activity history. The project should show that the date changed, not pretend the original commitment never existed.
Connect the affected work
Identify the task, area or trade activity that cannot proceed without the material. If the delay changes the planned sequence, that consequence should be visible to the superintendent and project manager.
Keep the source of the new date
A vendor email or trade-partner call may be the source of the revised commitment. Keep that communication connected to the delivery so the team can see where the date came from.
Escalate only when the project impact requires it
Not every three-day slip needs a formal issue. If the schedule absorbs it, the delivery event may be enough. If it blocks critical work or creates a decision, surface it as an issue or PM attention item.
Close the commitment at arrival
When the material actually arrives, mark the delivery complete and note any discrepancy. Planned arrival and actual arrival are different project facts.
Keep the original condition or communication, the current responsibility and the next action connected instead of recreating the same item in multiple places.
Why this is useful in Timbrana
Timbrana keeps the revised delivery date connected to the work that depends on it, so a date change becomes useful project information instead of just another calendar edit.
What this means for the company
A delivery delay becomes a coordination signal instead of a date hidden in a calendar. The company can see whether the slip is harmless, whether crews need to be resequenced and whether the PM needs to become involved.