The Sunday night compliance check
A 15-minute habit before Monday's kickoff. Read the compliance matrix against the calendar. Find the four things that will hurt you in week three. Write the email Sunday night so Monday is not the day you discover them.
Sunday at nine PM. The Monday kickoff for a new RFP response is in eleven hours. Most proposal managers spend those eleven hours sleeping. The ones who run the cleanest weeks spend fifteen minutes first.
The Sunday night compliance check is a habit we picked up watching disciplined proposal managers across several teams. It is short, it has a fixed shape, and it produces an email that lands at 7 AM Monday and changes the whole shape of the kickoff.
Here is the shape.
What you do
Open the compliance matrix. (If there is no compliance matrix, you do not have a compliance check, you have a hope. Build the matrix first. See Stage 4 of the eight-stage pipeline.)
Open the calendar. The submission date, the gold-team review, the red-team review, the pink-team review.
Read the matrix against the calendar. You are looking for four specific things.
One. Any requirement whose answer depends on a person who is on PTO during the week the answer is needed. Engineering lead is in Portugal week three; the technical architecture answer is due in week three. That is not a problem you find on Tuesday morning. That is a problem you reroute Sunday night.
Two. Any requirement that requires a fresh artifact (a SOC 2 report, a current insurance certificate, a signed reference letter) where the artifact is older than the buyer’s stated freshness window. “Provide insurance certificate effective within the last 90 days” — when was yours issued? Check now. Renewing one of these in week three is a fire drill. Renewing one in week one is a calendar item.
Three. Any requirement where the answer is “we do not currently do this” and the team needs to decide whether to attempt it, sub-contract it, or take the deduction. These are the bid-shape decisions. They cannot be made by the writer in week three. They have to be on the kickoff agenda.
Four. Any requirement on the compliance matrix that has the same wording as a requirement we have answered well in the last four bids. Those are the cheap questions. They get assigned to the writer with the relevant prior answer and they close out in an hour. Naming them on Monday morning saves the team three hours of “where do I start” on Tuesday.
The email
Four bullets. Subject line: “Compliance check for [bid name] — four items for kickoff.” Body:
- One bullet per item, with a name attached. “Engineering lead PTO conflicts with technical architecture answer — Sarah, can you cover or do we move the answer date?”
- The fresh-artifact items, with a deadline. “SOC 2 report is 11 months old, buyer wants under 12 — finance needs to confirm new report lands by Aug 1.”
- The bid-shape decisions, listed for the kickoff agenda. “Requirement 4.2.7 asks for FedRAMP High — we are FedRAMP Moderate. Discuss bid posture in kickoff.”
- The cheap items, pre-assigned. “Requirements 2.1 through 2.4 match prior bid X — assigning to Mike with prior answers attached.”
Send it Sunday night. Monday’s kickoff has an agenda. Tuesday’s writers have a starting point. The four things that would have surfaced in week three surface in week one.
What this is not
It is not a substitute for the actual kickoff. It is a pre-read.
It is not a substitute for the compliance matrix. It is a stress test of the matrix against time.
It is not heroic. It is fifteen minutes. The work that pays off most in proposal management is almost always not heroic — it is the small ritual that surfaces a four-day problem in week one instead of week three.
If you do not have a current ritual that does this, try the next one. The Sunday cost is fifteen minutes. The week-three cost of skipping it is, in our experience, somewhere between half a day and a lost bid.