The expensive change nobody approved
The homeowner casually tells a worker, "Could you add recessed lights over here too?"
Back to all risk scenarios
Representative construction risk scenario
10The expensive change nobody approved
A representative construction near miss, what happens without Duxor, and how the connected response can prevent the loss.
Without Duxor
The electrician installs six additional lights. The GC bills for the change. The homeowner says, "I thought that was included." Nobody knows exactly what was discussed.
With Duxor
The worker records the request: "Homeowner requested six additional recessed lights in the family room." Duxor immediately creates a pending change request and tells everyone, "This work is not yet approved. Estimated cost and schedule impact are being prepared." The homeowner approves digitally before work begins.
What timely action can prevent
A surprise invoice, unpaid work, and a dispute over what was approved.
Risk-prevention scenario
Why this moment matters
A homeowner's casual request for six more recessed lights can become labor, material, inspection, schedule, contract, and billing work within minutes. If the crew treats the conversation as authorization, the contractor risks unpaid work and a dispute about what was included. If the request is forgotten, the customer feels ignored. The safe middle is to capture the request immediately while making its unapproved status unmistakable.
Duxor can convert the field conversation into a pending change request connected to the original scope, project location, requested work, and customer. The project team can then prepare pricing, markup, schedule impact, and approval. The platform supports approval and e-signature, but it should not infer customer consent from casual wording or release changed work before the configured approver confirms it.
Risk-prevention scenario
Signals Duxor can connect
A potential change becomes visible when the request conflicts with approved scope or lacks required authorization.
- 01
A customer, crew member, or trade describes added, removed, or different work during a conversation, photo review, site visit, or field update.
- 02
The requested item is absent from the accepted proposal, approved selection, current task scope, or previously approved change record.
- 03
Labor, material, schedule, inspection, or dependent-trade consequences need review before the crew can responsibly proceed with the request.
- 04
No valid approval or e-signature is attached, while an assigned person or crew is approaching the point where changed work could begin.
Risk-prevention scenario
A controlled response
The workflow must separate listening to the customer from authorizing contractual and financial work.
Capture without promising
The worker records the customer's requested quantity, location, and intent in the project conversation. Duxor creates a pending change request and communicates its status without representing that price, schedule, feasibility, or approval has already been decided.
Define the impact
An authorized estimator or project manager reviews scope, cost codes, labor, materials, markup, billing, schedule, and affected work. Duxor keeps those elements connected, but qualified staff supply and approve the commercial and technical judgment.
Present for approval
The customer receives the approved change proposal through the permitted customer view or communication channel. The proposal can show scope, price, and schedule impact, and work remains pending until the designated approver completes the required confirmation or e-signature.
Release the work
After approval, Duxor records the contract and project impact, updates the connected work according to authorized actions, and notifies the responsible crew. If the request is declined or revised, that outcome also reaches the field before anyone proceeds.
Risk-prevention scenario
Who needs to act
The customer can request, but defined project roles price, approve, and release the change.
Field worker or trade partner
Captures the request accurately, makes no unauthorized promise, and waits for a released instruction before performing changed work.
Project manager or estimator
Clarifies scope, prepares and reviews cost and schedule impact, selects the approver, and controls release to the field.
Customer or contract approver
Reviews the documented proposal, asks questions, and explicitly accepts, rejects, or requests revision through the approved process.
What stays on the project record
The project record should retain the original request and speaker, time, location, source conversation, related scope, pending status, clarifications, estimate inputs, markup, schedule impact, versions, reviewer, customer delivery, questions, approval or rejection, signature, release time, crew acknowledgement, billing effect, and resulting work. This separates what the customer asked from what the contractor proposed and what both parties approved.
What must be configured first
The accepted scope, budget, cost codes, customer contacts, and approver identities must be current before change detection can be useful. The company should configure pricing and markup authority, approval and e-signature requirements, audience permissions, and the rule that pending work is not released. Contract interpretation, code implications, price, schedule commitments, and final approval remain with authorized people. Duxor coordinates and records those decisions rather than making them silently.
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.