Master Operations · AI Workforce for Site & Programme Delivery

Your programme, recovered.

The workforce that runs while you walk the site. A sub delays the slab pour? Re-runs the critical path. Identifies affected trades. Drafts the EOT response. Orchestrates the catch-up. What you can't recover manually, the workforce recovers in days.

Start the 15-day pilotSee the Marketplace extensions
A project director's desk: printed P6 Gantt with red annotations on the left, Vonbuild's critical-path recovery on the right

Left — the Gantt you re-draw by hand every Monday · Right — the recovery options Vonbuild models overnight

Who Master Operations serves

Not just the project director.

The project director is the daily driver. But Master Operations runs into every signal that touches delivery — site coordination, engineering risk, supplier slip, claim defence. Four roles converge.
Project Director
Primary driver
Project Director
Recovery scenarios, portfolio reporting, EOT defence.
Site Manager
Also uses
Site Manager
Subcontractor coordination, snag tracking, daily reports.
Engineer
Also uses
Engineer
Technical impact of variations, sequencing alternatives.
Commercial Manager
Also uses
Commercial Manager
Variation cost analysis, claim quantum, EOT submissions.
Marketplace · Operations extensions

Six patterns your firm builds.

Reusable capabilities your firm builds once. Workflows, knowledge packs, mini-apps, always-on agents, encoded processes. The six below are examples — your library grows from your protocols. DSI keeps the governance gate.
Workflow
2 wk → 2 days
EXT-OPS-01

Recover the delayed project

The signature workflow below. Critical-path re-run. Recovery options. EOT defence. Coordinated catch-up briefs.
Agent
always-on
EXT-OPS-02

Multi-sub coordination autopilot

On your project, runs the always-on chase across every sub — flagging issues against the firm's full sub-performance history (non-sensitive). Portfolio-wide always-on monitoring = roadmap.
Process
2 wk → 2 days
EXT-OPS-03

Snag handover protocol

Your OPR / réception checklist, encoded. Every defect tracked, photographed, assigned, closed — to your house standard, on every project.
Mini-app
ad hoc
EXT-OPS-04

Run windowed delay analysis

Forensic windowed delay analysis (SCL Protocol-aligned). As-planned vs as-built variance, defensible in front of an arbitrator.
Knowledge pack
always-loaded
EXT-OPS-05

Multi-program portfolio reporting

Per-project programme dashboard today — budget, schedule, risk, change orders, refreshed daily. Multi-program aggregation across 8–15 projects = roadmap.
Workflow
6 wk → 1 wk
EXT-OPS-06

Assemble the ~5K-doc handover

As-built drawings, certificates, O&M manuals, warranties, test reports. Indexed, searchable, client-ready.
Inside the app · Marketplace

Where your firm's site methods live.

Every snag-handover protocol, every sub-coordination workflow, every windowed-delay analysis your team builds — versioned, audited, available to every project manager from day one.

Extensions

Context
vonbuild·Org=design_officeFunc=engineering
Filters
Organisation:design_office×Function:engineering×Disable auto-filters
+ Filter
⌕
Clear all
Plugins9— groups skills + agents + commands
Legal & Contractspluginvonbuild

Construction contract analysis, claims management and legal risk assessment

7 / 26 workspaces· Legal
1 skill
Estimation & Costingpluginvonbuild

Construction estimation — DPGF/DQE/BOQ analysis, quantity validation and unit price comparison

Active everywhere· Sales
2 skill
Site Operationspluginvonbuild

Site supervision, defect tracking, daily reports and works acceptance

7 / 26 workspaces· Ops
1 skill
Planning & Orchestrationpluginvonbuild

Multi-agent orchestration — workspace scan, document classification and execution roadmap generation

10 / 26 workspaces· Plan
1 agent
Procurement & Subcontractingpluginvonbuild

Supplier management, invoice verification, subcontract tracking

3 / 26 workspaces· Proc
1 skill
Technical Directionpluginvonbuild

Technical feasibility, pre-construction studies, engineering review (Eurocode / DTU / SIA)

3 / 26 workspaces· Tech
1 skill
Skills7— not attached to a plugin
DTU StandardsskillvonbuildFR

DTU pitfalls — installation errors causing non-conformities and insurance claims.

9 / 26 workspaces
SIA StandardsskillvonbuildCH

SIA standards — Swiss federation of engineers and architects technical norms

5 / 26 workspaces
FIDIC Contractsskillvonbuild

Standard FIDIC contracts — Red, Yellow, Silver books for international construction

5 / 26 workspaces
CCAG TravauxskillvonbuildFR

CCAG general administrative clauses for public works in France

5 / 26 workspaces
MCP3
Revit 2027mcptenant

Autodesk Revit 2027 — BIM model querying, family extraction, clash detection via Computer Use.

