The 18-section proposal management plan federal-construction primes and 8(a) subs use to run a Shipley-style capture-to-submission process. Kickoff agenda, color reviews, deliverable tree, key personnel, and the final submission checklist. CC Proposal Management Plan (PMP) Federal-construction · 8(a) sub or GC under $50M · Shipley-scaled capture-to-submission process
§ 1. Solicitation summary and bid/no-bid result.
RFP number: W912DR-26-R-0089 · Agency: USACE Norfolk District · Contracting officer: ___ · NAICS: 236220 · Set-aside type: 8(a) Sole-Source · Contract vehicle: MATOC · Period of performance: 5 years (1 base + 4 options) · Estimated value: $25M · Page-count limit: Vol I 60p / Vol II 30p / Vol III 20p · Submission: 2026-06-15 14:00 ET · Pwin rating: 0.55 · Bid/no-bid result: BID
§ 2. Win strategy and three theme statements.
Win strategy (2-3 paragraphs): ___ Theme statement 1: ___ Theme statement 2: ___ Theme statement 3: ___
§ 3. Proposal organization, volumes, and page allocations.
Vol I Technical (60p), sections 1-7 mapped to Section L paragraphs L.4.1 through L.4.7 Vol II Past Performance (30p), 5 projects × 5p + cover/index Vol III Price (20p), cost narrative + Section J cost-pricing matrix Vol IV Small Business Plan (per Section L.5), 8 pages
§ 4. Capture-to-proposal handoff package.
Customer-relationship history: ___ · Customer hot-button list: ___ · Competitive analysis (named competitors): ___ · Win-themes documentation: ___ · Teaming agreements signed: ___ · Key personnel commitments: ___ · Past performance pre-selected: ___ · Pricing strategy framework: ___
§ 5. Roles, responsibilities, and proposal team org chart.
Capture Manager: ___ · Proposal Manager: ___ · Volume Leads (Tech / PP / Price / SB): ___ · Solutions Architect: ___ · Graphics Lead: ___ · Pricing Lead: ___ · Color-Team Reviewers (Pink/Red/Gold/White Glove): ___ · Production Lead: ___ · SMEs: ___
§ 6. Proposal schedule with milestones and critical path.
Build the day-by-day schedule from RFP release to submission. Mandatory milestones: kickoff, draft outline lock…
What is a federal proposal planner?
A federal proposal planner is the schedule plus the ownership map for a federal proposal. Where the compliance matrix answers “what does this RFP require?”, the planner answers the two questions the compliance matrix can’t: who writes each section, and by when. It names the proposal manager, the volume leads for Technical, Past Performance, Price and Small Business, the color-team reviewers, the graphics and pricing owners, and the teaming-partner point of contact, then binds those names to the day-by-day schedule from RFP release through kickoff, Pink Team, Red Team, Gold Team, White Glove, and electronic submission.
The second job of the planner is traceability. Every section in every volume traces back to a specific Section L instruction and a specific Section M evaluation factor, and the planner is where that trace lives alongside the writer’s name and the review it has to clear. When an RFP amendment moves a sub-factor or tightens a page-count, the planner is what the proposal manager updates so nothing falls through, and at White Glove the planner is what gets reconciled against the compliance matrix one last time before the volumes ship. That’s the definition in one line: a federal proposal planner is the document that says who owns each proposal requirement, when they clear each review, and how the whole thing lands at the submission portal on time.
Why this template exists
Federal proposals fail in predictable ways. The capture manager has good win-themes in their head but never writes them down, so the proposal team starts cold. The compliance matrix gets built in week one but no one updates it as Section L/M language gets refined, so the final submission misses three sub-factor headers. The Pink Team review gets scheduled but skipped because the volume leads aren’t done yet, which means the Red Team becomes the first real review and there’s no time to act on the feedback. The pricing volume lands at the printer two hours before submission with a typo in the cost narrative. The capture-to-proposal handoff happens in a 30-minute call and half the win-strategy nuance disappears with it. Every one of these failures is a process failure, not a writing failure, and every one of them is what a proposal management plan is supposed to prevent.
The proposal management plan (PMP) is the document that turns a 30-day federal proposal sprint from chaos into choreography. It documents the win strategy from capture, names the proposal team and their swim lanes, lays out the volume structure and page allocations, schedules every color-team review, defines the daily stand-up cadence, and locks down the submission process so the team isn’t improvising at 11pm the night before. Shipley’s Proposal Guide and SM&A’s federal-proposal methodology both build their entire process on a written PMP. So do the in-house BD organizations at Lockheed, SAIC, and Booz Allen. The construction-federal world has been slower to adopt it, partly because most construction firms don’t run enough proposals to justify a 30-person business development team, but the discipline scales down. A two-person proposal team running a single $15M MATOC bid still benefits from writing the PMP.
This template is the practitioner’s version. It’s built for an 8(a) sub or a federal GC under $50M revenue running its own capture without a 30-person BD team. Color reviews scaled to two reviewers per team, daily stand-ups tight at 15 minutes, key-personnel resumes practical (not 30 pages), pricing strategy linked to the cost volume without requiring a dedicated pricing analyst. Eighteen sections cover the full proposal lifecycle: bid/no-bid summary, win strategy + theme statements, volume + section structure, capture-to-proposal handoff, roles and responsibilities, schedule with milestones, color-team reviews (Pink, Red, Gold, White Glove), daily stand-ups, compliance matrix linkage, graphics and action captions plan, pricing strategy, teaming agreement coordination, past performance package, key personnel and resumes, production and electronic submission plan, post-submission Q&A handling, lessons learned and debrief plan, and the risk register.
What this is NOT: it’s not a substitute for a real capture process. If the win strategy isn’t there in capture, no PMP fixes it after the RFP drops. It’s not a writing template either. The volume leads still have to write good prose. And it’s not a project management tool that replaces a real schedule (Smartsheet, MS Project, or even a Google Sheet works fine for the day-by-day). What the PMP does is make the implicit explicit. Every assumption the proposal manager is making about who does what, when, and to what standard goes onto paper before the kickoff. That paper is what the Pink Team reviewers read before they walk in. It’s what the volume leads use when they push back on a key-personnel choice. It’s what the proposal manager points to when the capture manager wants to add a graphic at Red Team. The PMP is the rulebook everyone agreed to before the work started, and on a federal proposal, having a rulebook beats not having one every single time.
Use this template at proposal kickoff, before any volume work begins. Fill in the 18 sections during a single 2-hour session with the capture manager, proposal manager, and volume leads. Print copies for the kickoff meeting. Update the live version weekly through the proposal cycle. Archive the final PMP in the proposal record alongside the submitted proposal. That’s the artifact that powers the lessons-learned debrief 30 days after award notification, win or lose.
Who uses this
- Federal general contractors running MATOC, MACC, IDIQ, and stand-alone federal-construction proposals
- 8(a) certified subs preparing proposals as prime or as part of a teaming arrangement
- Proposal managers running the capture-to-submission process on a 30-60 day RFP response
- Capture managers handing off the win strategy to the proposal team at RFP release
- Business development directors standardizing the proposal process across multiple concurrent bids
If you don’t have your compliance matrix built first, start with the federal proposal compliance matrix Section L/M template. That’s the upstream document that makes the PMP actionable.
What’s included. 18 sections every federal PMP locks down
The proposal management plan documents 18 things every federal proposal team needs locked down before kickoff:
- Solicitation summary and bid/no-bid result. Capture the RFP number, agency, contracting officer, NAICS code, set-aside type, contract vehicle, period of performance, estimated value, page-count limit per volume, and submission date/time. Document the bid/no-bid decision result with the win-probability rating (Pwin) and the strategic rationale for bidding. This is the one-page executive summary anyone joining the proposal team mid-cycle reads first.
- Win strategy and three theme statements. Document the win strategy from capture in 2-3 paragraphs. What the customer’s hot buttons are, where the competition is weakest, and where you’re discriminated. Then commit to exactly three theme statements that every volume threads through. Themes are not features (“we have certified estimators”). They’re customer outcomes tied to your discriminators (“zero-rework procurement protects your schedule because we pre-qualified every long-lead vendor at capture”).
- Proposal organization, volumes, and page allocations. List every volume the RFP requires (typical federal-construction RFP: Volume I Technical, Volume II Past Performance, Volume III Price, plus optional Volume IV Small Business Plan or Section 8(a) compliance). For each volume, lock down section structure mapped to Section L/M, page-count allocation, font/margin requirements, and graphics-to-text ratio target. This becomes the volume leads’ contract with the proposal manager.
- Capture-to-proposal handoff package. Document what the capture manager hands off at RFP release: the customer-relationship history, customer hot-button list with evidence, competitive analysis with named competitors and their likely strategies, win-themes documentation, teaming agreements signed, key personnel commitments confirmed, past performance projects pre-selected, and the pricing strategy framework. Without this handoff documented in the PMP, capture knowledge stays in the capture manager’s head and the proposal team starts cold.
- Roles, responsibilities, and proposal team org chart. Name every role with the person filling it: Capture Manager, Proposal Manager, Volume Leads (Technical, Past Performance, Price, Small Business), Solutions Architect, Graphics Lead, Pricing Lead, Color-Team Reviewers (Pink, Red, Gold, White Glove), Production Lead, and Subject Matter Experts (one per major technical area). Lock authorities. Who approves graphic style, who arbitrates compliance disputes, who signs the final cost narrative. On a small-team proposal, one person fills three roles; that’s fine, but write it down.
- Proposal schedule with milestones and critical path. Build the day-by-day schedule from RFP release to submission. Mandatory milestones: kickoff, draft outline lock, first-draft volume completion (Pink), revisions, second draft (Red), revisions, near-final (Gold), proofreading and production (White Glove), final assembly, submission. For a 30-day RFP, lock dates for each milestone with 2-day buffers built in. For a 60-day RFP, build in additional storyboard-review and graphics-design milestones. Identify the critical path so when something slips, the proposal manager knows what’s negotiable and what isn’t.
- Color-team review schedule (Pink, Red, Gold, White Glove). Define each review’s purpose, scope, reviewer assignments, deliverable to reviewers (what they get), expected output (what they return), and turnaround SLA. Pink Team = first complete draft, focuses on compliance + win-theme alignment; Red Team = full proposal review, focuses on persuasiveness + competitive distinction; Gold Team = near-final, focuses on consistency + final-pass compliance; White Glove = proofreading + production-readiness. Scale reviewer count to team size. Two reviewers per team for a small firm, six for a large one.
- Daily stand-up cadence and status reporting. Set the daily stand-up time (15 minutes max), attendees (proposal manager + volume leads, no SMEs unless invited), agenda (yesterday’s progress, today’s plan, blockers), and status-reporting format (red/yellow/green per volume against schedule). Document escalation path when a volume goes red. Does it go to the capture manager, the BD director, the COO? Build in weekly executive-stakeholder check-in for visibility.
- Compliance matrix linkage and update process. The PMP references the compliance matrix as the single source of truth for Section L/M coverage. Document who owns the matrix (typically a junior PM or BD coordinator), update cadence (daily during writing phase), what triggers an update (any RFP amendment, any volume-section reorganization, any color-team finding that exposes a gap), and the matrix-vs-volume reconciliation process at White Glove. Treat the compliance matrix as a living artifact, not a one-time exercise.
- Graphics and action-captions plan. List every graphic the proposal will include. Organizational charts, technical approach diagrams, schedule graphics, past-performance maps, key-personnel highlights, win-theme visual reinforcement. For each graphic, capture the volume location, owner (volume lead or graphics lead), purpose (what the graphic proves), and the action caption (the bolded sentence under the graphic that ties it to a win theme or RFP requirement). Federal evaluators read action captions before they study graphics. No graphic ships without an action caption.
- Pricing strategy and cost-volume coordination. Document the pricing strategy from capture: target price as a percent of independent government cost estimate (IGCE), competitive positioning, escalation assumptions, contingency strategy, fee structure, and any teaming-arrangement profit split. Define the cost-volume coordination cadence. When does the technical volume get pricing data (you don’t want pricing assumptions baked into the technical narrative until the cost volume is mature). Document the pricing-strategy approval authority and the final cost-narrative review owner.
- Teaming agreements and subcontractor coordination. List every teaming arrangement signed for the proposal: prime/sub, joint-venture, mentor-protégé, small-business teaming. For each, document the scope of work allocation, key-personnel commitments from the team partner, past-performance projects the partner is providing, partner’s capture contributions, and the partner’s proposal-team representative. Schedule a partner kickoff at proposal kickoff plus 2 days. Document the partner-deliverable handoff dates so the prime isn’t waiting on a teammate’s past-performance write-up at White Glove.
- Past performance package and project selection. Identify the past-performance projects the proposal will use. Typically 3-5 projects per the RFP’s instruction. For each project, document the project ID, contract value, period of performance, customer point-of-contact (CPARS rating where available), relevance score against the current RFP scope, and the volume-lead-assigned writer for the past-performance write-up. Confirm CPARS or similar third-party-rating evidence is on file. Document any past-performance gaps and the mitigation strategy.
- Key personnel commitments and resumes. List every key personnel position the RFP requires (typical federal-construction RFP: Project Manager, Superintendent, QC Manager, Safety Officer; sometimes Estimator and Scheduler). For each, document the named individual, their commitment (full-time vs. part-time, days/week), their resume status (drafted, reviewed, finalized), their availability dates (tied to award and notice-to-proceed), and the customer-evaluation criteria the resume addresses. Federal evaluators read resumes for evidence of project-specific experience, generic resumes lose points.
- Facilities, security, and clearance requirements. Document any facility or clearance requirements the RFP imposes: facility security clearance level (FCL) required, personnel security clearance (PCL) levels for key personnel, project-site clearance requirements, controlled-unclassified-information (CUI) handling commitments, NIST 800-171 compliance posture, and CMMC certification level. For 8(a) subs handling federal facilities work, document the SCIF or controlled-area access controls. This section ties directly to the technical volume’s compliance-and-security narrative.
- Production and electronic submission plan. Document the final production process: electronic-file format requirements (PDF/A, separate files per volume, file-naming convention, page-numbering scheme), printed-copy requirements (number of hard copies, binding type, tabs and dividers), shipping logistics if hard copies required, and the electronic-submission portal (SAM.gov, PIEE, agency-specific portal) with login credentials confirmed and uploaded test-file readiness. Build in a 4-hour buffer between final assembly and submission deadline.
- Post-submission Q&A handling and amendment response. Define the post-submission process: amendment-monitoring assignment (who watches SAM.gov for amendments through evaluation), Q&A-response process if the agency issues clarification questions, oral-presentation prep if the RFP includes orals, and revised-proposal-response if the agency issues a request for final proposal revisions (FPR). Lock the proposal team’s post-submission availability for at least 30 days. Q&A and FPR responses can come anytime in that window with 5-7 day SLAs.
- Risk register and lessons-learned debrief plan. Capture the proposal team’s risk register. Top 5-10 risks with probability, impact, owner, and mitigation. Common federal-proposal risks: key personnel becomes unavailable, teaming partner misses deliverable deadline, pricing strategy proves uncompetitive at Red Team, RFP amendment forces volume restructuring late in cycle. Schedule the lessons-learned debrief for 30 days after award notification (win or lose), document the debrief agenda, and assign the debrief facilitator. Archive the lessons-learned with the final PMP.
How to use the template
Run the PMP as a living document through the proposal cycle. At RFP release:
- Capture manager and proposal manager fill in sections 1-4 within 24 hours of RFP release. This is the proposal-team-formation document. Sections 1-4 are what new team members read on day one.
- Convene the proposal kickoff meeting within 48 hours of RFP release. Walk through the entire PMP with the assembled team. Adjust sections 5-9 (roles, schedule, color reviews, stand-ups, compliance) based on team-member input.
- Lock the PMP at end of kickoff. The proposal manager owns the PMP from that point forward. Only the proposal manager updates it, and changes get communicated in the next daily stand-up.
- Reference the PMP at every color-team review. Reviewers should walk in having read sections 2 (win themes), 7 (current review’s scope), and the relevant volume’s section in 3. Archive the final PMP with the submitted proposal at White Glove. Use the archived PMP to drive the 30-days-post-award lessons-learned debrief in section 18.
Stop running federal proposals out of email and a shared drive.
The 18 sections above take a proposal manager and capture manager 2 hours to fill in at kickoff, and they save the team 40+ hours of mid-cycle friction across a 30-day federal proposal sprint. Multiply by the 4-8 federal proposals a small federal GC or 8(a) sub runs per year and the PMP discipline becomes the difference between winning 1-in-5 and winning 1-in-3. Contracts Connected centralizes proposal capture artifacts, compliance-matrix linkage, color-team review tracking, key-personnel and past-performance records, and teaming-partner coordination, so the proposal manager isn’t running the cycle out of an inbox and a shared drive. Pre-built integrations to SAM.gov amendment monitoring and SPRS verification fold the federal-specific gotchas into the workflow.
For educational purposes. These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.
Frequently asked questions about the proposal management plan
What is a federal proposal planner?
A federal proposal planner is the schedule plus the ownership map for a federal proposal. The single document that says who writes what, which color-team review each section clears, and which RFP requirement each section answers. It sits on top of the compliance matrix (which tells you what the RFP requires) and turns that requirement list into a day-by-day plan with named owners, review dates, and submission logistics. In practice the planner covers the whole capture-to-submission arc: the bid/no-bid result and win strategy from capture; the volume and section structure mapped to Section L/M; roles for the proposal manager, volume leads, and color-team reviewers; the Pink / Red / Gold / White Glove review schedule; the compliance-matrix update cadence; teaming-partner and key-personnel coordination; the pricing strategy handoff; and the final production and electronic submission plan. Without it, a 30-day federal proposal sprint runs out of an inbox. With it, every reviewer knows exactly what they’re reading, when, and why.
Do I really need a written proposal management plan for a small federal bid?
Yes. The reason small construction firms skip the PMP is that the proposal team is two or three people and “we all know what we’re doing”. Until someone gets sick at Red Team, the teaming partner ghosts on past performance, or the contracting officer issues an amendment that restructures the technical volume. A written PMP is what makes the next person who steps into the work productive in 30 minutes instead of 3 days. Eighteen sections sounds heavy; in practice, a small-team PMP is 12-15 pages and takes 2 hours to draft at kickoff. The ROI shows up the first time something goes sideways, and on a 30-day federal proposal cycle, something always goes sideways.
How is a proposal management plan different from a compliance matrix?
The compliance matrix tells you what the RFP requires. Every Section L instruction and every Section M evaluation factor mapped to where in your proposal you’ll address it. The PMP tells you how your team will get all that compliance work done. Who’s writing each section, when each color review happens, how amendments get folded in, what the production and submission process looks like. The compliance matrix is the what; the PMP is the how. You need both. They reference each other: the PMP’s section 9 documents the matrix update process, and the matrix’s “section X covered in Volume Y page Z” entries depend on the PMP’s section 3 volume-and-section structure being locked down. Build the matrix first (it comes from the RFP); then build the PMP (it comes from your team’s plan to address what the matrix requires).
Should the PMP be shared with teaming partners?
Yes. Share sections 1, 2, 3, 5, 6, 7, and 12 with teaming partners. Section 1 gets them oriented, section 2 ensures their writing threads the same themes, section 3 tells them what page-count allocation their content gets, section 5 names them in the team org chart, section 6 commits them to the schedule, section 7 includes them in the color-team review process, and section 12 is the partner-coordination section that defines what they owe and when. Keep sections 11 (pricing strategy) and 18 (risk register) prime-only. Those contain competitive-sensitive information. Some primes share an abbreviated PMP with teammates and keep the full version internal; either approach works as long as the partners get enough to do their work.
How early should color-team reviewers see materials?
Pink Team reviewers get the first complete draft 24-48 hours before the review. Red Team reviewers get the full proposal at least 48 hours before, ideally 72 hours, with a printed read-through copy plus a soft-copy. Gold Team reviewers get the near-final 24 hours before. White Glove reviewers get the production-ready version and need 12-24 hours for proofreading. Building these review-prep windows into the PMP’s section 6 schedule is what prevents the most common proposal-cycle failure: reviews that get scheduled but skipped because the materials aren’t ready in time. If a color-team review’s materials aren’t ready 24 hours before, the proposal manager has to make a call: delay the review (which cascades the schedule) or run it on partial materials (which limits the review’s value). Build the buffer into the schedule so this decision happens rarely.
What’s the right level of detail for the past-performance section in the PMP?
Section 13 of the PMP is project-selection and writer-assignment, not the full past-performance volume. For each of the 3-5 selected projects, document: project ID, contract value, period of performance, customer POC name and phone, CPARS rating if available, relevance score (1-5) against the current RFP scope, and the volume-lead-assigned writer. The actual past-performance write-ups live in Volume II of the proposal, not in the PMP. Keep the PMP entry tight, three lines per project. The PMP’s job in section 13 is to make sure the right projects get selected, the right writers get assigned, and the customer POCs are confirmed reachable before submission. Past performance is where federal proposals get differentiated; getting selection right is where winning starts.
How do amendments get folded into a proposal already in progress?
Document the amendment-response process in PMP sections 6 and 9. When SAM.gov posts an amendment, the proposal manager (or the assigned amendment-monitor) flags it within 4 hours, distributes the amendment text to the team within 24 hours, and convenes a 30-minute amendment-impact meeting within 48 hours to assess: does the amendment change the compliance matrix? Does it change page allocations? Does it change the submission deadline? Update the matrix immediately for any compliance changes. Update the PMP’s section 3 if volume structure changes. Update the schedule if the deadline shifts. Communicate all changes in the next daily stand-up. The most dangerous failure mode is treating a late-cycle amendment as “small” when it actually moves a sub-factor or adds a page-count constraint, and not catching the impact until White Glove. The amendment-impact meeting is the forcing function that prevents this.