Summary

Purpose and content

The summary provides a concise and compelling overview of your research project.
It should capture the essence, purpose, and expected outcomes of the project in just a few sentences — and motivate reviewers to read on.

Many reviewers read the summary first, using it to identify which projects:

fit within the foundation’s objectives, and

appear particularly promising or innovative.
The summary should reflect the key elements of your project description, including the purpose, methodology, and expected results.
It is similar to the lay summary but written for a scientific audience.
You may use technical terms, but always adjust the technical level to the reviewers who will assess your application.

Target group 👥

Reviewers with subject-specific expertise. You may therefore use technical terms in the summary, but still make sure to find out who will be evaluating your application, so you can adjust the level of technical detail accordingly.

Structure and requirements

Keep the summary brief and focused — typically no longer than half a page, or as specified by the foundation

Your goal is to present the project clearly and persuasively — the summary should both inform and sell your idea.

A strong summary answers five key questions:

What is the project's purpose (possibly with a hypothesis)?
Why are you particularly qualified to conduct the project?
Why should the project be conducted now (and not, for example, in five years)?
How will you solve the problem or test your hypothesis?
What results are expected, and what impact will they have?

Measurable effects - examples

If you can quantify the effect of your results, it is often an easily understandable and convincing selling point.

Clinical improvement: e.g., more accurate diagnosis or better treatment outcomes.
Policy changes: e.g., revised guidelines for screening programs.
Improved health technology: e.g., development of new digital tools or measurement methods.

Not all projects aim for a result that can be quantified. In such cases, explain instead what societal impact your project will have. If your project does not have a direct effect, clarify to the reader what indirect effects it may have.

Indirect effects – examples

Collaboration and networks: strengthened international or cross-sector collaboration.
Socioeconomic benefits: e.g., fewer hospital admissions, improved quality of life, reduction in costs.
Patient involvement: increased user engagement.

Tips and recommendations 💡

Have a colleague review your summary for clarity and precision..
Always follow the foundation's guidelines regarding the length of the summary. If no specific guidelines are provided, limit the summary to a maximum of half a page.
Avoid unnecessary complexity and focus on effectively communicating the project's value.

Evaluation checklist ✅

Is your summary clear and easy to understand?
Does it answer the five key questions precisely?
Is the technical level appropriate for the reviewers?
Does it follow the required length?
Does it highlight the project’s importance and impact?
Has it been proofread and checked for consistency?

Revised 17.11.2025

Anders Møller