About Lens

Lens exists because of one finding in the 2026 Manusights Findings Report: in our sample, 9 of 10 journal-fit issues at Nature Communications were critical severity. When the engine flagged a scope mismatch at that venue, the flag was almost never a polite revision request. It was a desk-rejection-grade signal that the wrong venue had been chosen.

The implication was clean: scope-fit problems are best surfaced before submission, not discovered in the editorial response. Compass already does this at the “I do not know where to submit yet” stage by returning the top 5 best-fit venues. Lens covers the next stage: “I have chosen a target. Will scope kill it?”

Where the data comes from

Lens uses the same 1,321-entry venue corpus as Compass. The corpus is sourced from OpenAlex with curated additions for top computer-science conferences. Scope text is sourced from each venue's own published aim-and-scope page where available, with editorial trimming for length. Coverage is densest for biomedical, chemistry, physics, materials, and CS venues.

The scoring rubric draws on the issue-class patterns documented in the 2026 Manuscript Findings Report (a study of 5,495 manuscripts reviewed in spring 2026, of which 835 were classified under the v4 review engine). Journal-fit issues accounted for 10.3% of all classified risks; 79% of journal-fit issues were critical severity. That distribution shaped how Lens calibrates the bands.

How it differs from the rest of the tool family

• Compass: you do NOT have a target venue. Compass returns the top 5 venues that fit.
• Lens: you DO have a target venue. Lens scores the scope-fit risk for that specific venue and offers lower-risk alternatives.
• Verify: you have a specific citation in your manuscript. Verify reads the cited paper's abstract and returns a verdict on whether it supports your claim.
• Audit: you have a Results section. Audit recomputes every reported p-value and flags arithmetic-inconsistent statistics.
• Sentry: you have a bibliography. Sentry flags retracted, hijacked, or DOAJ-withdrawn references.
• Manusights Readiness Scan: the paid tool that combines all of the above with a structural review of claims, evidence, and editorial fit.

Who maintains Lens

Lens is built and maintained by Manusights, a pre-submission manuscript review service for academic researchers. The team is led by Erik Jia (ORCID · LinkedIn). The corpus and scoring methodology are versioned and refreshed quarterly; the next refresh ships in August 2026.

Feedback

If a Lens score feels wrong for your paper, the most useful feedback is a one-line description of the venue, the paper's topic, and the score you got. Email erik@manusights.com. We use feedback to refine the scoring rubric in the next quarterly refresh.