0 / 26 workspaces
ERP 2027mcptenant

Sage / Cegid ERP 2027 — purchase orders, supplier ledgers, situation reports.

Active everywhere
HubSpotmcptenant

HubSpot CRM — deals, contacts, pipeline sync for the Sales tower.

0 / 26 workspaces
One pattern · The 3-month delay recovery

Recover a delayed project.

One pattern, many deliverables. Delay recovery today. Snag handover next. Multi-program reporting the week after. Same workflow: re-run the critical path, coordinate the trades, build the audit-grade record.
delay-recovery-builder.workflow47 workers · RUNNING
01Programme ingest
Pulls the live schedule from MS Project, P6, or Asta Powerproject. Indexes every activity, dependency, float consumption.
02Delay attribution
Windowed forensic analysis identifies the as-built deviation per work package. Attributes each slip to its triggering event.
03Critical-path re-run
Alternative sequences modelled with cost / schedule trade-offs. Resource leveling across the affected trades.
04Recovery options
Top 3 recovery scenarios with sub reallocation, weekend shifts, parallel zoning. Cost delta + schedule recovered per option.
05Coordinated brief
Per-sub catch-up brief + EOT defence file + client notification letter — drafted, ready for your sign-off.
Consolidated output · 2 days end-to-end
Updated programme · 47 subs coordinated · 3 recovery options modelled · EOT defence built · client notification drafted · 78 days recovered. Action-ready.
47
Subs coordinated
2 days
vs. 2 weeks senior
3 options
Recovery modelled
~80 days
Recovered
Time stats are illustrative — industry benchmarks (Monograph 2025, Part3 2025) compressed by the workforce model. Not measured Vonbuild outcomes per project.
Live process · Operations cascade

You query Operations. Five agents react. One status report.

A scheduled progress check fires. Master Operations spawns five site-monitoring agents in parallel. Schedule, snags, subs, slip — all reconciled into a single weekly status. Subcontractor follow-up auto-queued.

Signal

Weekly progress check fires at 14:32.

Any source can fire it: a file dropped in OneDrive / Google Drive / any drive, an email landing in Outlook, a scheduled task firing, or you pressing a button. In this scenario, an event arrives via SCHEDULE.

Source: SCHEDULE · weekly-progress-check.task
Routing

MASTER OPERATIONS routes.

It classifies the impact across 21 semantic categories and dispatches to the 5 specialized agents concerned. No human in the loop. No meeting scheduled.

5 specialized agents dispatched · 312 ms
Parallel reaction

5 specialized agents. In parallel.

Each agent accesses its own toolset — apps, browsers, MCP connectors, project documents and company knowledge — and produces a structured output. Concurrently, not sequentially.

AGENT
Schedule Planner
Gantt v3.2
dependencies remapped
AGENT
Subcontractor Tracker
12 chases
subcontractors followed up
AGENT
Progress Verifier
94% actual
vs 97% planned (W42)
AGENT
Defect Logger
8 snags
items pending sign-off
AGENT
Critical-Path Monitor
+4 days
critical path slip
5 outputs produced
Convergence

Outputs return. One narrative.

The 5 specialized agents return their outputs to MASTER OPERATIONS. It reconciles them into a single decision card.

1 reconciled decision
Validation

Handed to you. One click.

Master Operations delivers the weekly status. Schedule remapped, subcontractors chased, progress verified, defects logged, critical-path slip quantified. Full evidence chain. One trace ID. Status ready to circulate.

3 min · signal → decision
Self-scheduled trigger

T+3 DAYS LATER. The system wakes itself up.

During the parallel phase, a agent scheduled a follow-up task on its own. T+3 DAYS LATER — without you, without a meeting, without a reminder email — MASTER OPERATIONS wakes itself, dispatches the right agent, and executes autonomously. You delegated the mental load.

T+3minT+3 DAYS LATER · auto-fired
Auto-fired · 0 human intervention
Specialization · The corpus

Built for the standards your site runs on.

Pre-trained on the project-management corpus and coordination methods your work runs on, with regional handover variants.
Site management standards
ISO 21500 / 21502PMI PMBOKPRINCE2AACE TCMAACE 29R-03 (forensic delay)SCL Delay & Disruption ProtocolRéception / OPRBauabnahmeSIA BauausführungBS 6079NEC ECC clauses
Coordination methods
Critical Path MethodAs-planned vs as-builtWindowed delay analysisTime Impact AnalysisResource leveling3-week look-aheadSitrap / daily reportRFI / NCR trackingOPR / réservesPractical Completion / DLPSub catch-up planFloat consumption
A week with Master Operations

What changes for a site manager.

