FAR 4.1—Subpart 4.1

Contracting officer’s signature.

FAR 4.101 sets the basic signature rule for federal contracts: only a contracting officer may sign a contract on behalf of the United States, and the contracting officer’s name and official title must be typed, stamped, or printed on the contract. It also describes the normal order of execution, which is that the contractor signs first and the contracting officer signs afterward. Finally, it places a duty on the contracting officer to verify that the person or persons signing for the contractor actually have authority to bind the contractor, with the detailed authority requirements found in FAR 4.102. In practice, this section protects the Government from unauthorized commitments, helps ensure the contract is legally enforceable, and creates a clear record of who bound each side. It is a simple provision, but it is foundational to contract validity, signature authority, and file documentation.

Contractor’s signature.

FAR 4.102 explains how a federal contract must be signed depending on who the contractor is: an individual, an individual doing business as a firm, a partnership, a corporation, a joint venture, or an agent signing on behalf of a principal. Its purpose is to make sure the Government contracts with the correct legal entity and that the person signing has authority to bind that entity. In practice, this section is about signature form and signature authority, not just a clerical requirement; a wrong signature block or missing authority evidence can create enforceability problems, delay award, or require corrective action. The rule also tells contracting officers what they must verify before signing for the Government, including partner lists, corporate authority, and joint venture authorization. For contractors, it means the signature line must match the legal structure of the offeror or contractor, and the signer must be properly authorized. For contracting officers, it is a due diligence requirement to confirm that the Government is dealing with the right party and that the contract will be binding on that party.

Contract clause.

FAR 4.103 is a narrow but important contract-clause instruction that tells the contracting officer when to include the clause at 52.204-1, Approval of Contract, in solicitations and contracts. The section does not itself create a universal requirement to use the clause; instead, it makes inclusion dependent on agency procedures. In practice, this means the need for the clause is driven by internal agency policy or approval workflows, not by a government-wide FAR mandate. The section matters because it ties the solicitation and award package to any agency-specific approval controls that must be satisfied before a contract is finalized or becomes effective. For contractors, it signals that some agencies may require an additional approval-related clause in the contract documents, which can affect timing, internal review, and award processing. For contracting officers, it is a reminder to check agency procedures before issuing the solicitation or award and to ensure the correct clause is inserted when required.

Scope.

FAR 4.1000 is a scope provision that tells readers what this subpart is about and when its requirements apply. It covers the policies and procedures for assigning line items and subline items, including their identifiers, which are the basic building blocks used to describe, track, and administer contract requirements, deliveries, and billing. The section also includes a transition rule: agencies were given until October 1, 2019, to implement the requirements in FAR 4.1002 through 4.1008 so their information systems could be updated. In practical terms, this subpart matters because accurate line-item structure affects solicitation preparation, award documentation, contract administration, invoicing, property tracking, and reporting. It establishes the framework for consistent item identification across federal procurement actions and signals that the detailed rules in the later sections are mandatory, but subject to the stated implementation timeline for agencies.

Policy.

FAR 4.1001 states the basic policy for structuring procurement instruments so procurement data is accurate, traceable, and usable. It requires supplies and services to be identified as separately identified line items, and when needed, subline items. The section explains what line items are for: defining deliverables and organizing information about deliverables, including characteristics such as pricing, delivery, and funding information. It also explains what subline items are for: subdividing a line item into unique subsets to make administration easier and to distinguish characteristics like color, size, delivery date, destination, or place of performance. A key practical point is that when a line item has deliverable subline items, the parent line item becomes informational rather than itself a deliverable. In practice, this policy drives how contracts, orders, and other procurement instruments are written, tracked, billed, delivered, and administered.

Applicability.

FAR 4.1002 explains which procurement instruments are covered by the policies in this subpart, and it makes clear that coverage extends not only to the original instrument but also to amendments, modifications, and change orders. The section specifically applies to solicitations; contracts; agreements that include pre-priced supplies or services; and task and delivery orders. It also expressly identifies several contract types within the broader term “contracts,” including Governmentwide acquisition contracts (GWACs), multi-agency contracts (MACs), Federal Supply Schedule (FSS) contracts, indefinite-delivery contracts, and purchase orders. In practice, this means the subpart’s requirements are not limited to traditional stand-alone contracts, but reach across many common acquisition vehicles and ordering actions. The purpose is to ensure consistent application of the subpart’s policies wherever procurement actions are used, so agencies and contractors do not treat certain instruments as outside the rule simply because of their form. For contracting professionals, the key takeaway is to check whether the action is one of the listed instruments or a later change to one of them before deciding whether the subpart applies.

Establishing line items.

