DownstreamUSA 2026
FEATURED SPEAKER
Kate Marshall
Fractional Chief AI Officer
DATE
June 10, 2026
TIME
11:00AM PST
Keep Primavera P6 authoritative for the controlled schedule, but do not force every field commitment, constraint and daily update into it. Transform the P6 schedule into a connected execution-planning environment where teams can develop near-term activities, coordinate handoffs, record commitments, surface constraints and report progress with supporting evidence. FlowSpan keeps that work related to the relevant P6 activities and structures the resulting execution information for review. The scheduling engineer then controls what becomes an accepted status or forecast update in P6. The aim is to make schedule control easier and better informed while preserving professional judgment and accountability.
Primavera P6 is designed for project planning and control. Oracle describes P6 Professional as supporting work breakdown structures, critical-path-method scheduling, resource leveling and project tracking, with features aimed primarily at project planners and schedulers. Those capabilities make it an appropriate home for the governed project schedule.
The difficulty is not that P6 lacks schedule logic. It is that many of the conditions determining whether an activity will happen emerge outside the schedule update process.
A crew may lose access to a workface. A drawing may still be awaiting approval. A predecessor may be physically complete but not accepted. Equipment may be unavailable. Two teams may need the same space. A commitment made in a coordination meeting may change what can realistically be completed that week.
These signals often appear first in conversations, look-ahead plans, spreadsheets, planning boards, photos and individual follow-ups. By the time they are translated into formal progress or revised logic, the schedule can be accurately maintained according to its update cycle while still presenting a delayed picture of current execution risk.
The control schedule and field execution therefore operate at different levels of detail and cadence. Trying to make one system perform both jobs can either overload the P6 schedule with short-lived operational detail or leave the field working from disconnected plans that project controls cannot trace.
The practical answer is to distinguish schedule control from execution coordination while keeping them connected.
P6 should continue to govern the approved schedule structure, activity logic, baselines, calendars, constraints, progress rules and forecast dates according to the project's controls procedures.
Project controls retains responsibility for deciding what information is accepted into that record. A field observation should not become an approved schedule change merely because someone reported it.
The field needs enough detail to answer practical questions:
This is consistent with established collaborative-planning practice. The Lean Construction Institute describes Last Planner System planning as becoming more granular closer to execution, with make-ready planning, weekly commitments, daily coordination and constraint management tied to project milestones.
That detail does not all need to become separate P6 activities. It does need a traceable relationship to the controlled work it supports.
The execution plan should make it straightforward for the people closest to the work to report useful evidence without asking them to become P6 schedulers.
Useful signals include:
The objective is not continuous noise. Each signal should remain connected to an accountable person, the affected work and the evidence needed to interpret it.
Project controls should receive a structured exception view rather than reconstructing status from several meetings and spreadsheets.
The review asks:
Only after that review should accepted information enter the controlled schedule-update process. This preserves P6 governance while shortening the distance between field reality and the scheduler's evidence.
Once P6 has been updated, the resulting control dates and logic should inform the next execution-planning cycle. Keep the history behind the change: what was reported, what evidence supported it, who reviewed it and what was accepted.
FlowSpan transforms the P6 schedule into a more usable execution-planning environment while preserving its relationship to the controlled work. As teams report progress, constraints and evidence, it structures that information for review by the scheduling engineer. Accepted updates can then flow back into P6 through the project's governed process.
P6 control schedule → FlowSpan transformation and execution planning → team commitments and constraints → field status and evidence → scheduling-engineer review → controlled P6 update
The objective is to make the scheduling engineer's job easier, not replace their judgment with AI. FlowSpan provides better-structured execution evidence and a controlled way to translate it back into the schedule.
Suppose a P6 activity covers installation work planned for a two-week window. The field team breaks that controlled activity into the near-term sequence needed to execute it: confirm access, release the approved drawing, stage materials, complete predecessor work, install, inspect and obtain acceptance.
During the week, the team reports that access will be shared with another contractor and the inspection resource is not available on the planned day. Neither condition necessarily justifies an immediate change to the P6 activity. Both are execution signals that could affect it.
The construction team assigns owners and target dates to clear the constraints. Project controls can see the relationship to the P6 activity and monitor whether the issue is resolved before it affects the forecast. If it does affect progress or remaining duration, the scheduler receives the evidence and applies the project's normal status and change controls.
Without that connection, the field may manage the issue locally while the scheduler learns about it at the next update meeting. With it, the team has a chance to act before the impact becomes a historical explanation.
FlowSpan provides a shared project planning and execution environment for activities, handoffs, commitments, constraints and execution learning. Teams can use it to turn milestone, pull, look-ahead and execution plans into coordinated work while retaining the context created during planning and execution.
Optimality supports FlowSpan with connected context, knowledge, workflow, permissions and controlled AI-assisted processes. It can connect activities with the people, organizations, decisions, deliverables and meetings surrounding the work.
This does not change the system-of-record boundary. P6 remains authoritative for the controlled schedule. FlowSpan transforms uploaded P6 schedule information into a detailed execution-planning environment while preserving its relationship to the control schedule. As teams report progress, constraints and evidence, FlowSpan structures that information for review by the scheduling engineer. Accepted updates can then flow back into P6 through a controlled process. The precise update frequency, approval route and configuration can reflect each project's controls procedures.
This approach is designed to make the scheduling engineer's job easier. It gives the scheduler clearer execution evidence and a controlled way to translate it back into P6 without replacing their judgment or authority with AI.
Integration is the mechanism. The value is a shorter, more reliable path between the controlled schedule and execution reality.
The goal is not to make the field serve the schedule. It is to ensure that the schedule is informed by what the team is actually encountering while it executes the work.
Usually, field teams should report progress, constraints and evidence through a workflow designed for their role, while designated schedulers or project-controls personnel retain authority over the P6 schedule. The exact permissions depend on the project's controls model, but broad direct access is not required to obtain timely field information.
No. It often needs more operational detail but less scheduling complexity. A single controlled activity may relate to several near-term actions, handoffs, checks and commitments. Preserve traceability to the controlled activity without turning every short-lived field task into a P6 activity.
The movement of information can be automated without removing schedule governance. FlowSpan can structure field signals and proposed updates for the scheduling engineer, but accepted progress, logic and forecast changes should still follow the project's review and authorization rules. Automation should make the scheduler's work easier, not assume their authority.
Review frequency should reflect the pace and risk of the work. Daily coordination can surface new constraints and commitments, while project controls may review schedule-relevant exceptions at an agreed cadence between formal updates. The important point is that urgent signals do not wait unnoticed for the next reporting cycle.
Last Planner and other short-interval methods help teams make work ready, coordinate handoffs and make reliable near-term commitments. They complement the master schedule when the milestone and activity relationships remain traceable and project controls receives governed feedback from execution.
See how FlowSpan connects project planning to execution, while keeping established project-control systems in their proper role.