Product
A reconciliation engine for the documents your bid 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.
- Drawings
- Full plan sets, revisions, keynotes and details
- Specifications
- Every division, including Division 01 administrative requirements
- Addenda & changes
- Issued addenda, bulletins and change orders
- BIM & quantities
- Coordinated models and extracted quantity sets
- Proposed schedule
- P6 XER, MS Project XML or CSV activity exports
- Estimate & cost codes
- WBS, cost codes and takeoff summaries
- RFI records
- Bid-phase and construction-phase RFI logs
- 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.
Drafted response
A submission narrative for the owner or their consulting auditors.
Review package
An export bundle, watermarked as requiring human 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 costs you margin after award or hides revenue you are entitled to price. 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.
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, full audit logging, and a contractual guarantee your documents never train a model.
Workflow
Approve, dismiss or assign — then generate the package
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, generate the review package.
- Every state change is logged with user and timestamp
- Dismissals require a reason, preserved in the audit trail
- Assignments carry due dates and notify the owner of the item
- Review packages carry a sign-off page for your own professional
Drafted response to the owner
IPSES drafts the submission narrative for you: the checks that were run, the findings you chose to include, the resolution or clarification you're proposing, and the evidence references behind each one. You edit it, your professional signs it.
Re: Baseline Schedule Rev. C — Clarifications
Northstar Medical Center — Phase II. In advance of formal submission we identified 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…
Draft narrative — your team edits and signs it