Pooyan: Created page with "= Acceptance = ''From Risk Engineering / Civil Engineering'' TOC == Basic considerations == == Logical Framework == == Legislative Framework == == Procurement/Contractual Framework == The contracting objective is to ensure that the client (public or private) receives conforming products and services while keeping the overall costs of client contract surveillance reasonable. This objective is based on the premise that the Contractor is responsible for the manag..."

2025-11-29T23:12:50Z

Created page with "= Acceptance = ''From Risk Engineering / Civil Engineering'' __TOC__ == Basic considerations == == Logical Framework == == Legislative Framework == == Procurement/Contractual Framework == The contracting objective is to ensure that the client (public or private) receives conforming products and services while keeping the overall costs of client contract surveillance reasonable. This objective is based on the premise that the Contractor is responsible for the manag..."

New page

= Acceptance =

''From Risk Engineering / Civil Engineering''

__TOC__

== Basic considerations ==

== Logical Framework ==

== Legislative Framework ==

== Procurement/Contractual Framework ==

The contracting objective is to ensure that the client (public or private) receives conforming products and services while keeping the overall costs of client contract surveillance reasonable. This objective is based on the premise that the Contractor is responsible for the management and quality control of the contract products and services and the client is responsible for performance assessment.

The client interfaces with the contractor on a number of levels: the contract level, the periodic work plan level, the work package level and, often, for critical deliverables or products and services.<ref name="FAR">{{cite web |title=FAR 52.246-5 – Inspection of Services (Cost-Reimbursement) |url=https://www.ecfr.gov/current/title-48 |publisher=Federal Acquisition Regulation |access-date=DATE}}</ref>

== Practice Framework ==

=== Information Technology ===

Microsoft Press defines '''acceptance criteria''' as “Conditions that a software product must satisfy to be accepted by a user, customer or other stakeholder.”
Google defines them as “Pre-established standards or requirements a product or project must meet.”

* Acceptance criteria are a set of statements, each with a clear pass/fail result, that specify both functional (e.g., minimal marketable functionality) and non-functional (e.g., minimal quality) requirements applicable at the current stage of project integration. These requirements represent “conditions of satisfaction.” There is no partial acceptance: either a criterion is met or it is not.<ref name="agile">''(Adapted from agile software development usage of “acceptance criteria” and “conditions of satisfaction”.)''</ref>

== Further Guidance ==

=== Contracting Definitions ===

* '''Acceptance''' – The act of an authorized representative of the client (e.g. Task Order Manager, COR/COTR) by which the client, for itself or as agent of another, approves specific deliverables, products, or services rendered as partial or complete performance of the contract, task order or project-governance (PG) quality requirements (“contract quality requirements”). (See also FAR 52.246-5, ''Inspection of Services – Cost Reimbursement''.)

* '''Authorized Company Certifying Official''' – An authorized representative of the Contractor who attests to certifications on behalf of the company.

* '''Acceptable Quality Level (AQL)''' – The maximum allowable quantity of non-conforming products or services, defined as either an absolute number or as a percent defective (or defects per hundred units), for which lots will be accepted, typically in conjunction with an established sampling procedure.

* '''Certification''' – The act of determining, verifying, and attesting in writing to the status of deliverables, personnel, processes, procedures, or items in accordance with specified requirements.

* '''Certification System''' – The administrative procedures for completing, reviewing, and approving the certificate of conformance; signed by an authorized party responsible for overall quality of the product or service.

* '''Certificate of Conformance''' – A document signed or otherwise authenticated by an authorized individual certifying the degree to which items or services meet specified requirements.

* '''Contract quality requirements''' – The technical requirements in the contract relating to the quality of the product or service and those contract clauses prescribing inspection and other quality controls incumbent on the contractor to assure that the deliverable conforms to the contractual requirements. (Task Order and Contract are used interchangeably in this definition.)

* '''Conditional acceptance''' – Acceptance of deliverables that do not conform to contract quality requirements, or are otherwise incomplete, that the contractor is required to correct or otherwise complete by a specified date.

* '''Critical nonconformance''' – A nonconformance (including incompleteness or delay, as applicable) that is likely to prevent performance (at the programmatic level) of a vital oversight function or substantially reduce the usability, functionality or reliability of the products or services for their intended purpose.

* '''Critical requirements''' – Requirements that are vital to the programmatic oversight function.
Examples: contractor products that are major inputs into critical decisions transmitted to senior executives, legislative staff, or other agencies.

* '''Government contract quality assurance''' – The various functions, including inspection, performed to determine whether a contractor has fulfilled the contract obligations pertaining to quality and quantity.

* '''Inspection''' – Examination and testing of supplies or services to determine whether they conform to contract requirements.

* '''Latent defect''' – A defect that exists at the time of acceptance but cannot be discovered by reasonable inspection.

* '''Major nonconformance''' – A nonconformance, other than critical, that is likely to materially reduce the usability, functionality or reliability of the products or services for their intended purpose.

* '''Minor nonconformance''' – A nonconformance that is not likely to materially reduce the usability, functionality or reliability of the products or services for their intended purpose, or is a departure from established standards having little bearing on the effective use of the products or services, or on reliance on the contractor’s assessments, evaluations or data.

* '''Patent defect''' – Any defect that exists at the time of acceptance and is not a latent defect.

* '''Quality Assurance (QA)''' – Actions taken by the client to check contractor-performed services to determine whether they meet the requirements and specifications of the work statement. QA activities provide confidence that the required level of quality is achieved.

* '''Quality Assurance Surveillance''' – The monitoring of contractor performance to assure that services received are timely and consistent with contract quality requirements.

* '''Quality Assurance Surveillance Plan (QASP)''' – The document used for contract quality-assurance planning and surveillance.

* '''Quality Control (QC)''' – Actions taken by the contractor to control the output of services so that they meet the requirements and specifications of the work statement.

* '''QC activities''' – Actions that involve the use of appropriate contractor policies and procedures in performance of the scope of work.

* '''Random sampling''' – A sampling method whereby each service output in a lot has an equal chance of being selected in order to estimate overall quality of the lot against an established standard.

* '''Routine requirements''' – Requirements that account for the majority of the contract effort. The client still demands quality work from the contractor but wants to minimize administrative expenses and maximize cost-effectiveness by not expending scarce contract-administration resources on intensive inspections when the contractor is delivering work that meets or exceeds expectations.

* '''Sample''' – One or more product or service outputs drawn from a lot.

* '''Sampling guide''' – A written procedure that describes what will be checked, the standard of performance, the performance indicators, and how checking will be accomplished (e.g. random or planned sampling), formulated to make use of the contractor’s quality plan.

* '''Significant requirements''' – Requirements other than critical, that if not met would materially reduce the usability, functionality or reliability of the products or services for their intended purpose.
Significant requirements may require client intervention to demand a higher standard of quality control on the part of the contractor.

* '''Surveillance activity checklist''' – Any acceptable format used by the client’s technical representative to evaluate the performance of the contractor. It can be used with random sampling or with other planned or scheduled surveillance activities.

== Beneficial Outcomes ==

''(Under construction)''

== Working definition of the term ==

''(Under construction)''

== Limitations of the definition ==

''(Under construction)''

== See also ==

* [[Program Management in Civil Engineering]]
* [[Civil Engineering Projects]]
* [[Management control]]

== References ==

<references/>

Acceptance - Revision history