Can I Submit an Abstract to a Conference Without the Results?

Your abstract submission deadline is three days away. Your data collection is still running, your analysis hasn’t started, and you have no results to speak of. Every researcher knows this specific kind of panic — the conference you’ve been planning to attend all year, the call for papers you bookmarked months ago, and now the clock is ticking on research that simply isn’t finished yet.

Here’s the short answer: yes, you can submit a conference abstract without results. What you’re writing is called a descriptive abstract — a type of abstract that presents your research background, research gap, research objective, and research methodology without requiring final results or conclusions. This format is explicitly accepted at major conferences across STEM, the social sciences, and the humanities, including organizations like the American Educational Research Association (AERA), the Association for Computing Machinery (ACM), and the American Sociological Association (ASA). It is not a workaround or a loophole. It is a recognized, legitimate submission format.

The trickier part is knowing how to write one well. A work-in-progress abstract still has to earn its place in a competitive peer review process, and conference program committees read thousands of submissions. Reviewers want to see a clearly articulated research gap, a credible methodology, and a convincing case for why your anticipated findings and expected contributions matter — even if that final chapter hasn’t been written yet. Get it wrong and you look unprepared. Get it right and you secure your spot on the program.

This guide walks you through exactly how to do that — which conferences accept abstracts without results, how to frame preliminary results and ongoing research honestly, what conditional language and future tense actually look like in practice, and where the line between transparency and academic integrity sits.

Yes, You Can Submit a Conference Abstract Without Results — But Here Is How

The short answer is yes. Many conferences explicitly accept abstracts for ongoing research, and even the ones that don’t spell it out often welcome work-in-progress submissions if you frame them correctly.

What you cannot do is pretend you have results when you don’t. That’s an academic integrity problem, and reviewers on the conference program committee will usually spot it anyway. What you can do is write an honest, well-structured abstract that makes a strong case for your research without leaning on completed findings.

Here’s the practical breakdown.

Know What Type of Abstract You’re Writing

Not all abstracts work the same way. A journal article abstract summarizes completed work — past tense, finished analysis, confirmed results. A conference abstract is different. It’s a proposal. You’re telling the committee what the research is doing, why it matters, and where it’s going.

A work-in-progress abstract takes that one step further. Some conferences — particularly in STEM, social sciences, and humanities — have dedicated tracks for this. The American Educational Research Association (AERA), for example, regularly accepts submissions under “works in progress” or “roundtable” formats specifically designed for researchers who are mid-study. The same goes for the Association for Computing Machinery (ACM) and Institute of Electrical and Electronics Engineers (IEEE) conferences, many of which include poster sessions built for preliminary results or ongoing research.

If you’re in sociology or literature, the American Sociological Association (ASA) and Modern Language Association (MLA) both host sessions that accommodate developing work. Check the call for papers (CFP) carefully. The language matters.

Build the Abstract Around What You Do Have

You may not have results, but you have other things that carry real weight with reviewers.

Your research gap. This is non-negotiable. You need to show there’s an actual problem in the existing literature that your work addresses. Be specific — name the gap, cite the conversation your research is entering.

Your research objective. One clear sentence. What does your study set out to find, test, or argue? Don’t bury it.

Your research methodology. This is where abstracts without results earn their credibility. A well-defined method — whether that’s a randomized controlled trial, grounded theory, discourse analysis, or a mixed-methods survey design — tells reviewers you know what you’re doing even if the data isn’t in yet.

Anticipated findings or expected contributions. This is where future tense in academic writing and conditional language in research become your tools, not your weakness. Phrases like “this study is expected to,” “findings will likely suggest,” or “results may contribute to” are entirely appropriate here. Don’t hedge so much that you say nothing — be reasonably confident about what direction your work is heading.

What to Actually Write, Paragraph by Paragraph

Most conference abstracts run between 150 and 300 words, though always check the abstract word limit in the CFP because it varies.

A clean structure for a results-free abstract looks like this:

1. Opening sentence — the research context and the gap (1–2 sentences)
2. Research objective — what you’re investigating and why it matters (1–2 sentences)
3. Methodology — how you’re doing it, enough detail to be credible (2–3 sentences)
4. Anticipated findings / expected contributions — where the research is heading and what it adds (2–3 sentences)

That’s it. You don’t need to pad it. Four tight paragraphs or even a single flowing paragraph in that order will read better than six vague paragraphs trying to compensate for missing data.

A Note on Preliminary Results

If you have any preliminary results — even partial data, early patterns, or pilot study findings — include them. Even one sentence of real findings strengthens the submission significantly. Reviewers know full results aren’t always possible by the abstract submission deadline, but preliminary results show momentum.

If you have nothing yet, don’t manufacture it. Stick to methodology and anticipated findings.

Check the Conference’s Abstract Revision Policy

Some conferences allow you to update your abstract after peer review or as the program gets finalized. If yours does, you might submit now with anticipated findings and revise closer to the event once results are in. Not all conferences offer this, but it’s worth checking the abstract revision policy before you assume you’re locked in from day one.

The bottom line: a descriptive abstract built on a clear gap, solid methodology, and honest expected contributions will get through peer review at a lot more conferences than researchers realize. You don’t need finished results. You need a finished argument for why the research is worth hearing about.

