How is this different from a research paper or group project rubric?

A research paper rubric grades a single written argument; a group project rubric grades a shared deliverable and teamwork. A capstone usually spans both — plus a process that unfolds over weeks or months and a live defense at the end — which is why this rubric has dedicated rows for process management and presentation that neither of the others need.

What if the student's driving question changed partway through the project?

That's normal and can score well — grade 'Process & project management' on whether the change was a deliberate response to what the student learned, documented at the time, rather than a last-minute rewrite to match whatever they ended up producing.

How do I grade the process when I only see the finished product?

Require checkpoint artifacts along the way — a proposal, a midpoint check-in, a draft — so 'Process & project management' has something concrete to grade rather than relying on the student's account after the fact.

Should all five rows count equally?

Adjust to match what your program values most. A program built around independent research might weight 'Driving question & depth of inquiry' and 'Reflection & synthesis' higher; a program built around a tangible product (engineering, art, design) might weight 'Product / deliverable quality' higher instead.

Capstone Project Rubric Template

A ready-to-use, analytic capstone project rubric for Culminating capstone project (independent or small-group, spanning multiple weeks) (Grades 9–12 and college). Score a capstone across the full arc it's meant to demonstrate — a driving question researched in depth, a finished product, and a presentation that shows the student can defend and reflect on their own work. Edit it for your own assignment, print it, or copy it into Google Docs.

Edit this template in the maker →

The capstone project rubric

Criterion	Excellent (4)	Proficient (3)	Developing (2)	Beginning (1)
Driving question & depth of inquiry	Poses a specific, arguable driving question (not a broad topic) and the finished project directly answers it, going beyond information that was easy to find in a first search.	Poses a clear driving question that the project mostly answers; one part of the project addresses the general topic rather than the specific question.	The driving question is present but broad or vague, and the project reads more like a report on a topic than an answer to a question.	No identifiable driving question; the project covers a topic without a specific question shaping what was researched or built.
Product / deliverable quality	The finished product (paper, prototype, performance, or design) meets a professional or near-professional standard for its form and fully realizes the project's stated goal.	The finished product meets the project's stated goal; one aspect (execution, polish, or completeness) falls short of a professional standard.	The finished product is recognizable as an attempt at the stated goal but has a significant gap in completeness or execution.	The finished product does not meet the project's stated goal, or a required component is missing.
Process & project management	Maintains a visible plan with milestones and deadlines, meets or renegotiates them with a clear reason, and can show specifically how the project changed direction in response to what was learned.	Maintains a plan with milestones; most are met, and any missed deadline is addressed with a reasonable adjustment.	A plan exists but several milestones are missed with no clear adjustment, or checkpoints show little evidence the student used them to guide the work.	No visible plan or milestones; the project shows no evidence of an ongoing process, as if it were completed in a single push.
Presentation & defense	Clearly explains the project's question, process, and findings to the audience, and answers follow-up questions with specific, accurate detail drawn from the work rather than generalities.	Clearly explains the project; answers most questions accurately, though one answer relies on a general statement rather than a specific detail from the work.	Explains the project but leaves gaps an audience member has to fill in, or struggles to answer more than a surface-level question.	Cannot clearly explain the project's question or findings, or cannot answer basic questions about their own work.
Reflection & synthesis	Explains specifically which skills or knowledge from multiple courses or experiences the project drew on, and reflects on a concrete way their thinking or approach changed over the course of the project.	Names some skills or knowledge the project drew on and reflects on what was learned, but the connection to a change in thinking or approach is asserted rather than explained.	Reflection is present but generic — describes what was done rather than what was learned or how it connected to broader skills.	No reflection on the skills used or what changed as a result of the project.

Four levels — Excellent (4) to Beginning (1). Print this page, or open it in the editor to change the wording, levels, or points.

How to use this rubric

A capstone project tries to prove something a single assignment can't — that a student can pose their own question, sustain independent work over months, and defend what they made. Grading it like a big research paper misses most of that: it drops the process entirely and treats the final product as the whole story. This rubric scores the question, the product, the process that got there, the defense, and the reflection as five separate things, because a strong final product built with no visible plan and a shallow defense is a different, weaker capstone than the same product backed up by both.

Why these criteria

Each row targets something the assignment is really teaching, with descriptors written to be observable rather than vague:

Driving question & depth of inquiry: A capstone is supposed to be built around a real question the student is answering, not a topic they're reporting on — this row checks whether the question is specific enough to actually drive the project.
Product / deliverable quality: The capstone's tangible output — whatever form it takes — has to meet a standard on its own, independent of how well the process was documented or the pitch was delivered.
Process & project management: A months-long project can't be graded only on the final artifact — this row makes the planning, checkpoints, and course-corrections along the way part of the grade, not just the finish line.
Presentation & defense: A capstone typically ends with the student explaining and defending the work to an audience — this row grades that defense as a distinct skill from the quality of the product itself.
Reflection & synthesis: The point of a capstone is to show the student can connect skills across a whole program of study, not just complete one assignment — this row grades whether that connection is actually named.

How to adapt it

For a capstone with no live defense (a written thesis submitted without a presentation), drop 'Presentation & defense' and add a second reflection prompt in its place addressing what the student would do differently.
For a group capstone, add a sixth row on individual contribution — reuse the Group Project Rubric's 'Contribution & participation' language — since 'Product / deliverable quality' and 'Presentation & defense' are otherwise scored once for the whole team.
For a shorter capstone (a single semester rather than a full year), lower the top-level bar on 'Process & project management' to require milestones at the start, middle, and end rather than an ongoing, adjustable plan.

Frequently asked questions

How is this different from a research paper or group project rubric?: A research paper rubric grades a single written argument; a group project rubric grades a shared deliverable and teamwork. A capstone usually spans both — plus a process that unfolds over weeks or months and a live defense at the end — which is why this rubric has dedicated rows for process management and presentation that neither of the others need.
What if the student's driving question changed partway through the project?: That's normal and can score well — grade 'Process & project management' on whether the change was a deliberate response to what the student learned, documented at the time, rather than a last-minute rewrite to match whatever they ended up producing.
How do I grade the process when I only see the finished product?: Require checkpoint artifacts along the way — a proposal, a midpoint check-in, a draft — so 'Process & project management' has something concrete to grade rather than relying on the student's account after the fact.
Should all five rows count equally?: Adjust to match what your program values most. A program built around independent research might weight 'Driving question & depth of inquiry' and 'Reflection & synthesis' higher; a program built around a tangible product (engineering, art, design) might weight 'Product / deliverable quality' higher instead.