A CLIN is a Contract Line Item Number. It identifies a contract line item used to organize a product or service for pricing, funding, delivery, inspection, acceptance, invoicing and payment. In practice, people often use “CLIN” to mean both the numbered line item and its identifier.
So, what is a CLIN from a program-controls perspective? It is a contractual organizing element that connects acquired scope with commercial and administrative terms. A CLIN may identify a hardware deliverable, a period of engineering services, data, training or another separately managed item. However, it is not automatically a Work Breakdown Structure (WBS) element, control account, work package or Integrated Master Schedule (IMS) activity.
What Is a CLIN Under the FAR?
The Federal Acquisition Regulation definition of a line item describes it as the basic structural element in a procurement instrument. It organizes the required product or service for pricing, delivery, inspection, acceptance, invoicing and payment. The line item number is the numeric or alphanumeric identifier assigned to that element.
FAR Subpart 4.10 requires procurement instruments to identify acquired supplies or services as separate line items and, when needed, subline items. This policy applies to solicitations, contracts, task and delivery orders, modifications and several other procurement instruments.
Under the FAR, a separate line item generally represents a deliverable with these characteristics:
- It is separately identifiable.
- It has a single unit price or total price, subject to stated exceptions.
- It has a single accounting classification citation, subject to limited exceptions.
- It has a distinct delivery schedule, destination, period of performance or place of performance.
- It uses one contract pricing type, such as fixed-price or cost-reimbursement.
These criteria help the Government administer the contract and maintain traceability. However, exceptions apply to indefinite-delivery contracts, not-separately-priced items, cost-reimbursement work and other defined circumstances. Therefore, the specific solicitation or awarded contract always controls.
What Information Does a CLIN Contain?
A CLIN is more than a four-digit label in Section B. Under FAR 4.1005-1, line items generally include distinct data elements that describe what the Government is buying and how it will administer that purchase.
Depending on the acquisition and pricing arrangement, the line item may identify:
- The line item or subline item number
- A description of the product or service
- The Product or Service Code
- The accounting classification citation
- The unit of measure and quantity
- The unit price and total price for fixed-price work
- Estimated cost, fee and total estimated cost plus fee for cost-reimbursement work
- The applicable contract type
- The delivery schedule, destination or period and place of performance
The CLIN description does not replace the Statement of Work (SOW), Performance Work Statement (PWS), specification or Contract Data Requirements List (CDRL). Instead, readers must interpret the line item with the other contract sections. Under the Uniform Contract Format, Section B addresses supplies or services and prices or costs, while Sections C through F address requirements, packaging, acceptance and delivery or performance. FAR 15.204-2 explains this structure.
How DoD CLIN Numbering Works
Department of Defense contracts follow additional rules in DFARS Subpart 204.71. For DoD contracts, Procurement Guidance Information specifies four numeric positions for a CLIN, running from 0001 through 9999. The numbers must be sequential, although they do not have to be consecutive.
For example, a contract might include:
- CLIN 0001: Nonrecurring engineering
- CLIN 0002: Prototype units
- CLIN 0003: Integration support services
- CLIN 0004: Contract data
Once assigned, a DoD CLIN number cannot be reused for a different line item within the same contract. In addition, the contract CLIN normally retains the corresponding solicitation line item number unless a valid reason supports a change.
CLIN vs SLIN
A Subline Item Number, or SLIN, subdivides a CLIN to support delivery tracking, payment, funding accounting or another administrative need. A SLIN may be deliverable or informational.
For DoD contracts, separately identified SLINs add two alphabetic characters to the parent CLIN. Examples include 0001AA, 0001AB and 0001AC. Informational SLINs use two numeric characters, such as 000101 and 000102. The DFARS PGI line-item procedures provide the governing numbering details and examples.
The distinction matters to schedulers. If 0001AA and 0001AB have different contractual delivery dates, the IMS should not rely only on the general parent description for CLIN 0001. The detailed delivery commitments reside at the deliverable SLIN level.
CLIN vs ELIN
An Exhibit Line Item Number, or ELIN, identifies an item within a contract exhibit. DoD contracts may use exhibits instead of placing a long list of line items or subline items in the main contract schedule. For example, Exhibit A could contain ELINs A001, A002 and A003.
Under DFARS 204.7101, an exhibit establishes requirements for deliverables. The DD Form 1423 CDRL is always an exhibit rather than an ordinary attachment. Therefore, program teams should review both the parent CLIN or SLIN and its referenced exhibit when planning data deliveries.
Why CLINs Matter to Schedulers and Program Controls
The CLIN structure establishes part of the contract’s commercial and administrative architecture. As a result, it can influence proposal pricing, cost collection, delivery planning, invoice preparation and performance reporting.
However, a CLIN rarely provides enough detail to build an executable schedule. The planner still needs the technical scope, WBS, organizational responsibilities, delivery requirements and contractual events. The Integrated Master Schedule guide for DoD programs explains how those elements come together in a time-phased execution model.
A CLIN Is Not Automatically a WBS Element
The WBS decomposes the product and project scope. A CLIN organizes an acquired product or service under the contract. Those structures may align, but no universal one-to-one relationship exists.
For example, one CLIN for a prototype vehicle could require design, software, procurement, assembly, integration and testing across several WBS branches. Conversely, one systems-engineering WBS element could support several CLINs.
Therefore, forcing every CLIN into a single WBS branch can distort responsibility and schedule logic. A better approach keeps the product-oriented structure described in how to structure an IMS using the WBS, while adding CLIN traceability where it supports contract management.
CLIN Dates Must Trace to the IMS
When a CLIN or deliverable SLIN has a contractual delivery date, period of performance or completion requirement, the schedule should represent the work needed to satisfy it. Usually, that includes a clear delivery or completion milestone supported by valid predecessor logic.
Still, planners should not copy a date from a pricing spreadsheet without checking the contract. Review Section B together with Section F, the SOW, exhibits, CDRLs and applicable modifications. If those documents conflict, elevate the issue through contracts management rather than selecting the most convenient date.
CLINs Support Schedule-to-Cost Traceability
A CLIN can provide one dimension of the crosswalk between scope, schedule and cost. For example, the IMS may include a custom CLIN or SLIN field. The cost system may also identify the applicable CLIN alongside the WBS, Organizational Breakdown Structure and control account.
However, the CLIN should not replace those structures. Instead, it supplements them. Effective schedule-to-cost integration preserves traceability without assuming that one contractual line item equals one control account or work package.
Also, do not assume the funded value of a CLIN equals its Budget at Completion (BAC). Contract price, obligated funding, estimated cost, fee and performance measurement budget serve different purposes. The program must reconcile them using the contract, accounting structure and approved Earned Value Management System procedures.
Fictional CLIN Example: Radar Modernization Program
Consider the fictional Orion Ridge Radar Modernization contract. Its Section B contains the following structure:
- CLIN 0001: Radar redesign, one lot, firm-fixed-price
- CLIN 0002: Two prototype radar assemblies, firm-fixed-price
- CLIN 0003: Engineering support, cost-plus-fixed-fee
- CLIN 0004: Contract data, not separately priced
The program’s WBS includes systems engineering, radar hardware, embedded software, integration, verification and program management. Those WBS elements do not map one-for-one to the CLINs.
Systems engineering supports CLINs 0001, 0002 and 0003. Meanwhile, the prototype delivery under CLIN 0002 depends on hardware, software and verification work from several WBS branches. CLIN 0004 data items also draw technical content from across the program.
The scheduler adds a CLIN field to relevant IMS activities and milestones. However, the team retains the WBS as the primary schedule hierarchy. It also creates controlled milestones for the prototype deliveries and each required CDRL submission.
Later, a contract modification adds a third prototype with a different delivery date. Contracts personnel determine the proper new line-item structure. After authorization, program controls updates the CLIN crosswalk, schedule scope, budget assignments and baseline records through the approved change process. This preserves the traceability discussed in maintaining baseline traceability.
How Proposal Teams Should Use CLINs
During a proposal, the solicitation CLIN structure provides a starting point for the price volume and execution plan. First, the team should identify each line item’s scope, contract type, quantity, unit of measure, delivery requirement and pricing treatment.
Next, the proposal manager should establish a crosswalk among the CLINs, WBS, basis of estimate, schedule and technical volume. This step helps expose omissions and inconsistent assumptions before submission.
For example, the pricing team may assume that CLIN 0002 includes environmental qualification testing, while the schedule places that work under CLIN 0001. The technical volume may assign the same testing to a third line item. A cross-functional review can resolve the inconsistency before it affects price or delivery credibility.
The solicitation instructions control the required proposal format. Although FAR 4.1007 addresses alternative line item proposals, an offeror should not restructure the requested CLINs casually. The team must follow the solicitation provision and document any proposed alternative clearly.
Common CLIN Mistakes
- Reading only Section B. A short CLIN description rarely defines the complete technical or delivery requirement.
- Ignoring SLIN-level dates. The parent CLIN may be informational when deliverable SLINs carry the actual quantities and delivery terms.
- Forcing a one-to-one CLIN-to-WBS mapping. This can weaken the product-oriented schedule and split work unnaturally.
- Treating CLIN value as performance budget. Price, funding, fee and EVMS budget are related but not interchangeable values.
- Using an internal charge code as if it were a CLIN. A CLIN comes from the procurement instrument, not the contractor’s internal coding system.
- Failing to process modifications across all systems. A new or changed CLIN may affect the IMS, cost tool, billing system, CDRL tracker and baseline records.
- Assuming every mapping convention is a regulation. Adding a CLIN field to every IMS activity may be useful, but it is not a universal FAR or DFARS requirement.
Practical CLIN Review Checklist
When reviewing a solicitation, award or modification, program controls should confirm:
- What product or service does each CLIN or deliverable SLIN acquire?
- What contract type applies to each line item?
- Where are the governing delivery dates or periods of performance stated?
- Does a CLIN refer to an exhibit, CDRL or attachment?
- Which WBS elements and control accounts support each line item?
- How will the IMS identify contractual delivery milestones?
- How do pricing, obligated funding and performance budget reconcile?
- What systems and baseline records must change after a modification?
This review does not transfer contracting authority to the scheduler or control account manager. Instead, it gives the program team enough traceability to execute the authorized contract correctly.
CLIN FAQ
Does CLIN stand for Contract Line Item or Contract Line Item Number?
CLIN commonly stands for Contract Line Item Number. Strictly, the line item is the contractual element, while the number identifies it. In everyday use, acquisition professionals often use CLIN for both.
Is a CLIN always separately priced?
No. A line item may be marked not separately priced when its price is included in another line item. Cost-reimbursement and indefinite-delivery arrangements also follow different pricing conventions. Check the contract and the applicable FAR or DFARS exceptions.
Can one contract contain different contract types by CLIN?
Yes. A contract can contain fixed-price, cost-reimbursement, time-and-materials or labor-hour line items in combination. The applicable type should be identified for each line item to support administration and payment.
Should every IMS activity contain a CLIN code?
Not necessarily. A CLIN field can improve traceability, especially for delivery-driving work. However, the contract, schedule reporting instructions and program procedures determine what is required. Avoid assigning a CLIN merely to populate a field when the activity supports several line items.
Who establishes the CLIN structure?
The Government establishes the contractual line-item structure through the solicitation and award process. Offerors may provide input or propose alternatives when the solicitation permits it. After award, only an authorized contract action can change contractual CLIN scope or structure.