What Is a Descriptive Abstract and Why Does It Matter Here?

Definition and Key Characteristics of a Descriptive Abstract

A descriptive abstract tells readers what a paper or presentation covers — not what it found. It describes the scope, purpose, and approach of the work without reporting outcomes or conclusions. Think of it as a map rather than a destination.

This is exactly why it works for ongoing research. You’re not hiding incomplete results. You’re writing the type of abstract that was designed for this situation.

Here’s what a descriptive abstract typically includes:

• The research gap your work addresses
• Your research objective — what you’re trying to find out or argue
• The research methodology you’re using or plan to use
• Anticipated findings or the questions the research aims to answer
• The expected contributions to the field

Notice what’s missing from that list: actual results. That’s intentional. A descriptive abstract doesn’t promise findings — it promises a conversation worth having.

This format is common across STEM conferences, social sciences conferences, and humanities conferences alike. The American Educational Research Association (AERA), for instance, accepts work-in-progress abstracts that follow this structure explicitly. The Institute of Electrical and Electronics Engineers (IEEE) and the Association for Computing Machinery (ACM) both host conferences where preliminary results or even just a well-defined research direction can satisfy submission requirements.

One practical note on language: descriptive abstracts for ongoing research lean heavily on future tense in academic writing and conditional language in research. Phrases like “this study will examine,” “findings are expected to show,” or “we anticipate that” are standard. They signal honesty about where the work stands — not incompleteness.

Keep it tight. Most conferences impose an abstract word limit somewhere between 150 and 500 words. A descriptive abstract doesn’t need length to do its job.

Conference Abstract vs. Journal Article Abstract — Core Differences

These two things share a name but serve very different purposes. Confusing them is one of the most common mistakes researchers make when preparing a submission.

A journal article abstract summarizes a completed study. It follows a structured format — background, objective, methods, results, conclusion — because the paper it represents is finished. Peer reviewers and readers use it to decide whether the full paper is worth reading. Results aren’t optional there. They’re the whole point.

A conference abstract works differently. It’s a proposal as much as a summary. You’re convincing a conference program committee that your research is worth a slot in the program. The work doesn’t have to be done. It has to be worth doing — and you have to make that case clearly.

A few concrete differences:

The American Sociological Association (ASA) and the Modern Language Association (MLA) both run calls for papers (CFPs) where the abstract functions purely as a proposal. You’re pitching a conversation, not reporting a study.

This distinction matters practically. If you write your conference abstract like a journal abstract — trying to force results you don’t have yet — it shows. Program committees read hundreds of abstracts. A vague, hedged results section reads as exactly what it is. A clean, honest descriptive abstract reads as confident and well-planned.

Know which format you’re writing before you start.

Which Conference Types and Academic Fields Accept Abstracts Without Results?

The short answer is: more fields than you probably think. But the specifics matter, because submission norms vary quite a bit depending on where you’re submitting and what kind of research you do.

STEM Fields — Science, Technology, Engineering, and Mathematics

STEM conferences have a complicated relationship with results-free abstracts. Some won’t touch them. Others actively expect them.

The Institute of Electrical and Electronics Engineers (IEEE) and the Association for Computing Machinery (ACM) both host hundreds of conferences annually, and many of those events explicitly accept abstracts based on a strong research objective and methodology — especially when the work is ongoing or when full results won’t exist until closer to the presentation date. Symposia focused on emerging technologies are particularly open to this. The reasoning is practical: the field moves fast, and requiring complete data at abstract submission time would exclude a lot of genuinely relevant work.

That said, you need to be careful with IEEE and ACM. Some flagship conferences expect at least preliminary results in the abstract. Always read the call for papers (CFP) carefully. Look for language like “ongoing research welcome” or “preliminary work considered.” If the CFP doesn’t say that, email the conference program committee and ask directly. That’s not a weird thing to do — it’s the smart thing.

In life sciences and clinical research, it’s common to submit abstracts mid-study. Conferences in those areas often have explicit abstract revision policies that let you update your submission before the final program goes out.

Social Sciences and Humanities

This is where results-free abstracts are most normalized. Honestly, in many social science contexts, submitting without final results isn’t just acceptable — it’s expected.

The American Sociological Association (ASA) and the American Educational Research Association (AERA) both run major annual conferences with calls for papers that routinely accept work-in-progress. In qualitative research especially, the idea of “final results” is often fluid. Your methodology, your research gap, your theoretical framing — those things carry significant weight with reviewers. A well-argued research objective can get you through peer review on its own if the question you’re asking is sharp enough.

Humanities conferences operate similarly. The Modern Language Association (MLA) conference, for example, accepts proposals based largely on argument and approach. You’re typically pitching an intellectual position or a line of inquiry, not reporting a completed experiment. Future tense in academic writing is completely normal here. So is conditional language in research — phrases like “this paper will argue” or “the analysis is expected to show.”

One thing that doesn’t change across social sciences and humanities: vagueness kills abstracts. Even without results, you need a concrete research methodology and a clear sense of your anticipated findings. Reviewers aren’t looking for certainty. They’re looking for seriousness.

Work-in-Progress Abstracts — A Special Submission Category

