Are you making these 7 proposal writing mistakes

7-proposal-writing-mistakes

It’s easy to become snow-blind when writing a business proposal, especially if you are performing more than one role in the team. And if you’re new to proposal development, bidding, and grant applications that are many pitfalls to avoid. Some are predictable, others less so.

7 Proposal Writing Mistakes for Beginners to Avoid

Here are some to avoid:

Before submitting your proposal, ask yourself the following questions:

  1. Specific – Does your proposal clearly identify a specific problem – or set of needs – that you intend to address? Put yourself in the reader’s shoes. Will they understand from the opening sentence what you’re offering?
  2. Narrative – Don’t try to be all things to all people. Keep the narrative focussed and, if you are covering several areas, link the topics together so they dovetail into your message. Also, remember to tie together your executive summary and the closing summary. They’re two sides of the same coin.
  3. Transparent – If you are bidding for part of a larger piece of work, for example, the security aspect of a software system, highlight this upfront. Don’t try to hoodwink the evaluators by creating any type of ambiguity.
  4. Guidelines – Are you clear on the funder’s guidelines? In other words, make sure your bid isn’t disqualified by omitting a specific requirements, for example, the need to submit several hardcopies instead of one, or financial documents that must be submitted.
  5. Make Contact If you have read their guidelines and are still unsure, call them up and look for clarification. Don’t be shy. Your competitors are doing this as well.
  6. Support your claims. It’s not enough to say you can deliver a product or service. Give evidence to prove it. For example, if it’s technical, include the fact sheets and any independent assessments.
  7. Trash Talk – it’s not unusual to know who you’re up against, especially if you’ve been shortlisted or made presentations. And it can be tempting to highlight a weakness in their product or a project where they fell down. It’s very tempting. Don’t. Avoid making any derogatory remarks about competitors. It reduces you in the evaluator’s eyes.

While this may seem obvious, when working on large projects, for example, where they are several writers contributing to the final document, make sure that none of them have spoken unprofessionally about your competitors. It’s something you made need to stress with younger team members or someone you suspect has a grudge against a competitors.

And, of course, for legal reasons, it’s best to nip these comments in the bud.

Credit: photo ~ gabilm

Free and Premium MS Word, Excel and Apple iWork Templates

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