What Is the Uniform Contract Format (UCF)?

The Uniform Contract Format, known as the UCF, is the standard template that federal contracting officers must use to organize solicitations and resulting contracts issued through negotiated procurements under Part 15 of the Federal Acquisition Regulation. It divides every solicitation into 13 labeled sections grouped across four parts, so a proposal manager sees the same architecture whether the buying agency is the Department of Energy or the Department of Veterans Affairs. The requirement comes from FAR 15.204-1, which directs contracting officers to follow the structure in Table 15-1 for every negotiated acquisition unless a specific exemption applies.¹

The Four Parts at a Glance

Before working through the individual sections, it helps to see the shape of the whole document. Part I is the Schedule, covering Sections A through H, and holds the commercial terms of the deal. Part II is a single section, Section I, containing the standard regulatory clauses. Part III is also a single section, Section J, the home for attachments and exhibits. Part IV covers Sections K, L, and M, and exists only during the solicitation phase; once the contract is awarded, Part IV drops off and Parts I through III become the binding agreement.¹

The section letters are not just filing labels. Contracting officers, program managers, and contractors reference them constantly during performance, so learning the layout pays off long after award.

Part I: The Schedule (Sections A Through H)

Section A is the solicitation or contract form itself. In most cases this is Standard Form 33, which functions as both the government’s solicitation cover and the offeror’s signature page for accepting the terms.²

Section B lists the supplies or services being purchased and the corresponding prices or costs, organized by Contract Line Item Numbers (CLINs). Each CLIN ties one deliverable to a unit price, and the FAR directs that Section B include item numbers, nomenclature, and quantities, including incidental deliverables like manuals and reports.³

Section C holds the description, specifications, or statement of work. This is where the contractor’s actual obligation is defined, and it is the section most often at the center of scope disputes later on. Section D covers packaging and marking. Section E lays out the government’s inspection and acceptance criteria, specifying what quality standards apply and when acceptance occurs.

Section F sets the delivery schedule or performance period, expressed either as calendar dates or as a number of days after contract award. Section G contains contract administration data, including who will manage the contract once it is signed. Two roles show up here. The Procuring Contracting Officer (PCO) awards the contract, and the Administrative Contracting Officer (ACO) handles day-to-day oversight, monitors performance, and issues routine administrative changes. The PCO delegates specific functions to the ACO but retains authority over certain items such as forward pricing rate agreements and final indirect cost rates.⁴

Section H closes out Part I with special contract requirements unique to the particular procurement. These are agency- or mission-specific provisions that do not appear in the standard clause library: key personnel restrictions that limit substitutions without government approval, government-furnished property terms, organizational conflict-of-interest provisions, and tailored security or information technology requirements.

Part II: Contract Clauses (Section I)

Section I is the standard clause library for the contract. It carries the regulatory clauses required by law or regulation for the specific procurement type, covering payment terms, dispute resolution, changes and termination rights, and compliance obligations. The contracting officer draws from the FAR clause matrix, and many clauses are incorporated by reference rather than reproduced in full. Depending on the dollar value and the nature of the work, provisions tied to the Prompt Payment Act or the Service Contract Act commonly appear.⁵

Part III: Attachments (Section J)

Section J collects the documents that support the contract but do not belong in the narrative sections. Technical drawings, wage determinations, data rights inventories, and security requirement checklists typically live here. Keeping them in Section J lets the main body stay focused on obligations and terms while still giving offerors the technical context they need to price and plan the work.

Part IV: Representations and Instructions (Sections K, L, and M)

Part IV appears in the solicitation but does not become part of the awarded contract. Section K gathers representations, certifications, and statements from offerors, including small business status declarations and other organizational data. Section L provides the submission instructions: formatting rules, page limits, volume structure, and file format requirements. Section M states the evaluation factors the government will apply to pick a winner. Once the contract is awarded, Part IV is typically detached, and only Parts I through III remain in force.¹

When the UCF Does Not Apply

If you are responding to a Request for Proposals under a negotiated acquisition, you are almost certainly working within this format. Several procurement types, however, are exempt and use different structures:

Construction and architect-engineer contracts, which follow FAR Part 36 and use Standard Form 1442 rather than the UCF layout.
Subsistence contracts, meaning food and perishable goods procurements, which have their own format.
Procurements where another section of the FAR prescribes a format that conflicts with the UCF.
Letter requests for proposals issued under FAR 15.203(e).
Specific procurements that an agency head or designee has exempted from the UCF requirement.

