Governance & Security|August 17, 2026|12 min read

Automating SCRM Documentation for Section 889 in Subcontractor-Heavy Proposals

Prime contractors need to validate and document subcontractor supply chain compliance at proposal time, not after award. Here is the governance architecture that prevents post-award surprises.

Projectory team

To automate Section 889 supply chain risk management (SCRM) documentation in subcontractor-heavy proposals, prime contractors need a governed supplier compliance register that captures each subcontractor's 889 attestation, tier, product category, evidence link, owner, and expiration date, then validates that data against prohibited-equipment lists and exclusion orders before the representation is signed. The failure most primes make is collecting attestations by email at the last minute and never revalidating them, which pushes discovery of prohibited telecom equipment into a post-award audit instead of proposal review.

This matters because the Section 889 clause flows down to subcontracts, a covered device in a delivered system can put you in breach, and the clause requires you to report covered equipment you find during performance, including when a subcontractor at any tier tells you about it [2]. The fix is architectural: build the validation into a repeatable proposal artifact so no one signs a representation they cannot defend.

Here is the governance model that catches these problems while you can still fix them.

The Post-Award Surprise That Should Have Been Caught at Proposal Time

Consider an illustrative case. A prime wins a mid-size IT services contract. During capture, it collected Section 889 attestations from its four named subcontractors, completed its representation in SAM.gov, and moved on. Eight months into performance, a supply chain review finds that one subcontractor installed video surveillance cameras from a covered manufacturer as part of the system delivered at a government site. The cameras came two tiers down, purchased through a reseller nobody had asked about.

The prime had a signed attestation on file. It said the subcontractor would not provide covered telecommunications equipment. It was wrong, and the prime had no evidence it had done anything beyond taking the sub at its word.

This is the pattern. Manual email-chain attestation collection breaks the moment you scale past a handful of vendors. A proposal with three named subs can touch many more sub-tier suppliers once you count resellers, integrators, and OEMs. Someone in BD forwards a PDF attestation form, chases signatures, drops the returned files into a shared drive, and never looks at them again. Nobody cross-checks the products against the covered entities named in the clause. Nobody records who owns each attestation or when it expires.

The legal floor is worth stating first. Under FAR 52.204-26, the offeror represents whether it provides covered equipment or services and, after conducting a reasonable inquiry, whether it uses them [7]. A reasonable inquiry is one designed to uncover information in the entity's possession, and it excludes the need for an internal or third-party audit [2]. The register in this article goes further on purpose, as an internal control. The core thesis is simple. SCRM validation has to happen before the representation is signed, not during a post-award audit. The representation is a statement of fact you are making to the government. If you cannot back it with dated, owner-assigned evidence at the moment you sign, you are betting your contract on hope. The rest of this article shows how to convert that scramble into a governed workflow that produces defensible evidence every time.

What Section 889, the SECURE Technology Act, and SBOM Mandates Actually Require

Start with the two halves of Section 889 of the FY2019 NDAA, because primes routinely conflate them.

Part A prohibits the government from procuring any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system, and the contractor is prohibited from providing such equipment, systems, or services to the government [2]. Covered equipment includes telecommunications equipment produced by Huawei or ZTE and, for public safety, government facility security, critical infrastructure surveillance, and other national security purposes, video surveillance and telecommunications equipment produced by Hytera, Hikvision, or Dahua [2]. Part B prohibits the government from contracting with an entity that uses such equipment, systems, or services as a substantial or essential component of any system, and this prohibition applies regardless of whether that use is in performance of work under a Federal contract [2][5]. Part B is the one that surprises people, because it reaches into your own internal operations, not just what you deliver.

The flow-down obligation is narrower than many primes assume, and that is exactly why it needs care. FAR 52.204-25 requires the contractor to insert the substance of the clause in all subcontracts, including subcontracts for commercial products and services, but excluding paragraph (b)(2), the Part B prohibition [2]. Your subcontractors therefore carry the Part A prohibition on providing covered equipment to the government and the reporting duty, while your Part B representation is about your own company's use. If a tier-2 vendor puts covered equipment into the system you deliver, you have a Part A problem and a reporting obligation, even though you never touched the equipment [2].

The SECURE Technology Act (Pub. L. 115-390) includes, as title II, the Federal Acquisition Supply Chain Security Act of 2018, which FAR subpart 4.23 implements along with the Federal Acquisition Security Council (FASC) regulation [3]. Under that act, the Secretary of Homeland Security, the Secretary of Defense, and the Director of National Intelligence can issue FASCSA orders that exclude named sources or covered articles from procurement actions or require their removal from agency systems [6]. This changes supplier eligibility mid-pursuit. A supplier you cleared during teaming can become the subject of an order weeks before submission, and your register has to catch that change rather than relying on a stale one-time check.

