A practical concept note template for development projects

Explain the idea before expanding the proposal

A concept note allows a partner or decision-maker to assess an idea before investing in a full proposal. It should explain the problem, who is affected, what change is proposed and why the approach is plausible. The required length and headings depend on the recipient; always follow a supplied template or call for proposals.

Start with a short problem statement supported by evidence you can identify. Describe the specific context rather than making broad claims about a country or population. Where data is unavailable, mark the gap and explain how it will be addressed.

Use these core sections

• Working title and summary: the idea in plain language.
• Problem and rationale: the gap, evidence and relevance to the intended partner.
• People and institutions involved: who the work serves and who helps shape it.
• Objective and intended results: the change, outputs and scope.
• Approach: the main activities and why they connect to the results.
• Implementation: roles, partnerships and indicative timeline.
• Resources: an indicative budget, assumptions and funding gap.
• Risks and assumptions: what could affect delivery or results.
• Monitoring: how progress will be observed and reviewed.
• Next step: the discussion, endorsement or funding decision requested.

Connect activities to a meaningful result

Consider a fictional project to improve programme reporting. Workshops are activities; an agreed reporting guide and trained staff are outputs. More consistent use of evidence in reports is an intended outcome. Explain why the activities could support that outcome and what additional conditions are needed.

Do not invent a baseline, target, partner commitment or budget to make the note look complete. Use a clearly marked placeholder and assign the follow-up work. This makes the note more useful for discussion and avoids presenting assumptions as facts.

Copy this concept-note prompt

Draft a concept note using this structure: summary, problem, objective, results, approach, implementation, resources, risks and monitoring.
Context and source evidence: [paste material].
Intended audience or funding call: [details].
People and institutions involved: [confirmed roles].
Proposed scope and duration: [details].
Budget information: [verified figures or labelled estimates].
Required length and format: [requirements].
Do not invent figures, partners or commitments. Mark evidence gaps and distinguish proposed results from confirmed facts.

Review for coherence

Read the problem, objective, results, activities and budget together. Each should support the same scope. If the proposed work cannot plausibly deliver the stated change within the time and resources available, narrow the claim or revise the design.

Ask a colleague unfamiliar with the idea to identify the problem, proposed response and requested decision. If those are difficult to find, simplify the note before making it longer.