samsearch
    Platform
    01InfluenceShape the requirement before it's on your competitor's radar.
    Signal
    Recompete window opens in 42 days
    Facilities maintenance IDIQ$8.4M
    Forecast
    Agency spend up 18% next FY
    DoD facilitiesQ3 window
    02CaptureFind and qualify the work across every market.
    Federal91%
    Network engineering support — GSA MAS
    GSA541512
    SLED88%
    Custodial services — Fairfax County Public Schools
    K-12561720
    DIBBS79%
    Aircraft hydraulic fitting — DLA Aviation
    DLANSN 5330
    03AnalyzeExtract requirements and build the compliance matrix.
    Compliance matrix
    L.2.1Technical approachVol I
    L.3.4Staffing planVol I
    M.1Past performanceEvaluated
    SOW breakdown
    Requirements extracted38
    Mapped to Section L/M38
    Every extractionCited
    Ask Sammy
    “Do we meet the small business set-aside?”
    04ManageRun the pursuit through to award.
    Pipeline
    QualifyFacilities support · USACE
    CaptureComms upgrade · DLA
    ProposalShipyard dredging · NAVSEA
    PriyaAlex
    This week
    Submit past performance refsThu
    Confirm subK teamingFri
    Upload SF 33Mon
    05RespondDraft and submit your response.
    Drafting · Volume I
    247 words
    RFI response
    CompanyAcme Robotics LLC
    UEIJK4M8…
    Capability narrativeDrafted
    06FinanceGet paid faster on what you win.
    Capital available
    $2.4M against your award
    Facilities maintenance IDIQAwarded
    Partner matched
    LenderFederal Capital Partners
    Draw available$2.4M
    UnderwritingCleared
    The platform
    Influence
    Capture
    Analyze
    Manage
    Respond
    Finance
    One pipeline, six stages, start to award.
    See the whole platform
    Solutions
    By industry
    Tech & softwareSoftware and SaaS companies entering GovCon.Defense contractorsPrimes and subs in the defense industrial base.ConstructionBuilders bidding federal, state, and local work.CybersecuritySecurity vendors pursuing federal mandates.
    By team
    Capture managers & BDPipeline, qualification, and win strategy.Proposal teamsCompliance matrices and proposal drafting.Subcontractors & primesTeaming, subcontracting, and partner fit.
    By company size
    Small businessesSet-aside and small business contractors.EnterpriseLarge contractors running multiple pursuits.ConsultantsAdvisors and capture consultants.
    Browse all industries
    CustomersPricing
    ResourcesNew
    Learn
    AcademyCourses, guides, and playbooks.WebinarsLive sessions and recordings.DocsProduct documentation and setup guides.Implementation planOperational rollout guidance.
    Tools & data
    Free GovCon toolsCalculators, lookups, and more.Gov ExploreContracts, agencies, and NAICS codes.GovCon eventsConferences, training, and set-aside events.
    Latest blogIntroducing the New SamSearch: The Operating System for Government ContractingSamSearch has a new brand, a new site, and a new way of explaining what the platform actually does — the operating system for government contracting, organized around six stages instead of a single search box. Here's what changed and why.Read the post →
    All resources and tools
    Sign inRequest a demo
    Home/FAR Navigator/4/4.1/4.1005/4.1005-2

    FAR Navigator

    • 1Federal Acquisition Regulations System
    • 2Definitions of Words and Terms
    • 3Improper Business Practices and Personal Conflicts of Interest
    • 4Administrative and Information Matters
      • 4.000Scope of part.
      • 4.1Subpart 4.1
        • 4.101Contracting officer’s signature.
        • 4.102Contractor’s signature.
        • 4.103Contract clause.
        • 4.1000Scope.
        • 4.1001Policy.
        • 4.1002Applicability.
        • 4.1003Establishing line items.
        • 4.1004Establishing subline items.
        • 4.1005Data elements for line items and subline items.
          • 4.1005-1Required data elements.
          • 4.1005-2Exceptions.
        • 4.1006Modifications.
        • 4.1007Solicitation alternative line item proposal.
        • 4.1008Solicitation provision.
        • 4.1100Scope.
        • 4.1101Definition.
        • 4.1102Policy.
        • 4.1103Procedures.
        • 4.1104Disaster Response Registry.
        • 4.1105Solicitation provision and contract clauses.
        • 4.1200Scope.
        • 4.1201Policy.
        • 4.1202Solicitation provision and contract clause.
        • 4.1300Scope of subpart.
        • 4.1301Policy.
        • 4.1302Acquisition of approved products and services for personal identity verification.
        • 4.1303Contract clause.
        • 4.1400Scope of subpart.
        • 4.1401Applicability.
        • 4.1402Procedures.
        • 4.1403Contract clause.
        • 4.1500[Reserved]
        • 4.1501[Reserved]
        • 4.1502[Reserved]
        • 4.1600Scope of subpart.
        • 4.1601Policy.
        • 4.1602Identifying the PIID and supplementary PIID.
        • 4.1603Procedures.
        • 4.1700Scope of subpart.
        • 4.1701Definitions.
        • 4.1702Applicability.
        • 4.1703Reporting requirements.
        • 4.1704Contracting officer responsibilities.
        • 4.1705Contract clauses.
        • 4.1800Scope of subpart.
        • 4.1801Definitions.
        • 4.1802Policy.
        • 4.1803Verifying CAGE codes prior to award.
        • 4.1804Solicitation provisions and contract clause.
        • 4.1901Definitions.
        • 4.1902Applicability.
        • 4.1903Contract clause.
      • 4.001Definitions.
      • 4.2Subpart 4.2
      • 4.4Subpart 4.4
      • 4.5Subpart 4.5
      • 4.6Subpart 4.6
      • 4.7Subpart 4.7
      • 4.8Subpart 4.8
      • 4.9Subpart 4.9
    • 5Publicizing Contract Actions
    • 6Competition Requirements
    • 7Acquisition Planning
    • 8Required Sources of Supplies and Services
    • 9Contractor Qualifications
    • 10Market Research
    • 11Describing Agency Needs
    • 12Acquisition of Commercial Products and Commercial Services
    • 13Simplified Acquisition Procedures
    • 14Sealed Bidding
    • 15Contracting by Negotiation
    • 16Types of Contracts
    • 17Special Contracting Methods
    • 18Emergency Acquisitions
    • 19Small Business Programs
    • 22Application of Labor Laws to Government Acquisitions
    • 23Environment, Energy and Water Efficiency, Renewable Energy Technologies, Occupational Safety, and Drug-Free Workplace
    • 24Protection of Privacy and Freedom of Information
    • 25Foreign Acquisition
    • 26Other Socioeconomic Programs
    • 27Patents, Data, and Copyrights
    • 28Bonds and Insurance
    • 29Taxes
    • 30Cost Accounting Standards Administration
    • 31Contract Cost Principles and Procedures
    • 32Contract Financing
    • 33Protests, Disputes, and Appeals
    • 34Major System Acquisition
    • 35Research and Development Contracting
    • 36Construction and Architect-Engineer Contracts
    • 37Service Contracting
    • 38Federal Supply Schedule Contracting
    • 39Acquisition of Information Technology
    • 40Reserved
    • 41Acquisition of Utility Services
    • 42Contract Administration and Audit Services
    • 43Contract Modifications
    • 44Subcontracting Policies and Procedures
    • 45Government Property
    • 46Quality Assurance
    • 47Transportation
    • 48Value Engineering
    • 49Termination of Contracts
    • 50Extraordinary Contractual Actions and the Safety Act
    • 51Use of Government Sources by Contractors
    • 52Solicitation Provisions and Contract Clauses
    • 53Forms
    Up to 4.1005
    subsectionUpdated April 16, 2026

    FAR 4.1005-2—Exceptions.

    Plain-English Summary

    FAR 4.1005-2 explains the main exceptions to the normal requirement to populate certain contract line item data elements in the procurement instrument. It covers three major areas: indefinite-delivery contracts, item description and product or service codes (PSC), and single unit price or single total price requirements. In practice, this section recognizes that some information is not known at the time of base award and can only be finalized when an order is issued, especially under IDIQ and requirements contracts. It also allows a more flexible line-item structure when detailed identification is captured in deliverable subline items, and it permits pricing structures that do not fit a simple single-price model for certain contract types and service arrangements. The purpose is to keep contract writing accurate and workable without forcing contracting officers to enter placeholder data that would be misleading or impossible to know at award. For contractors and contracting officers, the practical significance is that these exceptions affect how the contract is built, how orders are issued, and how pricing and descriptions are documented for auditability and downstream administration.

    Key Rules

    Order-level data for IDCs

    For indefinite-delivery contracts, certain data elements are not known at the time of the base contract award and must instead be provided when each order is issued. These include accounting classification, delivery date and destination, or period and place of performance.

    IDIQ and requirements quantity exception

    IDIQ and requirements contracts may omit the quantity at the line-item level for the base award if the total contract minimum and maximum, or the estimate for requirements contracts, is stated. This allows the contract to be awarded before exact order quantities are known.

    Multiple-award IDIQ pricing exception

    Multiple-award IDIQ contracts awarded under the cited simplified acquisition or source selection procedures may omit price or cost at the line-item or subline-item level for the contract award, as long as the total contract minimum and maximum is stated. The contract still must comply with the underlying IDIQ structure requirements.

    Narrative description allowed

    Item description and PSC are not required in the line item when associated deliverable subline items contain the actual detailed identification. In that case, the line item should use a general narrative description rather than duplicating the detail.

    Flexible pricing structures

    A single unit price or single total price is not required when priced deliverable subline items exist, when the line item or subline item is not separately priced, or when the acquisition uses cost-reimbursement, time-and-materials, or labor-hour pricing. The rule also allows firm prices for elements of the total price when the actual number of elements is unknown until performance.

    Estimated or firm total amounts

    For service contracts where the number of priced elements is not known in advance, the contracting officer may structure the instrument to show a firm or estimated total amount for each line item. This supports practical administration when the contract is based on labor hours or similar variable quantities.

    Responsibilities

    Contracting Officer

    Structure the contract or order so that omitted data elements are only omitted when this section allows it. The contracting officer must ensure required information is supplied at the order level for indefinite-delivery contracts, state the minimum and maximum or estimate where required, use general narrative descriptions when detailed data is carried in subline items, and choose a pricing structure that matches the contract type and the actual pricing basis.

    Contractor

    Provide accurate pricing, quantity, and descriptive information in the format required by the contract or order. The contractor must understand that some data may appear at the order level rather than the base contract level and should not assume omitted line-item data means the requirement is absent.

    Agency/Contract Writing System Users

    Enter contract data in a way that reflects the permitted exceptions and preserves traceability between line items, subline items, and orders. They must avoid forcing unnecessary fields into the base award when the regulation permits later completion at the order stage.

    Practical Implications

    1

    This section is especially important for IDIQ and requirements contracts because it prevents the base award from being cluttered with unknown quantities, destinations, or performance periods that will only be known later.

    2

    A common pitfall is omitting required minimums, maximums, or estimates when using the quantity exception; the exception does not eliminate those core contract structure requirements.

    3

    Another frequent mistake is treating a narrative line-item description as sufficient without ensuring the associated subline items contain the actual detailed identification needed for administration and reporting.

    4

    Pricing must match the contract type: trying to force a single unit price into a cost-reimbursement or labor-hour arrangement can create inaccurate records and downstream invoice or audit problems.

    5

    Contracting officers should make sure the contract writing system and order documents clearly show where the missing data will be supplied, so the award remains compliant and easy to administer.

    Official Regulatory Text

    (a) Indefinite-delivery contracts - (1) General . The following required data elements are not known at time of issuance of an indefinite-delivery contract, but shall be provided in each order at the time of issuance: accounting classification, delivery date and destination, or period and place of performance. (2) Indefinite-delivery indefinite-quantity (IDIQ) and requirements contracts . (i) IDIQ and requirements contracts may omit the quantity at the line item level for the base award provided that the total contract minimum and maximum, or the estimate, respectively, is stated. (ii) Multiple-award IDIQ contracts awarded using the procedures at 13.106-1 (a)(2)(iv)(A) or 15.304 (c)(1)(ii)(A) may omit price or cost at the line item or subline item level for the contract award, provided that the total contract minimum and maximum is stated (see 16.504 (a)(1)). (b) Item description and PSC . These data elements are not required in the line item if there are associated deliverable subline items that include the actual detailed identification. When this exception applies, use a general narrative description for the line item. (c) Single unit price or single total price . The requirement for a single unit price or single total price at the line item level does not apply if any of the following conditions are present: (1) There are associated deliverable subline items that are priced. (2) The line item or subline item is not separately priced. (3) The supplies or services are being acquired on a cost-reimbursement, time-and-materials, or labor-hour basis. (4) The procurement instrument is for services and firm prices have been established for elements of the total price, but the actual number of the elements is not known until performance ( e.g. , a labor-hour contract for maintenance/repair). The contracting officer may structure these procurement instruments to reflect a firm or estimated total amount for each line item.

    Back to 4.1005FAR Navigator
    samsearch

    The Complete AI Platform for Government Contracting

    Platform
    • Product
    • Pricing
    • ROI calculator
    • Integrations
    • Changelog
    Solutions
    • Solutions
    • Customers
    • Comparisons
    • Market watch
    Resources
    • Blog
    • Free GovCon tools
    • Glossary
    • Docs
    Company
    • API & partnerships
    • Careers
    • Support
    • Compliance
    • Trust centre
    • Contact
    Recognised & verified
    SOC 2 Type II Compliant, SamSearchAWS Partner - Advanced, SamSearch on AWS MarketplaceGartner Peer Insights Customer First, SamSearch
    Ask AI about samsearch
    Ask ChatGPTAsk ClaudeAsk Perplexity
    Follow

    © 2026 samsearch. All rights reserved.

    Terms of usePrivacy policy