Page limits are OK, but be reasonable.
AdminACT-IAC
(Admin, Better Government IT)
shared this idea
2 comments
-
Noah Nason III
commented
Let’s face it. The proposal costs go into O/H and the Government ends up paying. Reducing proposal effort is a great way to eventually reduce costs. Once way in which NASA reduced effort was to have a spreadsheet listing all tasks and subtasks. The contractor would them go thru and they would note for each a “yes/no/ or yes with comments.” Of course everyone said yes but most had comments. All assumptions were required to be in the comments and separately listed each time they were applicable. Contractors were given a page limit (a reasonable amount based on complexity of job) as attachments to this spreadsheet to amplify their approach. This method eliminated the need for a compliance crosswalk between the proposal and the SOW. It also made analysis of the proposal much easier. A limited preamble/executive summary was allowed. All-in-all this approach reduced cost to produce proposals and cost to evaluate them (both good things.)
-
ScubaBuddy
commented
Page limits need to be consistent with the complexity of the deal. Do not expect to get good response when Section C is 70 pages, but responses are limited to 5-10 pages. Use Section L to provide specific guidelines on what you would like to see. When possible, tables can provide concise responses to specific requirements and allow for shorter response.