Software transparency mandates extend SCRM past hardware. Executive Order 14028 directed agencies toward Software Bill of Materials (SBOM) expectations so buyers can see component provenance in the code they acquire [4]. For proposals that deliver software, SCRM now means tracking where code components come from, not only where devices come from.

Translate each requirement into a proposal decision:

  • Section 889 Part A: Under FAR 52.204-26, represent whether you do or do not provide covered equipment or services as part of your offered products or services [7]. Separately, because FAR 52.204-25 flows the Part A prohibition down, make sure no subcontractor at any tier delivers covered equipment into your solution [2]. Owner: solution architect. What breaks the bid: a covered component in the technical stack that nobody caught, at any tier.
  • Section 889 Part B: After a reasonable inquiry, represent whether your company does or does not use covered equipment or services [7]. Owner: SCRM lead with IT. What breaks the bid: an internal inventory nobody has checked against the covered entities.
  • FASCSA orders: Confirm no named supplier appears on an active order. Owner: procurement. What breaks the bid: a matched supplier with no substitution.
  • SBOM expectations: Provide component provenance for delivered software. Owner: engineering lead. What breaks the bid: a component with unknown or prohibited origin.

Why Your Subcontractor Attestations Are a Liability

An attestation you cannot verify is worse than no attestation, because it creates a paper record of diligence you did not actually perform. The common failure modes:

  • Expired attestations collected during a prior pursuit and reused without a fresh signature or date check.
  • Missing tier-2 coverage where the subcontractor attests for itself but never surveys its own resellers and OEMs.
  • Unsigned or draft reps that sit in the shared drive as placeholders and get treated as final.
  • Vendors added after teaming who join the delivery plan during proposal refinement and never receive an attestation request at all.

The defensibility gap is the real problem. When a contracting officer or an inspector general asks how you validated your Section 889 representations and your subcontractors' deliveries, "we emailed a form and they sent it back" is not a diligence process. You need dated, owner-assigned evidence that shows what you checked, when, and against which lists.

DimensionManual email collectionGoverned supplier register
AccuracyAttestations taken at face value, no product cross-checkProducts validated against FCC covered list and FASCSA orders
FreshnessNo expiration tracking, stale reps reused across bidsExpiration dates trigger automatic re-collection
Tier coveragePrime-to-sub only, sub-tiers invisibleRoll-up from every sub-tier into the prime representation
Audit trailFiles in a shared drive, no dated actionsTimestamped evidence with assigned owner per row
Change responseNew vendors slip through unrepresentedAdding a supplier triggers a validation gate

The table makes the choice obvious. Manual collection produces documents; a governed register produces evidence. Only one of those defends a representation.

The Governance Architecture: A Supplier Compliance Register

The center of a working SCRM program is a single register with a defined schema. Every subcontractor and sub-tier supplier is a row, and every row carries the fields you need to defend a representation.

At minimum, the register schema includes:

  • Supplier name and unique identifier (CAGE or DUNS where available)
  • Tier (prime, sub, sub-tier reseller, OEM)
  • Product or service category (hardware, telecom, software, services)
  • Section 889 status (clear, flagged, pending, excluded)
  • Evidence link (the signed attestation, SBOM reference, or exclusion check)
  • Owner (the named person accountable for that row)
  • Expiration date (when the evidence goes stale and re-collection triggers)

Each subcontractor's rows roll up into an internal readiness status for the pursuit. That status is a company control, separate from the representation itself: your FAR 52.204-26 representation speaks for your company [7], while the subcontractor rows support the Part A flow-down and the delivered solution [2]. If any sub-tier row is flagged, pending, or excluded, the internal status shows the pursuit as not ready for sign-off, and the team does not sign while a red row exists three levels down. This is the mechanism that would have caught the surveillance gear in the opening story: the tier-2 reseller would have been a row, and its product category would have flagged for a covered-manufacturer check.

Validation gates enforce the discipline. Three gates matter most:

  1. Prohibited equipment gate: any product category matching covered telecom triggers a mandatory cross-check against the FCC covered list before the row can go green.
  2. Stale evidence gate: any attestation past its expiration date reverts to pending and routes back to its owner.
  3. Unassigned owner gate: no row can reach green without a named owner, because unowned evidence is nobody's responsibility.

This register connects directly to your compliance matrix automation, where each SCRM requirement becomes a tracked row with owner, evidence, and status rather than a loose commitment.

Data Validation Workflows That Catch Problems Before You Sign

The register is only as good as the workflow that keeps it current. A working validation pipeline runs in four stages.

Intake. When a subcontractor joins the delivery plan, the system creates rows for that sub and prompts for its sub-tier suppliers. The attestation request goes out with a defined return date, not an open-ended "when you get a chance."

Automated cross-check. Returned attestations are checked against the FCC covered equipment list and active FASCSA orders. A product category flagged as telecom triggers a manual review rather than auto-clearing. This is the step manual processes skip entirely.

