Case Study 24.2 — The Reviewer's Temptation

A composite, illustrative case built to teach the peer-review confidentiality red line. The reviewer and applicant are composites; the confidentiality principle and funder prohibitions are real. Verify your funder's current reviewer AI policy.

Why this case: the other side of the table

Case Study 24.1 looked at AI from the applicant's side. This case looks from the reviewer's side — because the most categorical AI rule in the funding world governs reviewers, and because most grant writers will themselves serve as reviewers (a role this book encourages, Chapter 19). The line here is bright, and crossing it harms a real applicant. Meet Dr. Patel, an experienced researcher serving on a review panel, with a stack of confidential applications to critique on a tight timeline — and a tempting shortcut.

The temptation

Dr. Patel is reviewing a dozen applications, each long and dense, and the deadline is close. A thought occurs: I could paste each application into an AI tool, have it summarize the key points and even draft my critiques, and save hours. The AI is fast and capable; the summaries would be useful; the draft critiques would jump-start the writing. It feels efficient, even responsible — more time for more applications.

It is, in fact, a serious breach. Here is why.

Why it crosses the red line (Section 24.5)

Each application Dr. Patel is reviewing is confidential — entrusted by the funder, containing the applicant's unpublished ideas, preliminary data, and plans. Pasting it into a public AI tool means:

• The applicant's confidential ideas leave the secure review process and enter a third-party system that may retain, log, or train on them. The applicant never consented to that, and their unfunded-but-valuable idea could be exposed.
• It violates the confidentiality Dr. Patel agreed to as a condition of reviewing — a duty to the applicant and the funder.
• It breaches peer-review integrity — the system depends on reviewers handling applications within secure bounds and applying their own expert judgment, not outsourcing it.

Major funders, including the NIH and NSF, have moved to prohibit exactly this — reviewers using AI tools in ways that involve uploading or exposing the applications they review. For Dr. Patel, this isn't a gray area or a matter of personal judgment; it's a rule, and a sound one.

What Dr. Patel does instead

Recognizing the line, Dr. Patel does the review the right way:

• Reads the applications personally, within the funder's secure review system, applying expert judgment — which is, after all, why Dr. Patel was chosen as a reviewer.
• Writes the critiques personally, in Dr. Patel's own voice and expertise, without feeding any application into an external tool.
• Manages the time pressure by other legitimate means — focusing effort, using the funder's provided tools, or, if genuinely overloaded, telling the funder rather than cutting an unethical corner.

Dr. Patel also reflects on the golden-rule logic: one day my own confidential application will be in a reviewer's hands, and I would be appalled to learn it had been pasted into a public chatbot. The integrity of the system that will review Patel's work depends on every reviewer honoring the same line.

The applicant's stake

Picture the applicant whose proposal Dr. Patel almost uploaded: a researcher with a novel, unpublished idea, trusting the confidential review process to protect it. Had Patel taken the shortcut, that idea would have left the secure process — a real harm to a real person who did everything right. The red line exists to protect that applicant, and every applicant, including the reviewer's own future self.

What this case teaches

1. The peer-review red line is categorical. A confidential application under review never goes into a public AI tool — no summarizing, no critique-drafting, no exceptions. Major funders prohibit it.
2. Confidentiality entrusted to you is not yours to feed to AI. The principle extends to any confidential material — a colleague's draft, a partner's unpublished data.
3. The shortcut harms a real person. The applicant's unpublished ideas are exposed; the breach isn't abstract.
4. Reviewers were chosen for their judgment. Outsourcing the critique to AI defeats the purpose of expert review — and you'd want the same protection for your own application.

🔄 Retrieve: Without rereading, explain (a) why pasting a reviewed application into a public AI tool breaches confidentiality, and (b) the golden-rule reason every reviewer should honor the line. (Answers above.)