The MDA SHIELD final RFP is now live, and several items diverge from the draft—especially in submission mechanics, scope alignment, evidence requirements for Corporate Experience, and initial-order readiness. This briefing distills what changed, why it matters, and how to adapt your approach immediately—without fluff and without rework at the eleventh hour.

Quick internal reference: Our earlier primer remains useful for context on work areas and eligibility; see our SHIELD solicitation proposal preparation guide.

What’s New at a Glance (Admin & Submissions)

  • Q&A intake method: The draft referenced a questions matrix; the MDA SHIELD final RFP specifies submitting questions via a Microsoft Form. Confirm the exact link and cutoff in the final package.
  • Submission portal: Proposals submit through the PIEE Solicitation Module. Validate your roles and conduct a full-file upload rehearsal.
  • File hygiene: Follow the final naming conventions and stand‑alone documents rule. Confirm PDF, bookmarks, and page-count treatment for title/cover elements per Section L.
  • Offer period: Verify the offer acceptance period on the SF‑33 as specified in the final.

For platforms and regs, leverage the PIEE Solicitation Module for submissions, use SAM.gov for official notices and FPDS records, and consult the Missile Defense Agency for program background.

Corporate Experience: Evidence Rules Are Tighter

Why this matters: Corporate Experience is the backbone of technical acceptability. The final clarifies documentation pathways and elevates prime‑level relevance.

Key differences from the draft:

  1. Template realignment: Corporate Experience now uses Attachment L‑02 (not L‑03). Rebuild your tabbing, bookmarks, and file names accordingly.
  2. Prime vs. subcontract work: Prime‑level experience is preferred. If you rely on subcontract examples, the final requires specific corroboration (e.g., signature page excerpts or permitted documentation) or an authoritative data record.
  3. Verification sources: Acceptable verifiers typically include CO/COR/Program Manager signoff, or an FPDS record when applicable. Prepare FPDS evidence before you lock pagination via SAM.gov (FPDS records are now hosted in SAM).
  4. Recency & alignment unchanged: 5‑year recency and clear mapping to Section C work areas remain pivotal. Demonstrate at least two work areas with depth, not merely adjacency.

Action: Build an evidence gate for each example card:

  • Is it prime‑level? If not, do we have the required subcontract proof?
  • Do we have CO/COR/PM signoff or a clean FPDS record?
  • Are the work areas explicitly traceable to Section C language (same terms, not synonyms)?

Section C Scope: Titles, Traceability, and Initial‑Order Impact

The MDA SHIELD final RFP adjusts a facilities‑related work area title (now commonly referenced as Facilities Engineering and Sustainment) and refreshes several CDRLs.

What to change in your crosswalk:

  • Exact naming: Update your capability matrix, resumes, and corporate experience headers to match the final work‑area titles verbatim.
  • Traceability language: Mirror terms used in Section C, then reference them in each relevant Performance Narrative and in Corporate Experience headers, so evaluators see immediate alignment.
  • CDRL movement: Several CDRLs shift into the initial order. That means parts of your management and readiness artifacts must be truly Day‑1 capable (e.g., kickoff plan, program controls, reporting cadence).

For terminology and data items, see the DoD CDRL/DID primer.

Proposal Structure & Page Treatment (Section L)

The MDA SHIELD final RFP clarifies how Table L‑1.3 and related instructions treat title pages, tables, graphics, and appendices.

Practical implications:

  • Pagination discipline: Lock a page‑count plan that anticipates any title/cover inclusion rules. Don’t assume; trace back to the exact final language.
  • Stand‑alone documents: Each volume or attachment must stand on its own—bookmarks, figure lists, and internal cross‑references should not depend on another file.
  • File assembly SOP: Create a pre‑submission SOP: compile → validate bookmarks → regenerate PDF/A if required → reopen to confirm searchability and page count.

Evaluation Notes (Section M) and Competitive Range

While SHIELD intends to award the IDIQ to qualifying offerors, the final introduces/clarifies Competitive Range practices. If discussions are opened, documentation gaps become time‑critical.

What to do now:

  • No‑gap posture: Treat every verification element (signoffs, FPDS, CDRL readiness) as if discussions will be selective and brief.
  • Consistency checks: Cross‑verify dates, contract numbers, obligated values, and customer references across Corporate Experience, resumes, and management plans.

Corrections to Earlier Messaging (Webinar/Article)

  • Questions matrix → Microsoft Form: Update internal trackers and client‑facing instructions to reflect the new Q&A intake.
  • L‑03 → L‑02: Replace template labels, bookmarks, and file names in all instructions and checklists.
  • Facilities work area title: Align resumes and example titles to the final wording (Facilities Engineering and Sustainment).

For baseline context, revisit our SHIELD solicitation proposal preparation article.

Readiness Checklist for the MDA SHIELD final RFP

  1. Corporate Experience pack (L‑02): Prime examples prioritized; subcontract examples include required excerpts or proof.
  2. Verification on file: CO/COR/PM signoff letters (or emails per RFP allowance) and/or FPDS records exported and cited consistently.
  3. Section C wording mirrored: Work‑area titles match the final; narratives show explicit traceability, not generic capability claims.
  4. CDRL readiness: Initial‑order deliverables drafted and templated; kickoff and reporting cadence defined.
  5. Pagination & assembly: Title/cover handling per final; bookmarks, figure/table lists validated; PDF properties checked; file names conform to RFP.
  6. Q&A and submissions: Q&A posted via Microsoft Form per final; PIEE roles confirmed; a full rehearsal upload completed 48 hours before final submission.

Frequently Asked Clarifications

Q1: Does the MDA SHIELD final RFP change Corporate Experience recency?
A: No—plan against a 5‑year window and demonstrate coverage in at least two Section C work areas with depth.

Q2: Can subcontract experience still be used?
A: Yes, but the bar for substantiation is higher. Expect to include specific documentation excerpts or an accepted data source (e.g., FPDS via SAM.gov) to validate scope and role.

Q3: Are price/cost volumes evaluated at base IDIQ award?
A: SHIELD emphasizes technical acceptability and qualifications at the base IDIQ level; price dynamics emerge in task‑order competition.

Q4: What exactly moved into the initial order?
A: Specific CDRL adjustments are in the final; treat Day‑1 program management and reporting artifacts as production‑ready.

Closing Perspective

The MDA SHIELD final RFP rewards teams that anchor their narrative in verifiable contract history, use the exact Section C lexicon, and package their evidence with zero ambiguity. Shift your effort from generic capability prose to traceable demonstrations—and assemble your volumes so an evaluator can confirm acceptability in one pass. For a compact view of our structured support options, explore our proposal services hub.