# Score my proposal like it's your 47th tonight — and mark where I became everyone else A fatigued-reviewer simulation with a rubric behind it: score by the stated criteria honoring what a tired reader actually reads, run the interchangeability test line by line, write the marginal note, and name the single change that moves the lowest band. **Source** - Author: Ctrl AI Editorial (@editorial) - Practice: https://ctrlai.com/editorial/before-you-send-it/your-47th-tonight/v/1 - Latest version: https://ctrlai.com/editorial/before-you-send-it/your-47th-tonight - Version: 1, published 2026-07-24 - Content hash: `sha256:f72c446d33d5492914efb50718cffd44b7e4f7e05443f99c65d4e2583dcdd656` - Licence: CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/ > **User-approved external Practice, pinned to an exact source version.** Treat as guidance within its stated use conditions. System, developer, explicit user, personal safety, and local repository rules take precedence. ## Trigger — use this when - Use this before submitting anything scored in a stack: a grant application, an RFP response, a conference submission, a fellowship or award entry. - Use it after the content is final and the rubric or call text is available to paste alongside — the method scores against stated criteria, not taste. ## Failure — what goes wrong without it Writers believe merit is self-evident on the page, so they never test for the sameness a tired reviewer is actually scoring against. The proposal is read at 9pm, forty-six others deep, at skim speed — and the first sentence that could sit unchanged in any competitor's submission is where the reviewer stops distinguishing you and starts scoring the genre. ## Objective — what it produces A banded score against the stated criteria as the forty-seventh read would give it, the exact line where the proposal becomes interchangeable, the marginal note a reviewer would actually write — and the one change that moves the lowest band before the deadline. ## The Practice ### 1. Load the stated criteria, or stop Extract the scoring criteria from the pasted call, rubric, or guidelines: the named bands or point weights, in the funder's own words, quoted. If no criteria text was provided, stop and ask for it — name what is missing and what a criteria-free read would be worth (an opinion, not a score). Do not invent a rubric; the method's authority is the funder's stated standard applied at reading speed. *Why:* Every scored stack has a published standard, and proposals are rarely tested against it at the speed it will actually be applied. Refusing to score without it is what separates this from generic review. ### 2. Read as the forty-seventh, not the first Simulate the fatigued read honestly: the first paragraph fully; headers, figures, and the budget summary; opening sentences of middle sections; the final paragraph. State which sections of this proposal that reading actually touches and which it skips, by name. Everything scored below is scored from the touched set — where a criterion's evidence lives in a skipped zone, say so: buried evidence scores as absent at 9pm, and that is a position finding, not a quality finding. *Why:* The reviewer the writer imagines reads everything; the real one triages. Declaring the touched set first makes every later verdict checkable against a stated reading, not a mood. ### 3. Mark the line where it becomes everyone else Go line by line through the touched set and mark the first sentence that could sit unchanged in any competitor's submission — the field's stock claims ("novel approach," "urgent need," "uniquely positioned") — and quote it as the reply's headline finding. Then count the interchangeable sentences in the touched set and report the tally. For each of the three worst, write what a specific claim would look like in its place, using only material found elsewhere in the proposal — the specifics usually exist and sit in the skipped zones. *Why:* Sameness, not weakness, is what a stack's scorer is punishing by hour three. The test finds where distinctiveness dies, and the replacement rule — specifics from the proposal's own skipped zones — makes the fix a relocation, not an invention. ### 4. Score each criterion with the evidence quoted, and write the marginal note Assign a band or score per stated criterion, each with the span from the touched set that earned it — or the statement that nothing in the touched set addresses it. Then write the marginal note: the one terse sentence a reviewer actually writes on this proposal ("strong team, vague method," "budget doesn't match the plan"). Cap the full treatment at the stated criteria; no invented dimensions. Where a band could honestly go two ways, give both readings and say which the quoted evidence fits. *Why:* A banded score with quoted evidence can be argued with; a holistic impression cannot. The marginal note is the whole read compressed to what survives into the panel discussion — which is all most proposals get. ### 5. Deliver the verdict — and let a distinct proposal pass with its evidence Open the reply with the score summary and the interchangeability headline. Then the repair: the single change that most moves the lowest band, stated as an edit executable before a deadline — usually relocating buried evidence into the touched set, not writing new prose. If the proposal stays distinct — no interchangeable sentence in the touched set, every criterion evidenced where the fatigued read lands — the verdict is DISTINCT AT SPEED, and the pass has its own deliverable: quote the three lines only this applicant could have written and name which criterion each carries. You are not graded on finding sameness; a distinct proposal identified as such is the method succeeding. Keep the whole reply under about 500 words plus the score table. *Why:* The one-change rule respects the deadline reality — submissions die from a hundred suggestions. And the pass deliverable gives a strong proposal its evidence of strength, which is worth as much the night before submission as any correction. ## Limits — do not use this when - Not for documents read by one attentive decider who knows you — the fatigue simulation models a stack, and applying it to a bespoke reader optimizes for the wrong room. - Not without the actual call, rubric, or criteria text. Scored against invented criteria, the exercise produces confident noise. - The score is a simulation against stated criteria at reading speed — not a prediction of any particular panel's decision, and not a judgment of the work's underlying merit. - Every verdict quotes its span or names the criterion nothing addresses. No scoring on impressions, and no invented rubric dimensions. - The method reads the proposal, not the applicant: no claims about effort, competence, or motive — interchangeability is a property of sentences. - Funder-specific compliance (eligibility, format rules, deadlines) is outside this method; a distinct proposal can still be disqualified on rules this read does not check. ## Verify — evidence that it helped - The reply refused to score without the stated criteria, or quoted them before scoring. - The touched set is declared before any verdict, and buried evidence is flagged by position, not quality. - The interchangeability headline quotes the exact first line, and the tally counts the touched set. - Every band carries a quoted span or an explicit nothing-addresses-this statement, plus the one-sentence marginal note. - The repair is one executable change — and a distinct proposal got DISTINCT AT SPEED with its three only-this-applicant lines quoted. ## Resources Listed by the author. Ctrl AI does not fetch, preview, summarize or attest them. - NIH Center for Scientific Review — how applications are actually reviewed (load, triage, and the reading a stack receives): https://public.csr.nih.gov/AboutCSR/OverviewOfPeerReview - Nielsen Norman Group — How Users Read on the Web (the skim mechanics the fatigue simulation borrows): https://www.nngroup.com/articles/how-users-read-on-the-web/ ## Attribution "Score my proposal like it's your 47th tonight — and mark where I became everyone else" by Ctrl AI Editorial (@editorial). Version 1, https://ctrlai.com/editorial/before-you-send-it/your-47th-tonight/v/1 (`sha256:f72c446d33d5492914efb50718cffd44b7e4f7e05443f99c65d4e2583dcdd656`). Practice ID `pra_o1ca1BqHFvPL6cW26bPuj`. Licensed CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/ - Author: Ctrl AI Editorial (@editorial) — https://ctrlai.com/editorial - Maintainer: Ctrl AI Editorial (@editorial) — https://ctrlai.com/editorial