The rolling Q4 capacity plan for proposal teams
A five-week look-ahead that reallocates the proposal team twice. Why a static quarterly plan breaks in Q4, and what a rolling version does instead.
A static Q4 capacity plan breaks in week two. Buyers move deadlines. New-vendor DDQs arrive in waves. SMEs take holiday days that weren’t on the plan. Teams that hold the plan constant ship fewer bids and burn the last week catching up.
The rolling version: a five-week look-ahead that reallocates the team twice.
The shape
Monday morning, the proposal manager pulls the next five weeks into a single view: every active pursuit, every expected DDQ, every SME’s declared availability, every color-team review on the calendar. The view is re-drawn weekly — last week drops off, a new week appears.
Two moments in the five weeks are reallocation points. The end of week two, and the end of week four. At those moments, the manager explicitly decides: does the team’s current load match the team’s current capacity? If not, something moves — a deadline gets renegotiated, a bid gets declined late, or a SME gets replaced on a section.
Why rolling beats static
Static plans assume the inputs are known. In Q4 they aren’t. The buyer who promised to post the RFP on November 10th posts it on November 21st. The engineering SME who allocated 20 hours to DDQs takes the Thanksgiving week off. The capture lead’s biggest account pulls forward a pursuit by two weeks.
A rolling plan absorbs these without ceremony. The reallocation points are scheduled, so reacting to change isn’t a special event — it’s Monday.
What the reallocation actually looks like
At week two and week four, the manager runs four checks:
- Total assigned hours vs. total available hours. If assigned exceeds available, something has to give.
- Per-SME load. The senior security engineer shouldn’t be on four DDQs concurrently even if the total math works.
- Color-team reviewer coverage. A red team scheduled without a named reviewer is a red team that won’t happen.
- Submission-day staffing. If two submissions land on the same Friday, the team needs a named submit lead for each.
When a check fails, the fix is one of: decline a pursuit (with a written rationale — see the bid/no-bid framework), renegotiate a deadline (ask, politely, early), or rebalance the SME roster.
The one discipline that makes it work
The plan is written down. A rolling plan that lives in the manager’s head isn’t a plan — it’s an anxiety. A shared document, re-drawn every Monday, with the two reallocation points on the calendar, is what turns the exercise into a team discipline instead of a solo burden. Lohfeld makes this point about proposal processes in general: most of the fixable problems are scheduling problems in disguise.