How to Collect RFP Process Feedback From Your Team

How to collect RFP process feedback from your team

A predictable, repeatable process for responding to RFPs helps your team work efficiently and win more business. But as your organization grows and your team gains experience, that process needs to evolve too. The only way to know what to change is to ask the people doing the work.

Responding to a 500 question RFP is tedious and time consuming, so it matters a great deal that any change to the process has buy in from the whole team before it rolls out. Skipping that step is how new tools and new steps quietly get ignored three weeks after launch.

Here are three practical ways to collect useful feedback as you evolve your RFP process.

Build a detailed plan for collecting feedback

Content management and RFP response work look different at every company. Depending on the size of your organization, a single person or an entire team might own one or more stages of the response process: intake, content gathering, drafting, subject matter expert review, compliance check, design, and final submission.

When you collect feedback, break each stage of your response process into its own category for discussion. That keeps the review thorough and makes sure no stage, step, or team member gets overlooked. Set aside dedicated time and space, virtual or physical, for your team to share their experiences, positive and negative, about each stage.

A few things to keep in mind:

Comb through every step, method, and tool your team uses to respond to RFPs, not just the ones you suspect are broken.

Aim to pair every problem raised with at least one possible solution, even a rough one, so the conversation moves toward action.

Use the right tools to gather input

Once you have a plan, choose tools that fit your organization and your team's working style. A short survey is usually the easiest way to start: a handful of focused questions about where people see room for improvement can open up a much bigger conversation. You can send a single survey covering the whole process, or break it into shorter surveys tied to specific stages, like content gathering or SME review.

Several established platforms support this kind of structured feedback collection, including 15Five, Qualtrics, and Google Forms.

After the survey closes, bring the team together to talk through the results as a group. Schedule a time that works for everyone and use a format people can actually participate in. In person, a whiteboard session with sticky notes works well for capturing pros, cons, and suggestions stage by stage. Remote teams can do the same thing with a shared document or a virtual whiteboard.

A few things to keep in mind:

Schedule the discussion, in person or online, at a time that genuinely works for the full team, not just the leads.

Use platforms or spaces that are accessible to everyone involved, including anyone working remotely or on a different schedule.

Comparing feedback collection methods

Create a safe space for open communication

Honest feedback only happens if people feel safe giving it. Start by being honest yourself. Acknowledge what is not working before asking the team to do the same: something like "we are completing every RFP that comes in, but a few of us are stretched too thin to do it well." That framing signals there is room for improvement at every level, including yours, and it lowers the stakes for everyone else to speak up.

As people share their opinions and experiences, stay receptive and avoid getting defensive, even when the feedback touches something you built or approved.

A few things to keep in mind:

Give your team room to voice opinions about the RFP process without fear of repercussions.

Treat constructive criticism as something that applies to everyone on the team, leads included.

Turning feedback into a better RFP process

Collecting feedback is only half the job. The other half is acting on it, ideally with a system that makes the next round of changes easier to track and roll out. A response management platform gives your team a single place to manage content, assign questions, and track where bottlenecks are actually happening, so the next feedback cycle has real data behind it instead of just impressions.

If you are ready to put a more structured process in place, RocketDocs is backed by decades of industry experience helping proposal teams improve their RFP process. You can also see how defined roles and responsibilities make the next stage of process improvement easier to manage.

Frequently asked questions

How often should we collect feedback on our RFP process?
Most proposal teams benefit from a structured feedback cycle once or twice a year, with a lighter check in after any major or high stakes RFP.

Who should be involved in giving feedback on the RFP process?
Everyone who touches a stage of the response, including proposal managers, subject matter experts, reviewers, and anyone in design or compliance, should have a chance to weigh in.

What is the best way to start if we have never collected feedback before?
A short, anonymous survey with a handful of open ended questions is usually the easiest first step and tends to surface the most candid responses.

How do we keep feedback sessions from turning into complaint sessions?
Pair every problem raised with a possible solution, and keep the group focused on specific stages of the process rather than general venting.

What if team members are afraid to be honest in a group setting?
Offer a one on one or anonymous option alongside any group discussion, since some people will only raise sensitive issues privately.

How do we know if a change to our RFP process actually worked?
Set a follow up checkpoint, usually after the next one or two RFPs, and ask the team directly whether the change helped, hurt, or made no difference.