The Saturday shuffle: reprioritizing the proposal queue

Saturday morning, ten minutes, coffee. The proposal queue gets re-priced.

The ritual is short by design. A team that runs it weekly stops shipping the bid that lost a week ago without anyone noticing the loss. A team that doesn’t ships the lost bid into Monday’s daily standup as if it’s still alive.

The four columns

Open a spreadsheet (or the queue view in the proposal tool). Each active proposal gets four scores re-validated:

1. Deadline pressure. Days remaining vs. days needed. Days needed is a function of the response volume and the team capacity, not a guess. A 200-question DDQ with a single SME on call is a different deadline pressure than a 50-question RFP with three SMEs available.
2. Probability of win. Same scoring rubric the bid/no-bid framework uses, applied at the current state of the bid. A proposal that scored 0.4 at kickoff might score 0.6 now if discovery has gone well. Or 0.2 if a competitor has been named the favorite.
3. Effort remaining. Hours, not story points. Estimated by the proposal manager, validated against the visible team utilization.
4. Strategic value. Has it changed since intake? A bid for a logo customer is worth more than the same-sized bid for a generic mid-market opportunity, but the strategic-value column also catches the inverse: a bid that was a logo three weeks ago and is now a routine renewal because the buyer’s executive sponsor left.

What you do with the scores

Three actions, in order.

De-prioritize bids whose probability has moved below the floor. The hardest move. Teams hold bids in the queue that they would not have started if the bid showed up today at its current probability. Saturday’s job is to flag those and either kill them or move them to the lowest priority.

Re-balance team allocation. Two SMEs scheduled for the bid that lost on probability this week. Move them to the bid that gained. The unit of allocation is human-week, not promise.

Notify the deal owner if the de-prioritization changes the sales conversation. A salesperson talking to a buyer doesn’t always know that the proposal team has down-graded the bid’s probability. A short note Saturday morning prevents the Monday-noon surprise.

What it doesn’t do

The ritual is not a planning meeting. It is not a strategy session. It is not the bid/no-bid decision (those happen at intake and don’t get repeated weekly). It is a weekly invariant check: are we still working on the bids we’d start if they showed up today?

The Lohfeld Consulting analysis makes a related point: proposal teams accumulate slow-rolling commitments that nobody sponsors actively. The Saturday shuffle is the cheap antidote — the moment in the week when accumulating commitments get repriced against current information.

Why Saturday

Two reasons.

1. The team is offline. Decisions don’t get prosecuted in real time; they accumulate as Monday-morning pre-decisions. Quiet ritual.
2. The week’s work is settled. The Friday submissions are out (or they aren’t, in which case the Friday-submit code smell post applies and the queue needs more aggressive surgery). The information from the week — the win, the loss, the redirect — has stabilized.

A Sunday version works too. Monday-morning is too late; the team has already walked into the queue as it was.

The takeaway

Ten minutes, weekly, written down, acted on. The cost of the ritual is one cup of coffee. The cost of skipping it is sometimes a quarter’s revenue moved to the wrong bid.