Some conferences solve the whole problem by creating a dedicated submission track for it. Work-in-progress abstracts are a formal category at many major conferences, and if this option exists, you should use it.

These tracks are common in computer science, education research, and design fields. AERA has structured sessions specifically for emerging scholars sharing ongoing research. ACM’s CHI conference has a well-known works-in-progress track with its own abstract word limit and formatting requirements, separate from full papers.

Submitting as a work-in-progress does a few things for you. It signals to the conference program committee that you’re not claiming finished findings. It shifts the evaluation criteria — reviewers know they’re assessing potential and methodology, not outcomes. And it removes the academic integrity pressure that comes with implying your results exist when they don’t.

There’s a practical upside too. Work-in-progress sessions often involve poster presentations or short talks rather than full conference papers. That gives you more flexibility and, frankly, a better fit for where your research actually is before the abstract submission deadline hits.

If a work-in-progress track is available and your research is genuinely in progress, don’t submit to the main track and stretch the truth about your results. Use the right category. Conference organizers build those tracks for exactly your situation.

Conference Abstract Submission Timelines — How Far in Advance Do You Need to Submit?

Timing matters more than most researchers expect. Miss the abstract submission deadline by a day and you’re out — full stop. Conference program committees don’t negotiate on this, and there’s rarely an appeals process for late submissions.

Here’s the general picture: major academic conferences typically open their call for papers (CFP) anywhere from six to twelve months before the conference date. The abstract deadline usually falls three to six months before the event itself. That’s your window.

How Timelines Differ by Field

Large STEM conferences run on tight, predictable schedules. The Institute of Electrical and Electronics Engineers (IEEE) and the Association for Computing Machinery (ACM) often set abstract deadlines that land one to two weeks before the full paper deadline. So you’re committing your title, scope, and methodology before you’ve even finalized your paper. That’s not unusual — it’s just how their submission pipeline works.

Social sciences move differently. The American Sociological Association (ASA) annual meeting typically opens abstract submissions about eight months out. The American Educational Research Association (AERA) follows a similar rhythm, often publishing their CFP in the summer for a conference held the following spring. That longer lead time is partly because peer review for accepted proposals involves significant back-and-forth.

Humanities conferences — including those organized under Modern Language Association (MLA) guidelines — can be even earlier. Some MLA panels have abstract deadlines nine to ten months ahead of the conference. If you’re presenting ongoing research or a work-in-progress abstract, that timeline means your “anticipated findings” section is doing real work. You may be projecting outcomes you haven’t touched yet.

Why the Gap Is Actually Useful for Incomplete Research

If you’re submitting without results, a long lead time is your friend, not your enemy. You have months between abstract acceptance and the conference itself — enough time for preliminary results to emerge, data collection to finish, or at least for your analysis to solidify.

The abstract you submit in October for a June conference doesn’t have to match your final presentation exactly. Most conferences have an abstract revision policy that allows minor updates to your abstract or presentation scope after acceptance. Check this explicitly in the CFP documentation. Some conferences — especially in STEM — require you to submit final slides or a camera-ready abstract months later, which is a second opportunity to incorporate actual data.

What the program committee is reviewing initially is your research gap, research objective, and research methodology. They’re deciding whether your work fits the conference themes, not whether your results are complete.

Practical Timing Advice

Set a reminder the day the CFP drops — not the week before the deadline. Here’s why: abstract word limits are typically strict (150 to 500 words depending on the conference), and writing a tight abstract under that constraint takes more drafting than you’d expect. Leaving yourself two to three weeks to draft, get feedback, and revise is realistic.

Also watch for multi-stage submission processes. Some conferences ask for a short abstract first (100–200 words), then a longer extended abstract or proposal if you pass the first screen. Each stage has its own deadline. Missing the first one eliminates you from both.

One more thing: if your research is genuinely ongoing, say so cleanly in your submission. Describing your work as ongoing research or framing expected contributions in conditional language isn’t a weakness — it’s honest, and most peer reviewers on the program committee respect it. What they won’t respect is a vague abstract that reads like you don’t know what you’re doing yet. Know your methodology cold. That’s what carries the submission.

How to Write a Conference Abstract Without Results — A Step-by-Step Guide

Writing an abstract without results isn’t just about leaving a section blank and hoping for the best. You need to construct the abstract so that the absence of results feels intentional and academically justified — not like a rushed submission. Each component has to work harder to compensate for what isn’t there yet.

Here’s how to do it systematically.

Step 1 — Clearly Establish the Background and Research Gap

Your first two to four sentences need to orient the reader fast. State the broad topic, then immediately narrow to the specific problem or gap your research addresses. Don’t spend half your word count on background — conference abstracts are typically 150 to 300 words, and the program committee isn’t reading a lit review.

The research gap is the hinge point. It’s what justifies why your study needs to exist at all. Something like: “While studies on X have examined Y extensively, the relationship between Z and W in low-resource settings remains poorly understood.” That’s a gap. Be precise about it.

Vague gaps get rejected. “Little research exists on this topic” is weak. Cite the actual boundary of existing knowledge — what’s been done, where it stops, and what falls through.

Step 2 — State Your Research Objective and Research Question Directly

