The Saturday backlog triage pattern
Thirty minutes on a Saturday morning, three buckets, and Monday is ready to go. A small operational ritual we use to keep the proposal backlog from compounding into chaos.
Most proposal-shop chaos is not a deadline problem. It is a triage problem that compounds across the week until Friday’s backlog becomes Monday’s emergency.
Here is the pattern that fixes it. Thirty minutes on a Saturday morning. Three buckets. Coffee.
The three buckets
Bucket 1 — bid/no-bid pending. Inbound RFPs from the week that have not yet had a bid/no-bid decision made. Each one gets either a date for the bid/no-bid call (next two business days, no exceptions) or a written no-bid with a one-sentence rationale. Items do not survive a second Saturday in this bucket.
Bucket 2 — drafts in motion. Active responses with a writing assignment open. For each one, two questions: is the next milestone (pink team, red team, gold team, submission) on the calendar with named attendees, and is the named drafter unblocked? If the answer to either is no, a single Slack message goes out with the specific blocker named and the person who can clear it tagged. Not a status request. A blocker call-out.
Bucket 3 — KB write-back. Notes from the week — debrief callouts, reviewer feedback that flagged a stale block, a SME comment that revealed a content gap — get written into the KB backlog with an owner. This is the bucket that compounds. A weekly 10-minute pass keeps the KB from rotting; skipping it for three weeks is how the corpus stops being trustworthy.
The discipline
The point is not the buckets. The point is doing it on Saturday morning, when the week’s pressure is off and the next week’s pressure has not started. Triage on Friday afternoon defaults to defending Friday’s choices. Triage on Monday morning is reactive — the inbox has already started shaping the day. Saturday is the only window when the proposal manager can look at the backlog as a whole rather than as a stack of incoming requests.
Thirty minutes is a real number, not a target. If it takes longer than 45, the backlog has metastasized; the fix is not a longer Saturday session, it is a process change in the weekday routine.
What we do not do
We do not write during this session. We do not respond to substantive questions. We do not draft new content. The triage pass is decision-only — bid/no-bid status, milestone calendar, blocker call-outs, KB write-back queue. Everything else waits for the workweek.
The cumulative effect over a quarter: Mondays start with a clear queue, the calendar reflects the actual state of the proposals in flight, and the KB stays current enough that retrieval keeps working. None of that is glamorous. It is the cheapest hour of operational discipline a proposal function buys all week.