7 owners · 170 rules · every finding quoted
Your contract names a spec. We check against that one.
USACE, NAVFAC, VA, NY OGS, VDOT, NYC DDC and TxDOT ask for different things, in different words, with different consequences. A schedule that satisfies one gets returned by another. Upload your .xer and read a numbered deficiency report against the section your contract cites, with the sentence each finding rests on.
A section, and the same structure as the schedule that builds it. Each bar carries the mark of the element it puts up.
It carries negative float: the chain running through it finishes after the contract date. A reviewer sees that before they see anything else.
Every finding in your report points at a bar like one of these, and cites the sentence that governs it.
Who we check for
Seven specifications, read line by line.
Each was mined from the issuing authority's own current edition. Every rule carries a verbatim quote and a paragraph number, and every requirement a schedule file cannot evidence is listed rather than quietly dropped — that count is printed on every report.
USACE UFGS 01 32 01.00 10 Project Schedule
Edition August 2026- Rules
- 70
- Can block
- 42
- Listed
- 42
NAVFAC UFGS 01 32 17.00 20 Cost-Loaded Network Analysis Schedules
Edition May 2025- Rules
- 70
- Can block
- 53
- Listed
- 9
VA 01 32 16.16 Network Analysis Schedules (Design-Build)
Edition 1 May 2022- Rules
- 7
- Can block
- 3
- Listed
- 10
- Not yet written
- 3
NY OGS 013200 Construction Progress Documentation
Edition 1 June 2024- Rules
- 9
- Can block
- 5
- Listed
- 16
- Not yet written
- 3
VDOT Progress Schedule — Category III
Edition March 2022- Rules
- 7
- Can block
- 5
- Listed
- 9
NYC DDC §1.06.25 Schedule of Operations
Edition 16 May 2022- Rules
- 5
- Can block
- 3
- Listed
- 5
TxDOT Item 8 Prosecution and Progress
Edition 2024 Standard Specifications- Rules
- 2
- Can block
- 0
- Listed
- 5
The gap no generic tool covers
Your schedule is fine. Your export isn't.
USACE reads your schedule as a fixed-column SDEF file. Every field has a start column, and a value that overruns its columns breaks the record. Primavera never warns you. RMS refuses the upload, and your progress payment waits.
ACTIVITY RECORD · ER 1-1-11 Appendix A
1 11 41 44 52
│ │ │ │ │
A1010 Install rooftop chiller units 030 20260415 20260514
└ 10 ch ┘└──────── 30 characters ────┘└3┘ └── dates ──┘
overruns → every field after it shifts left
Ten integers
Activity ID. ER 1-1-11 says ten digits. In USACE's own published 2,722-activity export, not one id is numeric — so we report it and tell you what the Corps' own file does.
Thirty characters
Description. Truncated silently at 30. In that same export, 69 percent of descriptions are exactly 30 characters long.
Twenty characters
Feature of Work. Since RMS patch 566, a contract set up for SDEF upload blocks manual FOW entry — the schedule is the only way in.
Three verdicts, never confused
A wrong "you will be rejected" is worse than a missed finding.
Where a specification says reasonable, as determined by, or subject to approval, this report does not decide. It shows the evidence and names the paragraph that hands the decision to your Contracting Officer.
The spec states it outright
An absolute requirement, breached — UFGS 3.3.8: “Mandatory constraints that ignore or affect network logic are prohibited.” Fix it before you submit.
The spec defers to a human
A duration cap TxDOT ends with “unless agreed upon with the Engineer” — the section names a route to an exception and this reader cannot see whether you took it.
No file can evidence it
Meetings, narratives, the Daily QC Reports your actual dates must match. Listed with paragraph numbers so the coverage claim stays honest.
One finding, in full
Every finding cites the sentence it rests on.
A finding without a citation is a bug. This is the shape of one — the requirement quoted, the activities named, and the trade reasoning a reviewer would apply.
3 curing periods exceed the 20-day cap
“Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc.”
C-2140 28 days on Standard 5 Day Workweek
Why this one matters. A 28-day cure on a five-day calendar asserts that concrete stops hydrating at the weekend. Curing is passive: once the compound is applied or the sprinklers are running, hydration continues without a crew. The seven-day calendar exists for exactly this, and the cure period comes from your structural spec, not from this one.
That last paragraph is the difference between a linter and an engineer.
Three steps, about four minutes
Export, upload, read.
Name your owner
One question. Type the agency, the state, or the CSI number off your spec book, and we set the engine to the section that governs you.
Upload the .xer
Straight out of P6, up to 60 MB. Add the previously accepted update and four more checks run that a single file cannot answer at all.
Fix, then submit
A numbered report, each finding with its paragraph and how to correct it. Your report stays at a private link on your account.
Pricing
One price. The first one is free.
- ContractYour owner's specification, paragraph by paragraph, plus the SDEF export simulation on USACE contracts.
- BenchmarkThe DCMA 14-point assessment — the language a prime contractor's own schedule review is written in.
- AuditGAO-16-89G, the criteria a federal Inspector General applies after the fact.
No subscription, no seat license, no call. Upload a file, read a report, decide whether the next one is worth $99.
Claim a free check
Send yourself the upload link.
We email a private link. It opens the check, set to the specification you chose. No password, no account.
Straight answers
The questions worth asking first.
Is this an approval?
No. This is an automated check against published specification rules. You remain responsible for verifying against your actual contract, and nothing here is an engineering opinion.
What happens to my schedule file?
By default we keep it, with its report, for your account, so you can reopen the report. It is never shared and never used to train anything. Tick “Do not keep” when you upload and the file is deleted as soon as the report is shown, and the report is not stored.
My contract is not one of the seven.
Send the section titled Project Schedule, Progress Schedule or Construction Schedule — it will be at CSI 01 32 xx — and it becomes an engine. Meanwhile the DCMA 14-point and GAO checks run on any file and the report says plainly which requirements were not checked.
How is this different from a DCMA-14 tool?
DCMA-14 is a generic public checklist and its thresholds are not your contract's. It allows 44-day durations where USACE allows 20. It checks none of the SDEF export conditions that decide whether your file uploads at all. We run it too, because your prime will — but it is the benchmark, not the requirement.
Microsoft Project?
Save as XML and upload that. Where your owner requires a native P6 .xer, the upload page says so and takes the .xer only.