What the FAR actually requires
FAR 52.219-9(d)(10) is the operative clause. Any prime contractor or subcontractor subject to a subcontracting plan must "designate a small business liaison officer." The clause specifies the SBLO's minimum duties, and they are not vague:
- Developing and promoting the company's program to identify small business, veteran-owned small business (VOSB), service-disabled veteran-owned small business (SDVOSB), HUBZone, small disadvantaged business (SDB), and women-owned small business (WOSB) sources
- Conducting market research to identify qualified small business subcontractors and suppliers
- Maintaining a source list or database of small businesses available for subcontracting
- Coordinating with contracting officers and SBA procurement center representatives (PCRs)
- Reviewing solicitations to identify set-aside and subcontracting opportunities
- Administering the company's subcontracting program and ensuring compliance with plan goals
- Preparing, submitting, and maintaining the Individual Subcontracting Report (ISR) and Summary Subcontracting Report (SSR) in the Electronic Subcontracting Reporting System (eSRS)
The ISR is due within 30 days after each reporting period ends (typically semi-annually). The SSR is due October 30 for the prior fiscal year. Missing these deadlines is a reportable compliance failure that contracting officers are required to document.
Who triggers this requirement
The subcontracting plan requirement kicks in when a contract exceeds the simplified acquisition threshold (currently $250,000) and the work has subcontracting possibilities. Large business prime contractors must submit subcontracting plans. Contracts with the Department of Defense, NASA, and the Coast Guard follow the same threshold under DFARS 219.702.
If the prime is a small business, no subcontracting plan is required, so no SBLO designation is required either. If a small business prime later grows out of its size standard and wins a large contract, the requirement applies to that award.
One nuance worth knowing: a company-wide or "master" subcontracting plan, approved under FAR 52.219-9(d), covers all eligible contracts for a 12-month period. One SBLO can administer a master plan across multiple contracts. Commercial plans work the same way. For companies with 20 or more active subcontracting plans across the portfolio, a single SBLO designation covering all of them is both permissible and common.
Full-time vs. collateral duty
The FAR does not require the SBLO to be a full-time role. The size and complexity of the subcontracting program determine whether it should be.
For a company with one or two contracts under $10 million and moderate subcontracting activity, the SBLO function typically rides as a collateral duty within contracts, compliance, or procurement. A senior contracts administrator who also handles reporting is a defensible approach as long as the duties are actually getting done.
For a company with a portfolio above $100 million in prime contracts and multiple agency customers, a dedicated SBLO becomes necessary. At that scale, the outreach calendar, database maintenance, eSRS filings, and coordination with SBA PCRs across several agencies is close to a full-time workload on its own.
The Government Accountability Office has cited companies for SBLO functions that existed on paper but had no real capacity behind them. Contracting officers reviewing ISR/SSR data can tell when an SBLO has done substantive outreach versus when a name was assigned to satisfy a clause.
What good SBLO performance looks like
The SBA's subcontracting program regulations at 13 CFR Part 125 describe what meaningful small business outreach looks like. Compliance-oriented primes do the minimum: they file eSRS on time and check the box. High-performing SBLO programs do several things differently.
First, they maintain an active source list that is actually used in procurement decisions. This means the SBLO has relationships with PTAC counselors, SBA district offices, and certifying bodies like NMSDC affiliates and WBENC regional partners. New supplier registrations go into a working database, not a spreadsheet no one reads.
Second, they track goal performance at the contract level before the reporting deadline. A good SBLO reviews subcontracting spend quarterly with the program manager or project executive, not two weeks before the ISR is due. Companies that discover a goal shortfall in the final month rarely close it.
Third, they participate in pre-solicitation conferences, vendor days, and industry days. These events generate direct relationships with small business owners who have relevant past performance. Some agencies, including DHS and DoD, publish upcoming small business events on their procurement forecast pages. An SBLO who attends two or three of these annually will build a pipeline that a passive one never will.
DCAA's view of SBLO costs
SBLO costs are generally allowable under FAR 31.205, but DCAA will scrutinize whether the costs are allocable to government contracts versus other business activities.
If the SBLO works exclusively on government contracts, the costs are direct or overhead charges to those contracts, depending on how the company's accounting practices are structured. If the SBLO also supports commercial subcontracting efforts or internal supplier diversity initiatives, cost allocation becomes an issue. DCAA expects the contractor to document the time split and charge accordingly.
For a collateral-duty SBLO who spends, say, 20 percent of their time on SBLO functions, a time-charging system that captures that allocation is the clean answer. For a dedicated SBLO, the salary and overhead are typically charged to a cost pool allocated to all government contracts benefiting from the function.
One practical note: DCAA has flagged cases where companies designated an SBLO but could produce no records of actual activity. No outreach emails, no meeting logs, no documentation of source development. That is not just a DCAA problem. A contracting officer who finds no evidence of SBLO activity during a compliance review can recommend a marginal rating on the small business factor of a past performance assessment.
Staffing the SBLO function in practice
The SBLO does not need to be a contracts attorney or a certified procurement professional, but they need enough standing inside the company to get purchase requests reviewed before award, not after. SBLO functions that sit entirely inside compliance or legal and have no connection to the procurement team rarely close goal gaps.
The most effective SBLO setups place the function inside business development or contracts, give the SBLO a direct line to the CPO or VP of Procurement, and connect them to project management so they know where subcontracting opportunities are actually forming.
Three action steps
- Pull your current eSRS filings and compare reported performance against plan goals for the last four reporting periods. If any contract is below 80 percent of goal, identify the gap and assign owner-level responsibility for closing it before the next ISR.
- Verify your SBLO designation is current and documented in writing. If the designated person has changed, update the record with your ACO and make sure the eSRS account reflects the correct contact.
- Schedule one outreach activity in the next 60 days, whether a PTAC event, a supplier day hosted by one of your agency customers, or a registration with a certifying body's supplier database. Document it. That documentation is the difference between a defensible SBLO program and a nominal one.
