Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Proposals

How to design projects for proposals and cohesive programs

Authors
Affiliations
Aegis Conservation
3point.xyz

Abstract

We present an iterative approach to preparing grant proposals, starting with a brief project summary, then moving to initial budget estimates, scope development, and timeline creation. The chapter stresses that project design is not a straightforward, linear process and advises professionals to revise their budgets, narratives, and objectives several times before submitting the final version. We then offer practical advice on preparing defensible budgets that account for inflation and include both salary and implementation costs throughout the project lifecycle. The chapter includes recommendations for funders to make the proposal process more efficient, promote participatory grant-making, and set realistic timeframes for applicants. Additional resources for ongoing learning in proposal writing and project development are provided.

Keywords:proposalsfundingplanningprogramgoalsobjectives

Iterative Design

The project and proposal development workflow is iterative, like program design and the budget process described in the budget section. In general, we suggest the following workflow to develop projects or a proposal:

  1. Brief. Create a 1-2 page brief with the following sections:

    • Executive summary. Three to five sentences max outlining the reason for the project, tasks, outcomes, timeline, and high-level budget.

    • Project goals. Link the project to the programmatic theory of change and goals, then list the project goals/objectives.

    • Tasks. These could be listed under project objectives and also called interventions or activities.

  2. Budget. Creating a back-of-the-envelope budget helps quickly estimate a project’s basic costs—like staff time, equipment, materials, and key activities, e.g., site assessments, community outreach, training sessions, and report preparation—before investing time in a full proposal. It’s a simple way to test feasibility and guide early planning decisions. Again, don’t worry about details; just make some rough estimates. Napkins (or junk mail) and a pen at a restaurant are good tools of the trade! Capture your proposal ideas and get rolling.

  3. Scope. Draft the proposal narrative or scope of work with a detailed description of tasks and activities by objective, using the brief from step one as a guide. At this point, it is worth adding a GANTT chart as a project timeline to show the workflow and check whether you’ve stacked too many activities at certain times or made your schedule too aggressive.

Don’t worry about fleshing out these sections in detail. When drafting the brief, focus on getting the ideas down. The details can be developed later.

Scope

Use the brief to flesh out a more detailed project scope and description. Don’t be afraid to write sections and then rewrite them. Give each section a rest for a few days, then return to it after working on other sections. Create a checklist from the proposal RFP solicitation package to ensure you don’t forget anything. The Forest Business Alliance has a template checklist that may be useful.

Send your proposed ideas to colleagues for review, or develop them across an interdisciplinary team or collaboratively if working with multiple partners.

Budget

Identifying and reviewing a proposal’s requirements and other project parameters early will help focus design efforts and keep expectations aligned with reality. One key parameter is the amount of money available for direct program implementation. Starting with a rough estimate of the required fieldwork will help you make realistic decisions about project scope and scale.

Say you’re developing a $1 mn budget project, dividing it into broad categories using a budget calculator (Table 1). In this simplified example, salaries (35%) include benefits and contracted labor. Implementation (50%) is for all non-salary project costs, such as supplies, equipment, and travel. Indirect (15%) is for an organization’s operating costs, e.g., rent, utilities, and fees. This immediately informs the project team how to allocate resources to the budget and project as they develop the proposal or project.

Table 1:Back-of-the-envelope budget calculator.

Item

Amount

Salaries

350,000

Implementation

500,000

Indirect

150,000

Total

1,000,000

The calculator will give you rough amounts for each broad category. You could also break it down by your objectives and tasks from step 1 and the rough budget.

Budget process

The project budget is the project’s core engine. Developing it with defensible numbers is critical to project success.

  1. Tasks. Create draft objectives and tasks.

  2. Budget rough draft. Draft a back-of-the-envelope budget by project category or deliverable, roughing out the approximate costs with rules that divide out salary implementation.

  3. Narrative. From the draft tasks and budget, write a proposal narrative.

  4. Timeline. Create a project GANTT chart with deliverables from the budget and narrative.

  5. Refined budget. Return to the budget and refine numbers—test assumptions about estimates for each line item. Increase amounts as necessary. You may need to factor in inflation, salary raises, or increases in material purchase amounts that may fluctuate with changing markets. Adjust the total budget to reflect what you think is a reasonable ask to the funder. This may require lowering some estimates.

Finalize

Put together your project design and share it. For both proposals and projects, copyedit your final version and then copyedit it again. Look at it in different formats and, ideally, let the proposal rest for a few days, then copyedit again. Printing out the key written components and editing with a red pen can also help catch additional mistakes or grammatical errors. This might seem like a waste of paper, but it can be effective for editing.

The FBA can also review projects and proposals, with our staff writers’ years of experience with proposal development and successful funding track records. However, we ask that you send them early, e.g., months before the due date or during the conceptual phase. Please contact us if you’re interested in a review.

Good luck!

Resources

The project design chapter is a very brief look at how to develop projects and proposals. You’ll want to dive deeper to develop your project and proposal craft. Here are a few additional resources to get going: