RFP and proposal checklist (pre-submission)
Short answer: A pre-submission proposal checklist is the final set of checks you run before submitting an RFP response. It confirms the response is compliant (every instruction followed, every requirement answered, every form signed), accurate (facts, names and numbers checked), consistent (price matches scope; cover letter matches the compliance matrix) and delivered correctly (right format, right portal, before the deadline). Run it at least one business day before the due date, and give each item an owner.
In Iris: before export, "Notify Unapproved" nudges everyone who still has open, unapproved answers, in one click.
Who this is for: proposal coordinators and managers doing the final check on an RFP, RFQ, tender or security questionnaire response.
On this page
- When should you run the checklist?
- The 45-item pre-submission checklist
- Which mistakes are fatal?
- How do you run the final check as a team?
- FAQ
When should you run the checklist?
| Checkpoint | When | Which sections |
|---|---|---|
| Kickoff | Day 1–3 | A (compliance setup) |
| After drafting | Before red-team review | B (content) |
| Final check | Internal deadline, ≥ 1 business day before due | All, especially C–F |
| Post-upload | Immediately after submitting | F (confirmation) |
The 45-item pre-submission checklist
★ = fatal if missed in most formal RFPs (can make the bid non-responsive). Download the checklist (XLSX) · Download the printable checklist (PDF)
A. Compliance with instructions
| # | Check | Owner | ★ |
|---|---|---|---|
| 1 | Every addendum and amendment received, read and acknowledged as required | Proposal manager | ★ |
| 2 | Response follows the prescribed outline and numbering | Proposal manager | |
| 3 | Every requirement in the compliance matrix has a response location | Proposal manager | ★ |
| 4 | Page limits met per volume or section | Coordinator | ★ |
| 5 | Font, margin and file-format rules followed | Coordinator | |
| 6 | Mandatory minimum qualifications met and evidenced | Proposal manager | ★ |
| 7 | Answers to the buyer's Q&A reflected in the response | Proposal manager | |
| 8 | Price kept out of non-price volumes if required | Coordinator | ★ |
B. Content quality
| # | Check | Owner | ★ |
|---|---|---|---|
| 9 | Every question answered; no blanks, "TBD" or placeholders | Writers | ★ |
| 10 | Each answer responds to the question asked, not a nearby one | Reviewers | |
| 11 | Yes/No questions answered Yes or No first, then explained | Reviewers | |
| 12 | Partial compliance stated honestly with the gap and plan (examples) | SMEs | |
| 13 | Win themes appear in the executive summary and key sections (guide) | Proposal manager | |
| 14 | Claims are backed by proof (reference, metric, certificate) | Reviewers | |
| 15 | Technical answers checked by the SME who owns them | SMEs | |
| 16 | Security answers match current policies and evidence | Security lead | |
| 17 | No other customer's name anywhere (search the files) | Coordinator | |
| 18 | Buyer's name, RFP number and title correct throughout | Coordinator | |
| 19 | Terminology consistent (product names, buyer's terms) | Editor | |
| 20 | Commitments (dates, SLAs, deliverables) are ones you can keep | Sales lead | |
| 21 | Executive summary written last and matches the final response | Proposal manager |
C. Pricing and commercial
| # | Check | Owner | ★ |
|---|---|---|---|
| 22 | Buyer's price form used without structural changes | Finance | ★ |
| 23 | Every price cell completed; totals recalculate correctly | Finance | ★ |
| 24 | Price matches the scope, staffing and schedule in the technical volume | Finance + PM | |
| 25 | Assumptions and exclusions stated | Finance | |
| 26 | Price validity period meets the RFP's minimum | Finance | ★ |
| 27 | Contract exceptions listed where the RFP requires, approved by legal | Legal | ★ |
D. Forms, signatures and attachments
| # | Check | Owner | ★ |
|---|---|---|---|
| 28 | All required forms completed (certifications, representations, questionnaires) | Coordinator | ★ |
| 29 | Signatures from an authorized signer, dated | Executive | ★ |
| 30 | Notarization, if required | Coordinator | ★ |
| 31 | Insurance certificates, licences, registrations attached as required | Coordinator | |
| 32 | Résumés for named key personnel attached and matched to requirements | PM | |
| 33 | References with current contact details (with permission) | Sales lead | |
| 34 | Security evidence (SOC 2 report or bridge letter, pen test summary) attached if requested (evidence checklist) | Security lead |
E. Formatting and production
| # | Check | Owner | ★ |
|---|---|---|---|
| 35 | Cover page and cover letter complete and correct | Coordinator | |
| 36 | Table of contents updated; page numbers correct | Coordinator | |
| 37 | Headers and footers show the RFP number and your company name | Coordinator | |
| 38 | Cross-references point to the right sections | Editor | |
| 39 | Tracked changes accepted and comments removed | Coordinator | ★ |
| 40 | File metadata (author, previous customer names) cleaned | Coordinator | |
| 41 | Files named as instructed and under any size limit | Coordinator | ★ |
| 42 | Proprietary-information markings applied as the RFP specifies | Legal |
F. Submission
| # | Check | Owner | ★ |
|---|---|---|---|
| 43 | Portal account working; upload tested before the deadline day | Coordinator | ★ |
| 44 | Submitted before the deadline (check time zone), or hard copies delivered with the right number of copies | Proposal manager | ★ |
| 45 | Confirmation received and saved; submitted files archived | Coordinator |
Which mistakes are fatal?
The ★ items are the ones that commonly make a response non-responsive: missing an addendum acknowledgement, a missing signature or form, an altered price form, blank required fields, page-limit overruns, a late submission. Content quality decides whether you win; compliance decides whether you're evaluated at all.
| Failure | Typical consequence |
|---|---|
| Late submission | Usually rejected without evaluation |
| Missing mandatory form or signature | Often non-responsive |
| Addendum not acknowledged | Can be non-responsive |
| Over page limit | Excess pages may not be read |
| Content error (wrong customer name) | Not disqualifying, but costly to credibility |
How do you run the final check as a team?
- Split the list by owner and send each person their rows with a deadline.
- Run sections C–F with fresh eyes. The person who built the document shouldn't be the only one checking it.
- Search, don't read, for names: search the files for every recent customer's name and the previous buyer's RFP number.
- Recalculate price from scratch, not by checking totals visually.
- Upload early. Many portals allow replacing a submission until the deadline.
- After submission, add any new, approved answers to your answer library.
How Iris helps
Iris is AI software for RFPs, security questionnaires and proposals.
- See what's still open. Per-question reviewers, approval history and bulk approve, and "Notify Unapproved" to nudge everyone with open work in one click. Route answers through review before export.
- No silent blanks. When your content doesn't support an answer, Iris says "There is not enough information to answer the question," flags it as Missing Info, and won't let it be approved as-is.
- Old customer names removed. Iris strips other customers' names out of reused past answers.
- Back into the original file. Export into the original Excel workbook, a branded Word template, CSV, or onto the source PDF, with cited files and attachments if you choose.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.
FAQ
What is a proposal checklist?
A list of checks run before submitting a proposal to confirm it's compliant, accurate, consistent and delivered correctly.
What should an RFP checklist include?
Compliance with instructions, content quality, pricing, forms and signatures, formatting, and submission. The 45 items above cover all six.
When should I start the checklist?
Set up the compliance items at kickoff and run the full list at your internal deadline, at least one business day before the due date.
Who should own the checklist?
The proposal manager owns it; individual items belong to the people best placed to check them.
Is this the same as a checklist for writing an RFP?
No. This checklist is for vendors submitting a response. Buyers writing an RFP need a different list.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
