How to Write a Paper Proposal (With Example)

A “paper proposal” is a short, self-contained document that pitches a piece of research or writing before the full paper exists — most often submitted to a conference program committee, but also used for edited-volume chapter calls, symposium panels, and some journal special issues that solicit proposals ahead of a full manuscript. It is a persuasive summary, not a first draft: reviewers are deciding whether to allocate you a conference slot or a chapter commission based on a few hundred words, months before the finished work is due.

This guide covers what a paper proposal needs to contain, how it differs from an abstract and from a funding proposal, and walks through a fully annotated, clearly-labelled illustrative example. It does not cover the mechanics of submitting through a conference platform once your proposal is written — for that, see How to Submit a Conference Abstract, which covers abstract-management systems, review timelines, and presenter registration.

Paper proposal vs. abstract vs. research/grant proposal

These three terms get used loosely and interchangeably in practice, which is part of why searches for “proposal for paper example” turn up a mix of genuinely different documents. They are not the same thing, and confusing them is one of the more common reasons a submission gets returned for revision:

Paper proposal — pitches a piece of writing or research that does not yet exist in final form to a conference program committee, panel organizer, or edited-volume editor. It is evaluated on the strength of the idea, the soundness of the planned approach, and fit with the call for papers. This is the document this guide covers.
Abstract — typically summarizes a paper that has already been written (or, for a conference, is close to final), submitted alongside or after the full text. Journal abstracts follow a structured or unstructured format tied to completed methods and results. In practice, many conferences ask for what they call an abstract but functionally review as a proposal — check the call for papers for whether results are expected to exist yet.
Research/grant proposal — a much longer document (often 5–15+ pages) requesting funding from a sponsor to carry out research, with required elements like a budget, timeline, and broader-impacts statement. See Letter of Support for a Grant Proposal and NSF CAREER Award Proposal Requirements for that document type. A paper proposal is not requesting money and does not need a budget.

What a paper proposal has to accomplish

A program committee or editor reads a large volume of proposals against a limited number of slots, usually without the benefit of the finished paper to check the claims against. Your proposal has to do three things in a tight word count, typically 200–500 words for a conference paper proposal (some societies allow up to 750–1,000 words for a full panel or symposium proposal; always follow the specific call for papers over any general figure):

Establish the problem or question clearly enough that a reader unfamiliar with your specific project understands why it matters.
Demonstrate a credible plan — method, data, or argumentative approach — convincing enough that reviewers trust the paper can actually be written by the deadline.
State the contribution: what will be different, known, or arguable after this paper exists that isn’t now.

Core components

Most paper proposals, across disciplines, converge on a version of the same structure, loosely following the logic of IMRaD even though the paper itself hasn’t been written yet:

Working title — specific enough to signal the actual topic, not a placeholder.
Problem statement / research question — what gap, debate, or unresolved issue the paper addresses, and why it matters to this specific audience or call for papers.
Brief context — one or two sentences situating the work relative to existing literature or debate; reviewers commonly flag proposals that omit this, since it’s the main evidence the author knows the field.
Approach / method — what you will do or have done: the data source, analytical method, theoretical framework, or argumentative structure. For work in progress, this section states the plan, not completed results.
Anticipated contribution or argument — the claim, finding, or contribution the paper will make. If results are not yet final, phrase this as a reasoned expectation (“preliminary analysis suggests…”) rather than asserting a result you don’t yet have.
Keywords — usually 3–5, used for track/session routing by the program committee.

Step by step