FAR 4.1003 explains when contracting officers must establish separate contract line items for deliverables and what characteristics make a deliverable suitable for its own line item. It covers five core tests: whether the deliverable is separately identifiable, whether it has a single unit price or total price, whether it can be tied to a single accounting classification citation, whether it has a separate delivery schedule, destination, period of performance, or place of performance, and whether it uses a single contract pricing type. The section also addresses special treatment for services, supplies, and first article requirements, including when a first article must be a separate line item and when a lot may be treated as one line item. In practice, this rule is about structuring the contract so each deliverable can be tracked, priced, funded, delivered, and administered cleanly. Proper line-item structure supports payment, property accountability, funding control, inspection and acceptance, schedule management, and reporting. The exception in 4.1005-2 means the rule is not absolute, so users must also check the related exception provisions before finalizing the contract structure.

Establishing subline items.

FAR 4.1004 explains when and how contracting activities may use subline items within a contract line item. It covers the difference between deliverable subline items and informational subline items, the purposes for which subline items may be used, and the structural rules that apply when a line item contains subline items. The section also ties subline items to performance tracking, deliverables, payment, and contract funds accounting, showing that they are not just a formatting tool but a management and administration tool. In practice, this means contracting officers must decide whether separate identification is needed at the line-item level or whether subline items are a better fit, while ensuring the contract remains internally consistent. The rule also limits what can be placed under a line item, requires all subline items under a line item to share the same contract type as the parent line item, and distinguishes between deliverable subline items that follow the characteristics in 4.1003 and informational subline items that do not. For contractors, this section matters because it affects how items are priced, tracked, shipped, invoiced, and administered, and because improper structuring can create confusion in payment, accounting, and performance reporting.

Data elements for line items and subline items.

Modifications.

FAR 4.1006 addresses how to identify and reference changes made through contract or procurement instrument modifications. It covers two related topics: when a modification adds a new item, such as an increased quantity, and when a modification affects existing line items. Its purpose is to keep the procurement record clear, traceable, and consistent so that every change can be tied to the correct line item in the contract file, invoicing system, and property/accounting records. In practice, this section helps prevent confusion over what was added versus what was changed, which is important for administration, payment, auditability, and later disputes. It also supports accurate line-item management across the life of the instrument by requiring a new line item number for newly added items and a direct reference to existing line items when those items are being modified.

Solicitation alternative line item proposal.

FAR 4.1007 addresses how solicitations should be written when the government wants to preserve flexibility for offerors to propose alternative line items. The section points readers to the related procedures in FAR 4.1008 and the commercial-item solicitation provision at FAR 52.212-1(e), showing that this is part of a broader line-item and pricing structure used in federal acquisitions. Its practical focus is on situations where the government uses units of measure such as kit, set, or lot, but the contractor may not be able to assemble and deliver everything in one shipment. In those cases, the solicitation should be structured so offerors can propose alternative line items that better reflect how the work or supplies will actually be delivered and priced. The purpose is to improve competition, reduce pricing confusion, and avoid forcing offerors into unrealistic line-item structures that could distort offers or create performance problems after award. In practice, this section helps contracting officers draft solicitations that match the realities of supply, packaging, and delivery while still supporting clear evaluation and administration.

Solicitation provision.

FAR 4.1008 is a very short but mandatory solicitation rule: it tells contracting officers to insert the provision at 52.204-22, Alternative Line Item Proposal, in all solicitations. In practice, this section is about ensuring every solicitation includes the standard government-wide provision that allows offerors to propose alternative line item structures when the solicitation permits it. The rule is part of the broader FAR framework for line item identification and proposal preparation, and it helps keep offers organized, comparable, and administratively manageable. Although the text is brief, its effect is important because it standardizes solicitation language and alerts offerors to the possibility of submitting alternative line item proposals where allowed. For contractors, it signals that the solicitation may permit a different line-item arrangement than the one initially requested, but only within the terms of the provision and the solicitation. For contracting officers, it is a mandatory inclusion requirement, not a discretionary one, so omission can create solicitation defects or evaluation issues.

Scope.

FAR 4.1100 is the scope statement for the subpart on contractor registration in the System for Award Management (SAM). It explains that the subpart’s policies and procedures are about requiring contractors to register in SAM, and it identifies the two core purposes of that requirement: increasing the Government’s visibility into vendor sources, including where those vendors are located geographically, for specific supplies and services, and creating a common Government-wide source of vendor data. In practical terms, this section tells contracting personnel and contractors why SAM registration matters and what the registration requirement is intended to accomplish across federal procurement. It does not itself set out the detailed registration steps or exceptions, but it frames the policy basis for the later rules in the subpart. For contractors, it signals that SAM registration is not just administrative paperwork; it is tied to eligibility, market visibility, and the Government’s ability to identify and manage vendors consistently. For agencies and contracting officers, it supports using SAM as the standard repository for vendor information and source identification.

Definition.

FAR 4.1101 is a definitions section for Subpart 4.11, and it does one specific but important job: it tells readers what the term “agreement” means when the subpart uses it. In this subpart, “agreement” is not a generic contract term; it specifically includes a basic agreement, a basic ordering agreement (BOA), or a blanket purchase agreement (BPA). That definition matters because the rest of the subpart’s requirements apply to these instruments, and users need to know exactly which arrangements are covered when the regulation refers to an “agreement.” In practice, this prevents confusion between these pre-negotiated instruments and other contract vehicles, and it helps contracting personnel apply the subpart consistently when managing, documenting, or referencing these arrangements. The section is short, but it is foundational because it sets the scope for how the subpart should be read and implemented.

Policy.

FAR 4.1102 sets the core policy for when offerors, quoters, and contractors must be registered in the System for Award Management (SAM) and how that registration information must be used in federal contracting. It explains the general rule that SAM registration is required at the time an offer or quotation is submitted so the offeror can satisfy annual representations and certifications, then lists specific exceptions for certain low-dollar, urgent, classified, overseas, emergency, and foreign-vendor situations. The section also addresses what contracting officers must do when an award is made under one of the exceptions, including when they should try to require SAM registration later. In addition, it governs how contracting officers must pull and use the contractor’s legal business name, DBA name, and physical address from SAM without alteration, which is important for accurate award documentation and data consistency. Finally, it covers SAM maintenance issues after award, including name changes, novation and change-of-name requirements, limits on changing EFT or payment information to reflect an assignee, and the need for assignees to register separately in SAM. In practice, this section is about identity control, payment integrity, and ensuring the government is dealing with the correct legal entity throughout the acquisition and contract administration lifecycle.

Procedures.

FAR 4.1103 explains the day-to-day procedures for checking and using System for Award Management (SAM) registration information in federal acquisitions. It covers when the contracting officer must verify that an offeror or quoter is registered in SAM, how that verification should be done using the unique entity identifier, when verification is not required before placing an order or call if the contract already includes the SAM maintenance clause, and the special exception for purchases using the Governmentwide commercial purchase card. It also addresses the timing requirement for contractors awarded under the exception in FAR 4.1102(a)(5), which requires SAM registration within 30 days after award or at least three days before the first invoice, whichever comes first. In addition, it requires agencies to protect SAM information from improper disclosure and directs contracting officers to provide the unique entity identifier, or the Electronic Funds Transfer indicator when applicable, to the payment office on contractual documents. In practice, this section is about ensuring the Government can validate entities, pay them correctly, and maintain the integrity and confidentiality of registration data while avoiding award or payment delays caused by missing or outdated SAM information.

Disaster Response Registry.

FAR 4.1104 requires contracting officers to consult the Disaster Response Registry in SAM.gov before awarding contracts for certain disaster-related work. The section applies when the Government is contracting for debris removal, distribution of supplies, reconstruction, and other disaster or emergency relief activities performed inside the United States and its outlying areas. Its purpose is to help agencies identify local or regional sources that have registered as available for disaster response work, which can support faster, more effective, and potentially more competitive emergency contracting. In practice, this rule is a mandatory market research and source-identification step for covered disaster response acquisitions, not a separate set-aside or award preference. The cross-reference to FAR 26.205 signals that this registry consultation is part of the broader disaster response contracting framework and should be considered alongside other emergency procurement requirements.

Solicitation provision and contract clauses.

FAR 4.1105 tells contracting personnel when to include the System for Award Management (SAM) solicitation provision and the related SAM maintenance contract clause. It covers two related topics: the provision at 52.204-7, System for Award Management, including Alternate I when a solicitation is expected to be awarded under the special procedures in 4.1102(a)(5), and the clause at 52.204-13, System for Award Management Maintenance. In practice, this section ensures offerors are properly registered in SAM before award and remain current after award, which supports responsibility determinations, accurate contractor identification, and reliable payment and reporting data. The rule is a drafting instruction for solicitations and resulting contracts, so its main significance is procedural: if the solicitation includes the SAM provision, the contract must also include the SAM maintenance clause. Contracting officers must apply the correct version of the provision based on the acquisition method and must not omit these clauses when they are required.

Scope.

FAR 4.1200 explains the purpose and scope of the rules governing contractor representations and certifications in the System for Award Management (SAM). It states that this subpart sets the policies and procedures for requiring contractors to submit and maintain their representations and certifications in SAM rather than repeatedly providing the same information to individual contracting offices. The section also establishes SAM as the Government-wide common source for this information, so procurement offices across agencies can rely on a single, current record. Finally, it explains that the contractor’s representations and certifications are incorporated by reference into the awarded contract, which gives them contractual effect without restating them in full. In practice, this means contractors must keep SAM information current and contracting officers must rely on SAM as the authoritative source for these data when making awards and administering contracts.

Policy.

