Acceptance Criteria: What Does Done Mean?

Acceptance is the moment the Government has enough objective evidence to say the contractor delivered what the contract required. The decision lives in the file, backed by inspection notes, test results, photos, and deliverable reviews. Concrete things, not impressions.

The customer side has a real role here. Contracting can write the clauses, build the award, and process the receiving report. But the customer usually knows what the thing must do, what the service must look like, and what failure would mean in the real world. Many CORs are customer staff. Many inspectors are customer staff. The signature that says "yes, this is acceptable" often comes from your side of the team.

01What acceptance means

Acceptance is the Government saying the supplies or services conform to the contract's quality and quantity requirements. That sounds formal because it is. Acceptance affects payment, ownership, risk, warranty timing, and what rights the Government has if a problem appears later.

Inspection and acceptance are related, but they aren't the same thing.

Concept	Plain-English meaning	Why the customer should care
Inspection	The Government looks, tests, reviews, samples, observes, or otherwise checks whether the contractor met the requirement.	If you don't define what to inspect, people inspect whatever is easiest to see.
Acceptance	The authorized Government representative says the supplies or services are acceptable under the contract.	Acceptance is generally conclusive on obvious defects that normal inspection would have caught — with limited exceptions for latent defects, fraud, and gross mistakes (covered in section 03).
Warranty	A separate contract right to correction after acceptance, when the contract includes a warranty.	If the item won't be used right away, warranty timing may matter more than the delivery date.

02Products: usually simple

Products are often the easiest place to define acceptance. The item is delivered, it's the item the Government ordered, it's the correct quantity, it isn't damaged, and it works.

For a simple supply buy, acceptable might mean:

The danger is when the product looks simple on paper but the Government can't actually tell whether it works at delivery. That's where customers need to slow down and explain the real use case.

03The delayed-install trap

Sometimes the Government receives a product long before it can use it. Maybe the equipment can't be installed until another project finishes. Maybe the room isn't ready. Maybe IT hasn't approved the network connection. Maybe the facility needs power, water, gas, racks, shielding, flooring, or a structural change before the item can be tested.

If that fact isn't in the contract, everyone may treat delivery as the finish line even though the Government still doesn't know whether the product works for its intended purpose.

When delayed installation or delayed use is foreseeable, tell contracting early. The answer may be a staged inspection plan, a separate installation or startup acceptance event, special testing, a warranty tied to installation or beneficial use, or another contract term the CO decides is appropriate.

The point is not to make every product buy complicated. The point is to identify when "delivered" and "acceptable" are not the same event.

04Services need observable standards

Services are harder because there's no box on a loading dock. The contractor performs over time. Acceptable performance is usually proven by records, observations, outputs, response times, completion rates, error rates, customer feedback, or other evidence the Government can actually evaluate.

For services, acceptance criteria should answer four questions:

A service standard doesn't have to be fancy. It does have to be observable. "Provide good customer service" isn't enough. "Respond to help desk tickets within one business day and resolve routine tickets within three business days unless escalated" gives the COR something to monitor.

05Construction

Construction has its own rhythm: submittals, site visits, inspections, punch lists, code issues, commissioning, as-builts, warranties, and final acceptance. Civil Engineering (CE) teams usually know this world better than the average customer office, so this training isn't trying to replace construction training.

Still, the basic acceptance question is the same: what objective evidence proves the work is complete and acceptable?

• Inspection points. Are there stages where work must be inspected before it's covered, buried, energized, or closed up?
• Punch list. What can be corrected after substantial completion, and what prevents acceptance?
• Closeout documents. Are as-builts, O&M (Operations and Maintenance) manuals, test reports, warranties, keys, training, or certifications required before final acceptance?
• Commissioning or testing. Does the system have to run under load, pass a pressure test, balance airflow, or demonstrate another performance result?

For construction-heavy work, bring CE or the technical experts in early. Don't let a general customer office invent acceptance language for work the engineers will have to enforce later.

06The five pieces of useful acceptance criteria

Useful acceptance criteria give the CO, COR, inspector, and contractor the same scoreboard. A strong package usually answers five things.

If any of those five pieces are missing, the requirement may still be awardable, but post-award administration gets blurry. Blurry acceptance is where customers end up paying for work they can't prove is good, or fighting about work they never defined well enough.

07How acceptance gets documented (and why DoD acceptance lives in WAWF)

Acceptance is a documented event. When a COR or inspector says the supplies or services are acceptable, that decision gets captured in a record so payment can be authorized, ownership can transfer, and the file shows who said yes, when, and on what evidence.

The form depends on the contract and the agency:

• Receiving report. Generic name for the document that captures inspection and acceptance. Says what was received, when, in what quantity, in what condition, and who signed.
• DD Form 250 (Material Inspection and Receiving Report). The traditional DoD supply-contract form. Still referenced in many contracts and still used in limited situations.
• Commercial invoice plus acceptance signature. Common on commercial-item buys and simplified actions.
• Service-specific acceptance records. Monthly QA reports, performance scorecards, deliverable acceptance memos, or other artifacts the COR keeps.

The customer-side takeaway: when your COR signs an acceptance in WAWF, that's the official act. Make sure they have evidence backing the signature — inspection notes, test results, photos, deliverable reviews — before they click accept.

08When something fails inspection

Not everything is acceptable on the first try. The contract usually gives the Government a menu of responses when supplies or services don't meet the requirement. The CO picks the response based on the facts, the clauses, the timing, and the consequences.

• Reject and require correction. The contractor fixes the defect and re-submits for inspection. Common for fixable supply defects and routine service shortfalls.
• Reject and require replacement. The Government sends back nonconforming supplies and the contractor delivers conforming ones. Time and shipping costs usually fall on the contractor.
• Conditional acceptance. The Government accepts with documented deficiencies, sometimes with a price reduction or a corrective-action requirement attached.
• Price reduction (consideration). The Government keeps the work but pays less because the delivered item is worth less than what was specified. Used when full rework isn't practical.
• Cure notice. Formal notice giving the contractor a deadline to fix performance before the Government considers stronger action.
• Show-cause notice. Formal demand for the contractor to explain why the contract shouldn't be terminated.
• Termination for default. The contract ends because of contractor failure. Heavy hammer; the file has to support it.
• Termination for convenience. The Government ends the contract for its own reasons. Not a failure response, but listed here because it sometimes shows up in adjacent conversations.

Customers don't pick the response. The CO does. But customers should:

• Document the failure with facts. Photos, dates, witness names, mission impact, what was tested, what failed.
• Notify the CO immediately. Don't try to handle it directly with the contractor. That can create unauthorized commitments or weaken the Government's position.
• Don't sign acceptance for something that isn't acceptable. Pressure to keep things moving is real. The signature isn't worth the paperwork mess that comes when the failure surfaces later.

09Weak vs. usable examples

10What to send contracting

You don't need to write the contract clause. Send the facts. The CO can turn those facts into the right contract structure.