Write up statistical results in proper reporting style
Turns software output into a correctly formatted results section with effect sizes, confidence intervals, and matching tables.
The prompt
Help me write the results section from my statistical output.
Style guide: [e.g. "APA 7", "AMA", "journal-specific"]
Hypotheses or research questions: [LIST in order]
Analysis output: [PASTE output from R, SPSS, Stata, Python, etc.]
Descriptive statistics and sample flow: [N at each stage, exclusions, missing data]
Tables or figures planned: [DETAILS]
Rules:
- Report results in the order of the hypotheses, primary before secondary, confirmatory before exploratory.
- For each test: the statistic with degrees of freedom, exact p-value, effect size, and 95% confidence interval, formatted per the style guide.
- Describe the direction and size of effects in words, not just significance. Do not interpret non-significant results as evidence of no effect.
- Report assumption checks and any corrections for multiple comparisons.
- No interpretation or causal language: that belongs in the discussion.
- Do not re-calculate or change any number. If something in the output looks inconsistent (df vs. N, p vs. statistic), flag it as [CHECK] rather than fixing it.
Return the results text, a formatted table shell populated with my numbers, and a list of anything missing for complete reporting.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Data & Analysis prompts
What to fill in
- e.g. "APA 7", "AMA", "journal-specific"
- LIST in order
- PASTE output from R, SPSS, Stata, Python, etc.
- N at each stage, exclusions, missing data
- DETAILS
- CHECK
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a data dictionary for a table or datasetProduces clear column-level documentation with definitions, types, allowed values, grain, and known caveats so others can use the data safely.
- Write commentary for a dashboard or KPI reportWrites the 'so what' narrative executives need alongside a dashboard — for sales, marketing, HR, finance, ops, or support.
- Write a SQL query from plain EnglishTurns a business question into SQL, with validation checks and an explanation.
- Write a monthly IT and security report for leadershipTurns ticket, uptime, and security metrics into a short report showing trends, risks, and decisions needed.