From sample review to your own environment
Start with the guided sample. It provides generated XER files, the settings used, and the engine's complete deliverables. No account or project upload is needed.
1. Choose the review you need
| Your question | Start with |
|---|---|
| What does this submission show against the governing clauses? | Schedule conformance review |
| Which missing information would let us finish the review? | Unanswered-clause worklist |
| Is the network suitable for the proposed analysis? | Source validation and schedule health |
| How does a stated delay affect the analysis? | A named retrospective method or prospective time impact analysis |
| What assumptions change the concurrency result? | Concurrent-period comparison |
| Can another reviewer follow the calculation? | Activity explanation and verification record |
The demonstration shows these questions using the same generated bridge scenario. Supplied delay events and responsibility assignments are inputs from an analyst, not facts discovered by the software.
2. Inspect a complete deliverable
Open the HTML report, read its qualifications and findings, and print it to PDF if needed. Markdown supports document workflows; JSON supports integration. The output identifies the governing documents, method, assumptions, evidence and limitations.
A clause without the required evidence is marked unevaluated or referred for judgment. It is not counted as a pass. How to read a report explains those distinctions.
3. Agree your enterprise scope
Email Charley Forey to discuss formats, governing specifications, expected workflow and installation requirements. Package delivery follows an agreement; the public site does not distribute the engine.
For agency and DOT review teams, bring the contract's actual incorporated specification and any supplementary requirements. An agency name alone does not establish which clauses govern a project.
4. Work through the local browser interface
The existing engine includes a browser interface on the reviewer's computer. Once installed, the workflow is to select local schedules, identify the baseline and governing requirements, inspect the report and missing-evidence worklist, supply additional terms, and save the result.
The engine requires Python 3.11 or later and has no third-party runtime dependencies. Installation is an administrator/onboarding concern; reviewers do not need to edit Python files. The current browser service is local to one computer. Shared hosting and organizational access controls require a separately agreed deployment design.
Readers support Primavera XER, Primavera XML, Microsoft Project XML and USACE SDEF. Binary .mpp files are not supported. File-format support and independently measured fidelity are different claims; read the limitations.
5. Confirm acceptance before reliance
Agree representative acceptance cases, reconcile computed dates and floats with the source scheduling application, and confirm the intended use with the responsible reviewer. Repeatability alone does not establish that an analysis is correct.
Request an enterprise package or arrange a walkthrough. See enterprise access and deployment for the commercial process and technical installation reference for implementation details.
Source: web/pages/start.md. Source commit date: 2026-09-11.