When TxDOT releases a new bid, pricing it correctly means finding every place the project's General Notes add to, or override, the Standard Specifications book, then working out what each one means for how the project actually gets built. That comparison, done by hand, line by line, against a thousand-page spec book, takes an experienced estimator days. Clarement has already run it on real TxDOT contracts pulled straight from the Bid Package: General Notes vs Spec findings ranked by severity, each one openable side by side on the source PDFs with the exact excerpts—so you're reading a risk register instead of a contract.
Line by line
Every TxDOT bid package includes General Notes specific to that project. Those notes have to be checked against the Standard Specifications (and Special Provisions where they override the book). Done by hand, that's a line-by-line read across two documents at once, and it takes an experienced estimator days, longer for anyone doing it for the first time or on an unfamiliar contract.
Reading two documents at once
General notes
Standard spec
Constructability
A material storage restriction can mean finding a new stockpile yard or delivering material in smaller loads, both of which slow production. A paving width under standard equipment minimums means supplemental hand work. A non-standard work window changes crew scheduling and overhead math entirely. None of this is abstract. Every deviation found changes how the project actually gets built, and how it gets built is what the unit price is based on.
Caught too late
A different slope requirement, a banned installation method, a wind-speed restriction that has to be built into the schedule instead of treated as an ordinary weather day, all of it is findable before the bid goes out. Found late, it turns into rework, quantity increases, and cost pulled from internal contingency after the job is already underway. In the more severe, and thankfully rarer, cases, a project expected to return a healthy margin returns none at all.
Found before the bid vs. found in the field
Found pre-bid
Priced into the number
Found in the field
Rework, RFI, contingency
General Notes vs Spec, ranked by severity
Each finding pairs a project General Notes Item with a Spec Item: severity, nature, and a clear statement of what differs—so you are reading a risk register, not a paraphrase.
Open a finding, see both source PDFs
Select a row to open the General Notes PDF and the Standard Specifications PDF together near the cited pages, with the exact excerpts from that finding highlighted.
General Notes
Project PDF
Spec Book
Standards PDF
Critical, high, medium, or low
Each General Notes vs Spec deviation is rated by likely cost or schedule impact so you can scan the register before you dive into the PDFs.
You're the one who'd otherwise be reading the General Notes against the standard spec book by hand, on every bid, working out what each deviation means for constructability before the number goes out the door.
Work restricted to nighttime hours only, 8:00 PM–6:00 AM.
Priced before it's out the door
Every deviation checked, not just the ones you spot
The risk that got missed at bid time becomes your problem in the field. Once a job is awarded, these are the same documents you're referencing constantly, not just once. A flagged register at pursuit, with the clause and page behind every item, means you're not the one discovering a deviation after the crew is already mobilized.
Side-by-side Spec comparison
Referenced constantly, flagged once
No surprise deviations after mobilization
Your scope sits inside someone else's contract, and a deviation buried in the prime's General Notes can still land on you. Seeing it flagged before you price your piece is the difference between a known cost and a change order later.
Material storage restricted to designated laydown area, no storage within 100 ft of creek crossing.
A known cost, not a change order
Flagged before you price your piece
A contract risk register is a severity-classified list of every place a project's General Notes add to, or override, the TxDOT Standard Specifications. Each finding is a General Notes Item matched to a Spec Item, with exact excerpts you can open side by side against the source PDFs.
TxDOT publishes the Standard Specifications book directly on txdot.gov. General Notes are part of each individual project's contract documents, issued with that project's plans and specifications.
Reading a contract tells you what's there. This tool lists General Notes vs Spec deviations by severity, then lets you open each finding side by side on the project General Notes PDF and the Spec PDF with the exact excerpts highlighted—without days of line-by-line reading.
Each finding is rated critical, high, medium, low, or informational based on the magnitude of contractor exposure (or incentive upside) in the General Notes vs Spec texts—not from Plan/Price or Bid/Field alone.
Real TxDOT contracts, pulled directly from the public Bid Package and already analyzed, with more added over time.
Not on this free tool, it's built to show the analysis on real TxDOT contracts today. Request POC access to run it on your own bid package.
When you select a risk finding, the tool opens the project General Notes PDF and the TxDOT Standard Specifications PDF together near the cited pages, with the exact General Notes and Spec excerpts from that finding.
No. It surfaces General Notes vs Spec deviations and ranks them by severity. What to do about each flag, including whether to price it, negotiate it, or accept the risk, is still a judgment call.
TxDOT currently. Additional state DOTs are planned.
Yes. The contracts already analyzed are free to review, no account required.
Every General Notes document already has whatever's different from the standard spec sitting in it, page by page, waiting to be found. Try the free tool and see what real TxDOT contracts turned up before you read your next one clause by clause.