Marketing & Communications Subcontracting for Federal IT Primes: The FAR 52.219-9 Play (2026)

Executive Summary

• Direct answer: FAR 52.219-9 requires any large business prime contractor awarded a federal contract exceeding $900,000 (updated threshold effective October 1, 2025) to submit an approved subcontracting plan with separate percentage goals for each socioeconomic small business category, reported semi-annually via ISR and annually via SSR in SAM.gov.
• Key insight: Most IT modernization RFPs already contain PWS requirements for strategic communications, stakeholder engagement, and public awareness campaigns. Primes that assign this scope to a named 8(a) communications subcontractor earn both socioeconomic subcontracting credit and technical evaluation points from one teaming decision.
• RC Strategies perspective: We have held the prime seat on NAVSEA and Army National Guard contracts and been named as a subcontractor on others. Our 8(a) certification (September 2024 through 2033) gives prime contractors verified SDB subcontracting credit and a communications team that understands CO expectations from both sides of the reporting relationship.
• Actionable takeaway: Before your next IT modernization proposal submission, map every PWS communications requirement to a named small business subcontractor in your FAR 52.219-9 plan. The compliance credit and the technical score improvement happen simultaneously.

Picture the solicitation: a $50 million IT modernization RFP with clear PWS language on stakeholder engagement, public awareness campaigns, and strategic communications. Your technical team is building the approach in one room. Your contracts team is building the subcontracting plan in another. The problem is that nobody has connected those two documents, and the contracting officer evaluating your proposal will. A well-structured subcontracting plan does more than satisfy FAR 52.219-9. When paired with the right 8(a) communications subcontractor, it simultaneously meets socioeconomic subcontracting goals and earns technical evaluation credit on the outreach requirements already written into the RFP.

What does FAR 52.219-9 require? FAR 52.219-9, "Small Business Subcontracting Plan," requires other-than-small business prime contractors on negotiated federal contracts exceeding $900,000 (effective October 1, 2025, for non-construction) to submit an acceptable subcontracting plan before contract award. The plan must include separate percentage goals for small business, small disadvantaged business, women-owned small business, service-disabled veteran-owned small business, HUBZone, and veteran-owned small business concerns. Primes report progress semi-annually (ISR) and annually (SSR) through SAM.gov. Failure to comply in good faith constitutes a material breach and may be considered in past performance evaluations.

What FAR 52.219-9 Requires, and What Changed in 2026

The current version of FAR 52.219-9 reflects FAC 2026-01, effective March 13, 2026, with the clause dated January 2025. This clause applies to negotiated acquisitions where the prime is other than a small business. Small business primes are exempt. That distinction matters: if your competitor on a full-and-open procurement is a small business, they carry no subcontracting plan obligation. You do.

When a Subcontracting Plan Is Required: The $900K Threshold

The subcontracting plan requirement triggers at contracts expected to exceed $900,000 for non-construction and $2 million for construction. This updated threshold took effect October 1, 2025, replacing the previous $750,000 floor. It applies to new solicitations and contracts issued on or after that date.

This is not a minor administrative update. Teams working off pre-October 2025 templates are working with stale data. If your boilerplate subcontracting plan still references $750,000, the contracting officer knows your compliance procedures haven't been updated in the current fiscal year.

The 15 Plan Elements Under FAR 19.704: Three That Get Missed

FAR 19.704(a) prescribes 15 required elements for every subcontracting plan. Rather than recite all 15, here are the three that BD and contracts teams most frequently underweight or miss entirely:

1. Separate percentage goals for each socioeconomic category. The plan must include individual goals for SB, SDB, WOSB, SDVOSB, HUBZone, and VOSB. A single blended "small business" goal does not satisfy the requirement.
2. Solicitation documentation records. For every subcontract solicitation above the simplified acquisition threshold, the prime must document whether small business concerns were solicited. If not, the plan must explain why not. This records requirement is a CO audit point.
3. Flow-down assurance. The prime must include FAR 52.219-9 in all subcontracts that offer further subcontracting opportunities. This creates a cascading compliance obligation that many teams forget to address in their teaming agreements.

Compliance Consequences: Material Breach, CPARS, and Liquidated Damages

