FAR 4—Administrative and Information Matters

Scope of part.

FAR 4.000 explains the scope of FAR Part 4, which governs the administrative side of contract execution and related recordkeeping. It covers policies and procedures for contract administration, contractor-submitted paper documents, distribution of contract information, reporting, retention of records, and contract files. It also states that Part 4 includes policies and procedures implementing certain security prohibitions and exclusions that limit Federal agencies from procuring, obtaining, or using specified products, services, or sources. The section further points readers to additional security prohibitions and exclusions in FAR subparts 25.7 and 40.2. In practice, this section tells contracting personnel and contractors where to look for the rules that control how contracts are documented, tracked, retained, and protected from prohibited sources or items.

Subpart 4.1

Definitions.

FAR 4.001 defines two core identification terms used throughout FAR Part 4: the Procurement Instrument Identifier (PIID) and the supplementary procurement instrument identifier. The PIID is the Government-unique identifier assigned to each solicitation, contract, agreement, or order, and it is the primary way the Government tracks and distinguishes procurement actions across systems and records. The supplementary procurement instrument identifier is a non-unique identifier used together with the PIID to identify a specific action within that instrument, such as an amendment number tied to a solicitation number. In practice, these definitions support consistent numbering, recordkeeping, reporting, and traceability for procurement actions, including delivery orders, task orders, basic ordering agreements, and amended solicitations. The section also points readers to FAR 4.1602 for additional guidance on PIID structure and use. For contracting personnel and contractors, the practical significance is that correct identifier use affects document control, data quality, auditability, and the ability to match related actions across the acquisition lifecycle.

Subpart 4.2

Subpart 4.4

Subpart 4.5

Subpart 4.6

Subpart 4.7

Subpart 4.8

Subpart 4.9