UFGS 01 32 01.00 10 · ER 1-1-11 · Primavera P6
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 just refuses the upload, and your progress payment waits.
A1010 is the P6 default, and it is
what almost every schedule uses.Why a clean DCMA-14 still gets returned
Generic checkers grade the plan. USACE grades the file.
DCMA 14-Point is a good health check and it is not a compliance check. It was written for schedule quality, not for one agency's contract. The conditions that actually stop an upload are not on its list.
A schedule can pass all fourteen points and still be refused at the gate. The two are answering different questions.
Three verdicts, and we never confuse them
A finding tells you what happens, not just what's wrong.
Where the specification states an absolute, we say so. Where it hands the decision to the Contracting Officer, we put the evidence in front of you and let you decide. One wrong “you will be rejected” is worse than ten findings we chose not to shout about.
The spec states an absolute
No tolerance in the wording, and nothing left to interpretation. Fix these before you submit.
Every activity carries a responsible party.
The contract decides, not us
“Reasonable”, “as determined by the Government”, “subject to approval”. We show the data and name the question.
Holidays identified — which ones is contractual.
42 requirements no file can show
Kickoff meetings, the narrative report, time-extension procedure, ownership of float. Printed as a checklist so nothing is quietly dropped.
Published, not promised
Read every rule before you pay for one.
Most compliance tools ask you to trust a number. Ours are two documents you can check against your own copy of the specification — generated from the rules the engine runs, so neither can describe a check that is no longer there.
Requirement index
Every rule, its paragraph number, and the sentence of the specification it rests on — quoted, not paraphrased. If we cannot quote it, we do not check it.
Open the index →Coverage of the section
All 87 paragraphs, each shown as checked automatically or listed for you to confirm. A pre-construction meeting cannot be evidenced by a file; we say so rather than skip it.
See the accounting →Editions we track
| Source | Edition in use | Status |
|---|---|---|
| UFGS 01 32 01.00 10 | August 2026 | Current |
| ER 1-1-11, Appendix A (SDEF) | 18 Sep 2017 | Current |
| RMS / QCS behaviour | Patch 624, Aug 2026 | Release notes tracked |
UFGS reissues every February, May, August and November. We re-audit the profile against the live edition each quarter, because a threshold that moved is worse than a rule that was never written — the next audit is November 2026.
Three steps, about four minutes
Export, upload, read.
Export your XER
Straight out of P6. No template to install, nothing to configure, and we never ask for your P6 login.
Add your contract details
Optional. Notice to proceed, CLINs, completion date. Each one unlocks more checks — what you leave out is simply not checked, and never counted against you.
Read the report
Every finding names the activity, quotes the paragraph it comes from, and tells you how to fix it in P6.
Comparing two updates? Upload the previous one too and we check the four things 3.9.1 calls artificially improving progress — activities added or renamed, durations changed, calendars swapped, actual dates rewritten.
One finding, in full
This is what you get, 68 times over.
Nothing is summarised into a score. You get the activities, the sentence from the spec, and what to do about it. Below is one finding in full — open the whole report to see all 66.
7 activities exceed 20 work days
“Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days.”
- A1240 — Interior Partitions Level 2: 28.0 work days
- A1310 — MEP Rough-in Level 3: 25.0 work days
- A1580 — Exterior Envelope Sealing: 24.0 work days
- …and 4 more, listed in the CSV
This edition allows no tolerance — the February 2023 edition did, and it was removed. Break these into shorter, separately trackable steps. Note that DCMA-14 permits 5% of activities over 44 days, so a schedule that passes a generic health check still fails here.
2 further activities exceed the cap and were not counted against you: both are concrete cure periods. Curing needs no crew — a curing compound or wet cover keeps hydration running through weekends — so 3.3.10 puts it on a 7-day calendar, and 28 days of cure is 28 work days there. What we did check is that they sit on that calendar. A cure modelled on a 5-day week asserts that concrete stops hydrating at the weekend.
Pricing
$99 a schedule. Your first one is free.
We are opening with a free first report because we want the feedback more than the money. You get the same report either way — the whole thing, not a teaser that stops at the interesting part.
Your first report. Complete, and no card.
- All 68 rules, with the paragraph each one quotes
- Every finding lists the activities by name
- SDEF export simulation — what breaks the upload
- The 42-requirement manual checklist
- HTML report and CSV of every finding
- A reply from a person about what the report said
One schedule, one report. No subscription.
- Everything in the free check
- Compare two updates against 3.9.1
- Re-check after fixes, same schedule, no charge
Claim a free check
Send your schedule. Get the full report.
Leave your email and we send you an upload link. Your first report is free — the complete thing, every rule, no card and no trial that quietly turns into a charge.
- The same report a paying customer gets, not a preview
- Your file is deleted after the report is produced
- We will ask what the report got wrong — that is the trade
Straight answers
What this is, and what it isn't.
Does a clean report mean the Government will accept my schedule?
No, and we will never say otherwise. This is an automated check against published specification rules. Verifying against your actual contract stays your responsibility — your project may carry amendments, agency supplements, or Contracting Officer direction that no tool can see.
What a clean report means is narrower and still useful: the conditions we can read from your file are satisfied, each one traceable to the sentence it came from.
Is this an engineering review?
No. It is software reading a file against published rules. It is not an engineering opinion, it approves nothing, and it certifies nothing. Your scheduler and your Contracting Officer decide what happens to your schedule.
What happens to my file?
It is processed to produce your report and deleted afterwards. We do not keep schedules, we do not train anything on them, and we never share them. A CPM schedule is competitive information and we treat it that way.
Which contracts does this cover?
UFGS 01 32 01.00 10, August 2026 edition — the Project Schedule section shared by USACE, NAVFAC and AFCEC, plus ER 1-1-11 Appendix A, which governs the SDEF export. That is 8,556 of the roughly 13,000 federal construction contracts awarded over $1M each year.
We re-audit against the live specification every quarter, because UFGS reissues in February, May, August and November. A profile built on a superseded edition is worse than no profile.
Do you check things the specification doesn't mention?
Yes, and they matter. QCS refuses a schedule update whose actual dates
disagree with your Daily QC Reports — that appears in no UFGS paragraph.
The prime contractor's responsibility code must be PRIM, which
the spec never says. A project identifier shorter than four characters
shifts every fixed column one place left, and RMS reports it as “not a
valid integer”.
These come from USACE's own RMS and QCS documentation. When the specification and the receiving system disagree, the system is the one that refuses your file.
My schedule is 4,000 activities. Will that work?
Yes. The largest file tested carries 6,977 activities. Thirty-nine real schedules have been run without a crash, including a corpus built specifically to break schedule parsers.