Don’t bury this. The research objective should appear as a clear, standalone statement. Program committees read dozens of abstracts quickly. If they have to hunt for what your study is actually trying to do, you’ve already lost them.

One clean sentence works better than three hedged ones. Something like: “This study examines how first-generation college students navigate institutional support structures in STEM programs at community colleges.”

If your conference uses a structured abstract format — common at AERA and some IEEE tracks — you may have a labeled “Objective” field. Fill it exactly as asked. If it’s a free-form abstract, still make the objective unmistakable, even without a label.

Avoid stating your question so broadly that it could apply to fifty other studies. Specificity signals methodological maturity, even when data collection is still ongoing.

Step 3 — Describe Your Methodology in Sufficient Detail

This is where no-results abstracts live or die. Without findings to point to, your methodology becomes the primary evidence that the work is credible and executable.

You need to cover four things concisely:

1. Research design — qualitative, quantitative, mixed methods, computational, archival, experimental
2. Data sources or participants — interviews with 30 practitioners, a dataset of 10,000 GitHub repositories, archival records from 1945–1970
3. Analytical approach — thematic analysis, regression modeling, discourse analysis, network analysis
4. Current status — data collection underway, IRB approved, pilot completed

That last one matters. Saying “data collection is currently underway” tells the committee this isn’t speculative — it’s in motion. ACM and ASA conference submissions both tend to scrutinize methodology closely in no-results abstracts, because the method is essentially your proof of concept.

Keep it tight. Three to five sentences is usually enough. You’re not writing a methods section — you’re demonstrating that one exists.

Step 4 — Articulate Your Expected Contributions or Anticipated Findings

This is your forward-looking argument. It replaces where results would normally go, so it needs to be substantive, not wishful.

Anticipated findings should be grounded in your theoretical framework or preliminary data. If you have any preliminary results — even from a pilot study or initial coding pass — mention them briefly. “Preliminary analysis of 8 interviews suggests three recurring themes related to institutional gatekeeping” is much stronger than “we expect to find interesting patterns.”

Expected contributions should answer a direct question: so what? Why does it matter to the field if your study finds what you think it will find? Frame this in terms of theoretical contribution, practical implication, or methodological advancement — whichever is most relevant to your field and that particular conference’s focus.

MLA-aligned humanities conferences often care most about interpretive contribution. IEEE and ACM audiences want to know about technical or systems-level impact. Calibrate accordingly.

One to three sentences here. Don’t oversell. The committee knows you don’t have results yet.

Step 5 — Use the Correct Language and Tense Throughout

This is a technical issue that trips people up. Using the wrong tense doesn’t just look sloppy — it can misrepresent the status of your research, which creates academic integrity problems.

For ongoing or future work, use:

• Future tense: “This study will analyze…”, “Findings will be presented…”
• Present progressive: “Data collection is currently underway…”
• Conditional language: “Results are expected to reveal…”, “The analysis is anticipated to show…”

Avoid past tense for anything that hasn’t happened yet. Writing “the study found” when you have no findings is a misrepresentation — and a serious one. Some conferences have abstract revision policies that allow updates closer to the presentation date, but that doesn’t give you permission to write as if work is complete when it isn’t.

Work-in-progress abstracts submitted to conferences like AERA or ASA’s annual meeting often use explicitly conditional framing throughout, and reviewers expect it. It’s not a weakness. It’s the appropriate academic register for research at this stage.

One practical tip: after drafting the full abstract, read through it once specifically checking tense. It’s easy to slip into past tense mid-paragraph without noticing, especially if you’ve been writing journal article abstracts alongside conference submissions.

How Reviewers Evaluate Conference Abstracts Submitted Without Results

Peer reviewers on a conference program committee are not expecting a finished study when they open your abstract. They know the timeline. Most abstracts are submitted months before the conference, and for many disciplines — especially in STEM conferences, social sciences conferences, and humanities conferences — work-in-progress submissions are a normal part of the process.

What reviewers are doing is making a judgment call: is this research worth a slot in the program?

That question gets answered by looking at a few specific things.

Clarity of the Research Problem

Reviewers want to see that you’ve identified a real research gap and can articulate it clearly. If your abstract opens with vague background and never pins down what problem you’re actually solving, it reads as underdeveloped — results or no results.

Be specific about what’s missing in the current literature and why your study addresses it. Two clear sentences here beat five rambling ones.

Soundness of the Research Methodology

This is where abstracts without results either earn trust or lose it. If you have no findings to show yet, your methodology becomes the evidence that you know what you’re doing.

Reviewers — particularly at IEEE, ACM, and AERA — will look hard at whether your research design is appropriate for your stated research objective. A vague “mixed methods approach will be used” tells them almost nothing. Naming the specific methods, your sample or data source, and your analytical framework tells them you have an actual plan.

Think of it this way: the methodology section of your abstract is doing the work your results can’t do yet.

Feasibility and Timeline Credibility

Can you realistically complete this research before the conference? Reviewers ask themselves this question whether they write it in their comments or not.

If your abstract submission deadline is eight months before the event, and you describe preliminary results already collected, that’s reassuring. If you’re describing a five-year longitudinal study with no data collected yet and the conference is in six months, that raises flags.

Be honest about where you are. If you have preliminary results, mention them. Even partial data strengthens your case significantly.