FAR 4.1201 establishes the policy for using the System for Award Management (SAM) to collect, maintain, and incorporate offeror and contractor representations and certifications. It covers four main topics: the requirement for offerors and quoters to complete electronic annual representations and certifications in SAM as part of registration; the duty of all registrants to review and update those representations and certifications at least annually so they remain current, accurate, and complete; special update rules for contractors that change small-business status before or after award under FAR 52.219-28; and the contracting officer’s documentation and incorporation duties when SAM data is used. In practice, this section is about making sure the Government relies on a single, current electronic source for responsibility and eligibility information, while preserving a clear contract file record of what was verified and when. It also ensures that changes disclosed by an offeror are captured in the file and that the representations and certifications become part of the contract by reference. For contractors, the rule creates an ongoing compliance obligation, not just a pre-award checkbox. For contracting officers, it reduces duplicate paperwork but requires careful file documentation and attention to any updates or exceptions disclosed during the acquisition process.

Solicitation provision and contract clause.

FAR 4.1202 tells contracting officers when to include the Annual Representations and Certifications provision at 52.204-8 and when to include the clause at 52.204-19, Incorporation by Reference of Representations and Certifications. It also explains an important exception for solicitations for commercial products or commercial services under FAR part 12, and it directs contracting officers to complete the applicable checkboxes in 52.204-8(c)(2). The section further requires use of 52.204-8 with Alternate I in certain future multiple-award solicitations issued after October 1, 2028, when more than one NAICS code will apply. A major practical feature of this rule is that when 52.204-7, System for Award Management, is included, many separate representation and certification provisions must not be inserted again, because their substance is already covered through the consolidated representation process. In practice, this section is about avoiding duplication, ensuring the right representations are collected at the right time, and making sure solicitations and contracts contain the correct FAR provisions for responsibility, eligibility, socioeconomic status, trade compliance, labor, environmental, and intellectual property-related certifications. For contractors, it signals which representations they will be expected to make in SAM or in the solicitation; for contracting officers, it is a checklist rule that affects solicitation drafting and contract formation.

Scope of subpart.

FAR 4.1300 is a scope provision that tells readers what this subpart is about: the policy and procedures for Personal Identity Verification (PIV) in federal contracting. It ties the subpart directly to two external authorities—FIPS PUB 201, which sets the government-wide standard for PIV of federal employees and contractors, and OMB Memorandum M-05-24, which implements HSPD-12 and establishes the common identification standard for federal employees and contractors. In practical terms, this section signals that the subpart is not creating a standalone identity program; instead, it is the FAR’s procurement-side framework for applying the government’s PIV requirements. Contractors and contracting officers should read this as the gateway to rules governing identity proofing, credential issuance, and access-related procedures for contractor personnel who need to work in federal facilities or systems. The section matters because it anchors contractor onboarding, badge issuance, and access control requirements in government-wide policy, helping agencies protect facilities, information systems, and personnel while maintaining a consistent identification standard across the executive branch.

Policy.

FAR 4.1301 establishes the governmentwide policy for personal identity verification (PIV) when contractor or subcontractor personnel need routine physical access to a federally controlled facility or routine access to a federally controlled information system. It requires agencies to apply FIPS PUB 201 and the related OMB implementation guidance, and to reflect those requirements in solicitations and contracts so offerors know the identity-verification rules before performance begins. The section also requires agencies to designate an official responsible for verifying contractor employee identity, which supports consistent issuance and control of PIV credentials. In addition, it addresses the return and accountability of government-provided identification products, such as PIV cards or similar badges, when they are no longer needed, when the employee leaves, or when the contract ends. Practically, this section is about controlling physical and logical access, preventing misuse of government credentials, and ensuring agencies and contractors have clear procedures for issuance, tracking, return, and enforcement, including the possibility of delayed final payment if the contractor does not comply.

Acquisition of approved products and services for personal identity verification.

FAR 4.1302 tells agencies how to acquire personal identity verification (PIV) products and services that comply with FIPS PUB 201, the federal standard for identity credentials and related components used for secure access. It covers the basic requirement to buy only approved PIV products and services, the preferred acquisition path through GSA Federal Supply Schedule 70, Special Item Number (SIN) 132-62 for HSPD-12 Product and Service Components, and the alternative process when agencies do not use that schedule route. It also addresses what agencies must do to ensure compliance when buying outside the GSA schedule, including certifying that products and services meet applicable federal standards, ensuring interoperability and lifecycle conformance, and maintaining a written plan for ongoing conformance. In practice, this section is about preventing agencies from buying incompatible or noncompliant identity verification solutions that could undermine security, interoperability, or long-term support. It matters to contracting officers, program offices, and acquisition teams because PIV purchases often involve hardware, software, services, and integration support that must work together across the federal environment. The section also points users to the government’s identity management resources for additional guidance.

Contract clause.

