Proving Peer Review Service: Editor Emails, Publons Records and Review Certificates

Why peer review evidence needs its own exhibit strategy

Peer review is designed to be invisible. Journals anonymize reviewers, editorial systems sit behind login walls, and most review activity leaves no public trace at all. An adjudicator reading a petition has no way to query a journal's internal database to confirm that a named individual reviewed a specific manuscript on a specific date. Unlike a published paper, which can be verified in seconds through a DOI or an indexing database, a peer review claim exists only in correspondence that the petitioner controls and must choose to disclose.

That asymmetry is the reason this category of evidence needs its own exhibit plan rather than a single summary line in a cover letter. The task is to reconstruct, from primary sources, four facts for each review event: that the invitation was real, who issued it, which journal or conference it was for, and that the review was completed. Each of these facts should be traceable to a document an outside party generated — an editor, an editorial management platform, or a publisher — not to a statement the petitioner wrote.

The material assembled under this heading is documentary, not argumentative. It typically feeds the reviewer criterion, but this section is concerned only with locating, redacting, and organizing the underlying records — emails, platform exports, certificates — so that later sections of the petition can cite them. No claims about significance or sufficiency belong here; those are handled elsewhere in the petition.

Collecting and redacting editor emails

Editor correspondence is the primary proof that a review request came from a journal or conference, not from the reviewer's own claim.

Locating the originals

1. Search your inbox for the editorial platform's automated sender addresses — Editorial Manager (em@editorialmanager.com), ScholarOne (onbehalfof@manuscriptcentral.com), and OJS (usually a journal-specific address). Search by journal name and by "review" or "referee."
2. Log into the editorial system itself if the emails were deleted; most platforms (Editorial Manager, ScholarOne) retain a correspondence history under the reviewer's task list, exportable as PDF or plain text.
3. Collect both the invitation email and any completion or thank-you email, since together they show the request and its fulfillment.

What to keep visible

• Editor's name and title
• Journal or conference name
• Manuscript ID number
• Dates of invitation and completion

What to redact

• Manuscript title or abstract, if the journal's confidentiality policy restricts disclosure
• Names or identifying details of co-reviewers
• Any embedded reviewer comments containing unpublished data

Use a PDF editor with permanent redaction (not just black boxes over text) to prevent recovery of hidden text. Export each email as its own PDF, named consistently, e.g., JAmChemSoc_2023-04-12_Smith.pdf. Keep a separate spreadsheet logging the original file location in case a reviewer or officer requests verification later.

Pulling verifiable records from Publons/Web of Science

Many journals now push completed reviews automatically into a reviewer's Web of Science (formerly Publons) account. This creates a third-party record independent of the editor emails you have already collected, and it is worth extracting in a form an officer can read without a login.

Steps to export the record

1. Log into your Web of Science account and go to the Reviewer Recognition / Peer Review section of your profile.
2. Open the full review history and use the export function to download a CSV listing journal name, review date, and verification status for each entry.
3. Separately generate the profile PDF (usually available from the public or private profile page), which presents the same data in a shareable, printable layout.
4. Save both files, naming them consistently, e.g. WebOfScience_ReviewRecord_2024.pdf and .csv.

Handling unverified entries

Some entries display as "unverified" because the journal did not confirm them electronically. For each unverified line:

• Match it against the editor emails gathered earlier; if a corresponding invitation or thank-you email exists, keep the entry and note the cross-reference.
• If no corroborating email exists, either request confirmation from the editorial office or drop the entry from your exhibit set rather than presenting an unverified claim on its own.

Before filing, reconcile the total review count on the Web of Science record against the number of email-documented reviews from the prior step; discrepancies should be resolved, not left for an officer to notice.

Requesting and formatting review certificates

Many journals will issue a certificate of review service on request even if one is not generated automatically. Some editorial systems (Editorial Manager, ScholarOne) have a self-service "download certificate" button under the reviewer's account history; if not, email the editorial office directly.

Requesting a certificate

1. Identify the editorial contact (managing editor or editorial assistant, not the handling editor of a single manuscript).
2. Ask specifically for: reviewer's full name, journal title, number of manuscripts reviewed, date range covered, and a signature or letterhead confirming the request came from the journal.
3. Avoid asking for manuscript titles or authors — the certificate should confirm volume of service, not disclose confidential content.
4. Save the reply and certificate together as one PDF, named consistently with the scheme used for editor emails.

When a journal declines

Some editorial offices do not issue certificates. In that case, build a self-made log summarizing service, corroborated by the emails and Publons data already collected. Use a simple table:

