Product

A reconciliation engine for the documents the project depends on.

IPSES reads the contract documents and your proposed schedule and estimate as two versions of the same project — then reports every place they disagree, with the evidence attached.

What goes in

You choose what to upload

The review only ever checks against the documents you provide. Nothing is inferred from other projects, and nothing leaves your tenant.

Plans & specifications: Issued plan sets and every division, including Division 01 administrative requirements
Addenda & changes: Issued addenda, bulletins and change orders
Proposed schedule: P6 XER, MS Project XML or CSV activity exports
Estimate & cost codes: WBS, cost codes and takeoff summaries
Contract exhibits: Milestones, liquidated damages and scheduling specifications

What comes out

Findings you can act on and defend

Schedule Health Score

A single composite of logic quality, realism and coverage.

Ranked findings register

Severity, category, evidence, dollars, days, confidence, status.

Financial impact model

How each number was derived, so you can defend it in a room.

Critical path & heatmap

Where exposure concentrates by trade and phase.

Key findings analysis

A focused summary of the findings you accepted, with evidence references.

Complete audit analysis

Every inconsistency, decision and supporting evidence from the review.

Check library

A proprietary check library, toggleable per submission

Checks span four domains. Each one exists for the same reason: an unresolved item in that domain either becomes unbudgeted cost after award or revenue that was never identified. Run everything on a first pass, then narrow to what matters for a specific submission — and choose which findings make it into the response you send.

Scope integrity

Does the schedule and estimate actually cover what the documents obligate you to build? Gaps here are unpriced work.

Schedule logic

Is the plan defensible? Logic and float defects are what get a baseline rejected and put you on the back foot.

Execution reality

Can it be built this way, at this pace, with these crews and these lead times? This is where delay cost is created.

Compliance & upside

Approvals, inspections and turnover — plus the compression and prefabrication upside sitting inside your own plan.

The individual checks and their thresholds are proprietary. We walk your team through the ones that fired on your project during the review.

Schedule mechanics

The specifics we check inside the CPM network

These are the mechanics a reviewer will interrogate line by line. Each one is a place where a defensible plan quietly becomes an indefensible one — and where days and dollars move.

Relationships

Finish-to-start integrity across the network: open ends, reversed logic, unresolved references, redundant ties, and lags used in place of real activities.

Longest / critical path

The driving path derived from your own logic and float, with the single-threaded stretches called out — one late release there moves completion directly.

Float

Negative float that means the plan already misses a date, and excessive float that almost always means missing logic rather than genuine slack.

Contract constraints

Where the documents say work cannot start before a stated date, milestone or access release, and the schedule starts it anyway.

Calendars

5-day versus 7-day workweek assignment, holidays and non-work days — the most common source of unexplained date movement in a submitted plan.

Shifts

Night, second and third shift assumptions, checked against whether a shift calendar and the crew cost actually back them up.

Agency standards

Caltrans and other agency scheduling requirements

Public work is accepted or rejected against a scheduling specification, not against good practice. We run those requirements as their own checks: Caltrans working-day contract accounting and controlling-operation reporting, baseline CPM submittal content, activity coding, float and duration limits, and agency review durations for submittals.

Caltrans working-day accounting and controlling operation
Caltrans baseline CPM submittal content and acceptance conditions
Other state DOT and public-agency scheduling specifications
Project-specific Division 01 scheduling requirements as issued

Need additional custom checks?

If your submissions are reviewed against something we don't run yet — Caltrans standards, another agency's scheduling specification, a project's Division 01 requirements, or your own internal review criteria — reach out. We build custom checks into your check library and they run on every review after that.

Request a custom check

Upload & run

Upload your files and run the checks yourself

Add your Primavera P6 .xer, Microsoft Project .xml or CSV activity export together with the plan documents you choose, toggle the checks you want, and the review runs against exactly those files. Upload is password protected and findings are only released to a signed-in reviewer. The first project is free; every additional review is billed per run.

Upload files and run a review

What the run produces

Activities parsed, percentage linked, and the derived driving path
Findings separated into negative risk and positive opportunity
Evidence for each finding: activity IDs, calendars, constraints, document references
Days impact and a calibrated confidence level per finding

Latest frontier models

Document understanding, quantity reconciliation and logic analysis run on current frontier models, benchmarked against completed projects. Model upgrades roll out without changing your workflow.

Evidence on every claim

Each finding cites the document, sheet or section and page, the affected activity ID, and a calibrated confidence level. Nothing is asserted without a source you can open.

Highest-level security

AES-256 at rest, TLS 1.3 in transit, per-tenant isolation, SSO/SAML, role-based access and full audit logging on every document you upload.

Workflow

Approve, dismiss or assign — then finalize the analysis

Findings are a queue, not a report. Your team works it: approve what's real, dismiss what isn't with a recorded reason, and assign the rest to the scheduler, estimator or trade partner who owns it. When the queue is clean, finalize the review analysis.

Every state change is logged with user and timestamp
Dismissals require a reason, preserved in the audit trail
Assignments carry due dates and notify whoever owns the item
The completed analysis records professional review and sign-off

Open the live workspace

Key findings analysis

IPSES presents the checks that were run, the findings you chose to include, the schedule and cost consequence of each one, and the evidence reference behind it. The complete audit analysis preserves the full findings register.

Key findings — Baseline Schedule Rev. C

Northstar Medical Center — Phase II. Nine items requiring clarification prior to acceptance, including a conflict between Spec 08 44 13 §2.3 and Drawing A-231 keynote 12 regarding north-elevation glazing performance…

Key findings — supported by the complete audit analysis