FAR 4.1303 tells contracting officers when to include the Personal Identity Verification (PIV) clause at 52.204-9 in solicitations and contracts. It covers two trigger conditions: routine physical access to a Federally-controlled facility and routine access to a Federally-controlled information system. The section also draws an important line by stating that the clause must not be used when contractor personnel need only intermittent access to Federally-controlled facilities. In practice, this rule helps agencies ensure contractor personnel are properly identified and credentialed before they enter sensitive federal spaces or systems, while avoiding unnecessary PIV requirements for occasional visitors or short-term access. It matters because the clause affects solicitation terms, contractor onboarding, badge processing, and access control planning, and it can delay performance if not identified early.

Scope of subpart.

FAR 4.1400 is the scope statement for Subpart 4.14, which implements the Federal Funding Accountability and Transparency Act of 2006 (FFATA), as amended by the Government Funding Transparency Act of 2008. This section explains that the subpart is about two main reporting topics: subcontract award data and the total compensation of the five most highly compensated executives of the contractor and subcontractor. It also points readers to the public website where first-tier subcontract award data can be viewed, which is USAspending.gov. In practical terms, this scope provision tells contractors, subcontractors, and contracting personnel why the reporting requirements exist and what kinds of information the government expects to be reported under the subpart. It matters because these transparency requirements support public accountability for federal spending and create compliance obligations that can affect award administration, subcontract management, and executive compensation reporting. Although this section does not itself prescribe the detailed reporting mechanics, it frames the legal basis and subject matter for the rest of Subpart 4.14.

Applicability.

FAR 4.1401 explains when the subpart on reporting subcontract information applies and how far that reporting reaches. It covers three main topics: the dollar threshold for applicability, the protection of classified information, and the limit on subcontract reporting to first-tier subcontractors only. In practice, this section tells contracting officers and contractors that the reporting requirement is not universal; it applies only to contracts valued at $40,000 or more. It also makes clear that the rule cannot be used to force disclosure of classified information, which preserves national security protections. Finally, it narrows subcontract reporting so that contractors do not have to report beyond the first tier, reducing administrative burden and defining the scope of required data collection.

Procedures.

FAR 4.1402 explains how agencies and contracting officers are to administer the executive compensation and first-tier subcontract award reporting requirements in FAR 52.204-10. It covers agency review of contractor submissions, how agencies should handle inconsistencies, the role of FPDS data in pre-populating subcontract reports, what happens when FPDS data is wrong, the consequences of contractor noncompliance, and the small-business-style reporting exception for entities with gross income under $300,000 in the prior tax year. In practice, this section is about making sure the government can collect accurate transparency data on executive compensation and subcontract awards while minimizing unnecessary burden and using existing procurement data to streamline reporting. It also makes clear that agencies are not expected to verify information they would not normally have supporting documentation for, such as compensation data, but they must still check for consistency with contract records and require corrections when discrepancies are found. For contractors, the section matters because reporting errors, missed submissions, or use of a generic entity identifier can create compliance problems and delay or complicate subcontract reporting. For contracting officers, it creates an active oversight and enforcement role, including FPDS data correction, contractual remedies, and performance-record consequences when reporting obligations are not met.

Contract clause.

FAR 4.1403 tells contracting officers when they must include the clause at 52.204-10, Reporting Executive Compensation and First-Tier Subcontract Awards, in solicitations and contracts. The section covers two main topics: the general rule that the clause must be inserted in all solicitations and contracts valued at $40,000 or more, and the exception for awards that are not required to be reported in the Federal Procurement Data System (FPDS) under subpart 4.6. In practice, this means the clause is tied to both dollar threshold and FPDS reporting applicability, so the contracting officer must check not just the contract value but also whether the action is reportable in FPDS. The purpose is to ensure the Government can collect and publish executive compensation and first-tier subcontract award information for covered procurements. For contractors, this clause creates reporting obligations and compliance risk; for contracting officers, it is a mandatory solicitation/contract clause decision that must be made correctly at award time.

[Reserved]

[Reserved]

[Reserved]

Scope of subpart.

FAR 4.1600 is the scope statement for Subpart 4.16, and it tells readers what the subpart is about: the policies and procedures for assigning unique Procurement Instrument Identifiers (PIIDs) to each solicitation, contract, agreement, order, and related procurement instrument. In practice, this means the government must use a consistent, unique identifier for every covered procurement action so it can be tracked, reported, managed, and retrieved across acquisition systems and records. The section is important because PIIDs are the backbone of procurement data integrity: they support auditability, lifecycle tracking, cross-system matching, and accurate reporting to oversight and data repositories. Although this section is brief, it establishes the scope of the rules that follow in the subpart and signals that the requirements apply broadly to procurement instruments, not just contracts. For contracting personnel and contractors, the practical significance is that the identifier assigned to an action is not a clerical detail; it is a required control element that affects documentation, administration, and data consistency throughout the procurement lifecycle.

Policy.