Keep manuscript IDs partially redacted if the journal requests confidentiality, but never redact the journal name itself — that removes the one fact an officer can verify independently.

Building the master peer-review index

Once the underlying evidence — editor emails, Publons exports, and certificates — has been collected and named consistently, the next task is to consolidate it into a single reference document rather than leaving an adjudicator to sift through a folder of PDFs. This index is a plain spreadsheet or table, not a narrative, and its only job is to make every review event traceable to its supporting file.

Setting up the working file

1. Create one spreadsheet (Excel or Google Sheets) titled something like PeerReview_MasterIndex.xlsx.
2. Use one row per review event — one manuscript, one round, one journal — even if the same reviewer handled multiple rounds for the same paper.
3. Sort rows chronologically by review date, oldest first, so the timeline reads cleanly from the start of the reviewing history to the most recent entry.
4. Keep the sheet in the same folder as the exhibit PDFs so it can be exported as the cover page for that exhibit group.

Keeping it synchronized

Update the index every time a new email, Publons record, or certificate is added or renamed. A mismatch between the index and the actual exhibit folder — a row pointing to a file that no longer exists under that name — is one of the most common self-inflicted errors in this part of a petition, and it is entirely avoidable with a short weekly check before filing.

Building the master peer-review index

Once editor emails, Publons records, and certificates are collected, consolidate them into a single chronological index. This table is what an officer sees first when opening the reviewer-criterion exhibit set, so it needs to stand on its own without requiring the reader to hunt through the underlying PDFs.

Table structure

Build the index with these columns:

List every review event, not just a summary count. One row per manuscript or conference submission reviewed, ordered by date.

Cross-referencing exhibits

1. Assign each row an exhibit number matching the actual filename and tab used in the exhibits binder or PDF bundle.
2. Keep exhibit numbering sequential and consistent with the numbering scheme used elsewhere in the petition.
3. Where a single review event is supported by more than one document type (e.g., email plus certificate), list both exhibit numbers in that row.

Placement

File this index as the first page of the reviewer-criterion exhibit set, ahead of the individual PDFs it describes, so the underlying documents follow in the same order as the table.

Common gaps and RFE triggers in review evidence

Before filing, check the evidence set against the gaps that most often trigger a request for evidence.

Claimed "ad hoc" reviewing with no editor confirmation

A statement that the petitioner reviewed manuscripts informally, without any email, editorial-system record, or certificate, reads as an unverifiable assertion. Every claimed review needs at least one document tying it to a named editor, journal, and date.

Publons entries left unverified

Entries in a Web of Science/Publons export marked "unverified" carry no independent weight on their own. Left uncorroborated, they read as self-reported claims. Either obtain editor confirmation for each one or drop it from the exhibit set.

Redactions that obscure the journal name

Redacting a manuscript title is normal; redacting or cropping the journal name or letterhead is not. If the journal identity is unclear, the reviewer criterion cannot be tied to a specific publication, and the document reads as unusable.

Mismatched dates between email and certificate

An invitation email dated one year and a certificate citing a different review period draws scrutiny. Reconcile dates before filing, or annotate the discrepancy with an explanation (e.g., certificate issued retroactively covering a broader range).

Single-source evidence with no corroboration

A single certificate or single email for a given review event, with nothing else confirming it, is read as thin. Pair each event with a second source — email plus Publons record, or certificate plus editorial-system screenshot — wherever possible.

Final packaging checklist before filing

Run through this list once the master index is complete and before the peer-review exhibit set is merged into the petition.

Corroboration

• Every row in the master index has at least two independent evidence sources (e.g., editor email plus Publons entry, or certificate plus email) — flag and address any row with only one source.
• No review event relies solely on an unverified Publons/Web of Science entry.

File naming and order

• All PDFs follow the same naming scheme (e.g., JournalAbbrev_ReviewDate_Editor.pdf or JournalAbbrev_ReviewDate_Certificate.pdf).
• Files are ordered chronologically or by exhibit number, matching the order in the master index — not scattered by type.
• File names contain no confidential manuscript titles or abstracts.

Cross-referencing

• Every exhibit number in the master index matches the number used in the petition's table of contents and exhibit list.
• No orphaned exhibits (PDFs with no index entry) or orphaned index rows (entries with no filed PDF).
• Redactions have been checked a final time to confirm journal names, dates and reviewer identity remain visible.

Final check

• The master index is placed as the cover document for the reviewer-criterion exhibit set, immediately before the underlying PDFs.
• Current USCIS filing, formatting, and document organization requirements have been verified directly on uscis.gov before assembly, since these can change between filings.

Once every box is checked, the exhibit set is ready to merge into the full petition package.