The homeowner thinks nobody showed up
Workers spend the morning performing exterior work. The homeowner is inside and does not see them.
Back to all risk scenarios
Representative construction risk scenario
16The homeowner thinks nobody showed up
A representative construction near miss, what happens without Duxor, and how the connected response can prevent the loss.
Without Duxor
At noon, the homeowner calls angrily: "Nobody showed up again." The office spends time reconstructing events and defending the crew.
With Duxor
Duxor gives the homeowner a live update: "The roofing crew arrived at 7:48 AM. Tear-off is underway on the rear section. Photos will be added this afternoon."
What timely action can prevent
Customer anxiety caused by silence.
Risk-prevention scenario
Why this moment matters
A homeowner may look outside, see no one, and conclude that another promised workday was missed even while a roofing crew is active behind the house. The office then spends time proving what happened, the crew feels unfairly questioned, and customer confidence drops. The underlying failure is not absence of work. It is absence of a timely, customer-appropriate view of work that is already recorded elsewhere.
Duxor can connect the assignment, approved work-hour check-in, task status, photos, and project timeline to a curated customer update. The homeowner should not receive internal chatter, private employee information, or unverified progress claims. A useful update states who or what crew arrived, what approved activity is underway, and when the next visible update is expected, based on current project evidence and audience permissions.
Risk-prevention scenario
Signals Duxor can connect
A confident customer update should rest on several current project signals, not location alone.
- 01
The scheduled crew has an active assignment and a geofence or approved manual check-in tied to the homeowner's project and work window.
- 02
The current task identifies exterior, rear-yard, roof, delivery, or other work that may not be visible from the customer's normal viewpoint.
- 03
A crew lead has recorded task progress, a field update, or photos that support what the project can accurately say is underway.
- 04
The customer profile defines preferred channel, level of detail, quiet hours, portal access, and which project information may be shared externally.
Risk-prevention scenario
A controlled response
The response should verify the work, translate internal state into plain language, and respect the customer boundary.
Confirm current presence
Duxor compares the assignment, arrival window, check-in state, and signal freshness. If a phone is unavailable or the evidence conflicts, the office or crew lead provides an approved manual confirmation with a reason instead of presenting uncertain location as fact.
Verify the activity
The crew lead or project record supplies the work area, current task, and available progress evidence. Duxor distinguishes an arrival from proof of a particular completion milestone and avoids turning presence alone into a stronger claim.
Prepare the customer view
The platform creates a concise update from externally permitted facts, such as crew arrival time, work underway on the rear roof, and when photos are expected. Internal notes, detailed worker movements, and unrelated project exceptions remain outside the customer audience.
Publish and monitor
An authorized user reviews the update when company policy requires it, or an approved low-risk template sends it automatically. Delivery, portal view, replies, and unresolved questions remain connected to the project so the office can respond without rebuilding the facts.
Risk-prevention scenario
Who needs to act
The crew records the work, the office controls the message, and the customer receives an appropriate view.
Crew lead
Checks in under company policy, identifies the active work area, and records enough progress evidence to support an accurate update.
Project manager or coordinator
Reviews uncertain facts, controls the customer audience, approves nonroutine communication, and answers questions that require context or judgment.
Homeowner
Receives a calm project update through the preferred channel or portal and can reply without entering an internal team conversation.
What stays on the project record
The project timeline should preserve the assignment, arrival window, check-in source, manual fallback reason if used, active task, progress evidence, update text, reviewer or automation rule, audience, delivery, portal view, customer reply, and any follow-up. This lets the company answer later questions with a clear sequence while protecting internal notes and location details that were never appropriate for the customer.
What must be configured first
Accurate customer visibility requires current schedules, crew assignments, task names, project contacts, and a documented check-in policy with visible employee permissions and manual fallback. Customer portal and communication settings must define audience, detail level, channel, and quiet hours. The company should approve reusable low-risk templates and require review for unusual, sensitive, or consequential statements. Presence is work-hour awareness for an assigned job, not continuous employee tracking or proof that work is complete.
Risk-prevention scenario
Related construction scenarios
See how Duxor connects more field problems to the people and actions that resolve them.
Bring Duxor one problem your team sees every week.
We will show you how a connected workflow surfaces it earlier and keeps the project moving.