FAR 4.1601 establishes the core policy for Procurement Instrument Identifiers (PIIDs), which are the unique numbers agencies use to identify solicitations and contract actions across the federal procurement system. It covers four main topics: the requirement to make each PIID unique Governmentwide for at least 20 years, the requirement to use the PIID in all solicitation and contract actions and in designated reporting/support systems such as FPDS and SAM, the transition from the older 2013 PIID format to the 2017 format using the agency identification code (AAC) in the first six positions, and the limited circumstances in which a PIID may be changed after assignment. In practice, this section is about data integrity, traceability, and consistency across procurement records, award systems, and reporting tools. It matters because a PIID is the primary identifier that ties together the solicitation, award, modifications, and downstream reporting, so errors can create compliance problems, reporting mismatches, and administrative confusion. The rule also protects historical records by requiring uniqueness for a long retention period and by limiting when a contracting officer may reassign a PIID. For contractors, the practical effect is that the identifier on the solicitation and award documents is not just a label; it is a controlled government record reference that must be used consistently throughout the life of the action.

Identifying the PIID and supplementary PIID.

FAR 4.1602 tells agencies how to identify the Procurement Instrument Identification Number (PIID) and any supplementary PIID on solicitation, award, and related procurement documents. It covers solicitations and solicitation amendments, contracts and purchase orders, delivery and task orders, blanket purchase agreements (BPAs), basic agreements and basic ordering agreements (BOAs), orders placed against BOAs and BPAs, modifications to those actions, and the placement of PIIDs on paper or electronic forms. It also addresses what to do when a form does not have a dedicated field for the PIID and how to handle additional agency-specific identification information. The purpose is to ensure every procurement action can be uniquely traced, linked to related instruments, and managed consistently across systems and documents. In practice, this section is critical for contract administration, reporting, auditability, and avoiding confusion when multiple related instruments exist under the same acquisition. It also helps agencies maintain clean records in electronic procurement systems and ensures that modifications and amendments are tied to the correct base action.

Procedures.

FAR 4.1603 explains how to build and use procurement instrument identifiers (PIIDs) and supplementary PIIDs so federal contracts, orders, solicitations, agreements, and related actions can be uniquely tracked across government systems. It covers the required PIID structure, including the 13- to 17-character format, the prohibition on special characters, the use of the issuing office’s Activity Address Code (AAC) in positions 1 through 6, the fiscal year in positions 7 and 8, the instrument-type code in position 9, and the agency-assigned serial number in positions 10 through 17. It also covers the separate supplementary PIID used for amendments to solicitations and modifications to contracts, orders, and agreements, including the numbering rules for solicitation amendments and for modifications, the office identifier in the first position of the supplementary PIID, and the sequencing rules for issuing those numbers. In practice, this section exists to ensure every procurement action is uniquely identified, consistently reported, and traceable in procurement databases and contract files. For contractors and contracting offices, the rule matters because incorrect PIIDs or modification numbers can cause reporting errors, award-document mismatches, payment or administration confusion, and data integrity problems in systems such as FPDS and agency contract writing systems.

Scope of subpart.

FAR 4.1700 explains the scope and purpose of Subpart 4.17, which is the FAR implementation of section 743(a) of Division C of the Consolidated Appropriations Act, 2010. This section identifies the legal authority behind the subpart, states that the rule requires agencies to report annually to the Office of Management and Budget (OMB) on activities performed by service contractors, and clarifies which agencies are covered. Specifically, it applies to executive agencies other than the Department of Defense (DoD) that are subject to the Federal Activities Inventory Reform Act (FAIR Act). It also makes clear that the information reported in the inventory will be publicly accessible. In practice, this means agencies must track and report service contractor activity in a way that supports government-wide oversight, transparency, and public visibility, and contractors may be asked to provide information that helps agencies meet these reporting obligations.

Definitions.

FAR 4.1701 provides the definitions used in this subpart, and it focuses on two specific terms: “FAIR Act agencies” and “first-tier subcontract.” These definitions matter because they determine which agencies are covered by the inventory-related requirements tied to the FAIR Act and which subcontract relationships count for reporting, tracking, or compliance purposes under this subpart. In practice, the section draws a line between true first-tier subcontracts—those awarded directly by the prime contractor to obtain supplies or services, including construction, for contract performance—and ordinary supplier arrangements that are part of a contractor’s general supply chain or indirect cost structure. That distinction is important because not every vendor relationship is treated as a subcontract for purposes of this subpart. Contractors and contracting personnel must therefore identify the correct agency coverage and correctly classify downstream purchasing arrangements to avoid overreporting, underreporting, or applying the wrong compliance standard.

Applicability.

