Tutorials
Beating Novelty Rejections at NeurIPS: A 7-Step Playbook
A practical guide for ML researchers on framing novelty, surviving reviewer critiques, and writing rebuttals that actually move scores at NeurIPS, ICLR, and CVPR.
October 2, 2026
Every ML researcher knows the sting of a 'limited novelty' review score. You spent nine months on a paper. The reviewer spent nine minutes on it. And somehow 'this feels incremental' becomes the hill your submission dies on.
So how do you fight back? This tutorial walks through a 7-step playbook for addressing novelty concerns in AI conference papers, inspired by a recent r/MachineLearning thread where a computer vision researcher asked exactly this question. We'll cover how to frame contributions, write bulletproof rebuttals, and distinguish meaningful incremental progress from work reviewers will reject on sight.
What You'll Learn
By the end of this guide, you'll know how to:
- Diagnose what reviewers actually mean when they write 'novelty is limited'
- Structure your intro so novelty is impossible to miss
- Write a rebuttal that moves borderline scores
- Decide whether to resubmit, re-scope, or redirect to a workshop
- Use tools like Claude to pressure-test your framing before submission
This is written for researchers submitting to NeurIPS, ICLR, CVPR, ICML, and similar venues. The same principles apply to EMNLP and ACL, with minor adjustments.
Prerequisites
You should have:
- A draft paper, or at least a complete method and experimental section
- Access to the venue's reviewer guidelines (seriously, read them)
- A thick skin (not optional)
- Ideally, a mentor or senior collaborator who's reviewed before
And one mindset shift: novelty isn't a property of your idea. It's a property of how you present your idea against the backdrop of prior work. Two papers can describe the exact same technique. One gets rejected as incremental. The other wins a best paper award. The difference is framing.
Step 1: Diagnose What 'Not Novel' Actually Means
When a reviewer says your paper lacks novelty, they almost never mean 'this exact idea exists.' They usually mean one of five things:
- Too close to a specific prior work they've read
- The delta from baselines is unclear or seems small
- The problem is well-trodden and your angle isn't fresh
- The method is a known combination of existing components
- They didn't understand what's new because you buried it
Each of these needs a different response. If you don't diagnose correctly, your rebuttal will miss. Read the review three times. Highlight the exact sentence where novelty is challenged. Then ask: which of the five is this?
Most 'incremental' critiques are actually category 5 (buried novelty) in disguise. The reviewer skimmed. The novelty wasn't on the first page. They moved on.
Step 2: Front-Load Your Contribution
Your abstract should say what's new in sentence one or two. Not after a paragraph of context. Not in the fourth bullet of your intro. First. Sentences.
A weak novelty frame reads:
We study the problem of X. Prior work has approached X via A, B, and C. In this paper, we propose a new method.
A strong frame reads:
We identify a failure mode in method A that causes a 12% accuracy drop on long-tail classes. We fix it with a reweighting scheme that requires zero additional parameters and recovers 9 of those 12 points.
The second version does three things the first doesn't. It names a specific gap. It quantifies impact. And it hints at the mechanism. A reviewer who reads only your abstract knows exactly what's novel.
Step 3: Build a Novelty Checklist Table
Include a comparison table in your intro or related work section. Not for benchmarks. For contributions. Columns should include closest prior methods. Rows should list specific capabilities or properties.
| Property | Method A (2024) | Method B (2025) | Ours |
|---|---|---|---|
| Handles long-tail distributions | No | Partial | Yes |
| Zero extra params | Yes | No | Yes |
| Works on video | No | No | Yes |
| Theoretical guarantee | No | No | Yes |
This is one of the highest-value additions you can make. Reviewers love it because it respects their time. And it forces you to actually articulate your deltas, which is a useful exercise even if you don't ship the table.
The NeurIPS 2024 reviewer guidelines explicitly ask reviewers to assess 'how the submission advances the state of the art.' A table does that assessment for them.
Step 4: Separate Technical Novelty From Empirical Novelty
Not every paper needs a new algorithm. Some papers are novel because they ask a new question. Others because they produce a new dataset, a surprising empirical finding, or a counterexample that forces the field to rethink an assumption.
Name the type of novelty you're claiming. Explicitly. Something like:
- 'Our contribution is empirical: we show that technique X, assumed to require pretraining, works equally well from scratch.'
- 'Our contribution is methodological: we introduce the first algorithm that satisfies properties P1 and P2 simultaneously.'
- 'Our contribution is conceptual: we reframe problem Y as an instance of problem Z, enabling tools from Z to apply.'
Reviewers will often default to 'is this a new algorithm?' as their novelty test. If your paper is novel in a different way, you need to redirect them. Explicitly.
Step 5: Address the 'It's Just a Combination' Attack
This is the most common novelty attack and the easiest to pre-empt. If your method combines known components (attention + MoE + distillation, for instance), reviewers will accuse you of 'engineering not research.'
Two defenses work:
Defense A: Non-obvious combination. Explain why the combination wasn't obvious. Point to papers that tried similar combinations and failed. Point to interactions between components that only emerge when combined in your specific way. If component X ablates to -8% but component Y ablates to only -1% individually, yet removing both drops 15%, you have evidence of non-trivial interaction.
Defense B: The combination enables something new. Maybe no single prior work hits all three of (fast inference, small memory, long context). Your combo does. That's novelty, even if each piece is known. Make the capability explicit.
Step 6: Write the Rebuttal Like a Lawyer, Not a Scientist
Rebuttals aren't the time to argue the deep merits of your work. They're the time to move specific scores. Here's the structure that works:
- Thank reviewers once, briefly. Then stop with the pleasantries.
- For each novelty concern, quote the exact review text. This forces precision.
- State your response in one punchy sentence. Not a paragraph. One sentence.
- Follow with 2-3 sentences of evidence. Cite your own paper's section numbers, new experiments if the venue allows, or specific prior-work comparisons.
- End with a concrete paper change. 'We will add a paragraph on this in Section 3.2.' Reviewers like seeing concrete action.
And this is where AI assistants genuinely help. Running your rebuttal through Claude with a prompt like 'play a skeptical NeurIPS area chair, find the weakest argument' catches soft spots that your co-authors miss because they're too close to the work. ChatGPT works fine for this too, though in my view Claude Opus 4.6 is pretty solid at academic writing critique specifically.
Step 7: Know When to Fold
Some papers really are too incremental for a top venue. That's not a moral failing. It's a signal to either:
- Submit to a specialized workshop where the audience will value the specific contribution
- Combine with a follow-up result into a stronger single submission
- Rework the framing entirely around a different lead claim
The r/MachineLearning community has debated this extensively, and the rough consensus is that pushing a borderline paper through multiple top-venue rejections burns more time than a thoughtful workshop submission plus a stronger resubmission six months later.
Tips and Common Pitfalls
Pitfall 1: Overclaiming in the abstract. If your abstract promises a breakthrough and your experiments show a 2-point MMLU gain, reviewers will punish you harder than if you'd stated the real contribution plainly. Overclaiming is the fastest way to turn a positive review negative.
Pitfall 2: Ignoring the 'why now' question. Why wasn't this paper written in 2023? If a reviewer can't answer that, they'll suspect the contribution is marginal. A good 'why now' points to a recent capability (e.g., larger context windows, new benchmarks, new theoretical tool) that makes your approach newly feasible.
Pitfall 3: Writing related work as a book report. Related work sections should position your contribution against alternatives, not summarize them chronologically. Every paragraph should end with 'in contrast, we...'
Pitfall 4: Treating novelty and significance as the same thing. They're different reviewer criteria at every major venue. A paper can be highly novel but trivially significant, or deeply significant but not novel. Address both separately.
Testing Your Framing Before Submission
Try this exercise before you submit. Give your abstract and intro to someone outside your subfield. Ask them: 'What's new here, in one sentence?' If they can't answer, your novelty framing has failed, no matter how clever the work actually is.
Another test: search Google Scholar for the three closest prior methods. Read their abstracts. Then re-read yours. If a reviewer only read these four abstracts, would they conclude your paper is the one that pushes the field forward? If not, revise.
A third test (my favorite): write the one-sentence version of your contribution that you'd put on a slide. If that sentence contains the words 'improved,' 'better,' or 'enhanced' without a specific capability, you're in incremental territory. Rewrite until the sentence names something your paper can do that no prior work can.
Next Steps
If you're mid-rebuttal right now, prioritize Step 6. If you're drafting a new submission, start with Step 2 and Step 3. And if you're deep in a research direction that keeps getting called incremental across multiple venues, that's a signal worth taking seriously. Consider spending a week reading recent award-winning papers in your area, specifically to study their novelty framing, not their technical content.
The meta-point is that novelty is a communication problem as much as a research problem. Reviewers at NeurIPS and comparable venues now process tens of thousands of submissions per cycle. They're pattern-matching at speed. Your job isn't to prove novelty exists. It's to make novelty impossible to miss.
