RFP response process: how respondent teams run every bid

RFP Tips

Author:

Chris Mabry

Short answer: An RFP response process is the repeatable sequence a respondent team follows from the moment an RFP arrives to submission and debrief. It has nine steps: intake, go/no-go, kickoff, question breakdown and assignment, first draft, expert review, compliance and quality review, final approval and submission, and debrief. A good process names one owner and one output for every step, so nothing depends on a single hero working late.

In Iris: each step has a home: the RFP Analyzer for go/no-go, assignments for experts, citations and confidence labels for review, and export back into the buyer's file.

Who this is for: proposal managers, bid managers and presales leads who want every bid to run the same way.

On this page

  1. What are the steps of the RFP response process?
  2. Who does what? A RACI table
  3. A worked timeline: a 10-business-day bid
  4. Where do RFP processes break?
  5. How do you improve your RFP process?
  6. How Iris supports each step
  7. FAQ

What are the steps of the RFP response process?

 Intake → Go/No-Go → Kickoff → Breakdown & assign → First draft
                                                        ↓
       Debrief ← Submit ← Final approval ← Compliance review ← Expert review
#StepOwnerOutput (artifact)Done when
1IntakeProposal managerBid record: buyer, due date, format, contacts, documentsEvery document and addendum is logged
2Go/no-goSales lead + proposal managerGo/no-go decision with reasonsA named person decides, in writing
3KickoffProposal managerPlan: owners, internal deadlines, win themesEvery contributor knows their sections and dates
4Breakdown and assignmentProposal managerQuestion list or compliance matrix, each row with an ownerNo unassigned rows
5First draftProposal teamDraft answers with sourcesEvery row has a draft or a flagged gap
6Expert reviewSubject-matter expertsCorrected, approved answersEvery gap is answered by an expert
7Compliance and quality reviewProposal manager (second reader)Checked response against the compliance matrixEvery requirement mapped; format rules met
8Final approval and submissionExecutive sponsorSigned, submitted response; receiptSubmission confirmed
9DebriefProposal manager + sales leadWin/loss notes; library updatesNew approved answers saved; lessons logged

Build the compliance matrix in step 4 from our compliance matrix template, and make step 2 consistent with the go/no-go scorecard.

Who does what? A RACI table

R = responsible (does the work), A = accountable (owns the outcome), C = consulted, I = informed.

StepProposal managerSales lead / AESMEs (product, security, legal)Executive sponsorPricing / finance
IntakeA/RC—I—
Go/no-goRACCC
KickoffA/RRCIC
Breakdown and assignmentA/RCI—I
First draftA/RCC——
Expert reviewACR——
PricingCR—CA/R
Compliance and quality reviewA/RCC—C
Final approval and submissionRC—AC
DebriefA/RRCII

Rule of thumb: one "A" per row. If two people are accountable, nobody is.

A worked timeline: a 10-business-day bid

A fictional software company, "Larchmont Systems," receives a 180-question RFP with a 10-business-day deadline.

DayStepWhat happens
1Intake, go/no-goDocuments logged; requirements checked against existing content; sales lead says Go
1Kickoff30-minute call; win themes agreed; internal deadline set for day 8
2Breakdown and assignment180 rows split: 120 proposal team, 35 security, 15 product, 10 legal
2–3First draftDrafts produced from approved content; 22 rows flagged as gaps
3Clarifying questionsSent to the buyer before the question deadline
4–6Expert reviewSMEs answer the 22 gaps and correct drafts; reminders on day 5
7PricingFinance completes the pricing schedule
8Compliance and quality reviewSecond reader checks every requirement and format rule
9Final approvalExecutive sponsor signs the cover letter
9SubmissionSubmitted a day early; receipt confirmed
After awardDebriefApproved answers saved; two weak sections noted

The buffer day matters more than any tool: portals fail and signers travel.

Where do RFP processes break?

SymptomUsual causeFix
Every bid is a scrambleNo go/no-go step; the team says yes to everythingDecide in writing on day 1
SMEs answer lateAssigned by email, no single list, no remindersOne assignment list per person; nudge everyone with open work at once
Same question, different answersLibrary has duplicates and stale versionsOwners and expiry dates on approved answers; resolve contradictions
Last-minute compliance failuresFormat checked at the endBuild the compliance matrix in step 4
Good answers lost after submissionNo debrief stepSave approved answers back to the library at close
Unclear what was promisedCommitments scattered across answersExtract commitments when the project closes

How do you improve your RFP process?

  1. Measure two numbers: time from intake to submission, and how much of each first draft survives review. Improve the second and the first follows.
  2. Add the go/no-go step if you don't have one. Fewer, better bids is the largest gain most teams can make.
  3. Fix the library before buying speed. De-duplicate, assign owners and set review dates.
  4. Give SMEs less to do: send them only the rows that need an expert, with the draft and its source attached.
  5. Hold a 15-minute debrief on every result, win or lose, and update the library the same day.

How Iris supports each step

StepIn Iris
IntakeUpload Excel, Word, PDF or CSV (75 MB per upload), or start from a Salesforce opportunity; group multi-file bids in a Project Hub
Go/no-goRFP Analyzer: summary, key dates, requirements checked against your content (met / partial / likely not met), and a Go, Review or No-Go recommendation from your own criteria
Breakdown and assignmentEvery question extracted as a row; assign questions or sections to people or groups; a My Assignments page per person
First draftDrafts from your Knowledge Map and Approved Answers Library, with citations and a High, Medium, Low or Contradictory label; "There is not enough information to answer the question" where content is missing
Expert reviewComments and @mentions; "Notify Unapproved" nudges everyone with open work in one click
ApprovalPer-question reviewers and approval history; multi-step approval workflows (Review, Approval, Sign-off) are in beta
SubmissionExport into the original workbook, a branded DOCX template, CSV or PDF
DebriefApproved answers feed the library through an inbox; commitments are extracted when a project is finalized; reports show average time to approval and IRIS AI Efficiency (how much of each draft survived review)

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 the RFP response process?
The sequence a respondent team follows from receiving an RFP to submitting it and learning from the result: intake, go/no-go, kickoff, assignment, drafting, expert review, compliance review, approval and submission, debrief.

How long should an RFP response take?
It depends on size and deadline. Plan backwards from the due date and keep at least one buffer day before submission.

Who should own the RFP process?
A proposal or bid manager owns the process; the sales lead owns the go/no-go decision; an executive signs off.

What's the difference between the RFP process and writing the response?
The process is who does what and when; writing is the content. See how to write an RFP response.

How does AI fit into the RFP process?
Mostly in first drafts and review: drafting from approved content, showing sources, and flagging gaps for experts. Keep human approval before submission.

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.