Match a conference proposal to the call without inventing results
Plan a conference proposal around the actual call, work status and session promise, using an original fictional decision map.
About 5 min read · Allow extra time for the practical checks
Read the actual call for proposals, identify the kind of contribution it invites and explain the work you can honestly present. A conference proposal needs to help reviewers judge relevance, content and feasibility. Copying a journal abstract into a submission form can leave those questions unanswered.
Check the session category, audience, format, required fields and deadline before drafting. Some events welcome work in progress; others require completed research. Do not assume that a workshop, individual paper and panel use the same submission rules or that every event reviews proposals anonymously.
Turn the call into decisions
Keep a brief working note linking each material requirement to a decision about your proposal. Identify which parts of your work fit the event’s theme, what listeners would gain and what you could cover in the available format. If the fit depends on claiming findings you do not have, reconsider the proposal or ask whether another category is appropriate.
Indiana University of Pennsylvania’s short-proposal guidance connects conference proposals with the interests of particular attendees, the conference theme and the organisers’ expectations. Apply those principles to the actual call. The source’s typical lengths and descriptions of review arrangements are not universal conference rules.
A theme connection should be substantive. Merely repeating a phrase from the call does not explain what your work contributes. Describe the specific question, material or argument that makes the connection reasonable.
Distinguish the project from the proposed session
Explain what the work investigates and how you approached it, then explain what you will present. These may be related but are not identical. A large project can support a tightly focused talk; a discussion session may need an account of what participants will do as well as the topic they will discuss.
Make the work’s stage clear. Separate observations already supported by your material from analysis still under way and activities merely planned. If the call allows unfinished work, describe its current status and proposed contribution honestly. Expected results must not appear as completed findings.
Do not promise an outcome simply because it sounds useful to delegates. Explain the actual takeaway you can support: an argument to assess, a comparison to discuss or a documented approach whose limits you will examine. A proposed session does not establish that participants will change their practice.
Work through a fictional call-to-proposal map
The event, call and project below are wholly invented teaching material. They do not represent an actual opportunity, acceptance decision or research finding.
Imagine a fictional symposium on access to campus collections. Its fictional call welcomes a discussion of work in progress and asks applicants to describe what participants would discuss. A writer has compared the wording of two collection-request pages but has not interviewed users or evaluated an intervention.
| Fictional call requirement | Material available | Defensible proposal decision |
|---|---|---|
| Explain relevance to collection access | A comparison of request-page wording | Explain the particular access question raised by differing instructions |
| State the work’s current stage | Document comparison completed; user experience not studied | Identify the comparison as the basis for discussion and retain the unstudied experience limit |
| Describe the proposed discussion | Possible interpretations of the differing wording | Invite discussion of what further information is needed before recommending changes |
| Identify a takeaway | A bounded document-comparison example | Offer a way to examine instruction consistency, without promising improved access |
“An intervention that improves collection access” would overstate this fictional work. A more accurate description would explain that the session examines inconsistent wording and asks what evidence is needed before proposing a change. This is a planning contrast, not a finished abstract to submit or evidence that the fictional event would accept it.
Draft for the review decision
Give the reviewer enough context to understand the problem, the basis for your account and its relevance to the session. Use the required headings if the call supplies them. Where it asks for methods, findings or participant activities, answer those fields directly rather than leaving the reader to infer them from a broad topic description.
Use relevant scholarship where required and preserve attribution. Define unfamiliar terms for the expected audience. A proposal can be concise while still identifying the material behind its claim and the limit on its interpretation.
Check that the title and body describe the same proposed contribution. Remove promises that the session cannot meet. If necessary, narrow the topic so the proposed explanation fits the format instead of compressing several projects into a list.
Check the submission package separately
Review the actual word limits, anonymity instructions, presenter information and other required materials. A biography belongs in its designated field when requested; it should not be inserted into an anonymous proposal. Follow the event’s own instructions rather than assuming either arrangement applies everywhere.
Keep a copy of the final text and any submission acknowledgement. Acknowledgement establishes receipt, not acceptance. If the proposal is accepted, revisit it when planning the slide sequence so the presentation delivers what was promised. Use an accurate short biography for the organiser’s separate introduction request.
