Free tool built on real TxDOT contracts, See how it works ↓

From TxDOT general notes to a contract risk register, built on real TxDOT contracts.

When TxDOT releases a new bid, pricing it correctly means finding every place the project's General Notes and drawing 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, flagging every deviation by severity, with the exact clause and page it came from, so you're reading a risk register instead of a contract.

What it actually takes to price a TxDOT bid correctly

Line by line

General notes and drawing notes get checked against the standard spec, line by line

Every TxDOT bid package includes General Notes specific to that project, plus notes on individual drawings and sheets. Both have to be checked against the Standard Specifications and Special Provisions, since special provisions override the standard spec wherever the two conflict. 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

Days of manual cross-referencing

What one deviation changes

Material storage restriction

New stockpile yard or smaller loads

Non-standard work window

Crew scheduling and overhead recalculated

Changes constructability

Constructability

What's different determines constructability, and constructability determines the price

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 missed deviation doesn't surface until it's already in the field

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

Missed deviation

What this tool shows you, on real TxDOT contracts

Executive summary

The one-look version of contract risk

Every analyzed project gets a residual risk rating, a go/no-go read, and a severity breakdown, critical, high, medium, and low, before you open a single clause.

Residual riskMEDIUM

Risk findings

Every deviation, with the exact clause behind it

Each flagged risk includes the description, the clause article and section it came from, the exact contract text, and the page number, so nothing is a paraphrase you have to go verify yourself.

GN-14 · p.45HIGH

Notice obligations

Every deadline the contract actually requires

Every notice requirement is pulled out on its own: what triggers it, how many days you have, what happens if you miss it, and the exact clause it comes from.

Lane closure notice48 hrs

Built for the people reading TxDOT contracts directly

Lead estimators

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.

General notes · p.45FLAGGED

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

Project engineers and project managers

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.

Notice obligation

Trigger, lane closure§7.3
Notice required48 hrs

Referenced constantly, flagged once

No surprise deviations after mobilization

Specialty contractors and subcontractors

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.

Buried in prime's general notesFLAGGED

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

FAQs for TxDOT contract risk register

What is a TxDOT contract risk register?

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 one tied to its exact clause, page, and contract text.

Where can I find TxDOT's Standard Specifications and General Notes?

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.

How is Clarement's tool different from reading the contract yourself?

Reading a contract tells you what's there. This tool tells you what's different from the standard spec, ranks it by severity, and gives you the exact clause and page behind every flag, without the days of line-by-line reading it normally takes.

How are risks classified by severity?

Each finding is rated critical, high, medium, or low based on the type of deviation and its likely cost or schedule impact, alongside an overall residual risk rating and go/no-go read for the project.

Which TxDOT contracts are included in this free analysis?

Real TxDOT contracts, pulled directly from the public Bid Package and already analyzed, with more added over time.

Can I run this on my own project?

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.

What counts as a notice obligation?

Any requirement in the contract to notify TxDOT of something on a deadline: what triggers it, how many days you have, and what happens if you miss it, each one pulled out with its exact clause.

Does this replace a lead estimator's or project engineer's judgment?

No. It surfaces what's in the contract and ranks it by severity. What to do about each flag, including whether to price it, negotiate it, or accept the risk, is still a judgment call.

Are these tools limited to TxDOT, or do they cover other state DOTs?

TxDOT currently. Additional state DOTs are planned.

Is this free to use?

Yes. The contracts already analyzed are free to review, no account required.

See what's actually different in your next TxDOT contract

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.

Try the free tool