When you order from GSA Federal Supply Schedules, you normally give multiple schedule holders a fair shot. The post-RFO GSAM 538.7104-3 tells you when and how you can go to a single source instead, and what the file has to show to support that call.
The five statutory exceptions, what the file actually has to show, and where the post-RFO controlling text lives.
Under the RFO, the FSS ordering procedures that used to sit in FAR Subpart 8.4 were moved into GSAM Subpart 538.71. The old "limited-sources justification" lane now lives at GSAM 538.7104-3 and is called a sole source justification. The concept is the same: when you place an order against an FSS contract and you are not competing among schedule holders, you owe the file a written justification that supports the call.
The GSAM is significantly leaner than the old FAR text. Most notably: the old eleven-element verbatim list and the FAR-driven dollar-threshold approval ladder are not in GSAM 538.7104-3. The content standard is now "in writing and include sufficient detail and supporting rationale to support the exception used." Approval levels are set by agency or local policy. What hasn't changed: you still need a defensible file, the justification still has to be posted publicly, and a thin justification is still a problem.
Each FAR Part has its own lane for restricting competition. The lanes survived the RFO; some of the names and citations moved:
FAR Part 6: Justification and Approval (J&A). Non-commercial, open market procurements above the SAT.
FAR Part 8 (now GSAM 538.7104-3): Sole source justification on Federal Supply Schedule orders.
FAR Part 12: Commercial sole source path. Commercial item buys using simplified procedures.
FAR Part 16: Exception to Fair Opportunity. Task and delivery orders off IDIQ and requirements contracts.
When someone says "sole source on a schedule," a sharp CO hears "GSAM 538.7104-3, not FAR Part 6."
This is the lighter of the two tiers. GSAM 538.7103-2(c) routes a sole source action in this range to GSAM 538.7104-3(a), which says the ordering activity CO must determine in writing that the circumstances of the acquisition deem only one source reasonably capable of providing the products, services, or solutions. The GSAM gives examples: urgency, exclusive licensing agreements, and items particular to one manufacturer (brand name).
There is no formal statutory-exception list at this tier. The file standard is the CO's written determination plus the underlying facts that support it. Document who you considered, what made them not capable, why the one source you picked is capable, and how price reasonableness is established. The shorter the dollar figure, the shorter the file can be, but it still needs to be defensible if a reviewer pulls it.
Above the SAT, GSAM 538.7104-3(b)(1) lists five statutory exceptions. You have to cite which one applies and support it in the file.
(i) Unusual urgency. The need is of such unusual urgency that following the normal procedures would result in unacceptable delays in fulfilling that need. Genuine and unforeseen, not poor planning.
(ii) Only one source capable. Only one source is capable of providing the products, services, or solution required at the level of quality required because the offering is unique or highly specialized. The key word is "capable." If only one schedule holder can actually meet the specific technical requirements, this is your exception.
(iii) Logical follow-on to a competitively issued FSS order. The order should be issued on a sole source basis in the interest of economy and efficiency because it is a logical follow-on to an FSS order already issued on a competitive basis. Note the qualifier: the prior FSS order has to have been competed. A sole source follow-on to a sole source order does not stack.
(iv) FSS BPA minimum guarantee. It is necessary to place the order with a particular FSS contractor to satisfy a minimum guarantee established in the FSS BPA. Narrow, but it exists in the GSAM.
(v) Law expressly authorizes or requires the specified source. A statute names the source or directs that the purchase be made from a specified source. Rare, and when it shows up it usually shows up clearly.
The current GSAM does not enumerate elements. GSAM 538.7104-3(b)(2) says, in full: justifications must be in writing and include sufficient detail and supporting rationale to support the exception used. That is the entire content rule.
What "sufficient detail and supporting rationale" looks like in practice for an above-SAT sole source file is not a regulatory checklist. It is a defensibility question. A thorough above-SAT file generally still ends up covering:
None of those are GSAM-mandated line items the way the old FAR's eleven elements were. They are the working parts of a file that holds up under review. Build the file to the underlying logic, not to a checklist.
The current GSAM 538.7104-3 does not contain dollar-threshold approval levels. The old FAR 8.405-6 ladder ($900K, $20M, $90M / $150M for DoD/NASA/Coast Guard) is not in the controlling GSAM text.
Approval authority for a sole source justification is now whatever your agency or component supplement and your local delegation matrix say it is. For DAF activities that may run through DAFFARS, MAJCOM supplements, and the local SCO or Senior Contracting Official delegation. For other components it runs through their agency supplements. Pull the actual delegation document and have the right approver named in the file before you ask anyone to sign.
For above-SAT sole source justifications, GSAM 538.7104-3(b)(3) requires the justification to be made publicly available within 14 days after award. Urgency-based justifications under 538.7104-3(b)(1)(i) have 30 days. Posting goes on the Government-wide Point of Entry (currently SAM.gov) or the ordering activity website, and the minimum posting period is 30 days.
Before posting, screen the justification. The GSAM requires you to identify and remove contractor proprietary data, and to evaluate whether the justification or portions of it are exempt from disclosure under the Freedom of Information Act or FAR Part 24. Where publication would compromise national security or otherwise involves extraordinary circumstances, the GSAM provides an exception.
Check the Sole Source Examples tab to see what a defensible above-SAT file looks like, and how it falls apart when the rationale is thin.
Same scenario, two very different justifications. A base Communications Squadron needs to order a SIEM/SOAR cybersecurity platform through GSA MAS. The order is above the SAT, so a written sole source justification under GSAM 538.7104-3(b) applies. The GSAM content standard is "sufficient detail and supporting rationale to support the exception used" — the good example shows what that looks like in a thorough file; the bad example shows what falls apart. Click highlighted sections for coaching notes. Blue borders = strong. Red borders = problems.
The controlling current text. Five statutory exceptions for above-SAT, written-determination standard for above-MPT/below-SAT, publication rules, and screening requirements. This is where the file authority actually lives now.
Open GSAM 538.71The full subpart that replaced FAR 8.4 under the RFO. Includes the MPT, above-MPT/below-SAT, and above-SAT ordering procedures, plus BPAs, OLMs, brand-name rules, and disputes.
Open GSAM 538.71The official deviation guide explaining what changed in FAR Part 8 under the Revolutionary FAR Overhaul and where the procedures moved. Cross-reference this before citing pre-RFO FAR Part 8 sections.
Open Part 8 Deviation GuideThe online Request for Quote (RFQ) tool for GSA Schedule orders. Where you post schedule solicitations.
Visit GSA eBuy