Foundations and Trends in Information Retrieval Submission Guide
A practical FnT IR submission guide covering the abstract-plus-TOC first step, monograph scope, and editorial fit.
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 to approach Foundations and Trends in Information Retrieval
Use the submission guide like a working checklist. The goal is to make fit, package completeness, and cover-letter framing obvious before you open the portal.
Stage | What to check |
|---|---|
1. Scope | Send the abstract and table of contents first |
2. Package | Secure preliminary acceptance |
3. Cover letter | Develop the full monograph draft |
4. Final check | Submit source files and figures after acceptance |
Quick answer: This Foundations and Trends in Information Retrieval submission guide starts with the most important rule in the official instructions: do not start by cold-uploading a finished paper. FnT IR asks authors to first send an abstract and table of contents for initial review.
Only after preliminary acceptance does the full monograph enter the formal submission and review path. That alone separates it from most review journals.
Run a Foundations And Trends In Information Retrieval pre-submission readiness check before clicking submit, or work through this guide manually.
From our manuscript review practice
The biggest Foundations and Trends in Information Retrieval mistake is treating it like a normal survey journal when it is really a proposal-first monograph venue. The first object under judgment is the abstract and table of contents, not the finished PDF.
Foundations and Trends in Information Retrieval: Key submission facts
Requirement | Details |
|---|---|
Publisher | Emerald Publishing |
Journal type | Survey and tutorial monograph venue |
First step | Send abstract and table of contents for initial review |
Full-draft timing | Only after preliminary acceptance |
Target length | About 50 to 100 pages (the journal's aims and scope; the general Foundations and Trends guidelines say 50 to 200) |
Article types | Survey monographs, tutorials, retrospectives, state-of-the-art reviews |
Original research papers | Not considered for publication |
Manuscript formats | Microsoft Word (LaTeX accepted only with a PDF) |
Abstract length | Structured abstract, at most 250 words including keywords |
Reference style | Alphabetical |
That structure tells you what the journal is really buying: not a review article with extra length, but a field guide that can survive as both a journal issue and a book-like monograph.
What FnT IR is actually screening for
Foundations and Trends in Information Retrieval is selective in a way that many strong IR authors underestimate.
Editors are usually asking:
- does this topic actually justify a 50 to 100 page monograph
- will the piece teach the field rather than summarize it
- is the author team authoritative enough to guide readers through the area
- does the proposed structure show tutorial value, not just literature coverage
That is why many otherwise respectable review ideas are weak here. The venue wants a monograph that becomes a reference point, not just a nice survey.
FnT IR step-by-step submission checklist
The first step is an editorial pitch packet, not a full manuscript upload. The Emerald guidelines route abstracts through the journal's ScholarOne site and ask authors not to submit by email.
- define a topic broad enough for a 50 to 100 page monograph
- draft an abstract that explains what the monograph teaches
- build a table of contents around concepts, not chronology alone
- state briefly why the topic deserves synthesis now
- explain why the author team is well placed to write it
- send that packet to the editor-in-chief or publisher for initial review, through the journal's ScholarOne site rather than by email
- prepare the full draft only after preliminary acceptance
Readiness check
Run the scan against the requirements while they're in front of you.
See score, top issues, and journal-fit signals before you submit.
Before you send the initial abstract and table of contents
Pressure-test these questions before you contact the editor or publisher:
- can you explain what an IR reader will understand better after reading the monograph
- is the topic broad enough to sustain long-form treatment without padding
- is the outline organized around concepts, questions, or decisions rather than chronology alone
- would a broad IR reader care, not just one narrow benchmark community
- does the author team look like a credible guide to the topic
If those answers are weak, the problem is usually topic shape, not manuscript polish.
What the official materials make explicit
The current Emerald materials for the journal are unusually direct.
Official signal | Why it matters |
|---|---|
FnT IR publishes exclusively long review and tutorial papers | Do not pitch a conventional review article or primary research paper |
Original research papers will not be considered for publication | The venue is not a disguised research lane |
Initial submission is an abstract and table of contents | The proposal stage is the real first gate |
Each issue is a 50 to 100 page article written by research leaders | Topic breadth and author authority both matter |
Full draft enters review only after preliminary acceptance | The journal is screening concept before labor |
Use "monograph", "tutorial", "review", or "survey" rather than format-specific labels | The output is intentionally multi-format and long-form |
That makes the workflow simple to understand. The first thing under evaluation is not whether the manuscript is polished. It is whether the topic and architecture deserve a monograph.
Get the mechanics from the journal, then stress-test the package yourself. The review tells you whether your paper clears the Foundations and Trends in Information Retrieval fit check before upload, especially around proposal is really a research paper in disguise, topic is too narrow, and draft offers coverage but not teaching. Paid Manusights reviews include a 60-day money-back guarantee, and we do not train models on submitted manuscripts.
Decision risks before submitting to Foundations and Trends in Information Retrieval
Most rejections at this venue trace back to one of four mismatches between what the authors wrote and what a monograph editor is actually buying. Work through each before you send the pitch.
1. The proposal is really a research paper in disguise
The journal's official submission information explicitly says original research papers will not be considered for publication. Authors still miss this by wrapping a research contribution in survey language.
2. The topic is too narrow
A narrow ranking method, one benchmark family, or one system component can be important and still too small for a 50 to 100 page tutorial monograph.
Check the topic is too narrow before submitting to Foundations and Trends in Information Retrieval →
3. The draft offers coverage but not teaching
FnT IR wants tutorial value. A literature map without synthesis, conceptual comparison, or open-problem framing usually feels too thin.
4. The author team has not made the authority case visible
This is a monograph venue written by research leaders. If the proposal does not show why the authors should guide readers through the area, the pitch weakens immediately.
Before submission, a survey-monograph readiness check is often more useful than another formatting pass.
What a strong initial pitch packet should contain
A strong first packet is short, editorial, and structural.
It should usually include:
- a working title that states the real conceptual territory
- an abstract that says what the monograph teaches
- a table of contents that shows the teaching logic
- a short note on why the topic needs synthesis now
- a concise author-authority explanation
- a short checklist confirming the proposal is a monograph pitch rather than a disguised research-paper submission
That packet does more real work than a prematurely polished full draft.
The manuscript requirements after preliminary acceptance
Once the concept clears the first screen, the formal preparation rules matter more.
- Microsoft Word is the expected format, and LaTeX files are accepted only with an accompanying PDF
- references should use alphabetical style
- figures should be submitted electronically as .ai, .eps, .jpeg, .bmp or .tif files at the highest resolution possible
- pages, equations, references, and footnotes should be numbered consecutively
- the piece should avoid format-specific words like "chapter" or "book" and instead use terms like "monograph" or "review"
Those details reinforce the point that the product is meant to live in multiple formats. The house style exists to support that publishing model, not just to create cosmetic uniformity.
Additional pre-submission review patterns for Foundations and Trends in Information Retrieval
In our pre-submission review work across long-form survey proposals aimed at venues like Foundations and Trends in Information Retrieval, we see four patterns show up repeatedly before any editor needs to say no:
- The topic is real but not monograph-sized: this usually happens when the authors confuse "important topic" with "topic that can sustain a 50 to 100 page teaching document."
- The outline is chronological rather than conceptual: that produces a history lesson, not a tutorial monograph.
- The proposal sounds like a literature survey rather than a field guide: editors want a reason the monograph should exist, not just proof that many papers exist.
- The authority case is implied rather than stated: at this level, author credibility is part of editorial fit.
A monograph-fit check is useful here because most failures happen at the concept stage, not because the final PDF lacked polish.
Foundations and Trends in Information Retrieval versus nearby alternatives
Journal | Best fit | Think twice if |
|---|---|---|
Foundations and Trends in Information Retrieval | Long tutorial or survey monographs that organize an IR area deeply | The topic cannot justify monograph length or lacks strong tutorial value |
ACM Computing Surveys | Broad and authoritative CS surveys in a more conventional journal format | The work really needs monograph scale and pedagogy |
Computer Science Review | Broad expert surveys for a general CS audience | The topic is strongly IR-centered and deserves longer-form treatment |
Narrow IR review venue or workshop tutorial | More bounded or practical topic coverage | The concept genuinely needs field-level monograph treatment |
That comparison is important because many good IR surveys are too short or too narrow for FnT IR even when they are very publishable elsewhere.
Submit If
- the topic clearly deserves a 50 to 100 page monograph
- the abstract and table of contents show tutorial or survey value immediately
- the monograph teaches the field rather than cataloging papers
- the authors have a credible authority case
- the best first step is clearly a proposal, not a cold full-draft upload
Think Twice If
- the work is still basically a primary research paper
- the topic is too narrow for long-form monographic treatment
- the outline is mostly chronological literature coverage
- the tutorial value is weak even if the bibliography is strong
Before you send the pitch, run a proposal-first monograph check (or with proposal context via the readiness flow) to see whether the concept belongs here or in a more conventional survey venue.
In our pre-submission review work on Foundations and Trends in Information Retrieval proposals, we see that the editorial triage pattern at Now Publishers monograph-tutorial journals favors proposals where the cover-letter pitch names a failure pattern in the existing IR literature (a teaching gap that successive ACM Computing Surveys reviews have not addressed) that the monograph addresses.
Editors routinely reject proposals that read as comprehensive coverage of recent papers and consistently screen for proposals that demonstrate awareness of the journal's editorial culture around long-form tutorial pedagogy.
In our review of proposals targeting FnT IR and adjacent monograph venues (ACM Computing Surveys, Computer Science Review), we see that strong proposals position the monograph as the field's go-to teaching reference for the next 5 to 10 years, not as a snapshot of the past 24 months.
Frequently asked questions
Foundations and Trends in Information Retrieval is not a normal one-step upload journal. The official Emerald author guidelines for the Foundations and Trends journals say authors should first send an abstract and table of contents to the editor-in-chief or publisher for initial review. Only after preliminary acceptance should the full manuscript be submitted.
The journal publishes long survey and tutorial monographs in information retrieval. The journal's aims and scope say each issue is a 50 to 100 page article written by research leaders in the field, covering tutorial treatments, retrospectives, and state-of-the-art reviews.
No. The journal's official submission information explicitly says original research papers will not be considered for publication. The venue is for surveys, tutorials, and broad monographic treatments.
Common reasons include pitching a primary research paper instead of a survey, choosing a topic too narrow for a long monograph, writing a literature summary without enough tutorial or synthesis value, and sending a full draft before clearing the initial abstract-plus-table-of-contents stage.
Sources
- Foundations and Trends author guidelines, Emerald Publishing
- FnT IR aims and scope, Emerald Publishing
- FnT IR journal home, Emerald Publishing
- ACM Digital Library FnT IR collection
- An FnT IR monograph exemplar (illustrating the long-form tutorial pedagogy): DOI 10.1561/1500000076
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.
Private API processing. Your manuscript is not used to train models.
Put the guidance to work
Turn the guide into a complete submission package.
Use one final checklist, then verify the journal rule that controls the files, declarations, and reporting details you will submit.