Data calls typically occur early in the proposal effort, but can ostensibly happen at any point during the proposal planning or writing processes.
A common problem with proposal teams is that it is so easy for authors to avoid communicating—particularly when one or more author is working virtually.
Successful proposals must be two things: compliant and responsive.
Storyboards have long been a part of our standard proposal best practices. We all know that the proposal giants include storyboarding as an integral part of the proposal development process, but where did this concept of storyboards originate?
There is a common misconception that developing a compliant proposal is relatively easy — you just follow the instructions in Section L of the Request for Proposal (RFP), the way Dorothy and Toto in The Wizard of Oz followed the yellow brick road.
So, you’re about to start proposal writing for the first time. Maybe you’re transitioning careers, or maybe you’re a recent college graduate, stepping into government contracting culture for the very first time.
Tight page limitations are becoming a more frequent challenge as contracting officers continue to look for ways to streamline their acquisition processes.
Did you know that Microsoft has a staggering 1.2 billion Microsoft Office users worldwide? These users include millions of professionals who rely on Microsoft Office software every day and use only a fraction of its capability.
As proposal professionals, we know that compliance is king, but did you know that MS Office has tools to help you work smarter AND achieve compliance?
We know that Evaluators evaluate and score submitted proposals. Therefore, as bidders looking to win work, we should aim to make the evaluators’ jobs as painless as possible.
It seems that the trend in Requests for Proposals (RFPs) these days is to provide prospective offerors with a voluminous Statement of Work (SOW) or Performance Work Statement (PWS) and then give them minimal page count in which to address it in the proposal.