Writing Project Proposals 2016
Writing Project Proposals 2016
Writing Project Proposals 2016
Many donors and funding agencies have their own format for project proposals. Some require a
short concept note, giving an overview of the main elements of the project, prior to submitting
a full proposal. If the response is favourable, resources, time and effort can be committed to
preparing comprehensive documentation. Overviews of topics that are usually addressed in a
proposal are presented below.
Fundamental research (returns expected in 25 years – outcome uncertain)
Applied research (returns expected in 15 years – outcome predictable)
Development (returns expected in 5 years – outcome expected)
Practical execution of a task (returns expected on project completion)
Applied Research, Development Projects and Practical Implementations are usually funded as a
contract with delivery obligations.
All proposals must include certain basic information. These basics include:
Why are you doing this project or why do you want to do this project?
What will you be doing?
How will you be doing it?
Who will be doing it?
Where will it be done?
How long will it take?
How much will it cost?
1
Who are we (organization) and how do we qualify to meet this need?
Proposal Headings
Introduction/Background:
Briefly describes the project and how it developed
This is often considered the most important part of the proposal because it is the reviewer’s
first impression. Even though it appears first, write it last because it is a summary of the
proposal. This section should be concise and cover the description of the project covering
objectives, need, and methodology. It should identify the expected outcomes of the project.
It should also describe the format for the rest of the proposal.
2
Purpose and Objectives:
What will the project accomplish?
What are the objectives and are they measurable?
Why are we considering it?
Indicate the expected outcomes of the project, preferably in measurable terms. This shows
what you will do, for whom, by how much, and by when. When the project is completed, you
will be able to evaluate it and determine whether the project succeeded or not in achieving
its objectives. Identify short-term and long-term objectives.
In this section, include a short description about your organization - past, present, and
projected operations. It should also include the following:
Contact information
Vision and mission of the company/organization
Recent achievements (if applicable)
Short background of the community that will benefit from the project
Background of the management team
Number of staff
Past projects that were previously funded (if applicable) – cite how the funds were
used and its impact to the served community.
The proposed project should be evaluated against the overall strategies of the organization to
ensure that it is properly aligned with your strategic goals.
In this section, include a short description about how the project will support the mandate of
the funder, specifically the areas of focus that are specified for the grant programme.
3
Project Deliverables e.g. Value/Benefits/Messages:
What are the projects deliverables? In other words what will be project produce
What values and benefits will members derive?
What are the messages?
What is its relevance to members?
What is its relevance to customers or clients?
In this section you will want to describe in relative detail the features of each of the project's
products/deliverables. You may wish to separate deliverables into phases and indicate
optional components given time.
The critical part of the proposal and is the longest part. It is a plan of action for how the
objectives will be achieved. This section usually starts with a description of the overall
approach, its relevance, effectiveness, and innovativeness. Then it gives details on
methodology, the population being addressed, and how anticipated problems will be
managed.
Timelines:
What are the timelines e.g. one quarter, one year, multiple years?
Describe how long (days, months) specific tasks or components of the project will take. If
possible, include a milestone chart in this section.
Budget/Resources:
What is the budget?
What is the financial impact?
How is the project to be resourced? (Staff, Engage consultants, partnership, etc.)
What are the estimates of time and money?
Budgets are cost projections. They show the annual and overall cost of the project. A detailed
budget should be divided into categories such as salaries, development of training materials,
capacity building activities, purchase of equipment, fringe benefits, travel, supplies,
equipment, etc. Indirect costs should also be shown. Sub-categories should provide a line
item detailed breakdown of the funds requested. This should be accompanied with a budget
narrative to clarify and justify the figures. If matching funds are to be provided by the
grantee, identify the amount and budget category.
4
Budgets also represent a window into how projects will be implemented and managed. Well-
planned budgets reflect carefully thought-out projects. Be sure to only include those things
the funder is willing to support.
Don't forget to list in-kind support and matching revenue, where appropriate. Be flexible
about your budget in case the funder chooses to negotiate costs.
TOTALS 28,625.00
5
Describes the means by which the grantee and funding agency will know if the project has
accomplished its objectives. It may also describe plans for collecting additional information to
improve the project. What is the purpose of the evaluation, what data will be collected, how
will it be analyzed, and how will the results be reported? Plans for disseminating products
and findings to the sponsor and to the community at large can also be described in this
section. How will the results of this program be disseminated?
Possible Complications/Challenges:
What are the potential challenges and complications?
Any identifiable obstacles and risks (threats) that might prevent the successful attainment of
the project goals must be considered. Each risk must be analyzed, quantified, and prioritized
as much as possible with the information available at this stage. Risk responses, including
mitigations, risk sharing, risk avoidance, and risk tolerances should be described in this
portion of the project proposal.
Supporting materials are often arranged in an appendix. These materials may endorse the
project and the applicant, provide certifications, add information about project personnel
and consultants, exhibit tables and charts, etc. For projects that include collaborations or
partnerships, include endorsements from the partnering agencies.
Policies about the inclusion of supporting materials differ widely among funders. Whether to
allow them usually depends upon how materials contribute to a proposal's evaluation.
Restrictions are often based on excess volume, the element of bias, and relevance.
Find out if supporting materials are desired or even allowed. Be prepared to invest the time
to collect resources, produce a tape, document capability, update a resume, collect letters,
include reference reports or whatever is needed.
Deliverables
6
A deliverable is something tangible and measurable.
A milestone and a deliverable are two different concepts. A milestone has a symbolic purpose
and is not a physical creation (and therefore can represent things that are not tangible, such as
hitting the three month mark of the project). A deliverable, on the other hand, defines the class
of tangible (i.e. physical) products that the project produces on its path towards achieving its
ultimate goal. As a result, a project will have significantly fewer milestones than deliverables.
However, a milestone can also be a deliverable. For example, an agreed-upon and accepted
milestones is three months in the future, and represents the recruiting of a Project
Management Assistant (remember that milestones are not activities in themselves, but simply
represent special activities in the project). This hiring of a Project Assistant is also a deliverable:
at the three month mark, the project activities have led to the production of a tangible product:
the Project Management Assistant.
This means that many milestones will in fact be deliverables, but many deliverables will not be
milestones. Milestones are used to flag key events.
Project Goals
Goals are high-level statements that provide the overall context for what the project is trying to
accomplish. One of the goals of a project might be to "increase the overall satisfaction levels
for clients calling to the company helpdesk with support needs". Because the goal is at a high-
level, it may take more than one project to achieve.
Project Objectives
Objectives are concrete statements describing what the project is trying to achieve. The
objective should be written at a lower level, so that it can be evaluated at the conclusion of a
project to see whether it was achieved or not. Goal statements are designed to be vague.
Objectives should not be vague. A well-worded objective will be Specific, Measurable,
Attainable/Achievable, Realistic and Time-bound (SMART).
7
deliverables, they are written at too low a level. If they describe the features and functions,
they are requirements, not objectives.
Follow-Up on a Proposal
Contact the funding source about the status, evaluation, and outcome of your proposal. It is
important to request feedback about a proposal's strengths and weaknesses, although this
information may be unavailable with a very large volume of submissions.
Reference information may also be useful if you choose to approach the same or different
funder again with your idea.