Monday. Mason 2 weeks behind. The agent re-ran the critical path overnight. By 7am: 3 recovery options modelled, EOT case prepared, per-sub catch-up briefs drafted. Monday choosing the option. Tuesday executing. Wednesday the slab is pouring.
Input · Sub slip detected
Mason 2 weeks behind
5 affected trades · 8 critical activities
Output · 7am next morning
3 recovery options modelled. EOT case prepared. Per-sub catch-up briefs drafted.
Input · Always-on
P6 schedule under watch
Daily updates · float consumption
Output · Continuous
Drift detected before site notices. Alerts at float consumption thresholds. Variance attribution.
Input · Practical Completion
5,000-document handover
As-built · O&M · warranties
Output · 1 week
Indexed handover pack. Gaps flagged. Defects liability dossier ready. Client-acceptance ready.
The picture you used to assemble by Friday is on your screen by 7am Tuesday. What you can't recover manually, the workforce recovers in days.
Always on · Always aware

The site remembers itself.

Every site report. Every RFI. Every NCR. Every sub message. Captured the moment it lands. Connected to the programme. Indexed for the claim that hasn't happened yet.
Project-centric · firm-aware on non-sensitive · sensitive stays gated
47 documents indexed
Ingestion processing 47 documents
Automatic capture

You don't upload. It sees.

Every daily report logged in Procore. Every RFI raised. Every NCR closed. Every Teams thread with the subs. Every programme update in P6. Captured the instant it arrives. The site memory grows itself.
Hidden connections

Dots you can't see, joined.

A daily report from week 14. An RFI on the mason works. A weather delay note. A sub's late material delivery. The system sees the chain. Ask anything across the project — get a sourced answer in seconds.
Team-shared

Your conductor sees what the planner re-ran.

Site QS sees the daily report the field agent ingested. Project director sees the programme the planning agent updated. Foreman sees the RFI the structural agent answered. Same site memory, different views.
EOT-ready

The EOT file is built before the EOT claim.

When the contractor disputes the delay, the file is there. Every event timestamped. Every weather day logged. Every sub message preserved. Every causality traced. Nothing to reconstruct.
Working into the future · Self-scheduling
Visible in your Outlook · calendar "Vonbuild"

Schedule any task — once or recurring.

The same modal your site manager uses to schedule a Monday walk is the engine the agent uses to schedule its own future work — autonomously, no prompt needed. Both surface in the same Outlook "Vonbuild" calendar. The agent chases the laggard subs; you read the exceptions.
Option A · One-time
Option B · Recurring
Live demo · Computer Use on your stack

It runs Procore, P6, and Teams the way your team does.

No new app for your site team to install. The agent operates the systems they already trust — re-runs the critical path inside your existing schedule, posts updates to your existing site report, sends coordination messages from your existing Teams.
app.procore.com/projects/aldgate-tower/schedule/recovery-2026-05
Worker · running
Trades affected
Mason · 14d slip
Electrical · blocked
MEP · blocked
Cladding · queued
Concrete · pour pushed
42 more affected ↓
Worker action — critical_path_recompute
Re-running critical path — 47 activities affected by mason 14-day slip in zone B3
elapsed 00:23 · est. remaining 00:12
Recovery options modelled
Option ASecond mason team · +£287K · recovers 18 days
Option BRebar resequence · +£42K · recovers 12 days
Option CWeekend shifts × 4 · +£163K · recovers 22 days
EOT caseBuilt · ready for legal review
Operates inside your existing stack
MS ProjectPrimavera P6Asta PowerprojectProcorePlangridDaluxTeamsSharePoint
Site WiFi tolerant. Runs server-side. Site teams open results when connectivity returns.
Mechanism · How it works

One event. N coordinated responses. One recovered programme.

01
Decompose
The event breaks into per-trade, per-zone, per-package impacts. Every affected activity in the critical path identified.
02
Spawn workers
One worker per affected sub, per zone, per WBS element. 47 affected activities, 47 workers. No queueing.
03
Load extensions
Marketplace extensions run — critical-path engine, delay-attribution analyzer, sub coordination orchestrator, snag tracker.
04
Consolidate
Updated programme + 3 recovery options + per-sub catch-up brief + EOT defence pack + client notification — ready for your decision.
Master Operations is the workforce that does the chasing your day eats. 47 subs on a project? The agent maintains the live programme, reads every site report, watches every Teams thread, intervenes only where the system needs you — exception-driven, not status-meeting-driven. The site manager you have stays on the site. The chase happens on its own.
Four routes. One promise.

How the work actually gets done.

When the agent picks up a task, it works through these four routes in order. Whatever produces a real, verifiable result, ships. If nothing does, you hear back — never with a made-up number.
01
A tool that already exists

Reach for what's on the shelf.

Your firm has built this workflow before. Or Vonbuild ships it out of the box. The agent picks the right one and runs it — like your engineer reaching for a checklist they trust.
02
A tool the agent builds

Make the missing one.

Need a calculation nobody's done in your firm yet? Hand the agent the norm — EN 13474 for glazing, Eurocode 2 punching shear, RT2020 thermal. It builds the calculator, checks it against known cases, runs your project. Next project, that calculator's already in your firm's library.
03
A tool that talks back

Connect straight through.

Some of your software — Revit, a growing list of cloud tools — lets the agent connect directly, without going through screens. No clicking, no waiting. The cleanest route when it's available.
04
A tool the agent uses like you would

Click through, like an engineer would.

Everything else — Robot, ETABS, Coupa, Procore, your supplier portals. The agent logs in with your licence and works the interface exactly as your engineer or QS would. Same software, same result, same paper trail. None of your hours.
Or — you hear back, with the reason
No made-up numbers
When none of the four routes works, the agent tells you what it tried, where it stopped, and what would unblock it. It does not invent a number to fill the gap. The output on your screen is always a real result from a real tool — or there's no output.
Polycentric model

Operations alone, or Operations in concert.

Operations leads (sole driver)
  • Delayed-project recovery
    Live programme re-run, recovery options, coordinated catch-up briefs.
  • Snag handover & DLP close-out
    Defect tracking through Practical Completion to DLP expiry.
  • Multi-sub coordination autopilot
    Always-on chasing across every sub on every project.
  • Multi-program portfolio reporting
    8–15 projects aggregated, refreshed daily.
Operations supports another lead
  • Variation impact assessment
    Engineering / Sales lead · Operations quantifies the schedule consequence
  • Sub termination
    Legal leads notice + reservations · Operations leads execution
  • Site dispute / claim defence
    Legal leads · Operations rebuilds the factual chronology from site reports
  • Bid resource validation
    Sales leads · Operations confirms feasibility within firm capacity
See the full polycentric model →
What this workforce guarantees

“I already run my programme in P6 / Asta. Where does the live schedule come from, and what happens to the critical path I've spent weeks tuning?”

The schedule comes from your file every time — P6, Asta, MS Project. The workforce reads it, never replaces it. Your critical path stays yours: the agent attributes slips, models recovery options, drafts the EOT defence. You pick which option goes live, then push the updated programme back to your existing file. Tuning preserved. Logic preserved. Audit trail intact.
Your programme file stays the source of truth
P6, Asta, MS Project — your file holds the schedule. The agent reads it, computes against it, never overwrites your logic.
Critical-path impact, not replacement
Slip-by-slip attribution. As-planned vs as-built variance. Your CP tuning preserved; only float consumption and recovery options surface for your decision.
Recovery modelled, not imposed
Top 3 recovery scenarios with cost / schedule trade-offs. You pick the option. The push back to your programme file is yours to approve.
Forensic-grade delay record
Windowed analysis aligned with SCL Protocol. Defensible in front of an arbitrator years after Practical Completion.
audit_trail.json
{
"project_id": "ALD-TWR-2026",
"event": "mason_14d_slip_zone_B3",
"critical_path_recomputed": true,
"affected_activities": 47,
"recovery_options": [
  { "option": "second_mason_team", "cost_delta_GBP": "287K", "schedule_recovered_days": 18 },
  { "option": "rebar_resequence", "cost_delta_GBP": "42K", "schedule_recovered_days": 12 },
  { "option": "weekend_shifts_x4", "cost_delta_GBP": "163K", "schedule_recovered_days": 22 }
],
"eot_case_built": true,
"client_notification_drafted": true,
"subcontractor_briefs_drafted": 47,
"windowed_delay_analysis": "SCL_protocol_aligned"
}
Live demo · Audit trail

47 subs coordinated. Every causality traced.

Master Operations → per-sub worker → site report + P6 update + Teams chase. The full execution graph stays visible, SCL-Protocol-aligned, arbitration-defensible years after Practical Completion.
Conversation graph
Tick conversations to spawn or merge them.
0 selected
Merge 0 conversations
Into tower
Master
Legal
Sales
Technical
Operations
Procurement
Cancel
Live demo · Human-in-the-loop

The agent drafts. You decide which recovery ships.

Every EOT letter, every sub catch-up brief, every client notification blocks for your explicit approval. The agent models the recovery options; you pick one and lock the programme. Liability stays with you.
Governance

Your site data stays in your existing project tools.

Tenant-resident inside your existing Microsoft 365 or Google Workspace. Procore, P6, and SharePoint credentials stay in your secret store. Site reports, RFIs, NCRs never leave the project tools they already live in. Project-scope extensions need DSI approval before tenant-wide promotion.

Full security and governance architecture →

Start with the project that's quietly sliding.

The schedule you've been hoping to recover at the next milestone. The 47 subs nobody is chasing. That's where it earns it.
Start the 15-day pilotTalk to a site-savvy team member
Or explore another Master
Engineering →Legal →Procurement →Sales →Generalist →