Write a conference panel proposal around the question connecting the papers
Write a conference panel rationale that explains the shared question, distinct paper contributions and evidence limits.
About 5 min read · Allow extra time for the practical checks
Explain what the proposed session will help an audience examine, why these papers belong together and what each contributes to that shared question. A panel rationale should make the intellectual connection visible without replacing the individual paper abstracts or claiming agreement that the contributors have not established.
Start with the actual conference call. Check the permitted session format, required fields, contributor arrangements and submission procedure. This guide concerns writing the rationale; it does not submit a proposal, secure participants or guarantee acceptance.
Distinguish the panel’s question from its topic label
“Libraries and local history” identifies a broad area. It does not explain what a particular collection of papers will make possible. Ask what an audience could understand from their combination that a single presentation would not provide.
In their 2 September 2014 article Crafting an Effective Panel Proposal for 2016 Annual Meeting in Perspectives on History, Francesca Trivellato and Andrew S. Sartori advise explaining the overarching rationale connecting the papers rather than supplying successive summaries. Their article addresses that historical AHA meeting context. It is a useful writing principle, not the current rules for your conference.
Write the question in ordinary language before adding specialist terminology. Check that the papers can actually address it. A shared word in their titles is weaker grounds for a session than a problem that each paper examines from a different, relevant position.
Test the connection with an original fictional panel map
All papers, places, evidence and proposed statements in this exercise are invented. They are not descriptions of actual research or confirmed participants.
Imagine a proposed session about how local libraries recorded their public-service priorities. The teaching materials describe three proposed papers:
| Fictional paper | Material it proposes to examine | Contribution to the shared question | Limit to preserve |
|---|---|---|---|
| A: Committee priorities | Meeting minutes from a fictional town library | How a committee recorded a service decision | A minute does not establish how every reader experienced it |
| B: Public explanations | Notices issued by another fictional library | How a service change was explained publicly | A notice does not establish whether readers agreed |
| C: Reader accounts | A defined set of letters about a third fictional library | How the letter writers described a service | The writers do not represent all users |
A possible shared question is: “How do different library records make public-service priorities visible, and what does each leave uncertain?” The papers approach that question through different records. Their difference gives the comparison a purpose; it does not make their evidence interchangeable.
A weak rationale would say that all three papers prove that libraries responded fairly to local needs. Nothing in the fictional map establishes fairness or a common effect across the sites. The proposed session should invite examination of those boundaries rather than announce an unsupported collective finding.
Draft the rationale without stitching abstracts together
A bounded opening for the fictional proposal could be:
This proposed session examines how different library records make public-service priorities visible. Bringing committee minutes, public notices and a defined set of reader letters into discussion allows the papers to compare institutional decisions, public explanations and reported experiences while retaining the limits of each record type. The session asks what becomes clearer through this comparison and which questions about readers’ experience remain unresolved.
This is an original teaching example. It is not a conference-ready abstract about real papers. In a real proposal, replace the invented scope with work the contributors have actually agreed to present and fit the conference’s requested length and format.
Explain the connection before detailing every paper. Then include enough about their distinct contributions to make the rationale credible. Do not repeat all the background, evidence and conclusions already covered in the paper abstracts. A reader should be able to find both the session-level purpose and the individual work behind it.
Keep proposed discussion separate from established results
Phrases such as “the session will examine” can describe an intended discussion. Phrases such as “the papers demonstrate” make a claim about their evidence. Choose between them based on the actual work, not on which sounds more confident.
Check any collective statement with the contributors. If one paper challenges another’s interpretation, do not smooth that disagreement into agreement. If the papers use different definitions, acknowledge the difference where it affects the session’s question. A coherent panel can support a useful disagreement without presenting the papers as one study.
Keep practical information accurate as well. Do not describe a suggested chair or discussant as confirmed. Check names, titles and contributions against the details each person has supplied, and follow the organiser’s rules for proposed and confirmed participation. An appealing rationale cannot compensate for an inaccurate contributor record.
Read the whole submission as one proposal
Compare the panel title, rationale and paper abstracts. Do they identify the same question and scope? Does each paper have a clear job? If removing one paper leaves the rationale unchanged, explain its contribution more clearly or reconsider the proposed grouping.
Use the guide to matching a conference proposal to its call for the individual submission task. Once a session is confirmed, the conference-chair guide helps prepare spoken running notes. A panel rationale has an earlier job: helping a reviewer see why this proposed conversation is worth bringing together.
