Baseline schedule
Set the as-awarded plan on the job and compare every update against it — not against last week's memory.
CPM scheduling
Know when the job slips — before the owner calls.
Most teams keep the schedule in Primavera or MS Project and copy a lookahead into email every week. AOS gives you a baseline schedule on the job with drift tracking and slip alerts tied to RFIs and change orders. The full critical-path engine, P6 import, and delay analysis are built and ready when your schedulers ask for them.
Baseline vs. actual
Slip alerts with context
Three-week lookahead
Linked to COs and RFIs
Your reality today
The schedule lives somewhere else.
Primavera or MS Project holds the plan. The PM tool holds RFIs and change orders. The field gets a PDF on Monday. Nobody sees drift until the owner asks why substantial completion moved.
Change orders don't update the plan.
Approved CO adds four days of glazing. The schedule file gets updated — maybe — in a separate step days later.
Lookahead is hand-maintained.
Someone exports tasks, trims to three weeks, and emails subs. Next week, start over.
RFI delays hide in the log.
An open RFI sits nine days. The schedule still shows the original start date for the affected trade.
Delay claims start from memory.
When slip becomes a dispute, you're reconstructing events from email instead of a dated record on the job.
What's in the Launch Pack
Schedule on the job — not in a silo.
Baseline schedule, drift tracking, and slip alerts ship with new GC accounts. The full critical-path engine, P6 and MS Project import, earned value, resource leveling, and forensic delay analysis are available when your schedulers are ready.
Available now in the Launch Pack · Available on request when you're ready for more
Slip alerts
Drift flagged with context when the finish moves past your threshold — critical-path moves escalate, minor float noise doesn't.
Three-week lookahead
The near-term window pulled from the live schedule for field crews and subs — not rebuilt in Excel every Monday.
Linked to the job record
Schedule tasks tie to RFIs, change orders, and pay-app progress on the same project — so slip has a paper trail.
Full CPM engine
Forward and backward pass, total and free float, four dependency types, and automatic recalc when the network changes.
P6 and MS Project import
Bring your Primavera P6 or Microsoft Project file into the native engine — activities, relationships, calendars, and constraints mapped.
Earned value and leveling
CPI and SPI from progress and cost, resource histograms, and over-allocation surfaced before the field finds out.
Time-impact delay analysis
Delay notices logged against activities with chronological attribution — defensible day-by-day when slip becomes a claim.
3 wk
Lookahead published from the live schedule
CO
Change orders flagged against schedule tasks
RFI
Open RFIs visible alongside drift
SOC 2-aligned
Aligned security practices; change history on key records
Related modules
Schedule connects to the rest of the job.
Slip doesn't happen in isolation. See how scheduling fits the platform, or start at all features.
Project Management →
RFIs, change orders, and daily logs on the same record — where most schedule drivers start.
Field Operations →
Daily logs and production notes that explain why the plan moved — from the trailer browser today.
Owner & Sub Portals →
Owner and sub schedule views through secure links — so the lookahead isn't another email attachment.
Construction Accounting →
Pay-app progress tied to schedule percent complete when your team runs both on AOS.
Estimating & Money →
Cost-loaded activities and material curves when you connect estimating to the schedule network.
AI & Automation →
Weekly schedule narrative drafts from live rollups — available when your schedulers want a first pass written for them.
See scheduling on a real job.
30-minute walkthrough using the work your team already does. Bring a recent lookahead or slip story — we'll show you what's in the Launch Pack today and what's available when you're ready for more.