The crew is running late, and nobody knows yet
The electrician was expected at 8:00. At 8:20, the homeowner is still waiting, the drywall crew is scheduled behind him, and the PM has not heard anything.
Back to all IQ scenarios
Duxor IQ scenario
01 V1The crew is running late, and nobody knows yet
A representative field moment, the connected Duxor response, and why it changes the outcome.
Duxor solution
Duxor detects that the arrival window is slipping, updates the ETA, alerts the PM, identifies the affected dependencies, and prepares the right customer and subcontractor notifications.
Why it works
The customer hears about the delay before the office does, and the PM sees the ripple effect before it becomes a wasted day.
Duxor IQ scenario
Why this moment matters
A late crew is rarely just a late crew. The missed arrival can leave a customer waiting, compress the trade's work window, threaten an inspection, and push every dependent activity behind it. The operational problem is not discovering the delay at noon. It is recognizing the exception while the project still has choices, then making sure each affected person receives the right version of the truth.
Duxor can compare the scheduled arrival with approved work-hour presence and ETA signals, then connect that exception to the project schedule, downstream work, and customer commitments. The useful output is a reviewable response, not a vague alert. The project manager should see what appears to be slipping, why the system thinks so, what work may be affected, and which communications or schedule changes need approval before they occur.
Duxor IQ scenario
Signals Duxor can connect
The warning becomes credible when several ordinary project facts point to the same exception.
- 01
The electrician has an active assignment and arrival window, but projected arrival now exceeds the company's configured tolerance.
- 02
Travel, route, geofence, check-in, or approved manual status provides evidence about whether the crew is en route or still unconfirmed.
- 03
The live schedule shows drywall, inspection, or another activity depending on electrical completion or access to the same work area.
- 04
The customer record contains arrival expectations, access requirements, preferred channel, quiet hours, and the people permitted to receive an update.
Duxor IQ scenario
A controlled response
The response should reduce uncertainty first, then coordinate only the changes that an authorized person accepts.
Verify the exception
Duxor presents the scheduled start, current status, projected arrival, signal freshness, and any uncertainty. If location is unavailable or the evidence conflicts, the system asks for a manual confirmation instead of treating an estimate as fact.
Trace the impact
The platform follows the connected schedule to identify affected tasks, appointments, crews, inspections, and customer commitments. It distinguishes a delay that can be absorbed from one that requires a new plan, while leaving the final operational judgment with the project team.
Prepare the recovery
Duxor assembles proposed next actions such as confirming the new ETA, notifying the superintendent, protecting a dependent crew, or preparing a customer notice. External messages and high-impact schedule changes are held for review unless an approved low-risk rule explicitly allows them.
Confirm and follow through
After an authorized user accepts the response, the relevant schedule state, internal notifications, and approved external communication are updated together. Unacknowledged instructions remain visible so the project manager knows whether the recovery plan actually reached the people who must act.
Duxor IQ scenario
Who needs to act
Each participant needs a focused responsibility, not the entire operational picture.
Project manager or dispatcher
Reviews the evidence and downstream impact, chooses the recovery plan, and approves consequential schedule or customer-facing changes.
Crew lead and dependent trades
Confirm the revised ETA or readiness, acknowledge changed instructions, and report any constraint that makes the proposed recovery unrealistic.
Customer
Receives only the approved arrival update, access request, or next step through the preferred channel, without internal notes or unnecessary location detail.
What stays on the project record
The project history should retain the original assignment, status evidence, projected arrival, exception time, affected dependencies, recommended actions, reviewer, approvals, notifications, acknowledgements, and resulting schedule changes. If the office supplied a manual status because a phone was unavailable, that fact and reason should be visible too. The record makes a later schedule question answerable without reconstructing the morning from calls and texts.
What must be configured first
Reliable detection depends on accurate assignments, arrival windows, dependency links, project contacts, and company-defined lateness tolerances. Presence must operate only during approved work windows under visible company policy, employee permissions, and a manual fallback. Customer preferences and audience rules must identify what may be shared and with whom. The company must also decide which routine notices are preauthorized and which external or high-impact actions always require project manager review.
Duxor IQ 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.