Peer Review Still Lives in Email, Not the Workflow Tab

Platforms route PDFs. Editors negotiate time, ethics, and extensions in threads. via.email compresses that mail without touching judgments.

The manuscript system is a workflow; peer review is still a thread

Publishing platforms love a clean queue. Humans live in the gaps: a reviewer needs another week, a conflict-of-interest note arrives after midnight, production discovers a figure permission problem, and the managing editor is the only person who knows which version is real. That coordination still happens in email because institutions do not share one login, time zones refuse to align, and the authoritative record is often the forward chain everyone searches when a dispute shows up six months later.

This is not a Luddite claim. It is an observation about multi-party trust. Peer review is a social process with ethical guardrails. Software can route files; mail carries negotiation.

Why editorial offices feel understaffed

<a href="https://www.oecd.org/content/dam/oecd/en/publications/reports/2024/03/using-ai-in-the-workplace_02d6890a/73d417f9-en.pdf" target="_blank" rel="noopener noreferrer">OECD survey work on AI in the workplace</a> captures both uplift and intensity when knowledge work speeds up without clearer responsibilities. Editorial offices are thin relative to submission volume; faster tools can help or can simply raise the expectation that every nudge is instant.

<a href="https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/superagency-in-the-workplace-empowering-people-to-unlock-ais-full-potential-at-work" target="_blank" rel="noopener noreferrer">McKinsey writing on superagency</a> keeps returning to workflow redesign, which for journals means deciding what is allowed to be automated versus what must stay visibly human. <a href="https://www.library.hbs.edu/working-knowledge/does-hybrid-work-actually-work-insights-from-30000-emails" target="_blank" rel="noopener noreferrer">HBS Working Knowledge summarized hybrid-work findings from tens of thousands of emails</a>, a useful parallel: asynchronous clarity matters more than heroic hours.

<a href="https://hbr.org/2019/01/how-to-spend-way-less-time-on-email-every-day" target="_blank" rel="noopener noreferrer">Harvard Business Review guidance on spending less time on email</a> stays relevant because batching is a fantasy during decision week. <a href="https://www.hbs.edu/ris/download.aspx?name=w33795.pdf" target="_blank" rel="noopener noreferrer">HBS research on generative AI embedded in real work tools</a> suggests assistance helps most when it sits where people already work, not in a side app reviewers refuse to open.

<a href="https://aiindex.stanford.edu/report/2025" target="_blank" rel="noopener noreferrer">Stanford HAI's AI Index</a> is macro background: the tooling surface area keeps expanding, which is another reason editorial leaders should choose delivery channels people will actually use.

Respectful automation: prepare, do not replace

via.email is built around addresses that return drafts and structured notes inside a thread. Humans still send external mail. That boundary matters for scholarly norms.

Extract Action Items at extract.action.items@via.email pulls who owes what by when from a reviewer correspondence chain—useful when three coordinators touch the same case across shifts. Distill to Three at distill.to.three@via.email gives the editor-in-chief a morning scan before the ethics call. Recap Call Notes at recap.call.notes@via.email turns editorial meeting shorthand into a sendable memo you still edit. Personalize Cold Outreach at personalize.cold.outreach@via.email can help draft polite reviewer invitations from the facts you supply, without inventing relationships you do not have. Extract Newsletter Insights at extract.newsletter.insights@via.email compresses society bulletins and policy updates into decisions you need this week.

via.email does not access your manuscript system, remember unrelated threads, or send messages on your behalf. File attachments depend on your plan.

What not to automate

Never outsource ethical judgments, authorship disputes, or accusations of misconduct to a model. Use tools to reduce reading load and drafting time, not to ghost-write accusations or promises you cannot keep.

A practical weekly rhythm

Monday: run Distill to Three on the escalation inbox so the desk knows which fires are real. Midweek: run Extract Action Items after production sync so permissions and figure fixes do not vanish between coordinators. Friday: Recap Call Notes on the editorial meeting so society leadership gets one coherent memo, not seven partial forwards. The point is not perfection. It is making handoffs legible when half the office is at a conference and the other half is covering reviews.

Cluster reading

Publishing editors already fight relevance overload in Editors: 42% of Email Is Relevant. AI Triage Helps. Manuscript slush pressure shows up in Editors Drown in Manuscripts. AI in the Inbox Cuts the Slush. For another field where the thread is the compliance record, see Clinical Coordinators: Your Thread Is the Compliance Record.

Peer review stays human; the inbox can be lighter

Journals will keep investing in platforms. Editors will keep living in mail because institutions and humans are messier than software. via.email offers a disciplined way to compress that mail without pretending the social layer can be replaced.

What is via.email?

AI agents that each lives at an email address. Just send an email to get work done. No apps. No downloads.

How to use?

Send or forward emails to agents and get results replied. Try it without registrations. Join to get free credits.

Is it safe?

Absolutely, your emails will be encrypted, deleted after processing, and never be used to train AI models.

More power?

Upgrade to get more credits, add email attachments, create custom agents, and access advanced features.