FAR 4.1702 explains who must follow the service-contract reporting rules in this subpart and what kinds of contracts are covered. It applies to FAIR Act agencies, except the Department of Defense where separate rules in 4.1705 control, and it reaches solicitations, contracts, and orders for services, including construction, when they meet or exceed the threshold in 4.1703. It also makes clear that the requirements extend not only to prime contractors but also to first-tier subcontractors. In addition, the section points readers to the statutory and OFPP guidance that governs how agencies compile and submit service contract inventories under section 743(a)(3) of Division C of Public Law 111-117. In practice, this section is the gateway to the broader service-contract information collection and reporting framework: it tells agencies and contractors whether the subpart applies before they get into the mechanics of data collection, inventory reporting, and contractor submissions.

Reporting requirements.

FAR 4.1703 explains when service contract reporting is required and how that reporting is handled for both prime contracts and first-tier subcontracts. It covers the reporting thresholds for cost-reimbursement, time-and-materials, labor-hour, and fixed-price service contracts, including special treatment for indefinite-delivery contracts such as IDIQs, Federal Supply Schedule contracts, GWACs, and multi-agency contracts. It also addresses the agency’s role in making sure contractors comply with the reporting clauses at FAR 52.204-14 and 52.204-15, reviewing the reported data for reasonableness, and notifying contractors when corrections are needed. In addition, it requires agencies to compile an annual service contract inventory, submit it to OMB, and publicly post the inventory with a Federal Register notice. The section also clarifies that much of the needed information comes from FPDS, while the remaining data must be supplied by the contractor. In practice, this section is about collecting reliable service-contract data so the Government can track spending, assess reliance on service contractors, and support oversight and workforce planning.

Contracting officer responsibilities.

FAR 4.1704 assigns the contracting officer’s duties for enforcing the service contract reporting clauses. It covers two different contract structures: other than indefinite-delivery contracts, where the contracting officer must ensure the Service Reporting Requirement clause at 52.204-14 is included in solicitations, contracts, and orders as required by 4.1705; and indefinite-delivery contracts, where the awarding contracting officer must ensure 52.204-15, Service Contract Reporting Requirements for Indefinite-Delivery Contracts, is included in the solicitation and contract, while the order-level contracting officer must verify that the clause is actually in the contract at the order stage. The section also addresses what happens when a contractor misses a reporting deadline: the contracting officer must take appropriate contractual remedies and must record the noncompliance in the contractor’s performance information under subpart 42.15. In practice, this section is about making sure the reporting clauses are properly flowed into the right instruments and that failures to report are enforced and documented, so agencies can collect required service contract data and maintain accurate contractor performance records.

Contract clauses.

FAR 4.1705 tells contracting officers which service contract reporting clauses must be included in solicitations and contracts when the reporting thresholds in FAR 4.1703 are met. It covers two different clause prescriptions: the standard clause at 52.204-14 for non-indefinite-delivery service contracts, including construction, and the clause at 52.204-15 for solicitations and indefinite-delivery contracts where one or more orders are expected to meet the reporting threshold. The section also identifies three express exceptions where neither clause is required: actions entirely funded by DoD, contracts awarded with a generic entity identifier, and classified solicitations, contracts, or orders. In practice, this provision ensures the Government can collect service contract reporting data where required, while avoiding duplication or impractical reporting in certain DoD-funded, classified, or generic-identifier situations. For contracting officers, the key task is to determine the contract type, whether the threshold is met or expected to be met, and whether an exception applies before award. For contractors, the practical effect is that reporting obligations may be built into the contract through the required clause, so they must be prepared to comply when the clause is included.

Scope of subpart.

FAR 4.1800 is a scope provision that explains what this subpart is about and how it fits into the broader federal identification framework. It states that the subpart prescribes policies and procedures for identifying commercial and government entities, primarily through the Commercial and Government Entity (CAGE) code system. It also explains the main uses of CAGE codes in federal procurement: exchanging data with other contracting activities, including contract administration and contract payment offices; exchanging data with other systems that need a unique contractor entity identifier; and identifying when offerors are owned or controlled by another entity. Finally, it points readers to the unique entity identifier requirements in FAR 4.605 and the solicitation provisions at 52.204-6 and 52.204-7, making clear that the unique entity identifier is a separate identifier from the CAGE code. In practice, this section matters because it tells contracting personnel and contractors which identifier is being used for which purpose, helps prevent confusion between CAGE codes and the unique entity identifier, and supports accurate data sharing, payment processing, and responsibility determinations across federal systems.

Definitions.

FAR 4.1801 provides the definitions used in this part for identifying ownership and control relationships in contractor representations and disclosures. It specifically defines "highest-level owner" and "immediate owner," and explains what it means for one entity to control another, including examples of control indicators such as ownership, interlocking management, family relationships, shared facilities and equipment, and common use of employees. These definitions matter because they determine how an offeror traces its corporate ownership chain and identifies the correct entities when completing required representations, certifications, and disclosures under this part. In practice, the section helps contracting officials and offerors determine who sits at the top of the ownership structure and which entity directly controls the offeror, reducing ambiguity in reporting and supporting accurate government records and compliance reviews.