Owner routing. Any flagged or pending row routes to its named owner with a specific action, such as "confirm reseller OEM source" or "collect updated attestation." The owner sees the row, the evidence gap, and the deadline.

Sign-off. As an internal control, the team does not sign the representation until the roll-up is fully green. The FAR does not require this gate, but it is the one that matters most in practice.

Freshness rules prevent stale reuse. Set an expiration window (six months for active pursuits is one reasonable choice) so any attestation older than that window reverts to pending and re-collects. Change triggers matter just as much: adding a subcontractor during proposal refinement automatically creates unvalidated rows, which turn the roll-up yellow until they are cleared.

Here is what a single SCRM row looks like when mapped like a compliance matrix entry:

RequirementEvidenceOwnerStatusNext action
889 Part A flow-down, Sub ASigned attestation, 2026-01SCRM leadGreenRevalidate at 6-month mark
889 Part A flow-down, Sub A resellerPending surveyProcurementYellowCollect OEM source by Fri
FASCSA order check, all subsCross-check logComplianceGreenRe-run before submission
SBOM, delivered appComponent list draftEngineering leadYellowResolve unknown component

The Internal Gate That Prevents 889 Surprises

This is a company control that goes beyond the FAR's reasonable-inquiry standard. Block representation sign-off until every tier is green. Not the top-level subs. Every tier, including resellers and OEMs the subs surveyed. A sub-tier row that was never created or never checked is the easiest way for covered equipment to reach a delivered system unnoticed. If your workflow lets someone sign while a single row sits yellow, you have a documentation process, not a control.

Building the SCRM Documentation Packet Evaluators Trust

Evaluators do not want your reassurance; they want artifacts. A defensible SCRM documentation packet has four parts.

The register export shows every supplier, tier, status, owner, and evidence link in one place. It demonstrates that you tracked the whole supply chain, not just your named subs. The attestation evidence provides the signed, dated documents behind each green row. SBOM references cover software provenance where you deliver code. A narrative diligence statement ties it together, explaining your process, your validation gates, and how you handle changes and expirations.

Rebuilding this packet from scratch for every pursuit is where teams lose time. Many of your suppliers appear across multiple bids, so their attestations and register rows should carry forward. A content reuse library lets you reassemble the packet across pursuits, pulling the current attestation for a supplier you have already vetted rather than re-collecting it, while the expiration rules make sure you never reuse something stale.

This is where Projectory helps with Section 889 compliance. It extracts the Section 889 and related clause requirements, such as FAR 52.204-25, from the solicitation into the compliance matrix with links to the source text, flags potential gaps for review, and lets you assign owners and track compliance status as the proposal comes together. Keep supplier attestations and FASCSA order checks attached to those rows, and have the owner update the row when an attestation expires or a new order is issued, so the packet draws from one record instead of copies that drift apart.

Frequently Asked Questions

Does Section 889 flow down to subcontractors? Partly. FAR 52.204-25 must be included in all subcontracts, but the flow-down excludes paragraph (b)(2), the Part B prohibition [2]. Subcontractors are bound not to provide covered equipment to the government, and you must report covered equipment a subcontractor at any tier tells you about [2].

How often should subcontractor attestations be revalidated? Set an expiration window and re-collect when it passes, for example every six months for active pursuits, and revalidate whenever a new supplier is added or a FASCSA order is issued.

What is the difference between Part A and Part B? Part A prohibits the government from buying equipment, systems, or services that use covered equipment as a substantial or essential component, and bars contractors from providing them. Part B prohibits contracting with any entity that uses covered equipment that way, even outside the federal contract [2][5].

Do SBOM requirements apply to hardware-only proposals? SBOM expectations apply to delivered software. If your solution includes no software you deliver, SBOM tracking is not the priority, but hardware SCRM under 889 still applies fully [4].

Your 30-Day SCRM Governance Rollout

Start narrow and prove the model before you scale it.

Week 1: Build a supplier compliance register for your top three active pursuits. List every subcontractor and every sub-tier supplier you can identify, and assign an owner to each row. Do not wait for a perfect schema; the seven fields above are enough.

Week 2: Run the automated cross-checks. Match every telecom or hardware product against the FCC covered list, and check every supplier against active FASCSA orders. Flag what needs review.

Week 3: Close the gaps. Route flagged and pending rows to owners with deadlines, collect missing attestations, and confirm sub-tier sources.

Week 4: Set your gates and expiration rules, then generate a documentation packet from the register.

The metric to track from day one: percentage of subcontractor evidence that is current and owner-assigned. If that number is below 100 percent when you sign a representation, you have found exactly the exposure behind the illustrative case at the top of this article. That prime relied on a green attestation over a tier-2 reseller row nobody had created. A governed register would have kept the roll-up yellow, blocked sign-off, and forced the reseller question before the bid went out. That is the difference between a document and a control.

References