Mark the commitment as a no-show
Do not simply delete the scheduled event or move it to tomorrow. Preserve the fact that the original commitment was missed.
Decide whether it needs attention
If nothing else depends on the work, the no-show may remain a scheduling exception. If another trade, inspection or milestone is affected, surface the item so the consequence is visible.
Do not fabricate a communication
If nobody called the trade partner yet, the system should not imply that contact occurred. The no-show itself is enough to create the need for follow-up.
Reschedule the same commitment
When a new date is agreed, reschedule the existing item. The project history should show scheduled, no-show and rescheduled rather than three unrelated entries.
Use patterns carefully
One missed day is a project fact. Repeated no-shows may become useful history for project management, but the operational goal is still to manage the current commitment rather than turn the system into a performance scorecard.
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 treats a no-show as a change to an existing commitment, not as a new disconnected note that someone has to remember later.
What this means for the company
The company gets a more accurate picture of reliability and project impact without forcing the superintendent to build a separate tracking system for missed commitments. The immediate goal remains getting the work back on track.