RFP preparation checklist for instruction compliance and complete attachments

A practical RFP preparation checklist is not a motivational poster. It is the minimum set of checks that stop avoidable disqualification: instructions, mandatory attachments, naming, portals, and sign-offs.

Most teams believe they basically follow instructions. Then a pricing form is missing, a font rule is ignored, or a security workbook is uploaded under the wrong filename. The evaluation committee never debates your win themes. You are already out.

This checklist is written for the person who actually builds the binder. Teams that later standardize on Tribble usually start by making these gates real objects, then wiring tooling around them.

How should you use a preparation checklist without theater?

Copy the gates into your bid tool or a shared sheet that people actually open. Every row needs an owner, a due time, a status, and an evidence link such as a file, ticket, or screenshot. If a row cannot show evidence, it is not done. Status values should match the rest of your response system so people are not translating across tools under stress.

Run the checklist at three gates: open on day zero to day one, freeze about forty-eight hours before due, and submit in the final hour. Do not invent a fourth war room if the three gates are honest. Pair the checklist with your broader RFP response strategies so the desk knows which packages even deserve the full gate sequence.

Theater happens when the checklist is a PDF nobody updates. Kill theater by requiring evidence links and reviewing misses weekly. Tie coordinator quality to defect rate, not speed alone. Celebrate the person who finds a missing attachment on Tuesday. That find is worth more than late-night heroics on Friday.

What happens in Gate 1 when you open the RFP?

Gate 1 is where most future pain is either prevented or baked in. Save the source package immutable as the original zip, PDF, or portal export. Extract instructions into a one-pager covering due date, time, timezone, portal versus email, page limits, formatting, mandatory forms, Q and A deadline, and blackout rules. List mandatory attachments with exact names if specified. Identify evaluation criteria and weights if published. Create the requirements matrix skeleton even if rows are empty.

Assign package roles early: instructions owner, matrix owner, narrative owner, security owner, pricing owner, and final submitter. Confirm bid or no-bid against kill criteria before the desk invests a week. Log buyer questions before the question deadline. Create the attachment manifest with expected files, owners, and status. Open exception capacity with SMEs for likely hard stems using your SME exception path.

Gate 1 fails silently when people start drafting narrative before the manifest exists. That is how Appendix C becomes a Friday invention. A strong coordinator blocks narrative kickoff until Gate 1 shows green on instructions and attachments, even when an AE is impatient. Impatience is cheaper on day one than humiliation on day five.

What happens in Gate 2 as you build and freeze?

Gate 2 is production with a freeze that people respect. Map every mandatory question to a stem ID or draft slot. Pull approved stems from the governed library first. Flag gaps as exception states, not silent blanks. Attach evidence tickets for security and compliance claims via a ticketed evidence loop. Draft narrative only after matrix coverage is known through requirement alignment.

Build the executive summary so it mirrors scored themes, not marketing fluff. Cross-check RFI and security language for contradictions. Validate filenames and file types against instructions. Run page, word, and format limits on the real export, not only the working doc. Freeze content for non-exception stems at T-48h and route remaining risk through an exception-only review queue.

Freeze is a kindness. Without it, every section stays soft forever and the final hour becomes fiction under pressure. Announce freeze in the opportunity channel with a short list of still-open exceptions so nobody is surprised. If sales tries a side edit after freeze, treat it as an exception reopen with owner and clock, not a quiet overwrite.

What happens in Gate 3 on submit day?

Gate 3 is cold verification, not creative writing. Re-read instructions with a different person than the primary drafter. Confirm the attachment manifest is complete with checksums or portal uploaded proof. Run a portal test upload if allowed. Confirm pricing forms are signed by the named authority. Confirm legal and security conditionals still sit inside written limits.

Remove internal comments and draft watermarks. Archive the final package hash or frozen folder. Save the submit receipt. Write back new or changed stems to the library within forty-eight hours. Run a same-week retro on checklist misses while memory is fresh.

The cold reader is sacred. If the same person who built the package also certifies it, you will miss what you normalized. Rotate cold readers across packages so the habit stays sharp. When a cold reader finds a defect, log it as a Gate 1 or Gate 2 miss so the system learns, not only the individual.

Scenario: The missing Appendix C

Due Friday at 5pm buyer local time. Thursday at 3pm the coordinator says the package is done because the narrative PDF looks polished and the pricing sheet is signed. The attachment manifest was never finished. Friday at 11am a quiet reader asks where Appendix C, the mandatory implementation plan, lives. It was discussed in Slack on Tuesday, never assigned, never put on the manifest. The team produces a thin appendix in four hours. Evaluation scores implementation last. The deal was not lost on product. It was lost on checklist discipline.

Strong path: Appendix C was on the day-zero manifest with an owner and a Wednesday freeze. If blocked, the bid desk knew Wednesday, not Friday. The owner either delivered a real plan or escalated for scope relief. The final cold reader checked the manifest line by line against the portal file list. Nothing optional was treated as mandatory, and nothing mandatory was treated as optional. Timezone math was confirmed against buyer local time, not the coordinator's laptop clock. Portal filename rules were tested on Thursday with a dummy upload when the portal allowed it.

After submit, the strong desk still spends twenty minutes on write-back and defect logging. The missing-appendix near miss becomes a permanent Gate 1 row with a validator field. Next quarter a new coordinator does not rediscover the scar by losing another deal. Managers coach from the manifest, not from a vague sense that people should be more careful.

How do attachment manifests prevent Friday surprises?

An attachment manifest is a table of reality. At minimum track file ID, required name, owner, source system, status, validator, and notes. Example rows cover technical volume PDF, security workbook, and pricing form. If a file is not in the table, it does not exist for package purposes.

When automation helps, it should parse instructions into checklist rows, validate required files present, block submit when the manifest is incomplete, bind stems to evidence tickets, and preserve export fidelity to Word or PDF. Automation should not invent missing attachments, mark compliance done without a human validator on Gate 3, or hide exception stems inside a false complete dashboard. For tooling context see RFP response automation and the proposal management software buyer's guide.

Common failure patterns include working-doc blindness where the Google Doc looks fine while the export breaks fonts and tables of contents, timezone math failures, optional questions treated as mandatory and the reverse, portal character limits ignored until paste fails, same-as-last-year attachments with stale legal entities, security workbooks answered without evidence, and dual packages by email and portal shipping different versions. Design the checklist so those failures are hard to miss.

Where Tribble fits

Tribble helps teams keep package state, stem state, and exception state in one operating surface so the checklist is not a ghost document beside the real work. Coordinators can see what is blocked, what is approved, and what still needs a human without rebuilding status in Slack. That does not remove the need for a cold final reader. It makes the strong path the default path when volume rises.

Tribble also helps when two tools used to disagree: the proposal draft and the security workbook. With shared stems, owners, and review state, a bake-off reviewer can see the same limits a customer will read later. That is the product fit that matters under volume: faster assembly without a second shadow truth system living in chat.

If your volume is tiny, a disciplined sheet can still win. If your volume is real, a checklist without system state becomes theater the moment two RFPs overlap. Connect checklist discipline to a governed answer layer rather than a library-first pile of unmanaged pastes.

FAQ

What to do this week

Take one live RFP. Build the full gate checklist with owners today. Run Gate 1 before any narrative drafting. Report defects found before submit and write the worst defect into next week's standing Gate 1 rows.