FAR 52.219-9 states that failure to comply in good faith with the subcontracting plan "shall be a material breach of the contract and may be considered in any past performance evaluation." That language is not advisory. It is contractual.

FAR 52.219-16 establishes liquidated damages for subcontracting plan violations. A material breach finding can trigger a Below Satisfactory CPARS rating, which follows the prime into every subsequent competitive proposal. The contracting officer is specifically instructed to ensure that offerors have not submitted unreasonably low goals to minimize exposure to these liquidated damages.

We have operated on both sides of this compliance obligation: as a prime contractor for NAVSEA and the Army National Guard, and as a subcontractor. The compliance mechanics look different from each seat.

The Communications Scope Already Written Into Your IT Modernization RFP

You have seen what the plan requires and what reporting looks like. Now look at where communications subcontractors actually live in these contracts, and why this is the most underutilized teaming slot in IT modernization.

The PWS Language Primes Routinely Overlook

Federal IT modernization RFPs consistently include PWS requirements for strategic communications, stakeholder engagement, public education, and public awareness campaigns. These are not soft requirements. Agencies learned from failed ERP implementations that technology rollouts without adoption support fail. One federal ERP modernization organized town halls attracting over 500 participants and created networks of more than 120 change agents. That work lives in a communications subcontractor's lane.

Federal strategic communications guidance is explicit: a Stakeholder Analysis is necessary to "strategically and proactively communicate and involve stakeholders in strategic communications activities," and the Communications Lead should be included early and throughout the entire process, providing frequent, audience-targeted communication updates.

What Communications Deliverables Actually Look Like Inside These Contracts

Common PWS LanguageCommunications Subcontractor DeliverableStrategic communicationsStakeholder communication plans, leadership messaging, Q&A toolkitsStakeholder engagementStakeholder analysis, engagement calendars, town hall facilitationPublic outreach / education campaignsAudience-targeted content, media placement, digital outreachAdoption campaignUser enablement content, awareness campaigns, feedback loopsCommunications lead / coordinatorEmbedded communications PM with government reporting

Why This Matters for Your Subcontracting Plan and Your Technical Score

When a prime maps this PWS scope to a small business communications subcontractor, two things happen simultaneously. First, the subcontractor's labor hours contribute to ISR-reported SB subcontracting dollars. Second, the technical approach can name a specific, credentialed communications team with documented federal performance, which is a scored evaluation differentiator.

Most primes either self-perform this scope inside a large-business team or assign it to a large-business sub. Either choice costs them subcontracting credit AND weakens the technical approach on the communications-specific PWS requirements. We have executed stakeholder engagement and public outreach from the prime seat on DoD contracts. When we sit in the subcontractor seat on your IT modernization program, we bring that same execution depth: the kind that shows up in your CPARS narrative, not just your ISR. See our strategic communications programs for the methodology we bring to these engagements.

Two Problems, One Teaming Decision

That is the scope analysis. Here is the business case for how it all connects: compliance credit plus evaluation credit from one teaming decision.

Subcontracting Plan Credit + Technical Evaluation Credit in One Team Slot

Adding a qualified 8(a) communications subcontractor to a proposal does two things simultaneously:

• It contributes verified SDB subcontracting credit toward the 5% statutory SDB subcontracting goal, plus small business subcontracting credit overall.
• It allows the prime's technical approach to name a specific, credentialed communications team with documented federal performance as a differentiator on scored evaluation factors.

How FAR 15.304(c)(4) Makes Small Business Participation a Scored Factor

Per 15 U.S.C. §637(d)(4)(G)(i), for solicitations that are not set aside for small businesses, involve consolidation or bundling, and offer a significant opportunity for subcontracting, the contracting officer shall include proposed small business subcontracting participation as an evaluation factor. The evaluation considerations include the extent to which specific small businesses are identified, including the products and services they will provide.

This means naming RC Strategies in the subcontracting plan, with specific scope and not a placeholder, turns a compliance obligation into a scored technical advantage.

The RC Strategies Difference: Prime Experience, 8(a) Certification, Measurable Performance

