A research white paper is a document researchers write in two distinct contexts that are easy to conflate: as a funder-requested pre-proposal screening document submitted before a full grant application, and as a researcher-authored synthesis that presents findings, technical analysis, or recommendations to a policy or stakeholder audience outside the peer-reviewed literature. Both senses are narrower than the generic “white paper” (a government or industry policy document; see CASRAI’s white paper entry) — this page covers the research-specific uses of the term that a researcher or research administrator is likely to encounter.
The two senses researchers actually run into
1. Funder pre-proposal white paper
Many federal funding agencies and private foundations use a short white paper as a first-stage filter before inviting a full application. Federal regulations governing Notices of Funding Opportunity explicitly recognize this mechanism: 2 CFR Appendix I to Part 200 (the uniform template federal agencies use to structure a Notice of Funding Opportunity, or NOFO) requires an agency to state whether pre-applications, letters of intent, or white papers are required or encouraged, and if so, how and when they must be submitted. The U.S. Department of Energy is one of the most consistent users of this exact terminology — many DOE Office of Science and applied-energy program FOAs require a mandatory white paper before an applicant may submit a full application, with the agency screening white papers for programmatic fit and inviting only a subset of submitters to proceed. See CASRAI’s Funding Opportunity Announcement (FOA) entry for how this fits into the broader solicitation structure.
In this sense, a research white paper is functionally a concept screening document: short (often 2-5 pages), non-binding in most solicitations, and evaluated on programmatic fit rather than full scientific merit. It is not a contract or a guarantee of an invitation to submit a full proposal.
2. Researcher-authored technical or policy white paper
Separately, researchers and research institutions write white papers to synthesize findings, argue for a technical approach, or inform policy — for example, a university research center publishing a white paper on the state of a technical field to support advocacy or industry engagement. This use overlaps with the generic white paper definition already on this site (which traces the term’s origin to UK government Command Papers) but is specifically research-authored and typically cites the underlying primary literature. It differs from a technical report mainly in audience: a technical report is written primarily for technical practitioners and often documents methods and results in detail for internal or sponsor use, while a white paper is written to persuade or inform a broader decision-making audience and de-emphasizes methodological detail in favor of implications and recommendations.
How a funder white paper differs from related pre-proposal documents
Solicitation language is inconsistent across agencies and foundations, and the same underlying document is sometimes called different things. As a practical distinction:
- White paper — typically the shortest of the three, focused on concept and programmatic fit; common in DOE and some other federal solicitations; often screened by program staff rather than external peer reviewers.
- Letter of intent (LOI) — usually shorter still, sometimes just a paragraph confirming an applicant’s intent to submit, mainly used by the funder for reviewer-conflict planning and applicant-volume forecasting rather than substantive screening.
- Concept paper / preliminary proposal — closer in scope to a condensed full proposal, sometimes carrying more of the required elements (preliminary budget, team qualifications) than a white paper, and in some agency usage (including some NSF preliminary-proposal mechanisms) reviewed with something closer to full merit review.
None of these terms are used with perfect consistency across funders — always follow the specific solicitation’s definition and required elements rather than assuming a term means the same thing it did in a different agency’s program.
Typical structure of a funder-requested white paper
Requirements vary by solicitation, but a funder white paper commonly includes:
- Cover page with FOA/solicitation number, applicant organization, and point of contact
- Statement of the problem or opportunity being addressed
- Proposed technical approach or research objectives, at a level of detail sufficient for programmatic screening but well short of a full research plan
- Anticipated impact or relevance to the program’s stated goals
- Rough budget range and period of performance (some solicitations require this, others don’t)
- Brief statement of team qualifications or organizational capability
Always work from the specific solicitation’s instructions rather than a generic template — page limits, required headings, and formatting rules (font, margins, file format) are typically mandatory and enforced administratively before any programmatic review occurs.
What happens after submission
For funder-requested white papers, the agency or foundation reviews submissions internally (this stage is usually not external peer review) and issues one of three outcomes: an invitation to submit a full application (sometimes with feedback or requested changes in scope), encouragement to submit despite reservations, or discouragement/non-selection. Some solicitations treat a discouraging response as non-binding — an applicant may still submit a full proposal — while others make the white-paper stage a hard gate. This distinction is always stated in the solicitation itself and should be confirmed before an applicant decides whether to proceed.
Common mistakes
- Treating the white paper as optional framing rather than a scored screen. Even when non-binding, program staff use white papers to allocate limited full-proposal review capacity — a weak white paper can reduce the odds of an invitation even where submission of a full application remains technically permitted.
- Exceeding page limits or omitting a required heading. Many agencies reject white papers administratively, without programmatic review, for failing to follow formatting instructions exactly.
- Confusing a funder white paper with a researcher-authored policy white paper. The two share a name but almost nothing else — a program officer expects a concise, solicitation-specific screening document, not a general-audience synthesis of a research area.
- Assuming “white paper” means the same thing across every funder. Confirm what a specific solicitation means by the term, and what it requires, rather than reusing a template built for a different program.
Frequently asked questions
Is a research white paper the same as a letter of intent?
No. A letter of intent is typically shorter and less substantive, mainly used by funders for planning purposes (forecasting application volume, identifying reviewer conflicts). A white paper is expected to describe the actual concept or approach in enough detail for the funder to screen it on programmatic fit.
Does every federal funder use the term “white paper” for pre-proposal screening?
No. Terminology varies by agency and even by program within an agency. The Department of Energy consistently uses “white paper,” while other federal agencies more often use “letter of intent” or “preliminary proposal” for functionally similar screening steps. Always follow the term and requirements used in the specific solicitation.
Is a funder white paper peer reviewed?
Usually not in the same sense as a full proposal. It is typically screened by program staff for fit with the program’s scope and priorities rather than sent out for external scientific peer review, though practice varies by funder.
How long should a research white paper be?
This is set by the specific solicitation and varies widely — commonly in the range of a few pages for a funder pre-proposal screen, though always confirm the exact page or word limit in the solicitation rather than assuming a standard length.
