Blood Reviews Submission Guide: Proposal Fit, Outline, and Expert Case

We reviewed the current Blood Reviews journal and author-facing pages on July 13, 2026. The publisher describes a review-only journal spanning clinical and laboratory hematology, with most articles commissioned but suggestions welcomed through a brief outline and topic-specific publication record.

The same publisher page provides a route for proposed review topics and reports aggregate timing and open-access information. Those figures help with planning but do not turn an outline into a prediction of invitation, review, or acceptance.

In our pre-submission review work with clinical synthesis manuscripts, the usual failure is not prose quality. It is a proposal that names a broad disease area without identifying the clinical decision, evidence conflict, or new development that makes another review necessary. The outline should let an editor see the reader, the question, the evidence boundary, and why this team can deliver a balanced answer.

Blood Reviews topic duplication hidden by a broad title. Compare the working title with the most recent reviews. A title such as "advances in myeloma" is not yet a review question, while a question about a specific treatment decision, monitoring problem, or evidence conflict can be tested for duplication.

Blood Reviews outline that lists literature instead of a clinical decision. Read the outline without its title. If sections merely divide the literature by year, molecular pathway, or therapy class, the abstract and conclusion will not show how a clinician or laboratory reader reaches a decision. Reorder the sections around the question, evidence, tradeoff, and boundary.

Blood Reviews recommendation without an evidence ledger. Compare each promised conclusion with the evidence ledger: trials, observational data, laboratory evidence, and expert interpretation should not blur into one strength claim. The author record is evidence too. A short list of topic-specific publications or complementary clinical and laboratory roles is more useful than a generic declaration of hematology expertise.

These checks prevent a common proposal mismatch: the abstract announces a practice recommendation, the outline contains no explicit evidence hierarchy, and the final section has no place for uncertainty or exceptions. In that situation, narrow the claim before contacting the journal. A focused proposal gives the editor a concrete reason to believe the finished review will add a decision-relevant synthesis rather than another broad overview.

The journal's current article list spans clinical and laboratory hematology synthesis rather than a single disease niche. For example, recent reviews cover platelets in venous thromboembolism (10.1016/j.blre.2025.101184), patient-reported outcomes in light-chain amyloidosis (10.1016/j.blre.2025.101181), and hemophilic arthropathy (10.1016/j.blre.2025.101180). These examples do not define an editorial formula. They are a useful check that the proposed review's question, evidence base, and reader consequence fit the journal's broad hematology-review role.

Use these checks before contacting the editors. They are not a claim about confidential editorial screening; they are a way to make the topic, outline, author record, and evidence boundary legible in a short proposal.

The topic is important but the proposed review is not yet distinct

A disease or therapy can be important while the review question remains generic. Identify the decision that changed, the evidence that conflicts, or the reader who lacks a usable synthesis. If a recent review already answers the same question, narrow the proposal to the genuinely new evidence boundary.

Check whether your review has a distinct synthesis question →

The outline lists papers instead of making a decision path

An editor should be able to see how the reader moves from definition to evidence to tradeoff to conclusion. Reorder sections around the clinical or laboratory decision. Keep uncertainty visible where trials, real-world evidence, mechanism studies, and expert practice point in different directions.

Check whether your outline makes the evidence path readable →

The author record does not establish topic authority

The journal asks prospective authors for a publication record on the topic. Do not substitute a generic CV. State the publications, practice setting, laboratory contribution, or methodological role that lets the proposed team evaluate the question honestly, including where outside expertise is needed.

Check whether the proposal makes the author-expertise case →

Follow the live author guidance for the current operational requirements. Before converting the outline into a full review, make a small evidence ledger: record the question, search boundary, inclusion logic, most influential trials or studies, competing interpretations, and the statement each conclusion can support. That ledger prevents the review from becoming a polished but selective literature summary. It also makes coauthor disagreement productive: authors can debate whether an evidence gap is a finding, a limitation, or a reason not to make a recommendation.

For a clinical review, distinguish the patient group, treatment context, outcome horizon, and implementation constraint. For a laboratory review, distinguish the model system, assay boundary, reproducibility risk, and relationship to patient-relevant inference. Those details help the final manuscript preserve the proposal's promised contribution.