Check your proposal's prior work before the panel does

The papers raised against a proposal often come from the field next door. Where they hide, how to find them first, and where unkwn42 can and can't help.

Rohit Pawar · · 3 min read · Updated

Key findings

  • unkwn42 holds about 59% of the last ten years of papers that OpenAlex files under Arctic and Antarctic ice dynamics, and around half for cyclones, ozone and ocean acidification.
  • It holds 3.5% or less of recent papers on hydrology and drought, marine biology, floods and fire, so a quiet result in those areas tells you very little.
  • Reviewer 2 reads a proposal summary the way a hostile referee would and lists the papers most likely to be raised against it, with the attack and a defence.

The review comment that hurts most on a proposal is rarely "this is wrong". It's the one that says the applicants seem unaware of some piece of work, followed by a paper you've never heard of. It reads as carelessness even when it isn't, and on a tight panel that can be enough.

Often, those papers come from next door.

Why it comes from the neighbouring field

A proposal gets read by people chosen because they know the area, and in many schemes some of them work in fields next to yours. They know their own literature far better than you do, including their own papers. That literature is written in their words, which often aren't yours. A search you ran in your field's vocabulary can come back clean while theirs is full of the thing you're proposing.

The same problem runs through time as well as across fields. Ideas get renamed, and the older work sits under the older name. I've written about two cases, marine heatwaves and yellow substance, where a search for today's term misses a real share of what was published under the old one.

Before you submit

None of this is complicated, but it's easy to skip when the deadline is close.

  1. Write the central claim of the proposal in one sentence. If you can't, a reviewer will write it for you, and you may not like their version.
  2. Search for that claim in the words the neighbouring fields would use, and in the older words for it.
  3. Read the recent papers of the people most likely to review it.
  4. Look at the last year of preprints, which most databases are slow to pick up.
  5. Say in the proposal how your work differs from the closest thing you found. A reviewer who sees you've already dealt with a paper has much less to say about it.

Where unkwn42 helps

The unkwn42 check is built for this. It takes a summary or abstract and its reference list, reads the central claim against the closest existing work, including papers that use other words, and lists the earlier papers a referee would expect you to cite, each with why it matters and how yours differs.

Some funders and institutions have rules about putting unpublished proposal text into online tools. Check yours before you paste a draft into anything, ours included.

Where it doesn't

Our corpus is strong in some areas and thin in others, and a quiet result only means something where we're strong. This is how much of the last ten years of papers that OpenAlex files under each topic we hold, measured on a random sample from each topic:

  • Arctic and Antarctic ice dynamics: 59% (95% range 54% to 64%)
  • Tropical and extratropical cyclones: 54% (49% to 58%)
  • Atmospheric ozone and climate: 53% (48% to 57%)
  • Ocean acidification: 49% (44% to 53%)
  • Hydrology and drought: 3.5% (1.7% to 7.0%)
  • Marine biology and ecology: 3.0% (1.4% to 6.4%)
  • Flood risk: 1.0% (0.3% to 3.6%)
  • Fire effects on ecosystems: 1.0% (0.3% to 3.6%)

If your proposal sits in the top half of that list, unkwn42 is a good first pass. If it sits in the bottom half, use it for the parts that touch our stronger areas and search elsewhere for the rest. Every result also carries its own coverage note, so you don't have to remember this list.

If you're writing a proposal now, run its summary through the check before the panel does.

Cite this post

Pawar, R. (2026). Check your proposal's prior work before the panel does. unkwn42 blog. https://www.unkwn42.com/blog/check-your-proposal-before-the-panel

This post as Markdown

unkwn42 is the missed-literature check you run before you submit: whether your main claim is already published, which earlier work a referee will expect you to cite, and whether your reference list is clean. Your first check is free.

Run a free check