Everybody assumes that the majority of an RFP response timeline should be devoted to the writing.
And yes, of course, the writing is very important. But there are many other pieces of the puzzle that contribute to a win. Pieces that take more time than we realize.
So, what does an effective response timeline look like? How much time does the proposal team need AFTER the first pass of technical writing is done?
On this episode of The RFP Success Show, I share my best practices for planning a successful response timeline, explaining why it’s crucial to get started right away—even if you decide not to bid.
I describe the challenge of compiling a response with multiple contributors, discussing how many days to build into a response timeline for strategy reviews, editing and formatting, final look and submittal.
Listen in for insight on building weekends, holidays and vacations into a response calendar and learn how to position yourself for a win by making sufficient time on the back end to finalize an RFP response.
Why it’s crucial to start on a proposal ASAP (even if you decide not to bid)
The challenge of compiling a response with multiple contributors and what to do about it
How many days to build into a response timeline for strategy review
My rule of thumb around how long to devote to editing and formatting an RFP response
Why I recommend building in an extra day for a final look and submittal
Why you need 10 to 14 days after the first pass of technical writing is done to position yourself for a win
How to work weekends, holidays and vacations into your response calendar
The importance of assigning a backup for every key person on the response team
What leaders can do to hold people accountable for meeting deadlines on a proposal response
Why we underestimate how much time it takes to finalize an RFP response
The RFP Success Company on YouTube
The RFP Success Company on LinkedIn
Email podcast@rfpsuccess.com
Email podcast@rfpsuccess.com
