How to Avoid Desk Rejection at Foundations and Trends in Information Retrieval (2026)
Avoid desk rejection at FnT IR by pitching a real monograph proposal, not a normal survey or disguised research paper.
Senior Researcher, Oncology & Cell Biology
Author context
Specializes in manuscript preparation and peer review strategy for oncology and cell biology, with deep experience evaluating submissions to Nature Medicine, JCO, Cancer Cell, and Cell-family journals.
Readiness scan
Find out if this manuscript is ready to submit.
Run the Free Readiness Scan before you submit. Catch the issues editors reject on first read.
How Foundations and Trends in Information Retrieval is likely screening the manuscript
Use this as the fast-read version of the page. The point is to surface what editors are likely checking before you get deep into the article.
Question | Quick read |
|---|---|
Editors care most about | A topic that can sustain a true monograph |
Fastest red flag | Submitting a primary research paper |
Typical article types | Survey monographs, Tutorial monographs, Research retrospectives |
Best next step | Send the abstract and table of contents first |
Quick answer: the fastest path to Foundations and Trends in Information Retrieval desk rejection is to submit something that is too small, too research-like, or too article-like for a proposal-first monograph venue.
That is the real screen. FnT IR is not a standard journal workflow. The official author instructions say it publishes exclusively long review and tutorial papers, that original research papers will be rejected, and that the first step is to send an abstract and table of contents for initial review. If the concept is not monograph-sized or the structure does not teach the field, the project is exposed before a full draft even matters.
In our pre-submission review work with FnT IR-style proposals
In our pre-submission review work with FnT IR-style proposals, the most common early failure is confusing a good survey topic with a real monograph topic.
Authors often know the literature and may already have a strong draft. The problem is that the manuscript still behaves like a long review article rather than a field guide that can sustain 50 to 100 pages without padding.
The official materials and the existing submission owner make the screen fairly clear:
- the venue publishes only long review and tutorial papers
- original research papers are explicitly rejected
- the first object under judgment is the abstract and table of contents
- the monograph has to work across multiple publication formats, not just as a journal article
That means the desk screen is usually asking whether the project is a credible monograph concept, not simply whether the authors know the area.
Common desk rejection reasons at Foundations and Trends in Information Retrieval
Reason | How to Avoid |
|---|---|
The proposal is really a research paper in disguise | Strip out research-paper logic and rebuild the project as a survey or tutorial monograph |
The topic is too narrow | Choose an area that can support a broad teaching document without filler |
The table of contents is chronological rather than conceptual | Organize by problems, frameworks, or decisions instead of paper history |
The project offers coverage but not tutorial value | Show clearly what readers will understand better after reading it |
The authors send a full draft without clearing the concept stage | Follow the abstract-plus-table-of-contents first step |
The quick answer
To avoid desk rejection at FnT IR, make sure the project clears four tests.
First, it has to be monograph-sized. The topic must sustain a long survey or tutorial without becoming repetitive.
Second, it has to be a genuine survey or tutorial. The official instructions explicitly rule out original research papers.
Third, the proposal has to teach. The table of contents should reveal a pedagogical structure, not only a list of subtopics.
Fourth, the abstract has to justify why this synthesis should exist now. Timing and relevance matter at the concept stage.
If any of those four elements is weak, the project is vulnerable before a full manuscript is even invited.
What FnT IR editors are usually deciding first
The first editorial decision at Foundations and Trends in Information Retrieval is usually a concept and scale decision.
Is this obviously a monograph rather than a normal article?
That is the first format screen.
Does the topic justify long-form treatment?
A good niche survey can still be too small for this venue.
Does the proposal teach?
Editors want a structure that helps readers understand a field, not a long bibliography.
Are the authors plausible guides for the area?
Authority is not the only criterion, but it is part of the editorial judgment.
That is why even strong IR topics still miss. The venue is screening for reference-level monographs, not only current topics.
Timeline for the FnT IR first-pass decision
Stage | What the editor is deciding | What you should have ready |
|---|---|---|
Initial abstract | Is the idea clearly a long review or tutorial? | A concise abstract that names the field problem and the reader value |
Table of contents review | Does the outline show monograph logic? | A concept-led structure rather than a paper-by-paper sequence |
Preliminary acceptance decision | Is the topic broad enough and useful enough to invite a full draft? | A convincing case for why the field needs this synthesis now |
Full-draft review | Does the monograph deliver on the proposal? | A manuscript that teaches, synthesizes, and organizes the area deeply |
Three fast ways to get desk rejected
Some patterns recur.
1. The project is just a standard survey article
This is one of the fastest ways to miss. FnT IR is looking for a long tutorial or survey monograph, not a conventional review article with extra pages.
2. The outline is a literature timeline
If the table of contents is mostly chronological, the project usually reads like a history of papers rather than a teaching document.
3. The topic is too small
Many otherwise publishable IR reviews are still too narrow to justify monograph treatment.
Desk rejection checklist before you contact FnT IR
Check | Why editors care |
|---|---|
The project is visibly a monograph concept | The venue is proposal-first and monograph-led |
The topic can honestly sustain 50 to 100 pages | Scope mismatch is easy to spot |
The outline teaches concepts, not just chronology | Tutorial value is part of the product |
The abstract explains why this synthesis is needed now | Timing and editorial purpose matter |
The work is unmistakably not a primary research paper | The official instructions explicitly reject those |
Desk-reject risk
Run the scan while these rejection patterns are in front of you.
See which patterns your manuscript has before an editor does.
Submit if your project already does these things
Your project is in better shape for FnT IR if the following are true.
The topic deserves a long-form treatment. The monograph would still feel necessary after cutting away a third of the references.
The outline is pedagogical. Readers can see how the document will teach the area from the table of contents alone.
The proposal is clearly a survey or tutorial, not a disguised research paper. This should be obvious immediately.
The synthesis has durable value. The monograph would function as a reference, not just as a current snapshot.
The abstract makes the need for the monograph explicit. That is often the most important sentence in the whole pitch.
When those conditions are true, the project starts to look like a plausible Foundations and Trends in Information Retrieval proposal rather than a smaller review pointed at the wrong editorial model.
Think Twice If
There are also some reliable warning signs.
Think twice if the topic only serves one benchmark family or one narrow method class. That is often too small for this venue.
Think twice if the proposal could easily become a standard review article elsewhere. That usually means it is not monograph-sized.
Think twice if the table of contents is just a list of subtopics without a teaching argument. Editors usually notice that quickly.
Think twice if the main novelty is your own recent research trajectory. That often means the project is still research-first rather than survey-first.
What tends to get through versus what gets rejected
The difference is usually not whether the topic is modern. It is whether the project behaves like a true monograph proposal.
Projects that get through usually do three things well:
- they justify why the topic needs long-form treatment
- they show a strong tutorial or synthesis structure
- they make it obvious that the work is not a research paper
Projects that get rejected often fall into one of these patterns:
- ordinary review article aimed at a monograph venue
- narrow topic that cannot sustain the length
- outline that summarizes literature without strong teaching logic
That is why FnT IR can feel unusual compared with other journal workflows. The main filter happens at the concept stage.
FnT IR versus nearby alternatives
This is often the real fit decision.
Foundations and Trends in Information Retrieval works best when the project is a true long-form monograph with strong tutorial value.
Computer Science Review may be better when the work is a strong broad survey but not truly monograph-sized.
ACM Computing Surveys may be better when the article is canonical and broad but still fits a more conventional review-journal format.
A narrower IR review venue or tutorial outlet is the honest owner when the audience is smaller or the scope is more bounded.
That distinction matters because many desk rejections here are owner-format mistakes in disguise.
The page-one test before you pitch
Before contacting the editor or publisher, ask:
Can an editor tell, in under two minutes, that this is a monograph proposal, that it is broad enough to deserve one, and that the outline teaches the field rather than just listing papers?
If the answer is no, the project is vulnerable.
For this venue, the first page should make four things obvious:
- the work is a monograph concept
- the topic can sustain long-form treatment
- the structure is tutorial or synthesis-led
- the project is not a disguised research paper
That is the real triage standard.
Common desk-rejection triggers
- primary research pitched as a review monograph
- topic too narrow for long-form treatment
- chronology-heavy table of contents
- weak explanation of why the synthesis is needed now
A proposal-first monograph check can flag those first-read problems before the editor ever sees a full draft.
For cross-journal comparison after the canonical page, use the how to avoid desk rejection journal hub.
Frequently asked questions
The most common reasons are that the project is not monograph-sized, the manuscript is really a primary research paper or ordinary survey, or the initial abstract and table of contents do not show enough tutorial and synthesis value.
Editors usually decide whether the topic justifies a long monograph, whether the work is genuinely a survey or tutorial rather than original research, and whether the abstract-plus-table-of-contents proposal shows a strong teaching structure.
No. The official author instructions explicitly say original research papers will be rejected. The venue is for long review and tutorial monographs.
The biggest first-read mistake is treating FnT IR like a normal review journal and sending a full draft or a small survey instead of a proposal-first monograph concept.
Sources
Before you upload
Choose the next useful decision step first.
Move from this article into the next decision-support step. The scan works best once the journal and submission plan are clearer.
Use the scan once the manuscript and target journal are concrete enough to evaluate.
Anthropic Privacy Partner. Zero-retention manuscript processing.
Where to go next
Same journal, next question
Supporting reads
Conversion step
Choose the next useful decision step first.
Use the scan once the manuscript and target journal are concrete enough to evaluate.