Internal comms
AuraScore 83/100

Quantitative Research Peer Review Readiness Checklist

Generate an internal verification checklist for technical teams signing off on mathematical research models before email distribution.

Use this template when validating mathematical modeling results and statistical integrity prior to circulating research briefs internally. It helps research leads verify peer review rigor, mathematical validation, and data sensitivity.

Template

Role: Lead Quantitative Researcher specializing in statistical validation and analytical peer reviews.

Context

  • Research Paper or Study Title: {{research_title}}
  • Principal Investigator / Lead Analyst: {{lead_mathematician}}
  • Primary Target Audience: {{target_business_unit}}
  • Core Theorems, Proofs, or Models Applied: {{key_theorems_or_models}}
  • Data Provenance and Integrity Notes: {{data_source_integrity}}
  • Sign-off Due Date: {{review_deadline}}

Task

Draft a structured internal communications checklist email sent to reviewing peers to systematically inspect, validate, and sign off on technical models before wide internal release.

Method

  1. Review the mathematical foundations in {{key_theorems_or_models}} against the stated baseline assumptions.
  2. Verify the underlying dataset provenance documented under {{data_source_integrity}} for completeness and sampling bias.
  3. Formulate specific verification items covering algebraic consistency, boundary conditions, and stress-test performance.
  4. Design validation criteria evaluating whether the analytical conclusions align precisely with the statistical outputs.
  5. Structure clear inspection gates for code reproducibility, formula auditing, and edge-case handling.
  6. Assemble the checklist into sequenced functional phases for reviewer execution prior to {{review_deadline}}.
  7. Provide an explicit sign-off status schema so reviewers can clearly mark approval or required remediation.

Constraints

  • Output MUST be structured strictly as an actionable internal communications checklist.
  • Technical items MUST differentiate between mathematical proofs and empirical data validations.
  • MUST NOT exceed 25 discrete checklist items across all stages.
  • Plain-text checklist formatting with brackets [ ] must be used for each verification line.

Output format

  • Email Header (Subject line, Sender, Recipients, Review Deadline: {{review_deadline}})
  • Executive Summary (1 short paragraph highlighting research scope)
  • Checklist Section 1: Theoretical & Mathematical Integrity (4-6 checklist items)
  • Checklist Section 2: Data Provenance & Empirical Validation (4-6 checklist items)
  • Checklist Section 3: Distribution & Translation Readiness (3-5 checklist items)
  • Sign-Off Protocol & Next Actions (clear 2-column tabular sign-off block)

Self-review

  • Confirm all variables ({{research_title}}, {{lead_mathematician}}, {{target_business_unit}}, {{key_theorems_or_models}}, {{data_source_integrity}}, {{review_deadline}}) are integrated.
  • Check that every checklist item is unambiguous, testable, and mathematically specific.
  • Ensure bracket formatting [ ] is uniformly applied across all verification gates.
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

emails
emails-internal
complex-reasoning-analysis-math
quantitative
peer-review
mathematics