China Construction Dispute Case Law: A Dataset Walkthrough for Cross-Border Counsel
Every large infrastructure or development project in China is a lawsuit waiting to be filed. The main contract layers into subcontracts, the subcontracts spawn change orders, the change orders unwind into a disputed settlement account, and somewhere in that chain a contractor goes unpaid, a building develops cracks, or a filed contract turns out to differ from the one the parties actually performed. The resulting litigation—construction dispute case law—is among the largest and most technically demanding bodies of civil precedent the Chinese courts produce. For any foreign developer, EPC contractor, lender, or legal AI team building China coverage, these judgments are the best available record of how a priority claim, a quality defect, or a black-and-white contract actually resolves—if you can get at them in a form you can use.
This piece is a walkthrough of China's construction dispute case law as a data problem: how the category splits into sub-causes that behave differently, why the decisive questions turn on findings buried in unusually long judgments, and what it takes to make priority, validity, and delay precedent searchable—for cross-border counsel and for legal AI teams. It is informational; it is not legal advice.
The substantive frame: construction is not one thing
The first mistake Western teams make is treating "construction" as a single research target. In the courts it is filed and decided under several distinct sub-causes of action, each with its own rules and its own recurring fights:
| Sub-cause | What's typically at stake |
|---|---|
| Construction-project contract | Settlement of the construction price, contractor's priority right to payment, validity of the contract, delay and change-order accounting |
| Quality & defects | Responsibility for defective works, rectification cost, the defects-liability period, and apportionment among parties |
| Decoration & fit-out | Smaller-scale interior works—scope, acceptance, and payment on renovation contracts |
| Survey & design | Liability for defective survey or design work upstream of construction |
These are not interchangeable. The rules on the contractor's priority right that dominate construction-price cases have no analogue in a survey-and-design dispute. A quality case turns on the defects-liability period and cost apportionment—questions that never arise in a plain payment fight. The unit of useful precedent is not "Chinese construction law"; it is judgments in the right sub-cause, in the right window, on the right issue.
The recurring trap: black-and-white contracts
The single most distinctive feature of Chinese construction litigation is the black-and-white contract problem—the "yin-and-yang" contract. Projects subject to mandatory tender are frequently governed by two inconsistent agreements: a filed or tendered version, and a separate side agreement on different terms, often signed to shift price or scope after the tender. When the two conflict, which one governs settlement of the construction price is a recurring and outcome-determinative question, and the courts have developed rules that turn on which contract was the substantive tendered one.
Two other issues recur with the same force and are worth naming because they surprise foreign counsel:
| Issue | Why it trips up foreign analysis |
|---|---|
| Payment even on an invalid contract | A construction contract may be void (e.g. unlicensed contractor, illegal subcontracting), yet where the works pass acceptance the contractor may still be entitled to payment by reference to the contract—invalidity does not automatically mean no payment |
| Contractor's priority right to payment | The contractor may hold a statutory priority over the project proceeds ranking ahead of some other creditors—whether it survives, and its scope and time limit, is frequently litigated and decisive in insolvency-adjacent situations |
Because the governing analysis on these questions has evolved—under the Civil Code and its construction-related judicial interpretations—construction precedent must be sliced by date and read against the rule in force, not treated as a single flat body of cases. A judgment on priority from one era may reason from a framework the current interpretation has refined.
Why this case law is genuinely hard to assemble
Construction is one of the hardest categories to assemble well, and the reason is not scarcity—it is depth. Several difficulties compound:
| Obstacle | Why it bites |
|---|---|
| Unusually fact-heavy judgments | A single construction judgment can run to a dense factual record—layered contracts, appraisals, settlement accounts—so the decisive finding is buried far deeper than in a typical civil case. |
| Distinct sub-causes | Contract, quality, decoration, and survey-design behave differently; "construction" as a filter is far too broad to be useful. |
| Rules that evolved | Priority, validity, and black-and-white contract analysis shifted under the Civil Code and its interpretations, so like-for-like comparison requires date slicing and rule awareness. |
| Numbers & findings buried in prose | The settlement figure, the appraised defect cost, the priority amount and its time limit sit inside reasoning text, often relying on an appraisal—keyword search cannot aggregate them. |
| Language & browse-first tooling | Sources are Chinese-language and built for human reading; filtering priority judgments by region, year, and outcome is awkward at best. |
So a question that sounds simple—"how have courts in this province treated the contractor's priority right where the main contract was held invalid, since the current interpretation took effect?"—turns into a manual slog through some of the longest judgments in the corpus. Answering it well is less a construction-law problem than a data-structure problem.
Turning it into a tractable dataset
Reframed as data, the requirement is concrete. To research China construction precedent reliably, you need a corpus where you can do four things a document dump will not let you do:
- Isolate the right matters. Filter to the specific sub-cause—construction-project contract, quality, decoration, survey-design—by cause of action and case-number conventions, rather than wading through everything that mentions "construction" or "project."
- Slice by the dimensions that decide the outcome. Narrow by sub-cause, region, court level, year, and outcome—because in construction work the governing interpretation in force and the local court's tendencies are part of the holding, not metadata.
- Cross the language gap. Query in English and read English summaries—especially valuable here, where triaging long judgments by hand is prohibitively slow—while the underlying authority stays the original Chinese judgment.
- Verify against the source. Every result carries a cited link back to the original document, because no commercial opinion—or AI answer—should rest on an unverifiable summary, least of all one turning on a priority amount or an appraised figure.
Those four capabilities are what a structured case law corpus provides and an unstructured one does not. Stable fields—case number, court, date, cause of action, parties, outcome—are what let you filter to, say, construction-contract judgments in a given province and window instead of keyword-guessing. We have described how those fields are modeled in our walkthrough of the case law API and document structure; construction is one of the practice areas where that structure pays off most, precisely because the judgments are so long and the category splinters into sub-causes whose rules have moved.
What this looks like for two kinds of teams
For cross-border and construction counsel
The research workflow becomes tractable. Scope the question—say, how courts in a given region have treated a contractor's priority right where the main contract was invalid, or how the black-and-white contract rule has been applied to settle price—retrieve the matching matters filtered by sub-cause, region, and year, read English summaries to triage the long judgments, then open the cited Chinese originals for the ones that bear on the project. For a developer facing a settlement dispute, a lender assessing a contractor's priority ahead of its security, or an EPC contractor weighing a delay claim, the value is reasoning from the current local pattern under the right rule rather than from a generic memo.
For legal AI vendors building China coverage
Construction disputes are high-value, technically intricate, and numerically precise—exactly the kind of use case that drives adoption of a legal AI product, and exactly the kind that punishes hallucination. An invented holding on priority, or a confident answer that an invalid contract means no payment, is worse than no answer. That makes it a textbook case for retrieval-grounded generation over a structured corpus: the model answers from retrieved, cited judgments—filtered to the right sub-cause, region, and rule era—rather than from parametric memory. If you are building this, the data layer is the whole game; see building China coverage into your legal AI for the stack view, and license vs scrape for why a maintained, freshly synced corpus beats a homegrown scrape in a category with judgments this long and rules this fluid.
The bottom line
China construction disputes are the litigation almost every major project eventually touches, and the case law is correspondingly vast and unusually deep. But that depth cuts both ways: the precedent that predicts whether a priority right survives or an invalid contract still gets paid is plentiful and almost impossible to use without structure, because it splinters into distinct sub-causes, turns on rules that evolved under the Civil Code, hides the decisive figures inside some of the longest judgments in the system, and lives in Chinese in browse-first databases. Whether you are construction counsel pricing a claim or a legal AI vendor supporting the question, the constraint is the same: you need the case law to be findable, by sub-cause, region, and year, with citations back to the source and the governing rule of the time in view. That is a data-structure problem before it is a construction-law one, and it is solvable with the right corpus.
That corpus is what SinoVerdict provides. We license a structured body of more than 130 million Chinese court judgments with stable fields, English queries and summaries, and cited links back to original judgments—delivered via bulk dataset, REST API, and MCP server, with daily updates that matter in a category where the governing interpretations keep being refined. Our clients include LexisNexis and China's leading legal databases. For construction work, that is the difference between guessing whether a priority claim will hold and seeing how courts in the relevant region, under the rule in force at the time, have actually treated it.
Frequently asked questions
Construction disputes are among the largest and most technically demanding civil matters in China. Construction-project contract disputes are a major category on their own, and they sit alongside related quality-defect disputes, decoration and fit-out disputes, and survey-and-design disputes. What makes the category distinctive is not only volume but complexity: a single project generates layered contracts, subcontracts, change orders, and settlement accounts, so the litigation turns on a dense factual record. For cross-border counsel and legal AI products, that means the precedent predicting whether a contractor's priority right survives or an invalid contract still gets paid is plentiful but buried in some of the most fact-heavy judgments the courts produce.
Construction projects that are subject to mandatory tender are frequently governed by two inconsistent contracts: a filed or tendered version, and a separate side agreement on different terms — often called black-and-white contracts, or the yin-and-yang contract problem. When the two conflict, which one governs settlement of the construction price is a recurring and outcome-determinative question, and the courts have developed rules for it that turn on which contract was the substantive tendered one. For research and dataset work this matters because the same fact pattern recurs constantly and the governing analysis has evolved, so precedent must be sliced by date and read against the rule in force, not treated as a single flat body of cases.
Construction is not one thing: construction-contract disputes, quality defects, decoration, and survey-and-design are distinct sub-causes with different rules, and treating them as one construction filter is too coarse. The decisive issues — contractor priority of payment, whether an invalid contract is still settled at contract price, delay and change-order accounting, the black-and-white contract question — turn on numbers and findings buried deep in unusually long, fact-heavy judgments rather than tidy fields, so keyword search cannot aggregate them. The rules have also evolved under the Civil Code and its construction-related judicial interpretations, so like-for-like comparison requires date slicing. And the documents are Chinese-language in databases built for human browsing. Turning that into a set you can filter by sub-cause, region, year, and outcome takes a structured corpus.
Yes, with the right data layer. The underlying judgments are in Chinese, but a structured corpus can expose them through English queries and English summaries while keeping cited links back to the original Chinese documents. That lets a team retrieve, say, contractor-priority or black-and-white-contract matters, filter by sub-cause, region, year, and outcome, and ground analysis in primary rulings without each lawyer first reading raw Chinese full text. Given how long and fact-dense construction judgments are, English summaries for triage plus cited originals for the decisive matters is especially valuable. It is informational research tooling, not a substitute for PRC-qualified counsel.
SinoVerdict licenses a structured corpus of more than 130 million Chinese court judgments with stable fields — case number, court, date, cause of action, parties, outcome — delivered via bulk dataset, REST API, and MCP server, with English queries, English summaries, and cited links back to original judgments. For construction work, that makes it possible to isolate matters by sub-cause of action, slice by region, year, and outcome, and read priority, validity, and delay questions against the rule in force at the time. It is a data and research layer for cross-border counsel and legal AI vendors, provided as informational tooling rather than legal advice.
Make China construction precedent findable.
Request a coverage report to see how SinoVerdict's 130M+ judgment corpus breaks down by sub-cause of action, court level, region, and year — then get a trial API key and test retrieval of contractor-priority, contract-validity, and black-and-white-contract rulings, in English, with cited links to the original judgments.
Request trial access