PROJECT DELIVERY · SCHEDULING & COORDINATION
When one thing moves,
the whole schedule knows.
Trade sequences, dependencies and cross-project resource views for builders running multiple jobs at once.
A live residential build programme: fifteen phases, assignment and priority. The interface and phase structure are the real ones.
- Models: Trade sequences
- Sees: Every live job
- On change: Dependent work re-flows
- Pairs with: Scheduling Agent
The schedule lives in one person's head.
Run the sequence below and watch what a connected programme does with one late inspection: dependent trades re-flow, float is consumed before dates move, the shared crew clash surfaces on its own, and the finish-day arithmetic updates in front of you - with a scheduler confirming the change before any site hears about it.
- Sequence by memory: Who follows whom on site is tribal knowledge; when the scheduler is away, the sites drift.
- Changes cascade invisibly: One delayed trade pushes five others, and nobody sees the knock-on until crews collide.
- Resources double-booked: The same crew is promised to two sites because no view spans both.
Templates, dependencies, and live re-sequencing.
The build programme running on a live residential project: fifteen phases, node-level task breakdown, assignment and priority. The interface and phase structure are the real ones.
- Model the sequence: Trade templates capture how your builds actually flow: stages, durations, dependencies.
- Schedule across projects: Crews and resources are visible across every live job, not one at a time.
- Re-sequence on change: When something moves, dependent work re-flows and conflicts surface immediately.
- Notify and confirm: Affected trades and crews are flagged; your scheduler confirms the new sequence before it lands on site.
The parts of a programme that usually
live in one person's head.
- Trade sequence templates: How your builds actually flow, captured once and reused on every job.
- Dependency and conflict detection: Predecessors and successors modelled, so a clash is a warning, not a discovery.
- Cross-project resource views: Crews and equipment visible across every live job, not one at a time.
- Change-driven rescheduling: A slipped trade re-flows the dependent work automatically.
- Scheduling Agent on top: The agent proposes the re-sequence; your scheduler stays on the decision.
Scheduling discipline from a live group.
Our scheduling capability is exercised daily across DDDI Group's construction operations. The same logic powers our materials & labour system for trade contractors.
| Before | With the system |
|---|---|
| The sequence lives in one head | Templates hold it, for every job |
| Changes discovered on site | Conflicts flagged in the office |
| Crews double-booked across sites | One resource view spans them all |
- Exercised: Daily, inside DDDI
- Also powers: Materials & Labour
- Status: Live
Moving parts in.
Consequences out.
Site apps and calendars keep working. The system reads progress and delivery signals inside a boundary agreed before anything connects.
- What the system reads: The moving parts a schedule has to reconcile. (Data in) (Programme templates and dependencies; Trade sequences and crew assignments; Delivery windows; Site progress updates)
- What it gives back: A schedule that shows consequences before they reach site. (Outputs) (A live, connected programme; Conflict and readiness flags; Re-sequence proposals for approval; Views per site and per trade)
- Confirmation calls, made for you: An AI call agent rings the trade or supplier, confirms the time, writes back the outcome, and hands the call to a person when a real decision is needed. (The last mile): Runs on your existing phone system. Every call recorded.
Common questions.
Is this a Gantt tool?
It includes programme views, but the point is operational: dependencies, crews and conflicts, not just a chart.
Can it start with one project?
Yes. Most teams start with one live job and extend across the portfolio once the sequence templates settle.
Does it connect to our existing tools?
Yes. See Integrations & Data for how we connect site and office tools.
WHERE PROJECT TIME ACTUALLY GOES
Building is the short part.
Actual building accounts for less than half of a project's total time - the Commission's example is an apartment complex that takes seven to 10 years to complete but involves only one to two years of actual building. The Commission's term for what unmanaged dependencies do to the rest of the programme is "cascading failures". One late gate reprices every trade behind it.
A schedule that carries its dependencies explicitly is how a delay stays a delay, instead of becoming a cascade. Figures as published in the Commission's February 2025 research paper, analysing data mostly to 2023-24.
A programme is only as good
as the day it survives.
Send us one live programme and the changes it went through last month. We will show you which of those changes the system would have made visible on the day.