How To Write Proposals That Get Accepted By Difficult Evaluators

What’s your success ratio with proposals?

25% is the average. Very few get over 50%. I help government agencies to evaluate proposals. Most bids that come across my desk make the same errors, use the same flawed strategies and are never accepted. And the next time, they repeat the same mistake. Here are some ways to avoid this. It’s not painful, it just requires effort.

Download Now for only $19.99

Download Template

Learn more about these Proposal Templates ]

What does a Proposal Evaluator Do?

My job is to reject your proposal. I fail proposals if they miss a requirement, avoid a clause or get the figures wrong. We received 36 proposals for the last RFP. Some were over 300 pages. The less I have to review, the better.

Tip: make sure the proposals are well-bound. We scribble all over them, book-marking pages, and adding comments. Don’t use cheap papers and poor ring-binders. If they fall apart, I’m not going to re-assemble your document.

  • I eliminate proposals that don’t measure up. This means they fail on a technicality, are over budget, don’t agree to the deadline or have omitted to include some document.
  • Then I review what’s left and make a short list.
  • For me, evaluating a proposal is a process of elimination, not a process of selection. That happens later.
  • When you start your proposal, don’t focus on getting selected, instead WRITE A PROPOSAL THAT CANNOT BE ELIMINATED!

Here’s how you can do this:

  • Write your proposal so that the evaluator cannot reject it on a technicality.
  • Respond to every requirement in the Request For Proposal (RFP). This means you cannot be dis-qualified on the grounds that you were “non-responsive to the RFP.”
  • Identify the solution. If it’s a product, name it & give the version number.
  • Don’t be vague. State clearly how you will do this. If possible, describe the solution in a single sentience.
  • Demonstrate that you have provided this expertise in a similar project.
  • Support you claims with case studies, white papers and other reports where you are given credit.
  • Provide pen portraits of your team. CVs go in the appendix.
  • List the benefits that your solution provides. Cross-reference these against the requirements. Itemize and prioritize each benefit.

Remember, the evaluators are looking for ways to disqualify you.

Conclusion

Write the proposal so that it cannot be eliminated.

Once you have this established, then drill-down into each requirements and respond from the perspective of the reader. Regardless of how good you think your proposal is, if you overlook a technicality, you’re out.

What have I missed? Let me know what you think below.

Thousands of templates to jump start your project

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan