Now I do it for everyone else bidding correctional and public safety work. Compliance matrices, transition schedules, personnel charts, architecture.
I know what these have to survive.
Four years designing RFP responses for a correctional vendor. The content arrived finished — my job was the page.
So let me be straight about the line. I don't write your technical approach, I don't know your evaluators, and I won't tell you what wins. Your capture people know that and I don't.
What I know is the production side, which is where most of these documents come apart. Page limits that don't fit the content. Word templates that break the moment a real graphic lands in them. A compliance matrix retyped by hand at one in the morning because an addendum moved three requirements. Evaluation copies coming out of a county photocopier in black and white.
I do: compliance matrices, transition and cutover schedules, key personnel charts, system architecture, past performance layouts, and production of the volume itself.
I don't: write your technical approach, build your price, or tell you whether to pursue.
Exhibit A — Compliance matrix
The column has to fit the full requirement language, at a size a person can actually read, inside a one-page limit. That's a typesetting problem. It usually gets solved by cutting the text, which defeats the point of the table.
| RFP ref. | Requirement, verbatim | Response | Rev. | Status |
|---|---|---|---|---|
| 3.2.1 | Provide continuous recording of all non-privileged inmate calls with 100% retention for the contract term | Vol. II, p. 14 | Add. 2 | Compliant |
| 3.2.4 | Maintain attorney–client privilege designation and exclusion workflow | Vol. II, p. 21 | Add. 2 | Compliant |
| 3.4.0 | Complete installation and full cutover within ninety (90) calendar days of notice to proceed | Vol. II, p. 33 | — | Compliant |
| 3.6.2 | Provide on-site technician response within four (4) hours for Priority 1 incidents | Vol. II, p. 48 | Add. 1 | Compliant |
| 5.0.3 | Demonstrate three (3) years' experience at a facility of comparable average daily population | Vol. I, p. 9 | — | Compliant |
Condensed face at 9.5 pt. Full requirement language fits without truncation inside a one-page limit.
Revision column so your capture lead can re-verify after each addendum instead of re-reading the volume. There are always addenda.
Exhibit B — Transition schedule
A schedule this dense has to survive being skimmed and then photocopied. The vertical marks the cutover. The hatched band is the dual-run window — whatever your team wants emphasised gets the structural treatment, not a colour swatch.
Hatched band is the dual-run window, when both systems are live. Flagged as its own device because your team will want it found immediately.
Nothing carried by colour alone. Evaluation copies get printed in mono more often than anyone plans for.
Exhibit C — Key personnel
Staffing charts here carry things a corporate org chart doesn't — on site versus remote, cleared versus not. Whatever distinctions your team needs marked, I build into the structure with weight and position rather than colour, so none of it is lost in reproduction.
Exhibit D — Past performance
Your team knows which figures a solicitation screens on — usually population and term. Those lead, at a size that can be read across a table, and everything else supports them.
Three records to a page, hairline-separated rather than boxed. The card grid most vendors use burns vertical space a page-limited volume can't spare. Client names redacted here, as they would be anywhere I can't get release.
Exhibit E — System architecture
Technical diagrams go to an IT reviewer and get skimmed by everyone else. My job is making sure the one point your team wants emphasised is the thing that reads first. Here it's custody of the recordings. I've seen vendor diagrams with fourteen boxes where you can't tell what the point was.
Whatever your team flags as the load-bearing point gets stated in plain language at the bottom of the plate, rather than buried inside a box.
Kickoff, not the night before.
Addendum 3 issuedNot because it's more work. Because arriving late means reformatting, and reformatting is the expensive way to buy a worse document. If the matrix is built first and the graphics are planned against the page limits, everything downstream is cheaper.
A typical engagement is one pursuit, kickoff through submission — matrix, graphics package, volume layout, and the production file in whatever form the solicitation demands. Addenda handled inside the engagement.
Commissary, food service, correctional healthcare, tablets and education, transport, reentry, detention technology, and adjacent public safety. Comfortable with county, regional, and state DOC formats.
Specimens use invented facilities, vendors, and figures. Redactions are a design device, not a disclosure — no former employer's confidential material appears here in any form.