FAR 4.8—Subpart 4.8

Scope of subpart.

FAR 4.800 is the scope statement for Subpart 4.8, and it tells you what the subpart is about: the requirements for establishing, maintaining, and disposing of contract files. In practice, this means the subpart governs the life cycle of the official contract record from the moment a file is created, through how it is organized and kept current, to how and when it is closed out, archived, or otherwise disposed of. The purpose is to ensure the Government has a complete, reliable, and retrievable record of contract actions for administration, audit, legal review, historical reference, and accountability. Although this section is very short, it is important because it frames all of the detailed file-management rules that follow in Subpart 4.8 and signals that contract files are not optional administrative paperwork; they are required records that must be handled systematically. For contracting officers, contract specialists, and other acquisition personnel, this scope statement means the agency must have procedures for creating and preserving the official file, keeping it accurate during performance, and disposing of it in accordance with applicable records rules.

General.

FAR 4.801 sets the basic government-wide rule for contract file creation and maintenance. It requires each office that performs contracting, contract administration, or paying functions to establish files for all contractual actions, and it explains what those files must accomplish: they must create a complete history of the transaction. The section also identifies the core purposes of that documentation, including supporting informed acquisition decisions, justifying actions taken, enabling reviews and investigations, and preserving essential facts for litigation or congressional inquiries. Finally, it specifies the types of files that must exist, including a file for cancelled solicitations, a file for each contract, and a general contractor file for records that are not tied to a single contract but relate to the contractor overall, such as management systems, past performance, or capabilities. In practice, this section is the foundation for sound file management, audit readiness, and institutional memory across the acquisition lifecycle.

Contract files.

FAR 4.802 explains how agencies must organize, maintain, protect, and retain contract files. It covers the three core file types in a contract file system: the contracting office contract file, the contract administration office contract file, and the paying office contract file. It also addresses when those files may be kept separately or combined, where files must be maintained, how to handle decentralized file systems, how to protect bid/proposal and source selection information, and the acceptable media for retaining files. In practice, this section is about making sure the government can document the acquisition, administration, and payment history of a contract in a way that is accessible, auditable, secure, and consistent with agency rules. For contractors, the main significance is that sensitive proposal and source selection information in government files must be protected from unauthorized disclosure. For contracting personnel, the rule is a records-management requirement that supports accountability, payment integrity, and later review, protest, audit, or litigation needs.

Contents of contract files.

FAR 4.803 explains what records are normally kept in federal contract files, both in the contracting office file and the contract administration office file. It is a records-management rule, but it also has real procurement significance because the file is the official history of the acquisition and the main source for audits, protests, reviews, disputes, closeout, and later contract administration. The section covers presolicitation documents, justifications and approvals, determinations and findings, funding evidence, synopses, source lists, set-aside decisions and market research, government estimates, solicitations and amendments, offers and quotations, responsibility determinations, preaward surveys, source selection records, labor compliance records, price analysis and cost data, audit reports, negotiations, contract type justification, deviations and approvals, award notices, signed contracts and modifications, debriefings, bonds, postaward conferences, notices to proceed and stop work, administration-function changes, waivers and deviations, engineering change proposals, royalty/invention/copyright records, completion and termination documents, cross-references, and other action documents. It also specifically calls for a chronological list of awarding and successor contracting officers, and for EDWOSB/WOSB set-aside or sole-source files to include market research and NAICS-code documentation tied to SBA underrepresentation designations. In the contract administration file, it adds the contract and modifications, administration-supporting documents, security requirements, pricing and audit support, preaward survey information, purchasing system information, subcontract consent, bonds, insurance, payment support, surveillance and quality records, property administration, and termination records. In practice, this section tells agencies what should be in the file so the government can show how and why it acted, and it tells contractors what records may exist and be relied on if a dispute, audit, or performance issue arises.

Closeout of contract files.

Storage, handling, and contract files.

FAR 4.805 tells agencies how to handle, store, convert, and dispose of contract files and related procurement records, and it ties those practices to the National Archives and Records Administration (NARA) General Records Schedule 1.1 for Financial Management and Reporting Records. It covers recordkeeping across all media, including paper, microfilm, and electronic records, and it allows agencies to convert original documents to alternate media if the conversion process preserves the record accurately and securely. The section also addresses when original signed documents may be destroyed, how to treat mixed files that contain both administrative and program records, and when an agency must seek NARA approval for shorter retention periods. Most importantly, it establishes retention periods for specific record types such as contracts and related proposals, contractor payrolls on construction contracts, unsolicited proposals, canceled solicitations, administrative copies, general contractor information, FPDS submissions, and records involved in investigations, protests, litigation, or enforcement actions. In practice, this section is the core FAR rule for contract file retention and records management, helping agencies preserve audit trails, support litigation and oversight, and avoid premature destruction of records that may still have legal, fiscal, or administrative value.