If your solicitation falls into one of these categories, the section labels and layout described above will not match what you see.⁶

Why Section M Shapes How You Respond

Section M does more than announce criteria. It signals which of two very different source selection methods the government is running, and that choice should drive the whole proposal.

Under the tradeoff process, the government can award to someone other than the lowest-priced offeror when the perceived benefits of a higher-priced proposal justify the added cost. The solicitation must state the relative importance of the evaluation factors, indicating whether non-cost factors combined are significantly more important than, approximately equal to, or significantly less important than price. This method rewards proposals that show superior technical capability or a better approach, even at a higher price.⁷

Under the lowest price technically acceptable (LPTA) method, the government awards to the lowest-priced proposal that meets the minimum technical requirements. Proposals are not ranked on non-cost factors, and tradeoffs are not permitted. Agencies use LPTA when the requirements are clear and well-defined, when exceeding the minimum would add little value, and when price is the dominant factor. Outside the Department of Defense, agencies face additional restrictions on when LPTA can be used, including documenting that evaluating technical proposals would require minimal subjective judgment and that the lowest price reflects total lifecycle cost.⁸

Tradeoff evaluations reward technical differentiation. LPTA evaluations reward a sharp price and a technical volume that demonstrates compliance cleanly, without spending pages exceeding the standard.

Preparing a Response That Fits the Format

Two administrative prerequisites come before drafting anything. First, register in the System for Award Management at sam.gov. Offerors are required to have an active SAM registration at the time they submit a proposal.⁹ Registration generates a Unique Entity Identifier (UEI), a 12-character alphanumeric code that identifies the business across the federal procurement system.¹⁰ Second, confirm the North American Industry Classification System (NAICS) code assigned to the solicitation. The contracting officer assigns a NAICS code to each solicitation, and the business must fall within the corresponding size standard to qualify as a small business for that opportunity.¹¹

Inside Part I, Section C deserves the most attention. Every task, deliverable, and performance standard referenced in Section B pricing and Section F schedule needs to trace back to what Section C actually says. Vague statement-of-work language is where scope disputes and cost overruns start. In Section B, tie each CLIN to a specific deliverable with a clear unit of measure and unit price.³

Section L instructions are enforced literally. Typical requirements include specified page sizes (usually 8.5 by 11 inches), minimum one-inch margins, minimum font sizes for body text and tables, and strict page limits for each proposal volume. Agencies commonly require separate volumes for technical, management, past performance, and pricing content, with each volume carrying its own page cap. Exceeding a page limit or using an unauthorized font can lead to the extra pages being removed from evaluation or, in some cases, the entire proposal being rejected. Electronic submissions usually must be in searchable PDF or native Microsoft Office formats, and password-protected files are often prohibited. Read Section L before writing, not after.

What Happens to the Format After Award

UCF contracts rarely stay static. Changes after award move through Standard Form 30, titled “Amendment of Solicitation/Modification of Contract.” The same form covers amendments to the solicitation before award, change orders issued under the Changes clause, unilateral modifications the contracting officer can make without contractor consent, administrative corrections such as typographical fixes, supplemental agreements negotiated between the parties, and adjustments to contract funding.¹²

One detail worth knowing: when a modification is expected to result in a price change, the estimated amount of that change is not shown on the SF 30 copies furnished to the contractor. The pricing negotiation runs separately from the modification paperwork. Each modification alters the baseline set by the original UCF sections, so tracking them against the original Section C scope and Section B pricing keeps performance and invoicing aligned with what was actually agreed.

1
Acquisition.GOV. FAR 15.204-1 Uniform Contract Format
2
U.S. General Services Administration. Standard Form 33 – Solicitation, Offer, and Award
3
Acquisition.GOV. FAR 15.204-2 Part I – The Schedule
4
Acquisition.GOV. FAR 42.302 Contract Administration Functions
5
eCFR. 48 CFR 52.232-25 – Prompt Payment
6
Acquisition.GOV. FAR 15.204 Contract Format
7
Acquisition.GOV. FAR 15.101-1 Tradeoff Process
8
Acquisition.GOV. FAR 15.101-2 Lowest Price Technically Acceptable Source Selection Process
9
Acquisition.GOV. FAR 4.1102 Policy
10
U.S. General Services Administration. Unique Entity ID is Here
11
eCFR. 13 CFR 121.402 – Size Standards for Government Procurement
12
Acquisition.GOV. FAR 43.301 Use of Forms