RC Strategies holds 8(a) certification from September 2024 through 2033. SBA 8(a) status qualifies as SDB credit in subcontracting reporting, with access to sole-source opportunities up to $4.5 million that give prime contractors additional teaming flexibility beyond competitive bids.

Most small businesses on federal contracts exist as a compliance line item. RC Strategies has held the prime seat on NAVSEA and Army National Guard contracts. That means when we join a team as a subcontractor, we understand the CO relationship, the deliverable cadence, the reporting burden, and the performance standard. We do not require prime oversight babysitting. We run our scope.

When an IT modernization program's adoption numbers are lagging and the CO is asking questions, we run toward that fire. We have been in that seat before. Execution is our DNA. We bring battle-tested commercial marketing technology, AI-enhanced audience intelligence, and a performance-first methodology, tied back to what the CO will see in the CPARS narrative and the ISR: a subcontractor who delivered.

Learn how RC Strategies partners with primes on federal communications subcontracting.

The Prime-Ready Subcontracting Checklist (FAR 52.219-9, 2026)

This checklist addresses the elements that BD and contracts teams most commonly miss when building a subcontracting plan for a communications-heavy IT modernization or public outreach contract. It is not a substitute for your contracts attorney's review. It is the practical cross-check before that review.

1. Threshold check: Confirm the contract value exceeds $900,000 (updated FAR 19.702 threshold effective October 1, 2025). If yes, an acceptable subcontracting plan is required from the apparently successful offeror before award.
2. Separate goals by socioeconomic category: The plan must include separate percentage goals for SB, WOSB, SDVOSB, HUBZone, SDB, and VOSB. Verify each goal reflects the updated statutory floors (SDB: 5%, WOSB: 5%, SDVOSB: 5%, HUBZone: 3%).
3. SDVOSB goal check: Confirm your plan reflects 5%, not 3%. The FY24 NDAA (P.L. 118-31) increased the SDVOSB goal. Old templates still show 3%.
4. Communications/outreach scope mapped to a named SB sub: If the PWS includes strategic communications, stakeholder engagement, public awareness campaigns, or public education requirements, those deliverables should be assigned to a named small business subcontractor, not absorbed into large-business overhead.
5. SAM.gov registration confirmed for all named subcontractors: Registration in SAM.gov is a requirement for doing business with the federal government. Confirm all named subs are active before proposal submission.
6. Solicitation records documented: For every subcontract solicitation above the simplified acquisition threshold, document whether small business concerns were solicited. If not, document the specific reason. This is a FAR 19.704(a) element COs check.
7. ISR/SSR reporting protocol established: Identify who on the team owns subcontracting report filing. ISRs are due April 30 and October 30 (semi-annually) plus within 30 days of contract completion. The SSR is due October 30 annually. All reporting is now in SAM.gov.
8. Good faith effort documentation plan: Build a rolling record of solicitations sent, responses received, and award decisions before the ISR is due. This is your good faith defense if actuals fall short of goals.
9. Subcontracting plan evaluation factor confirmed: Check whether the solicitation includes small business subcontracting participation as a scored evaluation factor per FAR 15.304(c)(4). If it does, naming specific subcontractors with defined scope earns measurable evaluation credit.
10. eSRS references removed from all compliance documentation: eSRS retired February 2026. Any internal procedures, templates, or campaign materials referencing eSRS require immediate updates to reflect SAM.gov as the filing platform.

Key Takeaways

The small business subcontracting plan under FAR 52.219-9 is not a back-office compliance exercise. It is a proposal strategy tool. Primes who treat it as a scored component, mapping specific communications PWS requirements to named 8(a) subcontractors, gain both socioeconomic credit on the ISR and technical evaluation differentiation in the same teaming decision. The $900,000 threshold, the 5% SDVOSB update, and the SAM.gov migration are the three compliance updates most likely to expose stale proposal templates in 2026.

RC Strategies brings 8(a)-certified SDB credit, prime contract experience with NAVSEA and the Army National Guard, and a communications methodology built for federal performance standards. If your next IT modernization proposal includes stakeholder engagement, strategic communications, or public outreach in the PWS, that scope belongs on a named small business subcontractor's line in your plan. Start the teaming conversation with RC Strategies.