Policy.

FAR 4.1802 establishes the policy for collecting and recording Commercial and Government Entity (CAGE) information in federal contracting. It covers when offerors must provide their own CAGE code, when the contracting officer must place that code in the contract and related electronic data transmissions, and when an offeror must also identify the CAGE code and legal name of any parent or controlling entity. The rule applies before award of contract actions above the micro-purchase threshold, but only when the solicitation or procurement also requires SAM registration or a unique entity identifier. In practice, this section helps the Government accurately identify the legal business entity it is awarding to, supports data integrity across procurement systems, and reduces confusion where a company is owned or controlled by another entity. It is especially important for award processing, contract administration, and automated reporting because the CAGE code is used as a key identifier in federal acquisition systems.

Verifying CAGE codes prior to award.

FAR 4.1803 addresses how contracting officers must verify a contractor’s Commercial and Government Entity (CAGE) code before award. It covers two verification paths: first, checking the offeror’s registration in the System for Award Management (SAM), where an active registration indicates the associated CAGE code has already been verified; and second, for entities that are not required to register in SAM, validating the CAGE code through the Defense Logistics Agency’s CAGE code search feature at https://cage.dla.mil. The purpose of the rule is to ensure the government awards only to entities whose identifying code is accurate and validated, which supports proper entity identification, reduces award-processing errors, and helps prevent misidentification or fraud. In practice, this means the contracting officer must not rely on an unverified code or assume a code is correct simply because it appears in an offer. The section is narrow, but operationally important because CAGE code accuracy affects award documentation, payment setup, and downstream contract administration.

Solicitation provisions and contract clause.

FAR 4.1804 tells contracting officers which solicitation provisions and contract clauses must be used when the government is collecting and managing Commercial and Government Entity (CAGE) code information. It ties the CAGE code reporting provision at 52.204-16 to other related provisions and clauses: 52.204-17, Ownership or Control of Offeror; 52.204-18, Commercial and Government Entity Code Maintenance; and 52.204-20, Predecessor of Offeror. In practice, this section ensures the government can identify the legal entity behind an offer, understand ownership/control relationships, and keep CAGE code data current throughout the acquisition and contract performance process. It also links CAGE code requirements to solicitations that already require a Unique Entity Identifier (UEI) or System for Award Management (SAM) registration, so offerors cannot treat CAGE-related data as optional or separate from basic offer eligibility. The section matters because inaccurate or outdated entity information can affect responsibility determinations, award eligibility, payment processing, and the government’s ability to track contractor identity across mergers, reorganizations, and successor entities.

Definitions.

FAR 4.1901 provides the core definitions used in the subpart on safeguarding covered contractor information systems. It defines five key terms: covered contractor information system, Federal contract information, information, information system, and safeguarding. These definitions matter because they determine what systems are subject to the subpart’s cybersecurity and protection requirements, what kinds of data must be protected, and what counts as the protective measures a contractor must use. In practice, the definitions set the scope for contractor compliance obligations, contract clause application, incident response expectations, and the government’s ability to require protection of nonpublic contract-related information. Understanding these terms is essential for both contracting officers and contractors because small differences in wording—such as whether information is public, whether it is merely transactional, or whether a system actually processes Federal contract information—can change whether the subpart applies.

Applicability.

FAR 4.1902 explains when the cybersecurity requirements in this subpart apply. It covers all acquisitions, including acquisitions for commercial products and commercial services, and it specifically notes that the rule applies even to commercial items other than commercially available off-the-shelf (COTS) items when a contractor’s information system may contain Federal contract information (FCI). In practice, this means the government does not limit these protections to noncommercial buys; instead, it looks at whether the contractor will handle or store FCI on its systems. The section exists to make clear that safeguarding FCI is a broad procurement requirement tied to the presence of government information in contractor systems, not to the type of product or service alone. For contracting officers, it is a trigger for deciding whether to include the applicable cybersecurity clauses and requirements. For contractors, it is a warning that even routine commercial work may bring cybersecurity obligations if FCI could reside on their systems.

Contract clause.

FAR 4.1903 tells contracting officers when they must include the cybersecurity clause at 52.204-21, Basic Safeguarding of Covered Contractor Information Systems, in solicitations and contracts. The section is focused on one core topic: protecting Federal contract information when that information may reside in or pass through a contractor’s or subcontractor’s information system. In practice, this means the clause is not optional when the trigger is present; it must be inserted into the solicitation and resulting contract so the contractor is on notice of the basic safeguarding requirements. The rule also reaches subcontractors at any tier, so prime contractors need to understand that the safeguarding obligation can flow down through the supply chain whenever lower-tier entities may handle covered information. This section matters because it connects the government’s information-protection policy to the actual contract terms that make the requirement enforceable.