Federal FY Q2 RFP surge playbook
What federal-facing proposal teams should have ready by April 1 to handle the fiscal-Q2 volume surge — pre-approved content, capture-lead calendars, bid/no-bid discipline, and what breaks under load.
Federal fiscal year Q2 is April through June. For federal-facing proposal shops it’s the year’s second-largest surge window after September — agencies push procurement actions to hit program-year targets, many contracting officers have just cleared their Q1 backlog, and the volume of posted RFPs on SAM.gov climbs sharply in the first two weeks of April.
This is the seasonal playbook. What should be ready by April 1, what to expect in the first three weeks, and the specific things that break under surge load. I’ve run this playbook on four federal teams over seven fiscal cycles. The mechanics are stable; the details shift each year.
What the surge looks like
Volumes vary year to year, but the shape is consistent:
- Week 1 (April 1–7). SAM.gov posting volume spikes roughly 30–40% above the Q1 baseline. Many postings are continuations of procurement actions that slipped from Q1. Amendment cadence on existing solicitations accelerates.
- Weeks 2–3 (April 8–21). Peak volume. Q&A deadlines on posted RFPs land mid-month; the amendments that follow land 5–7 days later, compressing vendor response windows.
- Week 4 onward. Volume stays elevated through mid-June, then declines toward end-of-FY. The Q4 spike (September) is larger, but Q2 has longer sustained elevation.
Our internal dashboard tracks this weekly, consistent with the Q1 SAM.gov cut. Customers should assume their own inbound RFP volume roughly doubles in Q2 week 2 relative to a Q1 average week.
The seven things to have ready by April 1
1. A written bid/no-bid scoring rubric with a floor
The Q2 kickoff triage post described the Monday-morning pre-screen. That runs on top of a full bid/no-bid rubric — five variables (strategic fit, probability of win, cost to produce, opportunity cost, deal quality), a published floor, and a named decision owner. If the rubric lives in someone’s head, you will say yes to too many bids in week 2 and miss the one you should have chased. Lock the rubric before April 1 and run every pursuit through it.
2. Pre-approved past-performance references, tagged by scope
The biggest avoidable failure in a Q2 surge is writing past-performance writeups from scratch. You need 15–30 references with approved language, tagged by scope: cloud-infrastructure, cybersecurity-assessment, data-analytics, etc. The past-performance writing grid post covers the structure. Pre-approved means the reference’s point of contact has signed off on the wording, the performance period is current, and the CPARS rating is documented. Writing this in week 2 of April is too late.
3. A pre-drafted executive-summary template per service line
Not a filled-in executive summary — a template with the structural scaffolding and the pre-approved win-theme library. Evaluators read the exec summary first; a generic one signals a generic response. A service-line-specific template with win themes ready to be customized to the specific RFP is the difference between a two-hour exec summary and an eight-hour one.
4. Compliance-matrix automation set up and tested
The compliance extractor (revised grammar notes) is most valuable when you have 8 active RFPs simultaneously. Manual compliance matrix construction is 4–6 hours per RFP and it’s the work that gets shortchanged first under load. Set it up, run it against two historical RFPs, confirm the matrix matches what your team would have built by hand. Do this before you need it.
5. Held capture-lead calendar time
Book 2-hour capture blocks on the calendar for every Monday, Wednesday, and Friday morning in April. Hold them empty. As bid/no-bids pass the rubric, the blocks get assigned to specific pursuits. Calendar blocks that are already held are easier to defend than calendar time that has to be requested.
6. Named SME owners for each service line
The SME bottleneck is the dominant failure mode of every surge. The 18-month SME update describes the current pattern. Before April 1, every service line should have a named primary and secondary SME, with their March/April availability confirmed and ticket-SLA expectations agreed. A new SME getting tickets for the first time in the middle of a surge will not respond on time.
7. A submission-checklist library, per portal
Federal submission portals (SAM.gov, individual agency portals, sub-prime vendor portals) each have quirks. Write a submission checklist per portal: file-naming convention, format requirements, attachment limits, typical portal behavior under load. Keep them in a shared doc. Pull the right checklist at kickoff, not at submit-minus-one.
What breaks under surge
Three patterns I see every Q2:
SME latency blows out. A team running at normal cadence has SMEs responding in 24–48 hours. A team in surge has SMEs responding in 5–7 days, because the SME is on three active pursuits simultaneously. The fix is not “ask the SME to respond faster.” The fix is fewer pursuits per SME, which comes from the bid/no-bid rubric actually being applied.
Color-team reviews get compressed. Pink team and red team slip because the draft isn’t ready; gold team becomes the only meaningful review and runs at submit-minus-one. This is the textbook failure mode and the textbook answer is: review dates are set at kickoff, the response schedule works backward from them, and if the dates slip the submission slips too.
The compliance matrix is built late. Because it’s tedious manual work, compliance matrices get deferred when the team is already stretched. Then sections get drafted against the team’s own structure instead of the RFP’s explicit categories. The draft has to be restructured at red team. Avoiding this is one of the reasons to get compliance-matrix automation in place before April 1.
The specific discipline that pays off
If you do one thing above everything else on this list, make it this: at kickoff, work backwards from the submission deadline to schedule every review date. Then lock the schedule. A surge failure mode is writers negotiating review slip because the draft isn’t ready. The correct answer is that the review runs on the scheduled day against the draft that exists at that moment. A review of an incomplete draft is still useful. A review that never happens because the draft wasn’t ready is catastrophic.
The eight-stage pipeline describes the full sequence. The Q2 surge test is whether your team can hold it under 2x normal volume.
What’s different this Q2 from last Q2
Two things.
Volume baseline. FY 2026 Q1 ran about 12% higher than FY 2025 Q1 on our SAM.gov cut. If that carries through, Q2 volume this year will be the highest we’ve seen.
AI-assisted drafting is operationally mature on most federal-facing teams now. The surge won’t be about drafting capacity — it will be about review capacity and SME capacity. Teams that invested in drafting AI last year but didn’t also invest in review tooling and SME workflow will find the bottleneck moved, not eliminated.
The takeaway
April 1 is the forcing function. Everything above is doable in March. Done in March, it’s a playbook you run. Done in the middle of April, it’s a plan you wrote while drowning.
Every Q2 I’ve worked on has punished the teams that tried to build infrastructure during the surge and rewarded the teams that built it before.