> ### Subpart 4.8- Government Contract Files

> ## 4.800 Scope of subpart.

> This subpart prescribes requirements for establishing, maintaining, and disposing of contract files.

> ## 4.801 General.

> (a) The head of each office performing contracting, contract administration, or paying functions shall establish files containing the records of all contractual actions.
> (b) The documentation in the files (see 4.803) shall be sufficient to constitute a complete history of the transaction for the purpose of-
> (1) Providing a complete background as a basis for informed decisions at each step in the acquisition process;
> (2) Supporting actions taken;
> (3) Providing information for reviews and investigations; and
> (4) Furnishing essential facts in the event of litigation or congressional inquiries.
> (c) The files to be established include-
> (1) A file for cancelled solicitations;
> (2) A file for each contract; and
> (3) A file such as a contractor general file, containing documents relating-for example-to-
> (i) No specific contract;
> (ii) More than one contract; or
> (iii) The contractor in a general way (e.g., contractor's management systems, past performance, or capabilities).

> ## 4.802 Contract files.

> (a) A contract file should generally consist of-
> (1) The contracting office contract file that documents the basis for the acquisition and the award, the assignment of contract administration (including payment responsibilities), and any subsequent actions taken by the contracting office;
> (2) The contract administration office contract file that documents actions reflecting the basis for and the performance of contract administration responsibilities; and
> (3) The paying office contract file that documents actions prerequisite to, substantiating, and reflecting contract payments.
> (b) Normally, each file should be kept separately; however, if appropriate, any or all of the files may be combined; e.g., if all functions or any combination of the functions are performed by the same office.
> (c) Files must be maintained at organizational levels that ensure-
> (1) Effective documentation of contract actions;
> (2) Ready accessibility to principal users;
> (3) Minimal establishment of duplicate and working files;
> (4) The safeguarding of classified documents; and
> (5) Conformance with agency regulations for file location and maintenance.
> (d) If the contract files or file segments are decentralized (e.g., by type or function) to various organizational elements or to other outside offices, responsibility for their maintenance must be assigned. A central control and, if needed, a locator system should be established to ensure the ability to locate promptly any contract files.
> (e) Contents of contract files that are contractor bid or proposal information or source selection information as defined in 2.101 must be protected from disclosure to unauthorized persons (see 3.104-4).
> (f) Agencies may retain contract files in any medium (paper, electronic, microfilm, etc.) or any combination of media, as long as the requirements of this subpart are satisfied.

> ## 4.803 Contents of contract files.

> The following are examples of the records normally contained, if applicable, in contract files:

> (a) Contracting office contract file.
> (1) Purchase request, acquisition planning information, and other presolicitation documents.
> (2) Justifications and approvals, determinations and findings, and associated documents.
> (3) Evidence of availability of funds.
> (4) Synopsis of proposed acquisition as required by Part 5 or a reference to the synopsis.
> (5) The list of sources solicited, and a list of any firms or persons whose requests for copies of the solicitation were denied, together with the reasons for denial.
> (6) Set-aside decision.
> (7) Government estimate of contract price.
> (8) A copy of the solicitation and all amendments thereto.
> (9) Security requirements and evidence of required clearances.
> (10) A copy of each offer or quotation, the related abstract, and records of determinations concerning late offers or quotations. Unsuccessful offers or quotations may be maintained separately, if cross-referenced to the contract file. The only portions of the unsuccessful offer or quotation that need be retained are-
> (i) Completed solicitation sections A, B, and K;
> (ii) Technical and management proposals;
> (iii) Cost/price proposals; and
> (iv) Any other pages of the solicitation that the offeror or quoter has altered or annotated.
> (11) Contractor's certifications and representations.
> (12) Preaward survey reports or reference to previous preaward survey reports relied upon.
> (13) Source selection documentation.
> (14) Contracting officer's determination of the contractor's responsibility.
> (15) Small Business Administration Certificate of Competency.
> (16) Records of contractor's compliance with labor policies including equal employment opportunity policies.
> (17) Cost or pricing data and Certificates of Current Cost or Pricing Data or a required justification for waiver, or information other than cost or pricing data.
> (18) Packaging and transportation data.
> (19) Cost or price analysis.
> (20) Audit reports or reasons for waiver.
> (21) Record of negotiation.
> (22) Justification for type of contract.
> (23) Authority for deviations from this regulation, statutory requirements, or other restrictions.
> (24) Required approvals of award and evidence of legal review.
> (25) Notice of award.
> (26) The original of-
> (i) The signed contract or award;
> (ii) All contract modifications; and
> (iii) Documents supporting modifications executed by the contracting office.
> (27) Synopsis of award or reference thereto.
> (28) Notice to unsuccessful quoters or offerors and record of any debriefing.
> (29) Acquisition management reports (see Subpart 4.6).
> (30) Bid, performance, payment, or other bond documents, or a reference thereto, and notices to sureties.
> (31) Report of postaward conference.
> (32) Notice to proceed, stop orders, and any overtime premium approvals granted at the time of award.
> (33) Documents requesting and authorizing modification in the normal assignment of contract administration functions and responsibility.
> (34) Approvals or disapprovals of requests for waivers or deviations from contract requirements.
> (35) Rejected engineering change proposals.
> (36) Royalty, invention, and copyright reports (including invention disclosures) or reference thereto.
> (37) Contract completion documents.
> (38) Documentation regarding termination actions for which the contracting office is responsible.
> (39) Cross-references to pertinent documents that are filed elsewhere.
> (40) Any additional documents on which action was taken or that reflect actions by the contracting office pertinent to the contract.
> (41) A current chronological list identifying the awarding and successor contracting officers, with inclusive dates of responsibility.
> (b) C ontract administration office contract file.
> (1) Copy of the contract and all modifications, together with official record copies of supporting documents executed by the contract administration office.
> (2) Any document modifying the normal assignment of contract administration functions and responsibility.
> (3) Security requirements.
> (4) Cost or pricing data, Certificates of Current Cost or Pricing Data, or information other than cost or pricing data; cost or price analysis; and other documentation supporting contractual actions executed by the contract administration office.
> (5) Preaward survey information.
> (6) Purchasing system information.
> (7) Consent to subcontract or purchase.
> (8) Performance and payment bonds and surety information.
> (9) Postaward conference records.
> (10) Orders issued under the contract.
> (11) Notice to proceed and stop orders.
> (12) Insurance policies or certificates of insurance or references to them.
> (13) Documents supporting advance or progress payments.
> (14) Progressing, expediting, and production surveillance records.
> (15) Quality assurance records.
> (16) Property administration records.
> (17) Documentation regarding termination actions for which the contract administration office is responsible.
> (18) Cross reference to other pertinent documents that are filed elsewhere.
> (19) Any additional documents on which action was taken or that reflect actions by the contract administration office pertinent to the contract.
> (20) Contract completion documents.
> (c) Paying office contract file.
> (1) Copy of the contract and any modifications.
> (2) Bills, invoices, vouchers, and supporting documents.
> (3) Record of payments or receipts.
> (4) Other pertinent documents.

> ## 4.804 Closeout of contract files.

> ## 4.804-1 Closeout by the office administering the contract.

> (a) Except as provided in paragraph (c) of this section, time standards for closing out contract files are as follows:
> (1) Files for contracts using simplified acquisition procedures should be considered closed when the contracting officer receives evidence of receipt of property and final payment, unless otherwise specified by agency regulations.
> (2) Files for firm-fixed-price contracts, other than those using simplified acquisition procedures, should be closed within 6 months after the date on which the contracting officer receives evidence of physical completion.
> (3) Files for contracts requiring settlement of indirect cost rates should be closed within 36 months of the month in which the contracting officer receives evidence of physical completion.
> (4) Files for all other contracts should be closed within 20 months of the month in which the contracting officer receives evidence of physical completion.
> (b) When closing out the contract files at 4.804-1(a)(2), (3), and (4), the contracting officer shall use the closeout procedures at 4.804-5. However, these closeout actions may be modified to reflect the extent of administration that has been performed. Quick closeout procedures (see 42.708) should be used, when appropriate, to reduce administrative costs and to enable deobligation of excess funds.
> (c) A contract file shall not be closed if-
> (1) The contract is in litigation or under appeal; or
> (2) In the case of a termination, all termination actions have not been completed.

> ## 4.804-2 Closeout of the contracting office files if another office administers the contract.

> (a) Contract files for contracts using simplified acquisition procedures should be considered closed when the contracting officer receives evidence of receipt of property and final payment, unless otherwise specified by agency regulation.
> (b) All other contract files shall be closed as soon as practicable after the contracting officer receives a contract completion statement from the contract administration office. The contracting officer shall ensure that all contractual actions required have been completed and shall prepare a statement to that effect. This statement is authority to close the contract file and shall be made a part of the official contract file.

> ## 4.804-3 Closeout of paying office contract files.

> The paying office shall close the contract file upon issuance of the final payment voucher.

> ## 4.804-4 Physically completed contracts.

> (a) Except as provided in paragraph (b) of this section, a contract is considered to be physically completed when-
> (1)(i) The contractor has completed the required deliveries and the Government has inspected and accepted the supplies;
> (ii) The contractor has performed all services and the Government has accepted these services; and
> (iii) All option provisions, if any, have expired; or
> (2) The Government has given the contractor a notice of complete contract termination.
> (b) Facilities contracts and rental, use, and storage agreements are considered to be physically completed when-
> (1) The Government has given the contractor a notice of complete contract termination; or
> (2) The contract period has expired.

> ## 4.804-5 Procedures for closing out contract files.

> (a) The contract administration office is responsible for initiating (automated or manual) administrative closeout of the contract after receiving evidence of its physical completion. At the outset of this process, the contract administration office must review the contract funds status and notify the contracting office of any excess funds the contract administration office might deobligate. When complete, the administrative closeout procedures must ensure that-
> (1) Disposition of classified material is completed;
> (2) Final patent report is cleared;
> (3) Final royalty report is cleared;
> (4) There is no outstanding value engineering change proposal;
> (5) Plant clearance report is received;
> (6) Property clearance is received;
> (7) All interim or disallowed costs are settled;
> (8) Price revision is completed;
> (9) Subcontracts are settled by the prime contractor;
> (10) Prior year indirect cost rates are settled;
> (11) Termination docket is completed;
> (12) Contract audit is completed;
> (13) Contractor's closing statement is completed;
> (14) Contractor's final invoice has been submitted; and
> (15) Contract funds review is completed and excess funds deobligated.
> (b) When the actions in paragraph (a) of this subsection have been verified, the contracting officer administering the contract must ensure that a contract completion statement, containing the following information, is prepared:
> (1) Contract administration office name and address (if different from the contracting office).
> (2) Contracting office name and address.
> (3) Contract number.
> (4) Last modification number.
> (5) Last call or order number.
> (6) Contractor name and address.
> (7) Dollar amount of excess funds, if any.
> (8) Voucher number and date, if final payment has been made.
> (9) Invoice number and date, if the final approved invoice has been forwarded to a disbursing office of another agency or activity and the status of the payment is unknown.
> (10) A statement that all required contract administration actions have been fully and satisfactorily accomplished.
> (11) Name and signature of the contracting officer.
> (12) Date.
> (c) When the statement is completed, the contracting officer must ensure that-
> (1) The signed original is placed in the contracting office contract file (or forwarded to the contracting office for placement in the files if the contract administration office is different from the contracting office); and
> (2) A signed copy is placed in the appropriate contract administration file if administration is performed by a contract administration office.

> ## 4.805 Storage, handling, and disposal of contract files.

> (a) Agencies must prescribe procedures for the handling, storing, and disposing of contract files. These procedures must take into account documents held in all types of media, including microfilm and various electronic media. Agencies may change the original medium to facilitate storage as long as the requirements of Part 4, law, and other regulations are satisfied. The process used to create and store records must record and reproduce the original document, including signatures and other written and graphic images completely, accurately, and clearly. Data transfer, storage, and retrieval procedures must protect the original data from alteration. Unless law or other regulations require signed originals to be kept, they may be destroyed after the responsible agency official verifies that record copies on alternate media and copies reproduced from the record copy are accurate, complete, and clear representations of the originals. Agency procedures for contract file disposal must include provisions that the documents specified in paragraph (b) of this section may not be destroyed before the times indicated, and may be retained longer if the responsible agency official determines that the files have future value to the Government. When original documents have been converted to alternate media for storage, the requirements in paragraph (b) of this section also apply to the record copies in the alternate media.
> (b) If administrative records are mixed with program records and cannot be economically segregated, the entire file should be kept for the period of time approved for the program records. Similarly, if documents described in the following table are part of a subject or case file that documents activities that are not described in the table, they should be treated in the same manner as the files of which they are a part. The retention periods for acquisitions at or below the simplified acquisition threshold also apply to acquisitions conducted prior to July 3, 1995, that used small purchase procedures. The retention periods for acquisitions above the simplified acquisition threshold also apply to acquisitions conducted prior to July 3, 1995, that used other than small purchase procedures.

> Document |  | Retention Period
> --- | --- | ---
> (1) Records pertaining to Contract Disputes Act actions. |  | 6 years and 3 months after final action or decision for files created prior to October 1, 1979. 1 year after final action or decision for files created on or after October 1, 1979.
> (2) Contracts (and related records or documents, including successful proposals) exceeding the simplified acquisition threshold for other than construction. |  | 6 years and 3 months after final payment.
> (3) Contracts (and related records or documents, including successful proposals) at or below the simplified acquisition threshold for other than construction. |  | 3 years after final payment.
> (4) Construction contracts: |  |
> (i) Above $2,000. |  | 6 years and 3 months after final payment.
> (ii) $2,000 or less. |  | 3 years after final payment.
> (iii) Related records or documents, including successful proposals, except for contractor's payrolls (see (b)(4)(iv)). |  | Same as contract file.
> (iv) Contractor's payrolls submitted in accordance with Department of Labor regulations, with related certifications, anti-kickback affidavits, and other related papers. |  | 3 years after contract completion unless contract performance is the subject of an enforcement action on that date.
> (5) Solicited and unsolicited unsuccessful offers, quotations, bids, and proposals: |  | .
> (i) Relating to contracts above the simplified acquisition threshold. |  | If filed separately from contract file, until contract is completed. Otherwise, the same as related contract file.
> (ii) Relating to contracts at or below the simplified acquisition threshold. |  | 1 year after date of award or until final payment, whichever is later.
> (6) Files for canceled solicitations. |  | 5 years after cancellation.
> (7) Other copies of procurement file records used by component elements of a contracting office for administrative purposes. |  | Upon termination or completion.
> (8) Documents pertaining generally to the contractor as described at 4.801(c)(3). |  | Until superseded or obsolete.
> (9) Data submitted to the Federal Procurement Data System (FPDS). Electronic data file maintained by fiscal year, containing unclassified records of all procurements other than simplified acquisitions, and information required under 4.601. |  | 5 years after submittal to FPDS.
> (10) Investigations, cases pending or in litigation (including protests), or similar matters. |  | Until final clearance or settlement, or, if related to a document identified in (b)(1) - (9), for the retention period specified for the related document, whichever is later.