The Sept 18 modified notice clarified key pathways to qualify under SHIELD, including corrections to Attachment L-02 and removal of the character limit for Field 6, while confirming that Small Business Offerors may rely on first-tier subcontractor corporate experience. With proposals due Oct 10 at 4:00 PM CT, the window is tight but workable for teams that validate evidence early and frame narratives directly to SHIELD scope. This update makes SHIELD subcontractor experience a practical bridge for firms lacking two prime examples—provided each entry is self-contained, corroborated (FPDS or CO/COR), and mapped to scope, scale, and complexity relevant to forthcoming task orders.

Key Points

  • Modified notice issued September 18, 2025 clarifies no character limit on L‑02 Field 6 and corrects L‑02 errors.
  • If you cannot provide two prime examples, subcontractor experience may be submitted in accordance with L‑3.0.
  • For Small Business Offerors, the Government will consider the corporate experience of first‑tier subcontractors.
  • Proposals due: October 10, 2025, 4:00 PM CT.
  • Anticipated PoP start: December 5, 2025.

Why this update changes the landscape

Many firms hesitated because they lacked two prime examples across SHIELD work areas. The update enables a practical path: you can now use SHIELD subcontractor experience to meet the threshold—while small businesses may also leverage first‑tier subcontractor projects. This expands the eligible field, rewards teaming, and allows emerging innovators to compete credibly—provided that each experience is validated and mapped clearly to SHIELD scope.

For a full program overview and rolling updates, see our MDA SHIELD solicitation profile.

What’s new in Attachment L‑02 (Corporate Experience)

L‑02 remains the authoritative template for Volume II (Corporate Experience), but the Government has corrected certain fields and removed the character limit for Field 6—the narrative section. For background on broader RFP adjustments, see our analysis of the MDA SHIELD final RFP changes. Practically, this means:

  • You have room to articulate problem → work performed → results → relevance without trimming critical details.
  • You must still keep each example self‑contained: do not rely on cross‑references to other volumes or annexes for key facts.
  • Every data element must be internally consistent and verifiable (contract identifiers, period of performance, dollar values, roles, customers).
Tip: Draft the Field-6 narrative last. After you anchor scope, role, period, and validation artifacts, use the narrative to connect the dots to SHIELD’s work areas and outcomes.

SHIELD subcontractor experience: what qualifies (and what doesn’t)

To benefit from the update, keep these rules in mind:

  1. Minimum count still applies. You still need at least two qualifying examples across the work areas (three recommended to strengthen coverage). If you don’t have two prime examples, use subcontractor examples permitted by the update.
  2. Role clarity is essential. Disclose whether your team member was the prime, JV member, or subcontractor, and make sure the referenced entity is part of your proposed SHIELD team.
  3. First‑tier only for SB consideration. For Small Business Offerors, the Government will consider first‑tier subcontractor corporate experience—lower‑tier subs do not satisfy the small‑business flexibility.
  4. Stand‑alone proof per example. Include FPDS printouts or a CO/COR validation letter; for subcontractor roles, a redacted subcontract agreement excerpt or prime attestation supporting the scope/role is advisable.
  5. No padding, no ambiguity. The absence of a character cap in Field 6 is not an invitation to be verbose. Precision and traceability beat length.

Building a qualifying slate fast

If you’re just getting started, this step‑by‑step primer will help you avoid common traps: SHIELD solicitation proposal preparation.

Step 1 — Inventory and map

Create a quick inventory of projects from your prime and first‑tier subcontractor portfolios. Map each to SHIELD work areas (e.g., S&T, systems engineering, cyber, test & evaluation, rapid prototyping, manufacturing). Shortlist 3–5 candidates that best cover scope, scale, complexity, and recency.

Step 2 — Validate early

For each shortlisted project, assemble validation artifacts now:

  • Prime/JV roles: FPDS records or customer letters.
  • Subcontractor roles: sub‑agreement excerpt (redacted as necessary) and performance corroboration (prime letter or CO/COR note).
    Early validation avoids last‑minute scrambles that can derail an otherwise strong package.

Step 3 — Draft crisp narratives for L‑02 Field 6

Use the extra space wisely:

  • Open with the mission need and your role (prime/JV/sub).
  • Explicitly tie activities to SHIELD scope areas using the Government’s terminology.
  • Quantify outcomes (cycle‑time reduction, TRL maturation, defect rates, cost/schedule variance, test throughput, cyber hardening metrics).
  • Close with why this experience is relevant to SHIELD task‑order execution.

Step 4 — Conduct a red‑team pass

Have a reviewer unfamiliar with the projects verify that each example is self‑contained, free of acronyms without definitions, and consistent across blocks (dates, dollars, customers, vehicles, NAICS).

How to leverage SHIELD subcontractor experience in teaming

Small businesses can now credibly anchor a submission around first‑tier subcontractor experience while showcasing prime capabilities in niche areas. Mid‑tier and large primes should reassess teaming gaps—partnering with specialty subs can sharpen coverage across SHIELD work areas and bolster the combined slate. In both cases, ensure:

  • Your organizational structure for SHIELD is clear (which team member leads which work area).
  • Past performance traceability lines up with the entity proposed for that work.
  • Conflict‑of‑interest and OCI mitigation are addressed where development and advisory roles intersect.
Practical frame: Treat SHIELD subcontractor experience as a bridge—use it to meet the bar now, then plan to harvest new prime references from early SHIELD task orders.

Submission mechanics and timing

  • Deadline: October 10, 2025 at 4:00 PM CT. Build your internal calendar backward with a 72‑hour upload rehearsal.
  • Portal: Submit via the PIEE Solicitation Module. Verify account roles and file‑size limits in advance.
  • File hygiene: Use the Government’s L‑02 template as provided; avoid changing properties or adding embedded objects that can corrupt fields.
  • Version control: Freeze a PDF of each example with the exact content pasted into L‑02 to resolve any later discrepancies.

Common pitfalls to avoid

  • Submitting fewer than two qualifying examples or mixing roles ambiguously (prime vs subcontractor).
  • Inconsistent identifiers (contract numbers, task orders) across narrative and validation artifacts.
  • Relying on external appendices to explain key facts instead of keeping each L‑02 entry self‑contained.
  • Ignoring the first‑tier limitation for small‑business subcontractor experience.

Who should lean in now

  • SB innovators with subcontract records in advanced prototyping, cyber hardening, sensor fusion, test & evaluation, or mission software.
  • Specialty subs whose niche wins can complete a team’s coverage of SHIELD work areas.
  • Integrators seeking to expand depth across scope areas through targeted first‑tier partners.

Resources