The Saturday compliance-matrix catch-up
A 45-minute Saturday routine for a shop that missed the Thursday compliance check-in. Five passes over the matrix, with a stop rule at the first unanswerable row.
Sometimes the Thursday compliance-matrix check-in doesn’t happen. The PM was in three other meetings, the matrix was 70% filled, the team agreed to “look at it Friday,” and Friday the team was drafting. Saturday morning, the deadline is Tuesday, and you’re looking at a matrix you haven’t audited in five days.
This is the routine for that Saturday. 45 minutes. Done in coffee.
Pass 1 — coverage scan (10 minutes)
Open the matrix. Filter for rows with no response pointer. Count them. If the number is over 15, stop and call the PM. The bid has a structural problem the Saturday routine can’t fix.
If the number is 1 to 15, write each one’s row identifier down. Those are the rows you’re chasing today.
Pass 2 — easy fills (10 minutes)
For each unaddressed row, ask: is the answer in the response and just not pointed at the row? Often yes. The drafter wrote the paragraph; nobody linked it. Add the pointer.
You’ll knock out roughly half the unaddressed rows in this pass. They’re the bookkeeping failures, not the substance failures.
Pass 3 — KB lookups (10 minutes)
For each remaining row, search the KB for the requirement language. If a block matches, paste the block reference into the response section that should answer the row, and tag it for editor review on Monday. You’re not finalizing — you’re surfacing candidates so the writer doesn’t start cold Monday morning.
Pass 4 — escalation triage (10 minutes)
What’s left? These are the rows that have no easy fill and no obvious KB hit. Open a triage ticket for each, tagged with the row, the deadline (Tuesday minus the review buffer), and the most likely SME owner. The PM will route them Monday.
If a row is not answerable — the buyer asked for a capability we don’t have, or a certification we don’t hold — flag the row red. Don’t try to write around it on Saturday. Red rows are a Monday conversation about whether to bid at all.
Pass 5 — the stop rule (5 minutes)
If you’ve found three or more red rows, write the PM a short email and stop the Saturday work. The bid may not be viable on its current terms, and continuing to fill in the matrix wastes Saturday on a bid that isn’t going out.
If you’ve found zero or one red rows, you’re done. The matrix is in a state Monday’s team can finish. You’ve moved the bid from “scrambling” to “finishing.”
Why this works
The temptation on Saturday is to draft. Drafting is the visible work. Compliance scanning is the invisible work that determines whether the draft gets credit on the buyer side.
The routine is biased toward catching structural problems early, even if it means the bid gets pulled. A bid that gets pulled on Saturday loses the team a weekend. A bid that ships Tuesday with three red rows hidden in the matrix loses the team a deal and the post-mortem time to figure out why.
This is also the routine I ran on the bid that became the October federal FY clock post. Worth the 45 minutes; saved a deadline-day surprise.