Working copy
Draft text, rebuilt from the manuscript on every change. Stubs and source passages are still here, and none of it is final. Back to the working copy contents
Drafted The chapter is written and still being revised.
The zombie lost to a file format
In March 2019 a German construction firm sent in the cheapest bid for a public contract, and lost it over a file. The buyer had asked for the priced bill of quantities as a data file, in the format German tendering software reads. The firm sent PDFs. The buyer threw the bid out, the firm went to court, and the case climbed to the Federal Court of Justice. In 2023 the court held that the electronic means a buyer asks for are part of a bid's form, as much as a signature is, and that a bid which ignores them must be excluded. It sent the case back to Cologne, and in 2024 the court there found the exclusion lawful. The cheapest bid stayed out.
The zombie lost to a file format.
A North American reader may find that harsh, and a little foreign. Here a bid is a price on a form, and the drawings are PDFs that every bidder measures for itself. But the rule isn't fussiness. In Germany the bid has been data for decades, and a bid that arrives as a printed table, however neat, can't go through the same machinery as the others. American highways work much the same way, and have for most of the life of the internet. This chapter visits the places where the tender already speaks to machines: what they share, what a bill costs and who carries it when it's wrong, what the project should copy, and what none of them has yet.
The bid is already a file
Germany's version is called GAEB, after the joint committee that keeps it. The committee was founded in 1966 and has its office at the federal building research institute. Its format has a file for each step of a tender: the description of the work, the invitation to tender, the bid, an alternative bid, the award, and on through the measured quantities to the final invoice. The buyer writes the bill item by item, with a long text that binds and a short text that doesn't, and puts its own quantity on every line. The bidder's program fills in the prices and the blanks the buyer left, each blank numbered so that it comes back in the right place, and returns the file. Competing programs read and write the format, and a software association certifies them, one version at a time, for five years. German contract rules make unit prices against the buyer's quantities the normal contract. They also put the burden of clarity on the buyer: the work must be described so that every firm reads it the same way and can price it without extensive preparation.
American highways got there by another road. Each state transportation agency measures its own designs and issues a list of pay items with quantities, and bidders return unit prices. On the lettings of 44 state agencies, that list arrives as a data file. The bidder opens it in a free program, types in its prices, signs with a digital ID and submits. An addendum arrives as a new version of the same file. The states own the program together, through their national association, and a private company builds and hosts it. Only the drawings and the specifications are still read as pages. Even the file is on the move: North Carolina has taken highway bids through a web page since July 2026, and the desktop program is due to retire in June 2027.
Austria is Germany's sibling, with one thing reversed. Its format, ÖNORM A 2063, is a national standard, and reading it costs about €430 for its two parts. The words that go in it are free. The federal ministry publishes standard item texts for building and for building services, free to download. Austria's procurement law tells buyers to take such texts into account where they exist, and to decide how far each price should be broken down, for example into labour and other costs. So a bill built on the ministry's texts prices each item twice, once for labour and once for everything else, and each part is adjusted for inflation on its own. Every such bill also ranks its own texts, so that when two disagree, everyone knows which one wins.
| Germany | United States highways | Austria | |
|---|---|---|---|
| The format | GAEB, kept by a public committee | The bid file of one shared program, owned by the states' association | ÖNORM A 2063, a national standard |
| The item texts | Licensed | Each state's own, free | The ministry's, free |
| Who measures | The owner | The owner | The owner |
| What a bidder needs | Any certified program | The states' free program, moving to a web page | Any program that supports the standard |
Norway and Switzerland run the same idea under standards of their own, and Britain has priced buildings from a bill of quantities drawn up for the owner since at least the 1820s. Three keepers, one design: the owner measures, the bid is a file, and the bidder's job is to fill in the prices. When several countries reach the same answer by different roads, that's the shape of a standard waiting to be written down, not a German habit.
Why the owner measures
Every system in that table shares one rule, and it matters more for bots than anything in the file. The owner measures. Someone counts the doors, the cubic metres and the tonnes once, and every bidder prices the same list.
That turns the bidder's job from reading pictures into reading words and numbers, which is what today's language models do well. On a 2026 test built from architectural and engineering drawings, the best models answered about 95 percent of the questions about the text on a sheet correctly. They counted symbols right only 40 to 55 percent of the time. They found the bedrooms and the toilets, which come with labels, and miscounted most of the doors, which don't.
With a bill, a bot never has to count a door. The drawings keep their engineering role, as the instrument the engineer seals and the builder builds from, and people read them as they always have. Chapter 1's mythical beast, the bug-free drawing, can stay in its cave: a bot pricing a bill never has to meet it. The project's estimator will work this way: the owner supplies the quantities, and the bot never has to read a plan.
If you've bid a building in Canada or the United States, you know the other way. It dates from the 1870s, when general contracting took hold in the United States and contractors learned to measure their own work. A British productivity team toured the United States in 1949 and found no quantity surveyors. At a meeting of British surveyors the following year, one speaker summed up the difference: in America, "the contractor took the responsibility for the accuracy of the tender information". So a building here is bid as one lump sum, and every bidder measures the same drawings.
Around 1969, the US National Bureau of Standards tried to put a price on that. For one $5 million government office building, it reckoned, the takeoffs of every general contractor, subcontractor and supplier bidding on it cost about $540,000 in all, roughly 11 percent of the building's value. It proposed giving every bidder the same quantities. Nothing seems to have come of it. The duplication is the cost of the North American way, and the misreadings are its risk. A bidder's bot inherits both.
What a bill costs, and who carries its mistakes
A bill isn't free. Someone has to measure the design before the tender, which needs a finished design and a paid measurer. Germany's fee scale gives the designer a tenth of its fee for preparing the tender, the quantities and the bill included. What the owner buys with that tenth shows up at both ends of the job.
At the bid, a lump sum costs more wherever the quantities are uncertain, because each bidder has to carry the quantity risk itself and prices it, like an insurer. A study of Massachusetts bridge work used a model of how bidders behave to estimate what asking for lump sums instead of unit prices would have done. The transportation department's spending would have risen by 133 percent on average, and by 85 percent on the middle project. On simple, well-defined work the gap shrinks and can even turn around. Florida keeps lump sums for jobs like fencing, signs and resurfacing. A 2007 study of about 2,400 of its contracts compared both kinds against the department's own estimates. At award, the lump sums came in about four points dearer than the unit-price contracts. By the end they were about two and a half points cheaper, because they grew far less during construction. For the bidder, a 2014 survey of British contractors put the cost of preparing a bid at about 0.57 percent of the project's value, without saying whether a bill came with it. Nobody seems to have measured what a bill saves the bidders, which is a strange gap in an industry that measures everything else.
A bill moves the reading risk to the owner. It doesn't remove it, and bidders notice. In Massachusetts, the same study found that bidders price higher on items whose quantities later overrun, by about 0.085 percent for every 1 percent of overrun. Chapter 2 found the same habit in Texas: on lines the state would later pay short, the bidders had already priced low. Germany polices the game with rules. A unit price can be reset when its quantity moves by more than 10 percent, and unless the contract says otherwise, the new price follows the actual cost plus a reasonable markup, not the bid. A bid that shifts money between items, or prices an item to exploit the buyer, can be excluded, under a line of rulings that runs back to 2004. The owner pays for its own measuring mistakes, and the rules try to stop it paying for them twice.
There's a subtler cost, and every estimator who has priced concrete knows it. A bill fixes the unit, but the bidder's method sets the cost. Germany's own rules for concrete work measure formwork by the square metre and then, in the same breath, leave the choice of formwork to the contractor. A rate built on reusing one set of forms twenty times is the wrong rate for one extra wall. Three countries have three answers. Britain's method for civil engineering has let bidders price their methods as separate items, apart from the quantities, since 1976. German federal buyers ask the leading bidders for a breakdown of each unit price, kept confidential and outside the contract, and use it to price changes. Austrian bills split each unit price into labour and other costs in the bill itself. For a bot, any of the three is cheap: a bidder's bot can explain its price at almost no cost. Whether bidders will want it to is another question.
Copy the design, not the file
So should the project simply adopt GAEB? Its design is the right one, and decades of German tendering have tested it. Its file isn't the project's to adopt.
GAEB's documentation is a free download, published, in its own words, as the basis for developing software. It carries the copyright of DIN, the German standards body, and no licence at all, and its one rule about the schema files is that they "may not be changed". Austria's format costs about €430, and buying it gives no right to copy it. Its item texts are free to use, but not to change or to sell. The American file belongs to one program that the states license. None of these can simply be republished as part of an open standard, and crossing the Atlantic doesn't help. Copyright travels under the old treaties, and each country judges it by its own law. The trade agreements with Canada and the United States add nothing on licences.
What does travel is a design. In 2012 the EU's Court of Justice held that the format of data files isn't protected by the copyright in a program, and American law has long excluded any "system" or "method of operation" from copyright. So the project can take what the three versions share and write it down in its own words as an open format. They share four things: the owner's quantities, a fixed list of lines with numbered blanks for the prices, a new version of the file for every addendum, and a rule for which text binds. From Germany and Austria it can add a file for each step and the links into the design model. Then it can publish a crosswalk to each version, so that a German, Austrian or American buyer could issue the open file without changing what its bidders already know.
The trade agreements do add one thing, and it's the rule the German case turned on. When a public tender runs electronically, the WTO's procurement agreement, which binds Canada, the United States and the European Union, requires the buyer to use systems and software that are generally available. German tender law carries the same rule, by way of the EU's procurement directive. The Cologne court found that the buyer could insist on its file because the format and the programs to fill it in were generally available, and because it offered bidders a free program to send their bids. A free, open format is the safest ground a buyer can stand on. A paid one needs a free road beside it.
The next zombie
The design side is moving too. buildingSMART, the body that keeps IFC, the open format for building models, is writing the next version as small records in plain JSON, stacked in layers that each party writes for itself. It began as IFC 5 and is now called IFCX. Its core is planned to become an ISO standard at the end of 2029, and its project plan puts "contractual" guides out of scope. Nothing in it covers cost, quantities or the steps of a tender. Nobody is writing the tender layer. The project could.
The stack is the right home for it. The owner's tender layer would sit on the design model and hold the items, the counting rules and the quantities, written once. Each bidder would add a thin layer of its own on top, holding nothing but its prices. Nobody would edit anyone else's file, and an addendum would be a small change to one layer rather than a fresh pile of pages. In one 2026 test, a change travelled as about 0.0004 megabytes, against 7.9 megabytes to resend the whole file the old way.
It is also where the bill itself starts to look like a zombie. A list of items typed by hand is a copy of what the model already knows, and copies drift from their source. Counting from a well-built model is nearly solved: one 2026 study differed from hand measurement by at most 0.75 percent on a concrete building. Reading drawings isn't, as the test with the doors showed. Once bots can count the model under rules anyone can read, a separate hand-typed list becomes one more thing that walks around looking alive.
What survives is the itemizing. The prices move onto the model's own elements, and the bid becomes a layer of prices on the design. A short list stays for what no model shows: site setup, temporary works, the formwork that is the bidder's own business, and anything priced by time. The counting rules are the piece to watch. Germany's sit in paid standards, but its road builders already bill from a published catalogue of quantity formulas, with programs to check them, so rules can be written as code.
Until the model can carry the rest, the list is a bridge, and a bridge can be built to come down. Each line can say where its number came from: the owner's measure, a count from the model under a named rule, or the bidder. A line counted from the model can name the model's version and the elements it was counted from. Then today's lists and tomorrow's models fit the same format, and the list for any kind of work can retire on a test instead of an argument. It retires when two bots built by different people count the same model under the same published rules and agree, and the contract says the model governs. American highways are the place to try it first. Texas issues item lists today, and its draft standard looks ahead to the model as the legal document on select projects. Pennsylvania has piloted that since 2023.
What none of them has
Here is the gap. Germany certifies the programs that write its files, and 16 American states are paying to certify the programs that read and write design models. Nobody checks the bot that reads the tender. No system publishes how far a bot's prices miss, measured the same way for every bot, and that is the number a buyer, a bidder or an insurer would need before relying on one. Measuring it is what chapter 17's test is for.
The checking needn't be invented. A standards body such as ISO, ANSI or CSA could hold the standard, and accredited auditors could certify the bots, much as Germany's software association certifies programs and testing bodies certify everything from boilers to bike helmets. There is one condition, and it hides in the fine print. ISO's usual licence forbids turning its documents into data models or software, and forbids using them for machine learning, evaluating language models included. A bot standard that bots may not read would be an odd thing to certify against. So the format and the test should stay free and open, the way buildingSMART publishes IFC for free while ISO sells the same text. A standards body can host the certification and a formal edition beside them.
For North American buildings, all of this starts a step further back. There is no owner's bill to put in a file, and each bidder still measures the drawings for itself, with a bot or without one. The smallest step is an owner's breakdown of the work, generated from the model where there is one and issued for information. The bidder keeps the lump sum and its risk, but prices a list instead of a picture. France has bought buildings that way for years. That is where chapter 17's template begins.
A highway job doesn't need a second bid file. A building still needs its first.