How to keep up with new research papers in your field

To keep up with new research, stop trying to read everything and build a small pipeline instead: a handful of well-written alerts that bring new papers to one place, one fixed slot each week to triage them, and a clear decision for every paper (read now, save to a project, or discard). Set up once, it takes about an hour a week and catches most of what matters to your work. This guide covers which alerts to use, how to write them, and how to stop them from burying you.

Why keeping up feels impossible

Three things make this hard, and none of them is a personal failing. First, the volume: any active field produces more papers each week than one person can read. Second, the papers arrive scattered across journals, preprint servers, conference proceedings and social feeds, each with its own notification system. Third, relevance is specific to you. A paper that matters for your second chapter may be irrelevant to the person at the next desk, so no general newsletter can do the filtering for you.

The realistic goal is not to see every paper. It is to see the papers that could change what you are doing, soon enough to act on them, without spending your reading time on searching.

Start from your projects, not from your field

Before setting up any alert, write down what you actually need to track. For each project (a thesis chapter, a paper, a grant), list:

• Two or three topic phrases that define the project, in the words authors use in titles and abstracts.
• Five to ten researchers or labs whose new work you would always want to see.
• Three to five key papers. Anything that cites them is probably relevant to you.
• The two or three journals where the work you care about most often appears.

Each line on that list becomes one alert below. Alerts built this way are narrow, and narrow alerts are the ones you will keep reading.

The sources worth setting up

You do not need all of these. Pick the two or three that cover your field, then add more only if you notice gaps.

• Journal table-of-contents alerts. Most publishers will email you the contents of each new issue if you register on the journal site. Use them for your two or three core journals only; beyond that they become noise.
• PubMed saved searches. Run a search, choose "Create alert" under the search box, and PubMed emails you new results on a daily, weekly or monthly schedule. You need a free NCBI account, and the saved searches live in My NCBI, where you can edit or delete them. "Create RSS" on the same page gives you a feed of the search instead of an email.
• Google Scholar alerts. On a results page, the envelope icon in the sidebar creates an email alert for that search. To follow a key paper, click "Cited by" under it and create an alert on that page, which emails you when new work cites it. To follow a person, open their Scholar profile and choose "Follow" for new articles by that author.
• arXiv listings. arXiv sends daily emails listing the abstracts of new submissions in the subject areas you subscribe to, and it publishes RSS and Atom feeds for every active subject category, updated daily.
• bioRxiv and medRxiv. bioRxiv offers email alerts by subject area and feeds of the most recent posts by subject category. medRxiv has its own alerts and RSS page for health sciences preprints.
• Semantic Scholar. You can set email alerts for an author (new papers and citations), for a paper (new citations) and for a topic. If you save papers into a library folder, its Research Feeds recommend recent papers based on that folder and on the papers you rate as relevant or not.
• An RSS reader. Many of the sources above offer feeds. Sending them to one reader keeps them out of your inbox and lets you skim everything in a single list.
• People. Society newsletters, your lab journal club and the colleague who always knows what just came out are slower than alerts but better at telling you what a paper means. Use alerts for coverage and people for judgment.

How to write a saved search that stays useful

A saved search is a standing question. Vague questions return hundreds of results a week, and you will stop opening the email within a month. Aim for a search that returns somewhere between a few and a few dozen new papers a week.

1. Combine two or three concepts with AND. One concept ("working memory") describes a field. Three concepts ("working memory" AND adolescents AND sleep) describe a project.
2. Add synonyms with OR inside each concept, in brackets: (adolescent OR teenager OR "young people").
3. Use phrase quotes for multiword terms, so "sleep deprivation" is searched as a phrase.
4. Restrict where the terms appear. In PubMed, the field tag [tiab] limits a term to the title and abstract, and [mh] searches the MeSH subject heading. The Advanced Search builder adds these for you. In Google Scholar, the author: operator limits results to a named author.
5. Test before saving. Run the search over the last year. If fewer than half of the first twenty results are relevant, tighten it. If papers you already know are missing, loosen it.
6. Name the alert after the project it serves, such as "Ch2 sleep and memory", so you know later why it exists and when to delete it.

A worked example in PubMed: "sleep deprivation"[mh] AND (adolescent[tiab] OR teenager[tiab]) AND "working memory"[tiab]. The same idea as a Google Scholar alert is simply the quoted phrases together: "sleep deprivation" "working memory" adolescents.

A weekly triage routine

Alerts only help if you process them. Reading each one as it arrives breaks up your day and feels like work without being work. Batch them instead: one slot a week, the same time each week, 45 to 60 minutes. Filter alert emails into a folder so they skip your inbox until then.

1. Skim titles only. Go through everything that arrived and mark anything that might matter. Most titles can be dismissed in a second or two. Do not open anything yet.
2. Read the abstracts of your shortlist. For each, ask one question: could this change what I do, cite or claim?
3. Decide, once, for every shortlisted paper. Read now, if it bears on what you are writing or running this month. Save to a project, with its DOI and a one-line note on why you saved it. Or discard.
4. Read the one or two "read now" papers in the same week, while you remember why they mattered.
5. Delete or archive the rest of the alert emails. An empty folder at the end of the slot is the signal that you are caught up.

The one-line note is the step people skip and regret. "Saved because it uses the same task with a younger sample" turns a pile of PDFs into a reading list with reasons attached. How to read a scientific paper covers what to do with a paper once it reaches the top of that list, and how to organize research papers covers where saved papers should live.

How to avoid alert overload

• Cap the number. Five to eight alerts in total is plenty for most people. Every new alert should replace an old one or earn its place.
• Prefer weekly to daily. Daily emails create daily guilt. Weekly digests fit the weekly slot.
• Prune every term. If you have discarded everything from an alert for a month, narrow it or delete it.
• Retire alerts with the project. When a chapter is submitted, its alerts go too.
• Accept that you will miss things. Important papers reach you more than once: through citations, journal club and colleagues. A system you keep using beats a complete one you abandon.
• Skip a week without penalty. If the folder has grown past what one slot can clear, skim titles for the last two weeks and delete the rest.

A setup checklist

• One list per project of topics, authors, key papers and journals.
• One or two saved searches per project, tested against the last year.
• Citation alerts on your three to five key papers.
• Author alerts for the people whose work you always read.
• A mail filter or RSS reader so alerts arrive in one place.
• A recurring weekly slot in your calendar, with a rule for every paper: read now, save, or discard.

Where a per-project briefing fits

Most of the work above is plumbing: writing queries, routing emails, and moving the papers you keep into the place where you read and cite them. A briefing that already knows the project does that plumbing for you. In Mosaic, each project has its own briefing, a feed of new papers matched to the project and grouped under theme headings. Matching uses the project title and topics, the papers already in its library, and what you save and dismiss, so you do not have to maintain a query by hand. How your briefing works describes it in full.

You can still steer it: add topic tags, limit by publication date or article type, ask for free full text only, and choose PubMed or Semantic Scholar as the source (Change what your briefing finds). The schedule runs from every day to every month, with optional email delivery, so a weekly briefing can replace the weekly alert folder (Set when your briefing arrives).

The triage decision is built in. "Save to library" puts the paper in the project, next to your notes and the documents you cite from, and Mosaic looks for an open-access PDF in the background. "Dismiss" hides it. Papers you find elsewhere, for example through a journal alert, can be saved to the same project with the Chrome extension. Mosaic is in an invite-only beta, and you can join the waitlist from the product page. The routine in this guide works with or without it.