Quality of the Anticipated Findings and Expected Contributions

You don’t have results, but you do need to explain what you expect to find and why it matters. This is where conditional language in research and future tense in academic writing become practical tools, not stylistic choices.

Phrases like “findings are expected to show” or “results will likely indicate” signal that you understand the difference between confirmed findings and projections. Reviewers in the American Sociological Association (ASA) and Modern Language Association (MLA) communities are used to this framing. It’s not hedging — it’s appropriate epistemic honesty.

What reviewers penalize is overclaiming. Don’t write “this study will prove” when you mean “this study will examine.” Academic integrity matters here, and reviewers notice when anticipated findings are stated with more certainty than the methodology can support.

Fit with the Conference Theme and Call for Papers

A technically solid abstract that doesn’t connect to the conference’s call for papers (CFP) still gets rejected. Reviewers score for thematic fit, and this is something you can control completely.

Read the CFP carefully. Use the language it uses. If the conference is organized around a specific theoretical framework or disciplinary concern, show how your research objective connects to it. This isn’t gaming the system — it’s demonstrating that you understand the scholarly conversation you’re entering.

The Abstract Word Limit and Writing Quality

This one sounds administrative, but it carries real weight. Reviewers are reading dozens or hundreds of abstracts. One that respects the abstract word limit, uses clear sentences, and doesn’t bury its point signals that the researcher can communicate — which matters for a conference presentation.

An abstract for a work-in-progress submission needs the same writing discipline as any other. Sloppy prose, excessive jargon, or going over the word count by 30% creates a negative impression before reviewers even evaluate the substance.

What Actually Gets You Rejected

Submitting without results doesn’t get you rejected. These things do:

• No clear research gap or problem statement
• A methodology so vague it’s unverifiable
• Anticipated findings that aren’t connected to the described methods
• Overclaiming what the research will “prove”
• Ignoring the CFP theme entirely
• Poor writing that makes the research hard to follow

If your abstract avoids those problems, the absence of final results is almost never a dealbreaker — especially for ongoing research in fields where the conference program committee actively invites work at earlier stages.

How to Check Conference-Specific Policies on Abstract Submission

Don’t assume. That’s the short version.

Every conference runs on its own rules, and what’s acceptable at an American Educational Research Association (AERA) annual meeting might not fly at an Institute of Electrical and Electronics Engineers (IEEE) technical symposium. The only way to know for certain is to go directly to the source.

Start with the Call for Papers

The call for papers (CFP) is your first stop. Every legitimate academic conference publishes one, and it usually contains more detail than people bother to read. Look specifically for language like:

• “work-in-progress submissions welcome”
• “preliminary results accepted”
• “results not required at time of submission”
• “research in progress track”

If any of those phrases appear, you’re in the clear. If the CFP says something like “submissions must include findings” or “results should be clearly stated,” that’s a signal to pay close attention.

Some conferences — particularly in STEM fields — run separate tracks specifically for ongoing research. The Association for Computing Machinery (ACM), for example, often distinguishes between full paper abstracts and work-in-progress poster submissions. Check whether those tracks have different abstract word limits or formatting requirements. They usually do.

Look for Submission Category Breakdowns

Most CFPs don’t just list one submission type. You’ll typically see a breakdown: full papers, short papers, posters, panels, workshops, and sometimes a dedicated work-in-progress category. Each has its own expectations.

If there’s a work-in-progress abstract category, that’s where abstracts without results belong. Don’t try to submit an incomplete study under the full paper category and hope reviewers won’t notice. They will.

Check the Conference Program Committee’s Past Proceedings

This takes an extra ten minutes, but it’s worth it. Go to the conference website and find proceedings from the last one or two years. Download a few abstracts from the same submission category you’re targeting. If you see abstracts written in future tense or conditional language — phrases like “this study will examine” or “we expect to find” — that tells you the conference program committee has accepted similar work before.

The American Sociological Association (ASA) annual meeting and Modern Language Association (MLA) conference proceedings are publicly searchable. Use them as reality checks.

Email the Organizers Directly

If the CFP is ambiguous, email. Keep it short. Something like: “I’m preparing a submission for [conference name]. My study is ongoing and results won’t be available at submission time. Do you accept abstracts based on research objectives and methodology alone, or are preliminary results expected?”

You’ll get one of three responses: yes, no, or “submit under the work-in-progress track.” Any of those is useful. What you can’t afford is to guess wrong and waste a submission.

Check the Abstract Revision Policy

This matters more than people realize. Some conferences allow you to update your abstract after initial acceptance — meaning you could submit now and revise with actual results closer to the presentation date. Others lock in your submission the moment it passes peer review.

If the conference has an abstract revision policy, it’s usually buried in the FAQ or the submission portal guidelines. Search the conference website for “revision” or “update submission.” If you can revise later, that changes your strategy significantly — you can submit now with anticipated findings and update with real data before the program is finalized.

Red Flags That Mean You Should Probably Wait

Some signals in a CFP mean a conference genuinely isn’t a good fit for incomplete research:

• The abstract submission deadline is only 6–8 weeks before the conference date (reviewers expect polished, complete work)
• The submission portal requires you to fill in a mandatory “Results” field with no option to mark it as pending
• The CFP explicitly states abstracts will be evaluated on contribution to the field based on demonstrated findings

