Play 4 Workflow Diagram (Visual)

This workflow maps the complete RFP response process from intake through submission. Use it to identify bottlenecks, assign clear ownership, and eliminate the chaos that kills proposal quality.

Step 1: Capture RFP Details

When an RFP arrives, log it immediately in your tracking system (Monday.com, Smartsheet, or a dedicated proposal tool like Loopio).

Required fields:

• Client name, industry, decision-maker contact
• Submission deadline (date + time + timezone)
• Submission method (portal URL, email address, physical address)
• Page limit, format requirements (PDF, Word, bound copies)
• Evaluation criteria with point values
• Estimated contract value and duration

Decision Point: Is the deadline realistic? If you have less than 5 business days for a complex RFP, flag it immediately for partner review.

Step 2: Run Go/No-Go Assessment

Schedule a 30-minute go/no-go call within 24 hours of receipt. Attendees: practice leader, BD director, proposal manager.

Evaluate using these criteria:

• Win probability: Do we have existing relationships? Have we done similar work? Are we on the shortlist or cold bidding?
• Strategic fit: Does this client/sector align with our 3-year growth plan?
• Resource availability: Can we staff this without pulling people off billable work?
• Margin potential: Will this hit our target 35%+ margin after accounting for proposal costs?

Decision Point: No-go if win probability is below 30% or if two or more red flags exist. Document the decline reason in your CRM

Step 3: Assign Core Team

If proceeding, assign roles immediately:

• Proposal Manager: Owns timeline, coordinates reviews, manages submission
• Technical Lead: Senior person who will lead the engagement if won
• Writer/Editor: Dedicated resource (internal or contractor) for content development
• Pricing Lead: Partner or director who owns budget and pricing strategy
• Designer: For layout, graphics, and final formatting

Send calendar holds for kickoff (within 48 hours) and all review milestones.

Step 4: Conduct RFP Teardown

The proposal manager leads a 90-minute working session to dissect the RFP.

Create a compliance matrix in Excel or Google Sheets:

• Column A: RFP section number and requirement
• Column B: Page limit for that section
• Column C: Assigned writer
• Column D: Due date for first draft
• Column E: Compliance status (compliant/non-compliant/needs clarification)

Flag any requirements you cannot meet. Decide whether to request a waiver or take an exception.

Step 5: Build Win Themes

Identify 3-5 win themes that will thread through your entire response. These are not generic ("we're experienced") but specific to this client's situation.

Example win themes:

• "We've implemented this exact system at 4 peer institutions in your state"
• "Our team includes the former CFO of your largest competitor"
• "We can start 2 weeks faster than typical because we have pre-cleared resources"

Document these in a one-page strategy brief that every writer receives.

Step 6: Create Content Outline

Break the RFP into sections and assign word counts. A typical structure:

Executive Summary (2 pages):

• Client's challenge in their words
• Your solution approach in 3-4 bullets
• Why you (win themes)
• Pricing summary

Technical Approach (40% of page count):

• Methodology
• Deliverables with acceptance criteria
• Timeline with milestones
• Risk mitigation

Qualifications (30% of page count):

• Firm overview (brief)
• Team bios with relevant project examples
• Case studies (2-3, highly relevant)

Pricing (separate volume if required):

• Fee summary table
• Assumptions and exclusions
• Payment terms

Assign each section to a specific writer with a due date 5 days before final submission.

Step 7: Draft Content

Writers work independently using the content outline and win themes document.

Provide writers with:

• Compliance matrix showing their assigned sections
• Win themes strategy brief
• 3-5 relevant past proposals for reference (redacted)
• Client research packet (annual reports, news articles, LinkedIn profiles)
• Style guide (active voice, client-focused language, no jargon)

Quality checkpoint: First drafts must be complete, not placeholder text. "We will provide excellent service" is not a draft.

Step 8: First Review Cycle

Proposal manager reviews all sections for:

• Compliance with RFP requirements
• Consistency with win themes
• Logical flow and transitions
• Responsiveness (are we answering what they asked?)

Return feedback within 24 hours. Use track changes and specific comments, not vague requests like "strengthen this section."

Step 9: Technical Review

Technical lead reviews for:

• Accuracy of methodology and approach
• Feasibility of timeline and deliverables
• Appropriateness of team composition
• Realism of assumptions

This is where you catch promises you cannot keep.

Step 10: Executive Review

Practice leader or partner reviews for:

• Alignment with firm positioning and brand
• Competitive differentiation
• Pricing strategy and margin
• Overall persuasiveness

Decision Point: If the executive review reveals major strategic issues, stop and regroup. Do not proceed to formatting with a flawed strategy.

Step 11: Design and Layout

Designer imports final text into InDesign or Word template.

Production checklist:

• Apply brand fonts, colors, and style guidelines
• Insert graphics, charts, and team photos
• Add headers, footers, and page numbers
• Create table of contents with hyperlinks
• Ensure consistent formatting across all sections

Time allocation: Allow 8-12 hours for design and layout of a 50-page proposal.

Step 12: Final Proofread

Assign two people who were not involved in writing to proofread the formatted document.

Proofing checklist:

• Spell check and grammar check (use Grammarly or similar)
• Verify all client names are spelled correctly throughout
• Check that all cross-references and page numbers are accurate
• Confirm all required forms and certifications are included
• Test all hyperlinks if submitting electronically

Step 13: Submit

Follow submission instructions exactly. If the RFP says "submit by 3:00 PM local time," that means their timezone, not yours.

Submission protocol:

• Submit 2 hours before deadline to allow for technical issues
• If using a portal, upload a test file first to verify format compatibility
• If emailing, send from a partner-level email address
• If delivering physically, use a courier service with tracking
• Save confirmation receipt (email confirmation, portal screenshot, courier tracking number)

Send a brief follow-up email to the client contact: "We've submitted our response and look forward to discussing our approach with you."

Step 14: Debrief Session

Schedule a 60-minute debrief within one week of submission, regardless of outcome.

Debrief agenda:

• What went well in the process?
• What caused delays or rework?
• Which content sections were strongest/weakest?
• What would we do differently next time?
• What reusable content can we extract for the library?

Document findings in a shared folder. Tag action items with owners.

Step 15: Update Content Library

Extract and save reusable content:

• Strong case studies
• Team bios
• Methodology descriptions
• Graphics and charts
• Pricing models

Store in a searchable repository (SharePoint, Dropbox, or proposal software). Tag by service line, industry, and content type.

Step 16: Track Outcome

When you receive the client's decision:

If you win:

• Document what differentiated your proposal
• Schedule a transition call within 48 hours
• Update your win rate metrics

If you lose:

• Request a debrief call with the client
• Ask specific questions: "What were the top 3 factors in the decision?" "How did our pricing compare?" "What could we have done differently?"
• Document feedback and share with the team
• Update your loss analysis tracking

Bottleneck #1: Late executive review Solution: Schedule the executive review session when you assign the RFP. Make it non-negotiable.

Bottleneck #2: Pricing delays Solution: Develop pricing 48 hours before you need it in the document. Do not wait until the last day.

Bottleneck #3: Scope creep during writing Solution: Lock the outline after the strategy session. Any changes require proposal manager approval.

Time allocation for a typical 50-page RFP with 15-day deadline:

• Days 1-3: Intake, qualification, strategy (20% of time)
• Days 4-10: Content development and review (60% of time)
• Days 11-14: Production and proofing (15% of time)
• Day 15: Submission and buffer (5% of time)

Adjust these ratios based on your team's capacity and the RFP complexity. The key is working backwards from the deadline and building in buffer time for the inevitable last-minute changes.