AI uses for records
Construction conditional approval dataset: what 812 change orders left open
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
A construction conditional approval dataset should record what each change order approval left open, whether scope, price basis, time or a dependency, and set the outcome label only from the change order family that followed. In 812 public California high-speed rail change orders, 23.2% were follow-ons to an earlier order, issued a median 529 days after it, while 1.0% said in words what they excluded or deferred.
Provenance trail
Construction conditional
Key takeaways
- A change decision has six answers, not two: approve, approve with conditions, approve part, direct now and price later, return for information, or reject.
- Conditions cluster in four places: the scope boundary, the price basis, the time entitlement and a dependency on someone else's work.
- In a public high-speed rail log, 188 of 812 change orders (23.2%) supplemented or revised an earlier order, and 61.8% of those came more than a year after the first approval.
- Only 8 records (1.0%) said in words what they excluded or deferred, so condition text usually has to be rebuilt from the family, the directive and later records.
- Label an approval only when its family has closed or a stated window has passed, and keep unfinished families in the set as open.
What decision does a construction conditional approval dataset capture?
It captures the moment an owner, architect or construction manager answers a change request with something other than a clean yes or no, and what that answer committed both sides to later. The AI task has two parts: given the request packet as it stood on the decision date, choose the right outcome and write its conditions; then, as the job proceeds, tell whether the work stayed inside them.
Six outcomes cover the decisions found in change logs and contract manuals: approve as submitted; approve with conditions on scope, price basis, time or a dependency; approve one part and defer the rest; authorize the work now and settle the price later; return the request for more information; and reject. A dataset that keeps only Approved and Rejected throws away the four answers in the middle, which are the ones a model gets wrong most expensively.
A useful answer rests on three linked layers of evidence: the decision-time packet (request, pricing backup, the triggering RFI or field direction, schedule data), the decision text with its conditions, and the later records that show whether each condition held. Much published research on construction text works on contracts rather than decisions, for example two 2023 arXiv studies that apply language models to contract review and to contract risk identification. Public change logs rarely hold all three layers, as the count below shows, so the rest of this guide designs a licensed set rather than a scrape.
Four things a conditional yes can leave open
A conditional approval leaves at least one of four things unsettled, and each binds later execution in its own way. The scope boundary limits what work the approval pays for. The price basis decides whether the number is final, capped or still being counted. The time entitlement decides whether days were granted, refused or reserved. A dependency makes the work wait on someone else, such as a utility owner, a landholder or a designer.
Public rules show why timing deserves its own fields. The Federal Highway Administration's rule for federal-aid highway contracts, 23 CFR 635.120, requires formal approval of major changes before they take effect, lets non-major changes be approved retroactively at the division administrator's discretion, and asks that time changes tied to a contract change be submitted with the related work change. Caltrans' Construction Manual treats an authorization to proceed before a change order is approved as an exception for extenuating circumstances and has the resident engineer record in the daily report who gave it.
Each open item needs its own field, the record that later settles it and an execution check. The examples quote the public change order log analyzed in the next section:
| Open item | How the approval leaves it open | Record that settles it later | Example in the public log |
|---|---|---|---|
| Scope boundary | Pays for a defined portion and names what is excluded or deferred | The later change order for the excluded work, field reports and pay items | CO 140 covers a bridge's substructure and says a subsequent change order will follow for the superstructure |
| Price basis | Sets a not-to-exceed ceiling, a provisional sum or a time-and-materials basis | Supplements that raise the ceiling, daily tickets and the final reconciliation | CO 18 on contract HSR 14-32 was revised four times to raise its not-to-exceed amount |
| Time entitlement | Prices the work but reserves or excludes schedule impacts | A later time extension or settlement order and the schedule analysis | CO 141 states that construction impacts, if any, are not included |
| Dependency | Lets part of the work start and holds the rest until a third party acts | Right-of-way delivery, utility relocation or permit records, then the follow-on order | CO 166 leaves a second phase until right-of-way delivery is complete |
| Direction before paper | Work is directed in writing before the change order is priced and signed | The directive linked to the change order that pays for it | CO 44 pays for work performed under directive letter DL-00054 |
What 812 public change orders show about approvals that stay open
Approvals stay open for a long time, and the record rarely says so. The California High-Speed Rail Authority publishes change orders on its transparency pages, and a public CSV conversion of its change order table, saved on GitHub in August 2021, lists 812 change orders on three Central Valley design-build contracts approved between June 2014 and June 2021. We counted how many were follow-ons to an earlier order and what the text of each says.
188 records, 23.2%, are supplements or revisions of an earlier change order, numbered like 88.10 or 18 R4, and 257 records (31.7%) sit in one of 71 families with more than one record. Where a family's first record is in the log, the follow-on came a median of 529 days after it, and 115 of 186 follow-ons (61.8%) came more than a year later. One environmental services order on contract HSR 13-06, first approved in April 2016, gathered ten supplements by January 2021, and the family of CO 24 on contract HSR 13-57 reached 28 records.
The text tells far less than the numbering. 95 records (11.7%) cite a directive letter, 24 (3.0%) carry an open price basis such as a not-to-exceed amount, a provisional sum or time-and-materials, and only 8 (1.0%) say in words what the order excludes or defers, with phrases such as not included in this Change Order or a date to be determined. In all, 291 records (35.8%) show at least one sign that the approval was staged or open-ended.
For a dataset, the lesson is about when to label. Had the first approval in the CO 18 family been labeled on its approval date in June 2017, the label would have missed four ceiling increases that ran to September 2020. The counts by measure:
| Measure | Records | Share of 812 | What it means for labels |
|---|---|---|---|
| Follow-on to an earlier change order (supplement or revision) | 188 | 23.2% | The first approval's outcome changes as the family grows |
| In a family with more than one record (71 families) | 257 | 31.7% | Label and split by family, not by record |
| Cites a directive letter | 95 | 11.7% | Work began on direction before the order that paid for it |
| Open price basis: not-to-exceed, provisional sum or time-and-materials | 24 | 3.0% | The approved amount was a cap or a running count |
| Says in words what the order excludes or defers | 8 | 1.0% | Condition text is rarely in the log; rebuild it from other records |
| Any of the four signs | 291 | 35.8% | More than a third of approvals were staged or open-ended |
Which records a business keeps for each change decision
The packet for one decision spans five record groups, and most companies keep them in different places. The change event or potential change order log holds the request and its status; RFIs, sketches and field directions hold the trigger; the estimate and subcontractor quotes hold the price build-up; the executed change order and any directive hold the decision; and daily reports, time-and-materials tickets, schedule updates and pay applications hold what happened next.
Software statuses capture part of this and lose the rest. Procore's default change order statuses include Pending - Proceeding, an item still pending while the work is being completed, and Pending - Not Proceeding, pending with the work stopped. Those values record that work went ahead before approval, the situation an authorization to proceed creates, but neither carries the condition itself. The cap, the excluded scope or the reserved days live in a PDF, a comment or an email.
Build each case as a workflow packet with the parts below, filled from the decision date backward and from the outcome window forward:
- Decision-time packet: the request, pricing backup, the triggering RFI or field direction, the schedule update current on the decision date and the contract's change clauses. Nothing dated after the decision enters this part.
- Decision record: the outcome class from the six above, the decision text verbatim, the approver's role and authority on that date, and any directive or authorization to proceed with its date.
- Conditions: one row per open item, typed as scope, price basis, time or dependency, with its bound (the portion, the ceiling, the days reserved or the awaited event) and the record expected to settle it.
- Execution trail: the daily reports, tickets, schedule updates and pay applications that touch the changed work, each dated.
- Family links: every later order that supplements, revises, credits or settles this one, found by number and by text reference, with the key that made each link.
- Outcome label and window: the label from the next section, the date it was set and the window applied.
How the outcome label becomes known, and when
The outcome of a conditional approval is known only when its change order family closes or a window fixed in advance runs out, and in the public log that often took more than a year. A label set earlier is a forecast recorded as a fact.
Five outcome values cover the families. Held: the work finished inside every condition and no follow-on changed the terms. Raised: a supplement increased a ceiling or added scope under the same approval. Converted: an open price basis was replaced by a fixed amount. Settled: the family was folded into a time-impact settlement or a dispute resolution. Open: the family had not closed at extraction. CO 45 on contract HSR 13-57, titled Time Extension No. 1, shows the settled path: a December 2017 order to settle time delays and impacts before August 31, 2017, followed in November 2019 by a settlement of later delays and certain disputes, then by orders paying delay-related escalation.
Open cases stay in the set as open, not as held. Dropping them makes approvals look cleaner than they were, because the families still growing are the ones that have not closed. The labels and their evidence:
| Outcome label | Evidence that sets it | Earliest it can be set | Common mislabel |
|---|---|---|---|
| Held | Closeout or final payment with no follow-on in the family | At family closeout | Labeling the case held on the approval date |
| Raised | A supplement or revision that lifts a ceiling or adds scope | When the follow-on is executed | Treating each supplement as a new, independent approval |
| Converted | A follow-on that replaces a cap, provisional sum or tickets with a fixed amount | When the converting order is executed | Reading the conversion as a cost overrun |
| Settled | A settlement or dispute-resolution order that names the family | When the settlement is executed | Labeling the original decision as wrong |
| Open | No closeout, and the window has not ended at extraction | Not final; revisit at the next extraction | Dropping the case or calling it held |
Casebook: six change requests and the answer a model should give
The casebook pairs each correct decision with the tempting wrong answer, because those hard negatives teach a model where conditions belong and where they do not. The six cases are illustrative: composites written for this guide, patterned on the record types above, describing no real project.
Case A is the control. A model that attaches conditions to everything is as wrong as one that never does, so the set needs clean approvals whose packets are complete. Cases B to F each turn on one fact in the decision-time packet that a reviewer can point to:
| Case (illustrative) | Decisive fact in the packet | Correct decision | Hard negative | What settles the label |
|---|---|---|---|---|
| A. Added door hardware on a tenant fit-out | Priced from unit rates, no schedule impact, design complete | Approve as submitted | Approve with a cap and reserved time out of habit | Closeout with no follow-on |
| B. Bridge redesign mid-project | Substructure drawings issued; superstructure still being finalized | Approve the substructure; defer the rest to a later order | Approve the whole bridge at the estimate | The later superstructure order and its price |
| C. Contaminated soil found during excavation | Extent unknown; disposal priced by the ton | Approve on time-and-materials under a ceiling, with daily tickets | A lump sum based on the first test pit | Tickets against the ceiling and any increase to it |
| D. Utility conflict found in the field | The owner's engineer directed the work in writing that day | Record the authorization to proceed; price it in a change order afterward | Treat the direction as approval of a price, or as unauthorized work | The change order that cites the directive |
| E. Change with a time extension request | Cost backup complete; schedule analysis not yet submitted | Approve scope and cost; reserve the days pending the analysis | Grant the requested days, or deny them outright | A later time extension order or the analysis |
| F. Request repeating scope paid earlier | Scope matches a change order executed last quarter | Return the request, citing the earlier order | Approve because it resembles approved requests | No follow-on; the earlier order stands |
Domain review checklist before a case enters the set
Every case needs adjudication by someone who has priced and scheduled changes, because condition types and outcome labels are judgment calls. The checklist is what that reviewer signs, and its failures decide whether a case is labeled in full, narrowed to the decision alone, or excluded:
At a glance
Domain review checklist before a case enters the set
Checklist · 9 items
- Decision-time cut: nothing in the packet postdates the decision, including later revisions of the same document.
- Outcome class: the reviewer assigns one of the six classes from the packet alone; a second reviewer repeats it on a sample, and agreement is reported.
- Condition typing: each open item is typed as scope, price basis, time or dependency, with its bound written as a value rather than a sentence.
- Family closure: the reviewer confirms the family has closed, or records the window and marks the case open.
- Text links: follow-ons found only by text, such as a supplement for a portion an earlier order deferred, are linked, and the linking key is stored.
- Directive pairing: every authorization to proceed is linked to the change order that paid for it, or flagged as unpaired.
- Funding mechanics: supplements that only top up a provisional sum are labeled as funding steps, not as failed estimates.
- Rights: the reviewer records whose records each layer is (owner, contractor, designer or subcontractor) and whether the supplier may license it.
- Redaction: names, signatures and contract sums are removed or generalized where the intended use does not need them.
0 of 9 ticked. Tick each item as you go.
What a licensor's records can and cannot show
A contractor's or owner's change records can teach decision structure and the long tail of follow-ons. They cannot by themselves show that a model is safe to approve changes, and a construction label on a dataset proves neither rights nor fitness for a high-stakes decision. That is the strongest objection to this design, and it applies in five ways:
- One owner, one delivery method: the public log covers three design-build contracts on one megaproject, while private commercial work, design-bid-build contracts and smaller owners number and stage changes differently.
- Numbering undercounts links: families here are found by number alone, yet CO 218 calls itself a supplemental change order for the superstructure of the same tied arch bridge whose substructure CO 140 covered, while carrying its own number, so the 23.2% follow-on share is a floor.
- Outcomes without reasons: the log shows what was approved and when, not the review comments, the alternatives weighed or the negotiation, which is the reasoning a decision model needs.
- Rights with several parties: owners, contractors, designers and subcontractors each hold parts of a change, and who may license which layer depends on their contracts, so counsel should check before any use.
- Bounded use: the set supports drafting, triage and consistency checks reviewed by a qualified person, not automated approval of structural, safety or code-related changes.
Specifying the data request for conditional change approvals
Ask for change order families, not change orders, and state the acceptance test in terms of linkage and decision-time completeness. A useful request names the record groups above, the years and contract types, the minimum share of families with a closed outcome, and how directives and text-linked follow-ons are to be joined.
SourceX finds datasets like this on request among businesses that hold the records, rather than selling from inventory, and its request form collects scope, volume, language, format, timing and licensing needs. Add the intended use and the acceptance test, for example: on a sample of families, every follow-on links to its base order and no decision-time packet contains a document dated after the decision. The supplying company approves the scope and terms and signs before any record moves; nothing here implies that such records are on hand or that a given set will pass the test.
How the change order count was made
Data: change-orders.csv in the GitHub gist kuanb/65e681e2239a1c4008f826b1132791bc at revision a84abc6, saved on August 22, 2021, a third-party CSV conversion of the Authority's published change order table; the official data are reachable here only through this copy. The official table on hsr.ca.gov could not be opened from this environment, so no official count was available to compare with the copy, the figures are the copy's, and orders approved after the conversion are missing. The file was read on October 28, 2026 as UTF-8 with any byte-order mark removed, by a script that reads only the file.
Rules as applied: each row is one change order. Contract is the CONTRACT NO. field, so rows labeled CP 2-3 and CP 2/3 count as one contract. Approval dates parse as month, day and four-digit year (736 rows) or month, day and two-digit year read as 20YY (76 rows); none failed, and impossible dates would have been rejected. A number's base is its leading digits read as an integer; anything after them (a point and digits, R or r and digits, an S suffix or a letter) makes the row a follow-on. A family is a contract plus a base. The gap is a follow-on's approval date minus its family's unsuffixed record, for the 186 follow-ons whose base is in the log.
Text flags search the title and description. Directive: directive letter or directive letters as whole words in any case, or DL followed by an optional hyphen or space and a digit, or DLs, case-sensitive. Open price: not-to-exceed (hyphen or space), provisional sum or sums, or time and material or materials with spaces or hyphens between the words, any case, or NTE and T&M, case-sensitive. Excludes or defers: not included in this, not included in prior, does not include, excludes all, subsequent change order or subsequent contract change order, final change order, to be determined, or if any, any case; all eight matching records were read. Shares are exact fractions rounded once, half up, and the median of an even count is the mean of the two middle values, rounded half up. Not measured: family links made only in text, amounts, review comments, any private project's records and anything about SourceX. The scripts and outputs are kept in the writer's scratch folder W09-main-004/bin.
Frequently asked questions
What is a conditional approval on a construction change order?
It is an approval that commits to the change but leaves something open: a portion of the scope, the final price, the schedule impact, or a start that waits on someone else. Those conditions bind the later work, so a dataset has to store them as typed fields and check later records against them.
How is an authorization to proceed different from an approved change order?
An authorization to proceed lets work start before the change order is priced and signed, so it settles timing, not price. Caltrans' Construction Manual treats it as an exception and has the engineer record who gave it, and the formal change order follows. In a dataset they are separate records that must be linked.
How long should a dataset wait before labeling the outcome?
Until the change order family closes, or until a window fixed in advance ends, with unfinished families labeled open. In the public high-speed rail log, 61.8% of follow-on orders came more than a year after the first approval, so short windows mislabel many cases.
Can public change order logs train a decision model?
They can teach family linkage, timing and how often approvals are staged, but not the reasoning behind decisions, because they omit review comments, alternatives and negotiation. Decision reasoning needs a contractor's or owner's own packets, licensed after each party's rights are checked.
Who owns the records in a change order packet?
Usually several parties: the owner holds the decision and its reviews, the contractor its proposals and costs, subcontractors their quotes and the designer its drawings. Which layers a supplier may license depends on the contracts, so counsel should review the specific documents.
Sources
- A CSV conversion of the California High-Speed Rail Authority's change order table, saved August 22, 2021: 812 change orders on three Central Valley design-build contracts approved June 2014 to June 2021, recounted for this article. Source
- The California High-Speed Rail Authority's transparency and accountability page includes a change orders section. Source
- Procore's default change order statuses include Pending - Proceeding (pending, work being completed) and Pending - Not Proceeding (pending, work stopped). Source
- 23 CFR 635.120: major changes need formal approval before taking effect; non-major changes may be approved retroactively at the division administrator's discretion; time changes tied to a contract change are submitted with the related work change. Source
- Caltrans Construction Manual section 5-3: an authorization to proceed with change order work is issued only for extenuating circumstances, and the resident engineer's daily report records who gave it. Source
- A 2023 arXiv study applies knowledge graph-enhanced large language models to automating construction contract review. Source
- A 2023 arXiv study applies a knowledge-augmented language model to construction contract risk identification. Source
Tell us what data you need
Share scope, volume, format, timing and licensing needs. Datasets are sourced on request.