Academic integrity matters here. Submitting to a conference that clearly expects complete results — and writing vague language to obscure the fact that you don’t have them yet — isn’t a gray area. It’s a problem. Find a conference that openly welcomes ongoing research instead. There are plenty of them.

What to Do If Your Results Arrive After Submission — Updating and Revising Your Abstract

This happens more often than you’d think. You submit your abstract in October, your data collection wraps up in January, and suddenly you have actual findings sitting in your hands — but the conference isn’t until April. Now what?

The answer depends entirely on the conference’s abstract revision policy, and yes, that’s something you need to check before you assume anything.

Check Whether the Conference Allows Revisions at All

Some conferences lock your abstract the moment submission closes. Others — particularly larger ones organized by bodies like the American Educational Research Association (AERA) or the Association for Computing Machinery (ACM) — have a formal revision window, usually a few weeks after acceptance notifications go out. Check the call for papers (CFP) first. If it says nothing about revisions, email the conference program committee directly and ask. Be specific: tell them your results have come in and you want to know if you can update your abstract before it’s printed in the program.

Don’t assume silence means no. A short, polite email often gets a practical answer.

What You Can Typically Change — and What You Can’t

Even when revision is allowed, it’s usually not a blank slate. Most committees will let you:

• Swap anticipated findings for actual results
• Adjust your contribution statement to reflect what you genuinely found
• Tighten language that was speculative (“results are expected to show”) into declarative statements
• Fix the abstract word limit compliance if your revision runs long

What they typically won’t let you change: your core research objective, your methodology, or the fundamental framing of the paper. If your results came back and completely overturned your hypothesis, that’s a different situation — and a much harder conversation to have with the program committee.

Update the Abstract You’ll Actually Present, Not Just the Submitted One

Here’s something researchers sometimes miss. Even if the conference locks the abstract that appears in the program booklet, you’re still presenting a talk or poster. Your slide deck, your handouts, your poster — none of those are frozen. Update everything you physically present to reflect your real results.

The abstract in the conference program is a record of what you intended to study. Your presentation is what you actually did. Reviewers and attendees understand that difference. They’ve lived it themselves.

Be Honest About What Changed

Academic integrity matters here. If your results came in and they’re substantially different from what you anticipated — say, your hypothesized correlation didn’t hold — don’t quietly bury that in your presentation. Acknowledge it directly. Frame it as a finding in itself. A null result or an unexpected outcome that you address honestly is far more valuable to your audience than a presentation that quietly sidesteps what actually happened.

The peer review process that got your abstract accepted was based on your research question and methodology, not a guarantee of a specific result. You’re not obligated to manufacture findings that match your abstract. You are obligated to present honest research.

When the Results Don’t Arrive in Time

Sometimes they just don’t. The conference runs in March, your analysis won’t be done until June, and that’s that. In this case, present what you have. Preliminary results, partial data, early-stage analysis — these are legitimate and genuinely useful to conference audiences. Be upfront about where you are. Say clearly during your presentation that full analysis is ongoing, and tell attendees when and where they can expect the complete work.

Conferences, especially in STEM fields like those affiliated with the Institute of Electrical and Electronics Engineers (IEEE), often include ongoing research tracks precisely because this is normal. You’re not failing to deliver. You’re showing your work in progress, which is exactly what that submission category was designed for.

Ethical Considerations of Submitting a Conference Abstract Before Research Is Complete

Submitting before you have results isn’t inherently problematic. But it can become a serious issue depending on how you frame what you have — and what you claim you’ll have by presentation day.

The core ethical obligation is straightforward: don’t misrepresent the state of your research. If your data collection hasn’t started, say so. If you have preliminary results but not final ones, describe them accurately. What you cannot do is write as though your findings are confirmed when they aren’t. That’s where honest researchers sometimes slip — not out of malice, but because they’re trying to sound more credible to reviewers.

The Problem with Overstating Anticipated Findings

This is the most common ethical misstep. Researchers write something like “this study will demonstrate that X causes Y” instead of “this study aims to examine the relationship between X and Y.” The first framing implies certainty you don’t have. The second is accurate.

Using conditional language in research isn’t just stylistic — it’s a commitment to academic integrity. Phrases like “we expect to find,” “preliminary analysis suggests,” or “results are anticipated to show” signal to the conference program committee and to readers that the work is ongoing. That’s honest. That’s acceptable.

What crosses the line is presenting fabricated or placeholder results as real data, even temporarily. Some researchers justify this by saying they’ll update the abstract before the conference. That doesn’t make the original submission acceptable.

Can You Submit Work You Might Not Finish?

This is a real concern, especially for PhD students and early-career researchers working on tight timelines. Life happens. Data collection stalls. Lab results take longer than expected.

The honest approach: submit only if you genuinely believe the work will be complete — or at least substantially advanced — by the presentation date. Conferences aren’t publication venues, so a work-in-progress abstract is standard practice at organizations like the American Educational Research Association (AERA) and the American Sociological Association (ASA). Both explicitly accommodate ongoing research. But that accommodation assumes you’re actually doing the work, not speculating about research you haven’t committed to.