Read the call for papers closely first. Note the required word count, whether results/data are expected to exist yet, any theme or track the conference wants proposals to address, and the exact submission deadline. Proposals that ignore the stated theme are a common, easily avoidable rejection reason.
Draft the problem statement before anything else. If you can’t state the question in one or two sentences, the proposal likely isn’t focused enough yet.
Write the approach section honestly. Reviewers are assessing feasibility as much as originality — an ambitious but vague method description reads as a risk that the paper won’t be ready by the conference.
State the contribution as a claim, not a topic. “This paper examines X” tells a reviewer what you’ll do; “this paper argues/shows/demonstrates Y” tells them what they’ll get out of attending or reading it. The second is stronger.
Cut to the word limit last. Draft slightly over, then cut context and hedging language before cutting the problem statement or contribution — those two sections carry the most evaluative weight.
Check citations if the call requires them. Many program committees expect at least a few references situating the work in existing literature, even in a proposal well under 500 words; an uncited proposal is one of the more frequent reasons reviewers recommend revision.

Illustrative example

The proposal below is an illustrative composite written for this guide — it does not describe a real study, real authors, or a real conference, and should not be cited as one. It exists only to show how the components above fit together in a roughly 250-word proposal.

Working title: Rethinking Data Sharing Compliance Language in Institutional Repository Deposit Workflows

Problem statement: Institutional repositories increasingly mediate researcher compliance with funder data-sharing mandates, yet the deposit-workflow language presented to researchers at the point of submission has received little attention as a compliance interface in its own right. This paper asks how the wording and sequencing of deposit-workflow prompts shapes researchers’ understanding of what a mandate actually requires of them.

Approach: Drawing on a comparative review of deposit-workflow interfaces across a sample of institutional repositories, the paper analyzes prompt language, required-field ordering, and embedded guidance text against the plain-language requirements of major funder data management plan policies.

Anticipated contribution: Preliminary review suggests considerable variation in how repositories translate funder mandate language into researcher-facing prompts, with implications for both compliance consistency and researcher burden. The paper will propose a small set of interface-language conventions repository managers can adopt to reduce ambiguity at the deposit stage.

Keywords: institutional repositories, data sharing, compliance, deposit workflows, research data management

Note what this example is doing structurally: the problem statement names a specific, narrow gap rather than a broad topic area; the approach describes a concrete comparative method rather than “the author will investigate”; and the contribution is phrased as a claim with a stated output (a set of proposed conventions), not just a restatement of the topic.

Common reasons paper proposals are rejected

Topic instead of argument. Describing what the paper is “about” without stating what it will show, argue, or find.
No visible method. A compelling question with no indication of how it will actually be answered reads as unready.
Ignoring the call’s theme or track. A strong proposal for the wrong conference, or the wrong track within the right conference, is still a rejection.
Over the word limit. Program committees reviewing hundreds of submissions frequently enforce limits strictly or penalize proposals that don’t.
No engagement with existing work. Especially in humanities and social-science calls, a proposal that doesn’t situate itself relative to any existing literature or debate reads as either unfamiliar with the field or insufficiently developed.

Frequently asked questions

What is a paper proposal?

A short document, typically 200–500 words, pitching a piece of research or writing that does not yet exist in final form to a conference program committee, panel organizer, or edited-volume editor, so they can decide whether to accept it before the full paper is written.

How is a paper proposal different from an abstract?

An abstract conventionally summarizes a completed or near-complete paper, including actual results. A paper proposal pitches work that is still in progress, describing a planned approach and an anticipated (not yet final) contribution. In practice many conferences use the terms loosely, so always check what the specific call for papers actually expects.

How long should a paper proposal be?

Most conference paper proposals run 200–500 words; some panel or symposium proposals allow up to 750–1,000 words. The call for papers for the specific venue always overrides any general figure.

Does a paper proposal need citations?

Often yes, even at a short length. Reviewers commonly expect at least brief engagement with existing literature to judge whether the proposed work is original and grounded, and a proposal with zero references is a frequently cited reason for a revise-and-resubmit request.

Is a paper proposal the same as a grant proposal?

No. A grant/research proposal requests funding from a sponsor and requires elements like a budget and project timeline that a paper proposal does not. See Letter of Support for a Grant Proposal for that document type.

What happens after a paper proposal is accepted?

Accepted proposals typically move into a submission platform for the full paper or presentation, often tied to presenter registration deadlines. See How to Submit a Conference Abstract for how that stage typically works.