Live Coordination
Connected project data, explicit rules, permissions, integrations, and current AI power the real-time coordination described throughout the V1 scenarios.
Real situations. Connected responses.
Every Duxor capability begins with a failure story contractors already know: a customer waiting at home, a late trade affecting three others, an important message disappearing, or a PM spending the morning rebuilding the truth.
A real moment a GC, PM, superintendent, subcontractor, or customer immediately recognizes.
How the platform connects the people, project, schedule, communication, and next action.
The connected project context that lets the software respond to the job, not just one isolated update.
Duxor IQ scenario
See how Duxor connects more field problems to the people and actions that resolve them.
Product direction in three horizons
The first 31 scenarios define V1 and describe how Duxor works across connected project operations. Planned capabilities add deeper prediction and optimization after V1. Future concepts depend on the physical world, network-scale intelligence, or substantial autonomy.
Connected project data, explicit rules, permissions, integrations, and current AI power the real-time coordination described throughout the V1 scenarios.
Capabilities that need accumulated operating history, calibrated prediction, deeper optimization, or more reliable visual reasoning.
Capabilities that depend on spatial modeling, sensors, broad external ecosystems, network-scale learning, or meaningful autonomous control.
The Duxor scenario library
Filter by phase or search by role, moment, or keyword. Every row is one real failure story and the connected response it triggers.
| Horizon | Scenario | Duxor solution | Why it works |
|---|---|---|---|
| V1 | 01 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. |
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. | The customer hears about the delay before the office does, and the PM sees the ripple effect before it becomes a wasted day. |
| V1 | 02 The customer stayed home for nothing A homeowner rearranged work, put the dog away, cleared the driveway, and waited all morning. The visit was moved internally, but nobody told them. |
Duxor connects schedule changes to customer commitments and automatically sends the updated time, what changed, and what the customer needs to do next. | A change that normally creates anger is handled before the customer ever has to ask, "Is anyone still coming?" |
| V1 | 03 A crew can arrive early, but the customer is not ready A crew finishes another job two hours early and heads toward the next project. The homeowner is away, and an unannounced arrival could turn useful time into another missed visit. |
Duxor offers the customer the earlier arrival and waits for approval before redirecting the crew. | An unpredictable field day becomes a customer convenience instead of another coordination failure. |
| V1 | 04 An unfamiliar worker is walking toward the house A truck pulls into the driveway. The customer has no idea who is arriving, what company they work for, or why they are there. |
Duxor sends the worker or crew name, company, purpose of the visit, expected arrival, and whether access or customer presence is required. | The customer feels informed and safe before the doorbell rings, even though nobody in the office had to send a manual message. |
| V1 | 05 The customer does not know what tomorrow will bring The homeowner wants to know who is coming, whether they need to be home, whether work will be noisy, and whether water or driveway access will be affected. |
Duxor turns the live schedule into a personalized next-day briefing with arrival windows, access needs, disruptions, and action items. | Every customer gets the kind of thoughtful preparation normally provided only by an exceptional project manager. |
| V1 | 06 The crew leaves, and the customer has no idea what happened Workers leave at 2:00. The customer cannot tell whether the work is complete, paused, blocked, or continuing tomorrow. |
Duxor combines completed tasks, notes, photos, inspections, and the next scheduled activity into a clear end-of-day update. | The customer sees progress without the superintendent spending the evening writing polished summaries. |
| V1 | 07 The jobsite is empty, so the customer assumes the project is behind Nobody is working at the house for two days. The homeowner sees inactivity but cannot see the inspection, material, or dependency work happening behind the scenes. |
Duxor explains the current phase in plain language, including what was completed, what the project is waiting on, and what happens next. | Invisible construction logic becomes understandable, so silence no longer looks like neglect. |
| V1 | 08 A customer request gets buried in a text thread The homeowner says, "My baby sleeps until 10. Please do not work in the nursery before then." The message is read once, then disappears under dozens of other messages. |
Duxor turns the request into a project instruction tied to the right room, date, task, and crew, then surfaces it when it becomes relevant. | The customer speaks naturally one time, and the instruction reappears at the exact place and moment where it matters. |
| V1 | 09 A customer sends a photo and says, "This does not look right" Water appears near a newly installed window. The customer does not know who installed it, what trade owns it, or who should receive the photo. |
Duxor connects the image to the project and location, preserves the context, creates an issue, and routes it to the right person for review. | One photo becomes a documented, assigned workflow without a chain of calls, texts, screenshots, and forwarded images. |
| V1 | 10 The superintendent is too busy to navigate software Walking the job with gloves on, the superintendent sees missing fire blocking that will affect inspection and drywall. He is not going to stop and fill out four forms. |
He says, "Duxor, create an issue for missing fire blocking, notify Daniel, hold drywall, and update the PM." Duxor prepares the connected actions for confirmation. | A spoken sentence changes the system of record and completes the administrative work around the field decision. |
| V1 | 11 An important message dies in conversation A subcontractor texts, "We are running 40 minutes late." The message is technically delivered, but nobody updates the schedule, customer, or downstream trades. |
Duxor turns the message into an operational event, identifies who is affected, and proposes the relevant schedule changes, notifications, and follow-up. | Communication stops being passive. The message itself becomes the coordinated response. |
| V1 | 12 One small delay quietly affects five other things Electrical slips by one day. That may affect inspection, insulation, drywall, another subcontractor, and the homeowner's expectations. |
Duxor follows the dependency chain and shows every task, person, appointment, and customer commitment that may need attention. | The system understands that the problem is not the late electrician. The problem is everything downstream. |
| V1 | 13 The PM has to rebuild the response from scratch A failed inspection creates six calls, three schedule edits, two customer updates, and a question about where to move the crew. |
Duxor presents the affected work, recommended notifications, suggested schedule changes, and next actions in one reviewable response. | Instead of discovering the solution one phone call at a time, the PM sees the whole recovery plan together. |
| V1 | 14 The field and office speak different languages The PM writes in English. The crew is more comfortable in Spanish. Important nuance is lost, and the PM becomes the translator for every exchange. |
Duxor delivers each message in the recipient's preferred language while preserving the original text, project, task, and conversation context. | Everyone participates in one operational conversation without separate threads or a human translator in the middle. |
| V1 | 15 The most important instruction was sent, but nobody knows whether it was understood A schedule change goes to the drywall subcontractor. The message shows as delivered, but the crew arrives anyway because nobody acknowledged it. |
Duxor tracks receipt, acknowledgment, unresolved status, and escalation rules, then alerts the next responsible person when necessary. | The gap between "sent" and "actually understood" becomes visible and manageable. |
| V1 | 16 Every customer wants communication differently One customer wants daily detail. Another only wants major milestones. One prefers text, another email, and another never wants messages after 7:00 PM. |
Duxor respects preferred language, channel, detail level, quiet hours, arrival notice, access needs, and presence requirements. | Automation feels personal because the system communicates the way each customer actually wants to be treated. |
| V1 | 17 Nobody can explain why the schedule changed Weeks later, someone asks why drywall moved. The answer is scattered across texts, calls, photos, emails, and memory. |
Duxor keeps messages, decisions, photos, voice actions, approvals, schedule changes, and acknowledgments connected to the work they affected. | Ask, "Why did this move?" and see the cause, decision, people notified, and resulting change in one place. |
| V1 | 18 The PM spends the morning asking people where they are The first hour of every day disappears into calls and texts: "Are you there yet? Did you finish? Did inspection pass? Where is the truck?" |
Duxor assembles live project status, schedules, crew presence, expected arrivals, vehicles, equipment, and urgent exceptions into one operating view. | The morning status meeting is already built before the owner starts calling people. |
| V1 | 19 The field hates software because software slows the field down A crew lead needs today's address, task, route, notes, checklist, and photos, but the app requires too much typing and too many screens. |
Duxor presents a fast, field-first daily experience with voice actions, arrival controls, current assignments, and only the information needed now. | The office becomes better informed without forcing the field to stop working and become office staff. |
| V1 | 20 The same skid steer is promised to two jobs Two PMs schedule the same equipment item for the same morning. Nobody notices until both crews are waiting. |
Duxor connects people, vehicles, tools, specialized crews, availability, reservations, maintenance status, and job assignments. | The conflict appears while it is still a calendar problem, not after two jobs have lost half a day. |
| V1 | 21 A crew is at the wrong place, or not where the day expects them to be A crew arrives at the wrong address, a vehicle is still at yesterday's job, or a specialized installer has been assigned elsewhere. |
Duxor compares assignments, schedules, current or last-known location, and resource responsibility to surface mismatches and conflicts. | The operating plan notices reality drifting away from the schedule before a person has to report it. |
| V1 | 22 The truth about the job is spread across six systems The estimate is in one place, schedule in another, photos in a third, customer communication in text messages, and the final cost in accounting. |
Duxor connects the lead, estimate, schedule, field work, communication, approvals, changes, costs, invoicing, closeout, and warranty history to one project timeline. | The reason, decision, work, customer experience, and financial effect remain connected instead of disappearing during handoffs. |
| V1 | 23 Tomorrow's delay is already visible today The electrical crew is scheduled for tomorrow, but today's job is behind, materials are not confirmed, and the prerequisite inspection is still open. |
Duxor checks incomplete prerequisites, current field progress, open inspections, unconfirmed materials, travel conditions, weather, and explicit project rules to flag work that is already at risk before anyone reports a delay. | The system warns about tomorrow's likely failure while there is still time to remove the blocker, move the crew, or reset expectations. |
| V1 | 24 The customer needs one clear answer, not a Gantt chart The project has hundreds of tasks, but the homeowner only wants to know whether things are healthy, what happens next, and whether they need to act. |
Duxor presents a project heartbeat with current phase, next milestone, schedule confidence, important changes, and customer decisions. | A complex construction schedule becomes understandable in five seconds. |
| V1 | 25 The customer asks a question nobody wants to route manually The homeowner asks, "Do I need to be home tomorrow?", "Can I use the sink tonight?", or "Why did the completion date move?" |
Duxor answers from the actual schedule, field notes, permissions, work status, and approved project information, with confidence limits and escalation when needed. | The project itself becomes conversational, without inventing answers or sending the customer through a phone tree. |
| V1 | 26 The project is on schedule, but the customer relationship is deteriorating There have been three schedule changes, two unanswered messages, repeated portal checks, and increasingly frustrated wording. |
Duxor watches explicit warning signals such as repeated schedule changes, unanswered messages, missed commitments, repeated status checks, and increasingly frustrated wording, then recommends personal outreach. | The system recognizes a relationship at risk before the complaint, bad review, or withheld payment arrives. |
| V1 | 27 A simple customer request has hidden project consequences The homeowner says, "Can we add heated floors?" It sounds small, but may affect electrical capacity, flooring, inspection, cost, and completion. |
Duxor identifies the affected trades, materials, approvals, dependencies, schedule, and likely cost implications before the change is approved. | The customer sees the real consequence of the request before a casual yes becomes an expensive surprise. |
| V1 | 28 The owner opens the system and sees too much data Twenty projects, dozens of crews, hundreds of tasks, and thousands of updates make a traditional dashboard harder to interpret than a phone call. |
Duxor creates an executive morning brief showing what is normal, what changed, which projects need attention, where customer confidence is at risk, and which actions matter most. | The owner gets a chief-of-staff briefing instead of another dashboard that creates more work. |
| V1 | 29 Everyone starts the day by rebuilding a to-do list PMs, superintendents, and crew leads each scan messages, calendars, notes, and yesterday's issues to figure out what matters today. |
Duxor generates a focused daily plan for each person based on assignments, deadlines, travel, unresolved decisions, exceptions, and role. | Every person opens the system and sees the few things that matter today, without someone manually recreating the list. |
| V1 | 30 The installer discovers the missing material after arriving The crew is scheduled, but the cabinet delivery moved, the receiving status is unclear, and nobody connected the supplier update to the field schedule. |
Duxor connects order status, delivery expectations, receiving, dependencies, supplier history, and scheduled work to flag material risk in advance. | The installer is no longer the first person to discover that the materials never arrived. |
| V1 | 31 Years later, nobody remembers why something was built that way An owner asks why an outlet is in an unusual location or why a product was substituted. The original team is gone. |
Duxor preserves the decision, approval, change, installer, date, supporting photos, product information, and resulting as-built condition as part of the project's permanent memory. | The connected project record becomes more valuable every year because it preserves why the building was built the way it was. |
| Planned | 32 An inspection fails, and the PM needs the best recovery plan The failure affects several trades and may either add cost or move the completion date. The PM has to decide quickly. |
Duxor proposes alternate sequences, crew moves, overtime, customer communication, and schedule options with estimated time and cost impact. | The system does not just report the disruption. It explains practical ways out and the tradeoffs between them. |
| Planned | 33 Two customers need completely different levels of reassurance One customer wants every detail. Another gets annoyed by constant updates. The PM cannot maintain a separate communication strategy for every project. |
Duxor learns preferred frequency, level of detail, successful communication patterns, and when a phone call works better than automation. | The customer experience adapts over time without requiring the PM to remember dozens of personal rules. |
| Planned | 34 The update says work is complete, but reality may disagree The flooring crew left early, required photos are missing, and field activity does not match the planned area, but the schedule still says complete. |
Duxor compares claimed progress, planned work, crew activity, required evidence, and visual inputs, then asks for confirmation before customer communication is sent. | The system checks whether the story matches the evidence before confidently telling the customer the wrong thing. |
| Planned | 35 The GC wants to know what happens if cabinets are two weeks late A supplier delay is possible, but the real impact depends on sequence, dependencies, crew availability, and what can be done out of order. |
Duxor simulates the likely outcome and compares recovery options, such as completing flooring first or moving crews to other work. | The schedule becomes something the GC can reason with, not just a collection of dates to edit. |
| Planned | 36 The company feels recurring pain but cannot prove where it comes from One supplier seems slow. One crew seems to create callbacks. One municipality feels difficult. The owner has opinions but not connected evidence. |
Duxor finds recurring sources of delay, margin loss, inspection failure, callbacks, customer frustration, and crew or supplier performance across project history. | The platform reveals expensive patterns the company has felt for years but never had enough connected data to prove. |
| Future | 37 The building is finished, but its knowledge disappears into folders Plans, photos, serial numbers, product selections, hidden utilities, warranties, and field decisions are scattered across closeout documents and personal memory. |
Duxor builds a living digital twin connecting the physical building to the complete project record and later service history. | The finished project leaves behind a useful digital version of itself, not a box of documents nobody can search. |
| Future | 38 The owner wants to know what is behind a finished wall A service technician needs to locate a pipe, wire, blocking, or hidden condition without opening the wall. |
Duxor combines pre-close photos, plans, measurements, spatial mapping, and augmented reality to estimate what is behind the surface. | Point a phone at a wall and see the project memory that existed before drywall covered it. |
| Future | 39 The crew is arriving, but nobody is home to provide access The customer approved the visit, but traffic changed the arrival time and the house is still locked. |
With permission, Duxor can coordinate temporary smart-lock or garage access, confirm crew identity, limit the access window, and expire credentials after the visit. | The project can securely open the right door for the right crew at the right time, then close the permission automatically. |
| Future | 40 The customer is about to return to a dusty or unsafe environment Sanding ran long, humidity is high, or air quality has not recovered, but the customer still expects to return at the original time. |
Duxor uses environmental signals such as dust, air quality, moisture, noise, temperature, or humidity to guide work and customer communication. | The project can protect the customer's real physical experience, not just update the calendar. |
| Future | 41 A routine progress photo quietly contains a serious clue A tile pattern may not match the approved selection, a railing may be missing, or a fixture may be offset from the drawing. |
Duxor reviews photos and video for possible mismatches, quality concerns, safety conditions, missing components, or unexpected progress, always subject to human review. | A photo taken for documentation can surface a hidden problem before the next trade covers it. |
| Future | 42 The wrong product arrives, but nobody notices until installation Two left-hand windows arrive when the order requires one left-hand and one right-hand unit, or a delivered finish does not match the approved selection. |
Duxor compares labels, counts, product imagery, purchase orders, approvals, and project requirements at receiving. | The system can question the delivery before the wrong material is installed and the schedule is damaged. |
| Future | 43 A pattern is too broad for one contractor to see Inspection times are increasing in a municipality, a supplier is slipping regionally, or a construction sequence is producing more callbacks across many companies. |
Using privacy-protected network data, Duxor detects trends across contractors, suppliers, project types, municipalities, and regions. | The platform can know that something is changing before any single contractor has enough data to prove it. |
| Future | 44 The operating plan becomes wrong a hundred times a day Traffic changes, crews finish early, deliveries move, customers respond, equipment fails, and inspections shift. People manually patch the schedule all day. |
Duxor continuously improves crew assignments, project sequence, travel, resource use, customer communication, and exception handling within company rules. | The operating plan adapts as reality changes instead of waiting for a person to notice every deviation. |
| Future | 45 People spend the day coordinating information the project already understands Routine changes still require someone to move dates, notify people, request acknowledgment, reschedule dependent work, and follow up. |
Within explicit permissions and guardrails, Duxor handles routine schedule adjustments, notifications, reminders, escalations, resource moves, and follow-up automatically. | People remain accountable for important decisions, but the project begins helping manage itself. |
The underlying idea
Each row is the same move at a different range: connect what just happened to everyone and everything it touches, then act while it still matters.
Connect the message, schedule, customer, people, location, dependencies, and next action while the day is still moving.
Recognize risk before it is reported, explain likely consequences, and recommend practical recovery options.
Give the building memory, connect visual and environmental evidence, learn across projects, and automate routine coordination within clear guardrails.
Product scope. V1 is the complete first-release scope and is described as the Duxor product throughout this site. Planned and Future are explicitly post-V1 and are not part of the first release.
The late crew. The missed handoff. The buried customer decision. The wasted trip. The schedule surprise. We will show how the connected workflow should respond.