Start with a short working document your team can update. You can use a shared document for the brief and a simple spreadsheet for tasks, dates and risks. The plan should serve the project, not create another layer of administration.
Define the need and intended change
Write down the problem the project addresses, the people it serves and what should be different by the end. For example, a workshop programme might aim to help participants practise a specific skill, rather than merely count attendance.
Agree on a small number of outcomes
Separate activities from outcomes. “Run four sessions” is an activity; “participants report greater confidence using the new skill” is an outcome. Record how you will check each outcome and when.
Set the scope and boundaries
List what the team will deliver, what it will not deliver during this phase and what must be decided later. This helps prevent extra requests from silently changing the budget or timetable.
Map stakeholders and decision makers
Identify participants, funders, delivery partners, staff and volunteers. Note who approves changes, who needs regular updates and whose feedback should shape the work.
Break delivery into tasks and milestones
Group the work into preparation, delivery and follow-up. For each task, name one owner and a due date. Include milestone dates for approvals, outreach, materials, events and the final report.
Check capacity and costs
Estimate staff or volunteer time, materials, accessibility needs, venue or online tools, travel and contingency. Compare these costs with available funding. If the plan exceeds capacity, adjust scope before launch.
Record risks and responses
Choose a few realistic risks: low registrations, a delayed partner response, staff absence or missing information. Give each risk an owner and a practical response. Review the list at regular check-ins.
Plan communication and consent
Decide how often the team, partners and funder will hear from you. If you collect personal information, agree who can access it, why it is needed and how your organisation’s privacy procedures apply.
Choose evidence to collect during delivery
Pick measures that match your outcomes, such as attendance, completion, participant feedback or follow-up results. Collect only what your team can use and report accurately.
Schedule review and handover
Book check-ins to update the task list, budget and risks. At the end, record what was delivered, what changed, lessons learned and where the final documents live so the next project starts with a stronger foundation.
What the finished plan should contain
A one-page brief with the need, audience, outcomes and scope; a task tracker with owners and dates; a budget; a stakeholder list; a short risk register; and a simple reporting schedule. Keep each item as detailed as the project requires.
If you want help turning this checklist into a working plan, see our nonprofit project management support. For projects preparing a funding application, explore our grant planning and proposal support.