CO
Change orders
Scope, cost, and time decisions
Linked to A1040
Schedule-led project control
Make the schedule the brain of the project.
The project should not drive an outdated schedule. The schedule should drive the project—connecting every activity, update, decision, document, delay, and downstream impact in one living source of truth.
Import from P6Update in contextExplain every change
Project snapshot
Schedule brain
P6 import
XER ready
Schedule state
Current
Change history
Tracked
Live activitiesProgress
A1040driving
Level 02 formwork
Ongoing · 4 days remaining
A1080
Electrical rough-in
Ready to start
A1120
Concrete placement
Starts in 7 days
Finish impact recalculated from current logicOn track
A living project record
Every project record should answer one question: which schedule activity did this affect?
Link change orders, submittals, invoices, RFIs, and supporting documents to the work they influence. The schedule becomes the common thread instead of another file that falls behind the project.
Schedule activity
A1040 · Level 02 formwork
The central project record
CO
Change orders
Scope, cost, and time decisions
SUB
Submittals
Reviews tied to planned work
INV
Invoices
Commercial records with context
RFI
RFIs & documents
Questions, answers, and evidence
Proactive, not reactive
Work from what the schedule says needs attention.
Update ongoing activities today. Clear the next activities to start. Prepare for upcoming work. Keep the full explanation when dates move. The schedule becomes a daily operating tool—not a report assembled after the fact.
Right now
Update the work while it is happening.
See every activity currently in progress and record field updates without leaving the report.
ActivitySchedule itemStatus
A1040Level 02 formwork68% complete
A1060MEP sleeves and embeds2 days left
A1070North elevation framingOn track
AI with project context
Better context creates better answers.
When schedule logic, progress updates, change history, and project records share the same activity context, AI can move beyond summaries and explain what happened, what happens next, and where the team can act.
Why was this activity delayed?When is the project expected to finish?What changed the critical path?Which mitigation protects the completion date?
Deep delay analysis
Why did concrete placement move?
01
Root change
Formwork duration increased by 3 working days.
02
Schedule effect
Concrete placement moved through the controlling FS relationship.
03
Project outlook
Forecast completion moved from October 15 to October 18.
04
Mitigation
Recover 2 days with an approved Saturday formwork shift.
Easy to start
Bring the schedule you already have. Make it useful immediately.
Import from P6, schedule the project, and move directly into the views your team can use every day.
Import the P6 schedule
Bring in an XER file and preserve the activities, calendars, durations, and logic you already built.
Update where the work happens
Use ongoing, ready-to-start, and lookahead views to keep the schedule current during the project.
Turn history into answers
Use the schedule, its change log, and connected project context to understand risk and decide what to do next.
Schedule first
Give every project decision a place in the plan.
Build a living schedule that helps the team understand the past, manage today, and prepare for what comes next.
Open Rapid PCA