If there’s real uncertainty about whether you’ll finish, reach out to the conference organizers before submitting. Ask about their abstract revision policy. Many conferences, including those run under the ACM and IEEE umbrellas, have mechanisms for withdrawing or updating submissions when circumstances change.

Withdrawal Is an Option — Use It Honestly

Pulling a submission isn’t a failure. If your research direction changes significantly, or you realize the methodology you proposed isn’t going to work, withdrawing the abstract is the responsible move. Presenting work that no longer reflects what you actually did — because you felt committed to a submission you can’t deliver on — damages your credibility more than a withdrawal ever would.

The conference program committee builds the schedule around accepted abstracts. Withdrawing late creates logistical problems for them. Do it as early as possible if you need to.

What About Co-Authors and Collaborative Research?

If the abstract lists multiple authors, every listed person should know about the submission and agree to its content. This sounds obvious, but it’s violated more often than it should be, particularly when a graduate student submits on behalf of a lab team under time pressure before the abstract submission deadline.

All named authors carry responsibility for the claims in the abstract. If the research is ongoing, all co-authors should agree on what language is appropriate for describing anticipated findings and expected contributions. Getting everyone on the same page before submission prevents disputes later — especially if the research evolves differently than expected.

The Specific Risk in STEM Versus Humanities Contexts

In STEM conferences, like those run by IEEE or ACM, reviewers are often more sensitive to claims about results because technical findings are verifiable. Overstating a preliminary result in an engineering or computer science abstract can damage your reputation in a field where precision matters intensely.

In social sciences conferences and humanities conferences — think MLA events or ASA annual meetings — theoretical framing and research objective clarity often carry more weight than numerical results. That doesn’t mean ethical standards are lower. It means the ethical risks manifest differently. In humanities contexts, the concern is more about misrepresenting your theoretical position or claiming a research gap that doesn’t actually exist.

Either way, the standard is the same: represent your work accurately for the stage it’s at.

Common Mistakes to Avoid When Writing a Conference Abstract Without Results

Most rejections of results-free abstracts don’t happen because reviewers dislike the concept. They happen because the abstract makes avoidable errors that signal the research isn’t ready — or that the author doesn’t quite understand what they’re asking reviewers to accept. Here are the ones that show up most often.

Promising Results You Don’t Have

This is the biggest one. Writing “this study will demonstrate that X causes Y” is a claim of certainty you cannot make yet. It’s not just premature — it’s an academic integrity problem.

Use conditional language. “This study expects to find,” “results are anticipated to show,” or “the analysis may reveal” are all honest ways to frame anticipated findings without overcommitting. STEM conferences like IEEE and ACM are particularly sensitive to this, since reviewers often have the technical background to spot inflated claims immediately.

Be careful with phrasing like “this research proves” or “findings confirm.” Those belong in a post-study abstract. Not here.

Being Vague About Methodology

If you don’t have results, methodology is doing a lot of heavy lifting. Reviewers need to trust that your approach will actually produce something worth hearing about at the conference.

Saying “qualitative methods will be used” tells nobody anything useful. What kind? Interviews? Discourse analysis? Grounded theory? At the American Sociological Association (ASA), for instance, reviewers expect to see enough methodological specificity to evaluate whether the design fits the research objective. The same applies across humanities conferences submitting to MLA — even textual analysis needs some framing of scope and interpretive approach.

A one-line methodology description is almost always insufficient when you’re submitting without results.

Ignoring the Research Gap

Some abstracts jump straight to “here’s what I’m doing” without ever explaining why it matters. That’s a structural problem.

The research gap is what justifies the whole submission. If you don’t name what’s missing from existing literature — or what problem your work addresses — reviewers have no way to assess the contribution your anticipated findings might make. This is especially true in social sciences conferences, where the framing of a problem often carries as much weight as the methodology.

One or two clear sentences identifying the gap is enough. You don’t need a literature review in 250 words.

Overloading the Abstract with Background

The flip side of ignoring context is drowning in it. Some researchers, anxious about the absence of results, fill the abstract with extensive background to compensate. It doesn’t help.

Abstracts have strict word limits — often 200 to 350 words depending on the conference. Every sentence spent on background is a sentence not spent on your methodology, expected contributions, or research objective. The conference program committee isn’t reading an introduction. They’re evaluating a proposal.

Cut background to the minimum needed to make the gap and the study make sense.

Misreading the Call for Papers

The call for papers (CFP) usually tells you exactly what the abstract should include. Not reading it carefully is a surprisingly common mistake.

Some conferences specify that they accept work-in-progress abstracts only under certain tracks. Others require you to flag that results are pending. The American Educational Research Association (AERA), for example, has distinct submission categories with different requirements depending on how far along the research is. Submitting a results-free abstract to the wrong track — or failing to check whether the conference accepts them at all — wastes your time and the reviewer’s.

Read the CFP before you write a single sentence.

Using Future Tense Carelessly Throughout

Future tense in academic writing is fine when used deliberately. Used carelessly, it makes the whole abstract sound like a wish list rather than a research plan.

