Final Report Rubric
STAT 184 — Summer 2026 Project
Submission
- One PDF per team to Canvas, rendered from a Quarto document in your team’s GitHub repo.
- Link to your team’s GitHub repo.
- Final commit pushed to GitHub repo by the deadline.
Due: Friday, June 26, 11:59 p.m.
- Structure: all sections in the Required report structure, in order.
- Length: at least 10 pages of body (narrative + figures + tables). The title page, references, and Code Appendix do not count.
- Figures: at least three, each with a caption, a numbered cross-reference, and discussion in the text.
- Table: at least one non-trivial (summary/aggregated) table, captioned and cross-referenced.
- Multivariate figure: at least one figure showing 3+ variables.
- Code: in the Code Appendix only.
Rubric (100 points)
Components below follow the required report structure in the project guidelines. Each figure earns its points only when it has a caption, is cross-referenced by number from the narrative, and is discussed in the text.
| Component | Points |
|---|---|
| Introduction & Motivation — clear and engaging | 4 |
| Research question(s) explicitly stated | 4 |
| Data Provenance documented (source, collector, purpose, cases) | 5 |
| Variables described and justified | 4 |
| Data Wrangling & Cleaning explained in narrative (not just code) | 5 |
| Non-trivial summary table (caption + cross-reference + discussion) | 5 |
| Figure 1 (caption + cross-reference + discussion) | 4 |
| Figure 2 (caption + cross-reference + discussion) | 4 |
| Figure 3 (caption + cross-reference + discussion) | 4 |
| At least one figure displays 3+ variables effectively | 4 |
| Findings / Conclusions clearly stated and tied to question(s) | 6 |
| Limitations & Future Work discussion | 4 |
| Body meets the 10-page minimum (narrative only; appendix/refs excluded) | 3 |
| References / citations of data and sources | 4 |
Code quality (15)
| Component | Points |
|---|---|
| Code runs cleanly (renders from scratch) | 5 |
| Meaningfully commented | 4 |
| Code in appendix, not body | 3 |
| Reproducible from GitHub repo | 3 |
Reproducibility (20)
| Component | Points |
|---|---|
| GitHub repo well-organized with README | 8 |
| All team members have commits | 6 |
| Data accessible (in repo or via working URL) | 6 |
AI use & integrity (5)
| Component | Points |
|---|---|
| AI use note included in report | 2 |
| Attribution of external sources | 3 |
Total: 100
Individual adjustments
Project grades may be adjusted up or down by up to 25 points per individual based on the oral checkpoints and observable team contribution. A student who could not engage with the project at the oral checkpoints will receive a lower individual grade than their team’s collective work would suggest.
Late policy
Late work for the final project requires a request to the instructor at least 24 hours before the deadline, with evidence of progress and a proposed new deadline. Without prior arrangement, late final reports lose 10 points per 24 hours, up to 48 hours. After 48 hours, no late submissions will be accepted or graded.