FAR 4.802—Contract files.
Plain-English Summary
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.
Key Rules
Three core file types
A contract file generally consists of the contracting office file, the contract administration office file, and the paying office file. Each serves a different purpose: award and contract formation, administration and performance oversight, and payment support and documentation.
Separate unless combined appropriately
These files should normally be kept separately, but they may be combined when appropriate, such as when the same office performs multiple functions. The key is that the file structure should match how the work is actually performed and documented.
Maintain files at the right level
Files must be kept at organizational levels that support effective documentation, easy access for principal users, minimal duplicate or working files, protection of classified material, and compliance with agency file-location rules. This is a records-management and security requirement, not just an administrative preference.
Assign responsibility for decentralized files
If files or file segments are spread across offices or outside organizations, someone must be assigned responsibility for maintaining them. Agencies must also establish a central control system, and if needed a locator system, so any contract file can be found promptly.
Protect sensitive procurement information
Contract files containing contractor bid or proposal information or source selection information must be protected from unauthorized disclosure. This ties directly to the procurement integrity protections in FAR 3.104-4 and the definitions in FAR 2.101.
Any medium is allowed if compliant
Agencies may keep contract files in paper, electronic, microfilm, or other media, or in a combination of media, as long as all requirements of the subpart are still met. The storage format is flexible, but the agency remains responsible for completeness, accessibility, and protection.
Responsibilities
Contracting Officer
Ensure the contracting office file documents the basis for the acquisition, the award, assignment of contract administration and payment responsibilities, and later contracting office actions. The contracting officer must also make sure the file is organized and maintained in a way that supports access, accountability, and compliance.
Contract Administration Office
Maintain the contract administration file to document actions that support and reflect contract administration responsibilities, including performance oversight and related administrative actions. This office must keep records sufficient to show what was done and why.
Paying Office
Maintain the paying office file with documentation that supports, substantiates, and reflects contract payments. The office must preserve records needed to verify payment actions and payment-related decisions.
Agency
Establish file-location and maintenance practices that satisfy the requirements for documentation, accessibility, minimal duplication, safeguarding classified information, and compliance with agency regulations. The agency must also decide whether files will be separate or combined and ensure decentralized files are centrally controlled and locatable.
Records/Files Management Personnel
Implement the agency’s filing structure, retention practices, and locator controls so contract files can be found promptly and maintained properly across organizational elements or outside offices. They must also support the use of paper, electronic, microfilm, or mixed media in a compliant way.
All Personnel Handling Contract Files
Protect bid, proposal, and source selection information from unauthorized disclosure and follow applicable security and records-handling rules. Personnel must avoid creating unnecessary duplicate or working files and must preserve the integrity of the official file.
Practical Implications
This section is mainly about making the contract record complete and usable. If the file does not clearly show the basis for award, administration actions, and payment support, the agency may struggle during audits, protests, disputes, or closeout.
A common pitfall is scattering records across offices without a reliable locator system. Decentralized files are allowed, but only if responsibility is assigned and the agency can promptly find the records when needed.
Another frequent issue is over-creating duplicate or unofficial working files. FAR 4.802 pushes agencies to keep files at a level that reduces duplication while still making them accessible to the people who need them.
Sensitive source selection and proposal material must be protected carefully. Mishandling these records can create procurement integrity problems and expose the agency to protest risk or disclosure violations.
The rule is media-neutral, so agencies can use electronic records systems, but only if the system preserves completeness, accessibility, and security. Moving to electronic files does not reduce the need for good indexing, control, and retention discipline.
Official Regulatory Text
(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.