A soldier is burned when a vehicle’s fuel system erupts after a rollover. A worker is maimed by a machine the state bought to a detailed set of drawings. In both cases the manufacturer says the same thing: “We only built what the government told us to build.” That sentence is the whole ballgame, because it invokes one of the most powerful shields in product litigation.
The government contractor defense lets a manufacturer escape liability for a design that injured someone — but only when the government, not the company, truly made the design call. It is a narrow, conditional immunity borrowed from federal law, and it fails the moment the maker turns out to have chosen the danger or hidden it. Whether a product was “made to spec” is where these cases are won and lost.
This article explains how the defense works in Massachusetts injury cases: what a manufacturer must prove to claim it, the line between specifications the government dictated and design choices the company made on its own, and why a maker that concealed a known risk cannot hide behind the contract. It is general information, not advice about a specific case. Because it sits inside the larger subject of defective products, our overview of what a product liability case involves is a useful companion.
What the government contractor defense actually is
Before you can beat the defense, you have to understand why it exists and how narrow it really is.
Where the shield comes from
The defense is a creature of federal law, not a Massachusetts statute. The U.S. Supreme Court recognized it in Boyle v. United Technologies Corp. in 1988, reasoning that when a contractor builds a product to the federal government’s design, holding the contractor liable under state tort law would interfere with the government’s own discretionary decisions — decisions that are themselves immune. In other words, the immunity the government enjoys for its design choices is extended to the private company that merely executed them. It is a displacement of state law in a specific, limited pocket, not a general license for manufacturers to avoid responsibility. Read that way, the defense is the exception, and ordinary product-liability responsibility remains the rule.
The three conditions a maker must prove
Under Boyle, a contractor gets the defense only if it proves all three of these things: the government approved reasonably precise specifications; the product conformed to those specifications; and the supplier warned the government about the dangers in the product’s use that were known to the supplier but not to the government. Miss any one of the three and the shield disappears. The burden sits on the manufacturer, and each element is a real evidentiary hurdle, not a formality — which is exactly why so many of these cases turn on documents about what the government actually reviewed and what the company actually disclosed.
A federal defense inside a state-law claim
An injured person’s underlying claim in Massachusetts usually rests on the implied warranty of merchantability, the state’s functional equivalent of strict product liability, hyperlinked here to Massachusetts General Laws chapter 106, section 2-314. The government contractor defense does not change what the plaintiff must show; it is an affirmative defense the manufacturer raises to escape a claim that is otherwise valid. That framing matters: the injured person still proves an ordinary defect case, and the contractor carries the separate burden of proving the federal immunity applies. If the contractor cannot carry it, the case proceeds like any other defective-design claim. That is worth emphasizing: raising the defense is not the same as winning it, and a contractor that pleads the defense but cannot prove its elements is in the same position as a manufacturer with no special immunity at all.
Did the government approve reasonably precise specifications?
The first Boyle condition is usually the battleground, because “made to spec” only counts when the government genuinely exercised its own judgment.
Discretionary approval versus a rubber stamp
The specification has to reflect an actual government judgment about the design, not a formality. Courts distinguish between the government meaningfully evaluating and approving a design — weighing the trade-offs and signing off — and the government simply accepting whatever the contractor proposed. A specification the contractor wrote and the government initialed without independent review is not the kind of discretionary approval the defense protects. The point of the immunity is to shield the government’s own design choices; if the government never really made the choice, there is nothing to shield.
Why “made to spec” is the heart of it
When the specifications are detailed and the government studied and approved them, the contractor that built exactly to those drawings has a strong claim that the design decision was the government’s. When the specifications are broad performance goals — “build a vehicle that can do X” — and the contractor filled in the dangerous details, the design decision was the company’s. Most disputes live in this gap. A plaintiff’s lawyer digs into how precise the specifications were, whether they dictated the specific feature that caused the injury, and whether the government approved that feature or left it to the maker.
Who has to prove what
Because the defense is the manufacturer’s to prove, the company must come forward with the specifications, the approval records, and evidence that the government exercised real discretion over the injuring feature. An injured person does not have to disprove the defense from the outset; the contractor must establish it. In practice that means the specifications, design-review minutes, and correspondence between the contractor and the procuring agency become the center of the case, and gaps in that record tend to cut against the party that bears the burden. A manufacturer that has lost or cannot locate the approval records is in a weak spot, because the absence of proof falls on the party required to supply it, not on the injured person who was never part of the contract. It also means an injured person should not be discouraged by an early, confident assertion of the defense, because the assertion and the proof are two very different things.
Discretionary specs versus the maker’s own choices
The defense protects orders the maker followed — not dangers the maker chose and then blamed on the contract.
When the maker chose the unsafe design
If the feature that hurt someone was the contractor’s own engineering decision, the fact that the product was sold to the government does not summon the defense. A company that selects an unsafe material, omits a guard, or routes a fuel line in a dangerous place has made a design choice, and it answers for that choice like any other manufacturer. The defense reaches only the aspects of the design the government actually specified and approved; everywhere the contractor exercised its own discretion, ordinary product-liability law applies with full force.
“It followed orders” and the limits of that answer
“We followed orders” is persuasive only for the parts of the design the orders actually covered. Contracts frequently set performance requirements while leaving the contractor free to decide how to meet them, and the freedom the contractor exercised is precisely where liability lives. Courts parse which specific design features were mandated and which were left open, because the immunity is feature-specific, not product-wide. A manufacturer cannot point to a thick specification on unrelated components and use it to excuse the one dangerous decision the government never made.
Design defects the government never dictated
Some defects have nothing to do with the design at all — a manufacturing error that departs from the approved drawings, or a failure that reflects sloppy production rather than the specified design. The government contractor defense does not touch those. It is a design-specification defense; it protects a maker that built the approved design correctly, not one that botched the build or deviated from the plans. An injured person whose harm came from a manufacturing defect or a departure from spec is outside the defense entirely, no matter who bought the product. In practice, distinguishing a design case from a manufacturing case early shapes the whole strategy, because a build defect sidesteps the government-contract question and can shorten the fight considerably.
Failure to warn the government of known risks
The third Boyle condition is its own defeater: a contractor that hid what it knew loses the shield even if the specs were precise.
The maker’s duty to share what it knew
The defense requires the supplier to have warned the government about dangers in the product’s use that were known to the supplier but not to the government. This is an affirmative disclosure duty baked into the immunity: a contractor cannot sit on knowledge of a hazard, deliver the product, and then claim the government approved a design it did not fully understand. If the company knew of a risk the government did not, and stayed silent, the third condition is not met and the defense fails no matter how detailed the specifications were.
“The government already knew”
Contractors often respond that the government knew as much about the hazard as they did, which, if true, satisfies the condition — there is no duty to warn the government of what it already understands. That turns the case into a factual contest about the state of each side’s knowledge: what testing the contractor had done, what failure data it held, what it told the procuring agency, and what the agency independently knew. The injured person’s lawyer develops the contractor’s internal records to show the company knew something the government did not.
Hidden dangers defeat the defense
When the evidence shows the manufacturer knew of a specific danger — from its own tests, field reports, or prior incidents — and did not disclose it, the shield collapses. This is where a “made to spec” case is frequently broken: not by disproving the specifications, but by proving the concealment. A contractor that withheld a known hazard has failed a condition of the very defense it invokes, and the claim proceeds as an ordinary defective-product case with the concealment now part of the story. Juries respond strongly to evidence that a company knew of a hazard and delivered the product anyway, so a concealment finding often reframes the case from a dry contract dispute into a straightforward account of a preventable injury.
Reading the specification the right way
Because the first Boyle condition rises or falls on what the specification actually said, learning to read it carefully is often the difference between a defense that holds and one that evaporates.
Precise design specifications versus performance goals
Not all specifications are alike. A true design specification tells the contractor exactly what to build — the dimensions, the materials, the placement of a part — and leaves little to the maker’s judgment. A performance specification sets a goal (“withstand this load,” “reach this speed”) and lets the contractor decide how to get there. The defense is strongest under a detailed design specification the government reviewed, and weakest under a performance goal the contractor filled in on its own. Where the injuring feature falls on that spectrum is usually the first thing a lawyer maps, because a performance-based contract often means the dangerous choice was the company’s to make.
Optional versus mandatory features
Specifications frequently mix mandatory requirements with options the contractor may choose among, and the distinction matters. If a safety feature was available and the contractor chose to leave it out, the government did not dictate that omission — the company did. If the specification affirmatively forbade the feature, the analysis changes. Pulling apart what the contract required, what it permitted, and what it left to the maker is how a lawyer isolates the specific decision behind the injury and tests whether the government, rather than the contractor, truly made it.
The role of expert engineering testimony
These cases are rarely resolved on the documents alone; they usually require an engineer who can explain what the specification did and did not dictate, how the injuring feature was designed, and whether a safer alternative was available and compatible with the contract. Expert testimony translates a dense specification into the plain question a jury can decide: did the government make this design choice, or did the manufacturer? A well-supported engineering opinion is often what prevents a contractor from stretching a narrow, feature-specific approval into a product-wide shield. The same expert usually addresses whether a safer alternative design existed that would still have satisfied the contract, since a feasible, contract-compatible alternative undercuts any claim that the government left the maker no safer option.
The other battles inside a spec-built case
Even where the government-contract question is live, a spec-built case rarely turns on that one issue alone. Several other fights tend to run alongside it, and they often decide the outcome as much as the Boyle conditions do.
Getting the specifications and approval file produced
The evidence that decides these cases — the specifications, the design-review minutes, the testing data, the disclosure correspondence — sits in the hands of the manufacturer and, sometimes, a government agency. None of it surfaces voluntarily. A plaintiff has to demand it through discovery, and contractors frequently resist on confidentiality or sensitivity grounds, which can require motion practice to resolve. Because the manufacturer bears the burden of proving the defense, gaps and delays in producing that record tend to cut against the manufacturer, not the injured person; a maker that cannot document precise government approval of the injuring feature has trouble carrying its burden. Pressing early and specifically for the specification and approval file is often what forces the “made to spec” story to hold up or fall apart.
Comparative fault and product misuse
Manufacturers in these cases raise the same everyday defenses they raise in any product claim: that the injured person misused the product or was careless. Massachusetts applies comparative negligence under Massachusetts General Laws chapter 231, section 85, under which a plaintiff who is not more than fifty percent at fault still recovers, with the award reduced by their share, and is barred only at fifty-one percent or more. Ordinary use of a product for its intended purpose is not misuse, and a foreseeable mistake by a user does not excuse a dangerous design. These arguments usually affect how damages are apportioned rather than defeating the claim, and they exist independently of the government-contract question.
When more than one company is responsible
A government-spec product is frequently the work of several companies: a prime contractor that built to the specification and subcontractors that supplied components. The government-contractor defense is feature-specific and company-specific, so it may shield one party as to one design element while leaving others exposed — a component supplier whose part was defective may have no defense at all, an issue that overlaps with ordinary component-part liability. Sorting out which company made which decision, and which of them can actually prove the Boyle conditions for the injuring feature, is central to identifying every responsible defendant rather than accepting the first “we built it to spec” answer.
What this defense means for an injured person
For someone hurt by a government-bought product, the defense is a hurdle, not a wall — and often it does not apply at all.
Military and government-supplied products
These cases arise around military vehicles, aircraft components, equipment supplied to state and municipal agencies, and machinery built to public specifications. A crash in a defective government vehicle, for instance, can support a claim against the maker much like any other vehicle crash claim, and a serious burn or crush injury from defective equipment is handled like any other catastrophic injury. The government-contract angle adds a defense the maker may raise; it does not change the fact that a dangerously defective product caused the harm.
The contractor, not the government, is the defendant
The defense is about suing the private manufacturer; claims against government entities themselves run through separate immunity and tort-claims rules and are a different analysis. For the injured person, the practical target is usually the contractor that designed and built the product, and the question is whether that contractor can prove all three Boyle conditions. Because the maker so often cannot — because it exercised its own discretion, or knew of a danger it did not disclose — a product built for the government is frequently still a viable case against the company that made it. Identifying every company in the chain — the prime contractor, subcontractors, and component suppliers — matters too, because the defense may shield one and leave another fully exposed.
The evidence that decides these cases
These claims are won in the documents: the specifications themselves, the government’s design-review and approval records, the contractor’s testing and failure data, and the correspondence showing what the company disclosed. A defective product built for the government can cause the same life-altering harm as any other — and the same categories of recovery, including medical costs, lost earning capacity, and compensation for pain, suffering, and lasting effects, are on the table. Preserving the product and forcing production of the specification and approval file is central to overcoming the defense. Where a defective government-supplied vehicle or machine causes a death, the analysis carries over to a wrongful-death claim brought by the family, with the same focus on what the government specified and what the contractor disclosed.
Deadlines and protecting a spec-built product claim
Because these cases depend on documents and the product itself, acting early is what keeps the claim alive.
The three-year deadline
A Massachusetts personal-injury claim, including one built on a defective product, generally must be filed within three years of the injury under Massachusetts General Laws chapter 260, section 2A. Because a spec-built case can require obtaining specifications and approval records from a government agency — which takes time — and because the product must be preserved, the practical window to act is shorter than three years. Waiting risks both the deadline and the loss of the evidence the case depends on.
Preserving the specifications and approval records
The injuring product, the governing specifications, and the government’s approval file are the heart of the case. Securing the product before it is repaired or scrapped, and moving quickly to obtain the specification and design-review records, is what allows a lawyer to test the maker’s “made to spec” story against what the government actually approved and what the company actually disclosed. These records rarely surface on their own; they have to be demanded and preserved deliberately. A prompt preservation letter to the manufacturer, and a targeted request for the specification and design-review file, are the practical first moves that keep the maker from later claiming the relevant records are simply unavailable.
When to call a Boston injury lawyer
If a product built for the military or a government agency injured you and the manufacturer is pointing to the contract, that defense is worth testing rather than accepting, because it fails whenever the maker chose the danger or hid it. A lawyer can preserve the product, obtain the specification and approval records, and pursue the contractor when the defense does not hold. Our Boston personal injury attorneys handle defective-product and product liability claims across the Commonwealth, including design cases that overlap with a design-defect analysis; these matters are handled on contingency, so there is no fee unless there is a recovery. If a government-spec product hurt you, you can reach out to have your options evaluated.
Reviewed and Approved By
This article was reviewed for legal accuracy by Daniel J. Larson, the founding attorney of Larson Law and a Massachusetts-barred personal injury lawyer in Boston. He represents individuals and families harmed by negligence in serious-injury matters arising from motor-vehicle collisions, unsafe property conditions, and other preventable incidents. Attorney Larson takes a litigation-first approach, building each case through detailed investigation, discovery, and expert development with the expectation that it may be tried. Before founding the firm, he defended doctors, hospitals, and other healthcare providers in malpractice litigation at a Boston firm — experience that informs how he anticipates the way insurers and defense counsel evaluate a claim. He is a member of the Massachusetts Bar Association and the Massachusetts Academy of Trial Attorneys.
Frequently asked questions
If a product was built for the military, can I never sue the manufacturer?
No. Building a product for the military or a government agency does not automatically immunize the maker. The manufacturer must prove three things: that the government approved reasonably precise specifications, that the product conformed to them, and that the company warned the government of dangers it knew about but the government did not. If the maker cannot prove all three — and often it cannot — the claim proceeds like an ordinary defective-product case.
What does “the government approved the specifications” really require?
It requires a genuine government judgment about the design, not a rubber stamp. If the government meaningfully evaluated and approved the specific design feature that caused the injury, that supports the defense. If the government merely accepted whatever the contractor proposed, or left the dangerous detail to the company, the approval was not the kind of discretionary decision the defense protects, and the maker remains answerable for its own design choice.
What if the manufacturer knew about the danger and did not tell the government?
Then the defense fails. One of its three conditions is that the supplier warned the government about known dangers the government did not know. A contractor that had test data, field reports, or prior incidents showing a hazard, and stayed silent, has not met that condition — no matter how detailed the specifications were. Proving that concealment is often how these cases are won.
Does the defense cover manufacturing mistakes too?
No. It is a design-specification defense. It can protect a maker that correctly built a design the government approved, but it does not cover a product that departed from the approved drawings or failed because of a manufacturing error. An injury caused by a build defect or a deviation from spec falls outside the defense entirely, regardless of who purchased the product.
Who do I actually sue in these cases?
Usually the private contractor that designed and built the product. Claims against government entities themselves run through separate immunity and tort-claims rules and are a different analysis. For the injured person, the manufacturer is generally the target, and the case turns on whether that manufacturer can carry its burden on all three conditions of the defense.
Results Disclaimer: Past case results, settlements, and verdicts mentioned on this website do not guarantee or predict a similar outcome in any future case. Every case is unique and depends on its own facts and legal issues.