The trick is to mix tenses with intention. Present tense works well for describing the research gap and framing the problem. Future or conditional tense fits the methodology and anticipated findings. Something like: “Existing studies have not examined X in context Y. This study addresses that gap by applying [method]. Results are expected to [outcome].” That reads as a coherent research plan, not a rough idea.

Submitting Without a Second Reader

This one is simple. You’re too close to your own work to catch every weak claim or vague passage.

Get someone — a colleague, a supervisor, a fellow researcher in your field — to read the abstract before you hit submit. Specifically ask them: “Does this convince you the research is worth hearing about at a conference, even without results yet?” If they hesitate, revise before the abstract submission deadline. After submission, depending on the conference’s abstract revision policy, you may have limited or no ability to fix it.

Frequently Asked Questions

Can I submit a conference abstract without having any results at all?

Yes. Many conferences — especially in STEM, social sciences, and humanities — accept abstracts based on your research question, methodology, and expected contributions. The key is being transparent. Don’t imply you have results when you don’t. Use future tense and conditional language to describe anticipated findings, and frame your submission as ongoing research. Organizations like the American Educational Research Association (AERA) and the Association for Computing Machinery (ACM) explicitly welcome work-in-progress abstracts.

Will reviewers reject my abstract just because it has no results?

Not automatically. The conference program committee is usually evaluating whether your research question matters, whether your methodology is sound, and whether the work fills a real research gap. A well-argued abstract with a clear research objective and solid method can score just as well as one with preliminary results. That said, weak abstracts with no results and no clear direction will get rejected — so the bar is still high.

What tense should I use when writing about findings I don’t have yet?

Use future tense and conditional language. Phrases like “the study will examine,” “results are expected to show,” or “findings are anticipated to contribute” are all standard in academic writing for in-progress work. Avoid writing “results show” or “data reveals” — that implies completed work you don’t have, which becomes an academic integrity issue.

How long should a conference abstract without results be?

Follow the abstract word limit in the call for papers (CFP). Most conferences set limits between 150 and 500 words. Don’t try to pad it because you lack results. A tight 250-word abstract that clearly states your problem, methodology, and expected contributions is stronger than a vague 400-word one that dances around the absence of data.

What if my results come in after I submit but before the conference?

Most conferences have an abstract revision policy that allows minor updates before the program is finalized. Check that policy immediately after submission. If you get results in time, update your abstract to reflect them — it strengthens your presentation. The Institute of Electrical and Electronics Engineers (IEEE) and similar organizations typically specify revision windows in their submission portals.

Is it dishonest to submit to a conference before my research is complete?

No — as long as you’re honest about where your research stands. Misrepresenting your progress is the problem, not the absence of results. Academic integrity means accurately representing your work. A work-in-progress abstract that honestly describes ongoing research is completely legitimate. What crosses the line is fabricating or implying data that doesn’t exist.

Do social sciences and humanities conferences treat this differently than STEM?

A little. The American Sociological Association (ASA) and Modern Language Association (MLA) have long operated with abstract-first submission models where theoretical framing and argument matter more than empirical results. STEM conferences like those run by ACM or IEEE increasingly accept work-in-progress tracks. The norms differ slightly, but the core expectation — honest, rigorous framing — is the same across all of them.

What happens if I get accepted but still don’t have results by the conference date?

You present what you have. Be upfront with your audience about the research status. Many conference presentations from ongoing studies focus on the methodology, theoretical framework, and preliminary signals rather than final conclusions. Audiences at academic conferences understand this. What you should not do is manufacture results or overstate what limited data you have.

Conclusion — Research in Progress Is Not a Reason to Sit Out a Conference

Waiting until your data is fully collected and analyzed before submitting a conference abstract is a choice, not a requirement. And for a lot of researchers, it’s a choice that costs them valuable opportunities.

The reality is that conferences — whether that’s AERA, ACM, ASA, or a smaller discipline-specific gathering — regularly accept work-in-progress submissions. They do it because the academic community benefits from hearing about ongoing research, not just finished projects. A well-framed abstract that clearly states your research gap, research objective, and methodology tells reviewers plenty. You don’t need results to make a convincing case that your work belongs on the program.

What you do need is honesty. Use conditional language and future tense deliberately. “This study will examine…” or “Findings are expected to…” aren’t hedges you should be embarrassed about. They’re accurate. They reflect where you actually are in the process, and experienced peer reviewers understand that.

A few things to keep in mind as you move forward:

• Always read the call for papers carefully. Some conferences have a specific work-in-progress track; others expect preliminary results even if they don’t say so explicitly.
• Check the abstract revision policy before you submit. If your results come in before the conference, some programs will let you update your abstract. Some won’t.
• Stick to the abstract word limit. This doesn’t change just because you’re writing without results.
• Don’t invent findings you don’t have. That’s where expected contributions cross into academic integrity territory.

Your research methodology is doing more work than you might think in an abstract without results. It’s the section that shows reviewers you have a real plan, not just an idea. Treat it accordingly.

The conference program committee isn’t looking for a finished dissertation. They’re looking for work that adds something to the conversation in their field — in STEM conferences, social sciences conferences, humanities conferences, wherever your work sits. A clear research objective and a compelling framing of the research gap can absolutely meet that bar.

Submit the abstract. Go to the conference. Present the work where it actually stands. That’s how a lot of the best academic conversations get started.