Contract Risk Register
GN-14
HIGH
432-6012
MED
D-14/U-06
LOW
GN-14 · high severity
GN-14 · page 45
Contractor will be allowed to perform work during nighttime hours only, 8:00 PM–6:00 AM.
Lubbock District · SL 88
Nighttime restriction
Bid tab — scope check
Riprap, Conc B
432-6008
Riprap, Conc B
432-6012
Scope mismatch
Plan sheet cross-check
D-14
24 in RCP
U-06
18 in RCP
Pipe size conflict
From a thousand-page DOT contract to a ranked risk register, in minutes.
Reads your bid package against the DOT standard specifications book, flags every overriding provision, scope conflict, and plan sheet discrepancy, and delivers a severity-ranked Contract Risk Register — with a highlighted PDF for each flag — in minutes instead of hours of manual cross-referencing.
Problems in DOT Contracts Risk Identification
Provision risk
Comparing general notes with standard specifications
DOT contracts layer project-specific general notes and special provisions on top of a standard specifications book — a material storage restriction, a nighttime-only paving window, a non-standard site access constraint. Each of these points contain a risk which needs to be priced into the bid, and this process takes hours of manual work of a Lead Estimator.
General notes · page 1,304
4.3.2(b) Contractor shall restrict material storage to the designated laydown area north of Sta. 412+00; no storage permitted within 100 ft of the creek crossing.
Clause 4.3.2(b) · not reflected in bid item 0100-0101
High severity
Bid tab — pay item comparison
Riprap, concrete (Class B)
432-6008
Grouted · flatter than 1:4 slope
Riprap, concrete (Class B)
432-6012
Ungrouted · 1:4 slope or steeper
Scope mismatch flagged
Line item scope
Two line items, one name, two different scopes
Line items in a bid tab can read almost identically and cover completely different work — differentiated only by a type suffix or a modifier buried at the end of a long spec section. Price the wrong scope, and the margin goes with it, before the estimator has opened the section that would have caught the difference.
Plan sheet conflict
Plan set discrepancies
Drainage, roadway, structural, and utility sheets are drawn by different teams and don't always agree with each other on a width, an elevation, or a utility location. That conflict usually isn't caught until the crew is already in the ground — the single most expensive point possible to find it.
Plan sheet cross-check
Sheet D-14 · Drainage
24 in RCP, invert 612.40
Sheet U-06 · Utility
18 in RCP, invert 611.90
Pipe size conflict
Clarement Solution for Contract Risk Identification
01
Analyzes full bid package against the DOT standard specifications
The project plan set from the bid package — general notes, special provisions, and technical specifications — is read alongside the applicable DOT standard specifications book, section by section. On a bid package running over a thousand pages, this comparison is done in minutes, not the hours it takes a Lead Estimator working alone.
Reading plan set against standard specifications
Project general notes
TxDOT standard specs
Page 412 of 1,034 · section by section
01
Analyzes full bid package against the DOT standard specifications
The project plan set from the bid package — general notes, special provisions, and technical specifications — is read alongside the applicable DOT standard specifications book, section by section. On a bid package running over a thousand pages, this comparison is done in minutes, not the hours it takes a Lead Estimator working alone.
Reading plan set against standard specifications
Project general notes
TxDOT standard specs
Page 412 of 1,034 · section by section
02
Flags overriding provisions, line item scope conflicts, and plan sheet discrepancies
Every provision that overrides, restricts, or adds to the standard spec gets flagged — material storage restrictions, non-standard paving windows, site access constraints. Line items that read almost identically but cover different scopes are separated out, with the specific spec section that makes the difference. Plan sheets are cross-checked against each other for the discrepancies that cause rework — mismatched utility locations, pipe diameters, elevations, or roadway widths between drainage, roadway, structural, and utility sheets.
Bid tab — pay item comparison
Riprap, concrete (Class B)
432-6008
Grouted · flatter than 1:4 slope
Riprap, concrete (Class B)
432-6012
Ungrouted · 1:4 slope or steeper
Scope mismatch flagged
03
Delivers a Contract Risk Register, classified by severity, in a highlighted PDF
Every flag is compiled into a Contract Risk Register, classified by severity, so the highest-cost risks surface first. Each item links back to a highlighted PDF of the original document — the exact page, provision, or sheet conflict marked for review — so the estimator can price it, send it back as an RFI, or clear it, without re-reading the package to find where it came from.
Contract risk register — ranked by severity
Material storage restriction · p.1304
HIGH
Pipe size conflict · D-14 vs U-06
HIGH
Riprap scope mismatch · 432-6012
MEDIUM
Nighttime paving window · p.842
LOW
4 flags · highlighted PDF linked to each
Read
Flag
Deliver
Built for Lead Estimators, Project Engineers, and Project Managers
Lead Estimators at Self-perform Contractors
On large, complex DOT design-build and bid-build packages, general notes and special provisions run for hundreds of pages on top of the standard spec book. Today, catching every overriding provision means hours of manual cross-referencing per bid, done by the most senior person on the team. That time gets returned to the estimating cycle, and every provision that would have been priced wrong or missed gets caught before the bid goes in, not after the contract's signed.
General notes · p.14
FLAGGED
Paving allowed only 9:00 PM–6:00 AM, Sunday through Thursday. All other work confined to normal hours.
17 risks hidden
Overriding provisions caught before the bid goes in
Lead Estimators at Specialty & Subcontractors
With a smaller team and no room to have someone read every spec section twice, a mislabeled or mispriced line item goes straight to the bottom line. One type suffix is the only thing separating two completely different scopes. Catching that difference at bid time, rather than after award, is the difference between a bid that holds its margin and one that doesn't.
Bid schedule — pay item comparison
604-0012 · RCP (18")
1,250 LF
604-0012-003 · RCP special
850 LF
5 scope errors
Mislabeled or mispriced items that hit your margin
Project Engineers & Project Managers
Discrepancies between drainage, roadway, structural, and utility sheets — a mismatched pipe diameter, a utility location that shifts from one sheet to the next — are far cheaper to catch on paper than in the ground. Once a crew is mobilized, the same conflict becomes a delay, an RFI, and a change order instead of a five-minute correction during plan review.
Sheets C-14 · D-08 · U-12
CONFLICT
Roadway sheet C-14: 30"
Drainage sheet D-08: 36"
Utility sheet U-12: 36"
Drainage sheet D-08: 36"
Utility sheet U-12: 36"
3 drawing conflicts
Cross-discipline issues caught before the crew mobilizes
FAQs for DOT Contract Analysis
What is contract risk identification in DOT construction bidding?
Contract risk identification is the process of finding project-specific general notes, special provisions, and technical specifications in a DOT bid package that override or add to the standard specifications book — restrictions on materials, work hours, site access, or means and methods that change cost and schedule but don't appear in the bid quantities.
How long does it take to manually compare general notes against DOT standard specifications?
On a bid package running over a thousand pages, comparing project-specific general notes and special provisions against the applicable DOT standard specifications book by hand typically takes days of a Lead Estimator's time per bid — time spent cross-referencing rather than pricing.
Can ChatGPT catch DOT contract risk?
Generic AI tools can read a plan set, but they don't have the DOT standard specifications book loaded as a comparison baseline — so they can't identify what's actually non-standard about a specific project's general notes and special provisions. Contract risk identification requires reading both documents together, not summarizing one.
Why do bid tab line items with similar names cover different scopes?
DOT bid tabs frequently include line items differentiated only by a type suffix or a modifier buried at the end of a long specification section — two items that read almost identically on the surface but represent completely different work. Pricing the wrong scope directly reduces bid margin.
How are plan sheet discrepancies like utility conflicts and pipe diameter mismatches identified before construction?
Drainage, roadway, structural, and utility sheets are drawn by separate teams and don't always agree with each other on a width, elevation, pipe diameter, or utility location. Cross-checking every plan sheet against every other sheet before mobilization catches these conflicts on paper, when they're a five-minute correction not in the ground, when they become a delay and a change order.
What is a Contract Risk Register, and how is severity classified?
A Contract Risk Register is a structured, prioritized list of every flagged contract risk — overriding provisions, line item scope conflicts, and plan sheet discrepancies — classified by severity so the highest-cost risks surface first. Each entry links to a highlighted PDF marking the exact page, provision, or sheet conflict for review.
What documents are needed to run a contract risk review on a DOT project?
A contract risk review requires the project plan set from the bid package (general notes, special provisions, and technical specifications) and the applicable DOT standard specifications book — the same documents a Lead Estimator already has on hand before bidding.
Which DOT standard specifications are supported?
Currently built around TxDOT standard specifications, with additional state DOT specification books planned.
Does this replace a Lead Estimator's judgment on pricing risk?
No. Contract risk identification surfaces every flagged provision, scope conflict, and plan sheet discrepancy in a ranked register. The Lead Estimator still decides how to price each risk, which items warrant a pre-bid RFI, and the final bid decision.
Is Contract Risk Identification available today, or only through a pilot program?
This is currently available as a proof-of-concept engagement.
Use it for your current Bid
Run your current bid package through it before you price it — general notes, special provisions, line items, and plan sheets checked in minutes, with a severity-ranked Contract Risk Register and a highlighted PDF for every flag. Request POC access and we'll walk your team through a live review.
Request POC access