Capstone Assessment Rubric

One rubric for all three capstone projects, because the differences between the roads are logistics and the standards are physics. Six dimensions, four levels each, one weighting table, one gate.

How to Use This Rubric

Self-assessment first. Before any instructor, mentor, or peer sees the work, score it yourself — in writing, with evidence cited for each dimension. Then get the outside pass (run it on Chapter 19's feedback protocol: specific, timestamped, about the goal). The gap between your scores and theirs isn't embarrassment; it's calibration data, the same skill as level-matching your A/Bs in Chapter 22 and trusting meters over mood in Chapter 33. Producers who self-score accurately mix better, because assessment is just diagnostic listening pointed at your own work.

Score what's evidenced. The deliverables are the evidence: the master, the stems or package, the session, the logbook, the QA numbers, the documents. An assessor can't credit reasoning that isn't written down — an undocumented good decision scores as luck, because from the outside that's what it is. This is why the logbook is a deliverable and not a suggestion.

Match the level that mostly fits. Read each dimension's four descriptors and pick the one that describes most of the work. Ties break downward: claims aren't evidence, and "almost Proficient" is Developing.

The 70% gate. A weighted score of 2.8 out of 4.0 — seventy percent, the same line the book's quizzes draw — is the pass threshold. It's a gate, not a verdict on you: below it, the dimension scores tell you exactly which chapters reopen, the way the symptom table turns "my mix is bad" into "cut the 200–400 Hz pileup." This rubric is a diagnostic instrument wearing an assessment costume.

The floor rule. Any dimension scored Beginning caps the project at "not yet," whatever the weighted sum says. A record with one genuinely broken dimension isn't release-ready, and no amount of excellence elsewhere buys that back.

The Six Dimensions

1. Technical Quality

The "is the record clean" dimension: noise, edits, levels, artifacts — the layer Chapters 21 and 31–33 specify and Chapter 30 teaches you to interrogate. Listen on good headphones at attentive volume; this dimension hides from speakers across the room.

Level What you find
Beginning Audible noise-floor jumps between sections; clicks or gaps at edit points; clipped peaks or distortion artifacts on the deliverable; levels that force the listener to ride volume; red lights still live in the session.
Developing Mostly clean, but a few edit seams are audible; occasional plosive or sibilance spikes survive; true peak exceeds the ceiling or headroom is accidental rather than managed; noise audible under quiet passages on headphones.
Proficient Clean noise floor; edits inaudible at attentive listening level; nothing clips anywhere in the chain; the session is gain-staged (sane track averages, healthy 2-bus); true peak compliant. A careful listener finds nothing to flag.
Professional Clean under solo-track scrutiny: room tone managed, fades on every region, transitions that survive full-attention headphone listening. The technical layer is invisible — nothing stands between the listener and the record.

2. Translation

Does it hold up where listeners actually are? The car, the phone speaker, the earbuds, the quiet late-night listen (Chapter 30), the mono fold-down (Chapter 25) — and for spoken word, the noisy-room and low-volume tests, weighted heavily.

Level What you find
Beginning Works only on the system it was made on; the car or phone test fails dramatically — bass vanishes or booms, the lead sinks, hats shred; mono collapses elements outright.
Developing Recognizable everywhere, but balances lurch between systems — the lead or the low end changes role; mono is mostly safe with notable losses; testing happened but late, as patching rather than process.
Proficient Passes the car, phone, earbuds, and quiet tests: balances shift, as physics insists, but nothing disappears or lunges; mono keeps the lead and the groove intact; the symptom-table run and its fixes are logged.
Professional Sounds intentional on every system, including ones you'd apologize for; the quiet test retains intelligibility and groove; translation was designed in from the static balance onward, and the revision history proves it.

3. Craft Decisions

Were the choices deliberate? Arrangement discipline (Chapter 16), frequency pockets (Chapter 22), space architecture (Chapter 24), dynamics and movement (Chapters 23 and 27). The question here is not "is it tasteful" — that's Dimension 6. The question is whether what's audible was chosen.

Level What you find
Beginning Parts stacked without defense; the 200–400 Hz committee in session; one reverb on everything, or none; static dynamics start to finish; asked why a move was made, the answer is a shrug.
Developing The arrangement is mostly defended but carries passengers; pockets attempted with collisions remaining (kick and bass still negotiating); space is inconsistent — some elements placeless; deliberate moves mixed with audible defaults.
Proficient Every element survives a mute test; one owner per frequency zone per moment; a coherent space architecture with shared sends and real front-to-back placement; dynamics shaped by section; the logbook defends each audible choice.
Professional Subtraction is visible in the work — what's absent is the point; pockets, space, and movement serve one identifiable design; focused listening keeps getting rewarded with intentional detail; no default survives anywhere audible.

4. Process & Documentation

The logbook dimension (Chapter 19): decisions traceable to reasoning, hygiene, versions — plus the collaboration documents on Project 2 and the cut list and licensing documentation on Project 3.

Level What you find
Beginning Logbook missing or reconstructed afterward ("I think I..."); the session is an archaeology site; no versions; decisions untraceable; backups theoretical.
Developing A logbook exists but gaps where the hard calls were; stages listed without decisions, or with "sounded better" standing in for reasons; hygiene partial — some naming, some colors; one backup, somewhere.
Proficient Every stage logged with its key decision and the reasoning; session in pro hygiene — named, colored, versioned, consolidated; 3-2-1 backup evidenced; a stranger could reopen and navigate; required documents complete and signed.
Professional The log reads like a method: decisions, the alternatives considered, the costs accepted; the documentation would let someone else finish or remix the record; the versions tell the story; archival thinking throughout — this session won't rot.

5. Release Readiness

Gates 4 through 6 as a dimension (Chapters 33, 35, 36): loudness QA, metadata, deliverables hygiene, and splits or rights where collaborators or licensed material exist.

Level What you find
Beginning Loudness unmeasured — "probably fine"; deliverables are a loose folder of misnamed bounces; metadata absent or self-contradicting; collaborators exist but splits were never discussed.
Developing Loudness measured but off-target without justification, or true peak above ceiling; the package is mostly complete with naming inconsistencies; metadata drafted but never verified against the documents.
Proficient Integrated LUFS and true peak measured and written down, target named and justified with hedged platform awareness; the deliverables package is complete and self-contained; metadata read against the split sheet or licensing docs, line by line; Gates 4–6 pass with evidence.
Professional The package would survive a distributor's and a label's QA without a question; every alternate verified top to tail; the release plan or release executed on the four-week doctrine; the rights paperwork is boringly, wonderfully complete.

6. Identity & Taste

The Chapter 40 dimension, weighted gently on purpose: does it sound like someone? Not "is it innovative" — coherent and recognizable beats novel and scattered.

Level What you find
Beginning A grab bag — sections that could be from different records; or a competent photocopy of one reference with no decisions of its own detectable.
Developing Moments of identity — a sound, a space choice, a vocal attitude — inside generic surroundings; references audible as templates rather than as a compass.
Proficient A coherent aesthetic across the record: tempo, space, color, and vocal choices agree with each other; a listener could describe "the sound of this" in two sentences; genre violations are chosen, not accidental (Chapter 18).
Professional It sounds like someone — recurring decisions a stranger could attribute on a second listen; influences metabolized rather than imitated (Chapter 40); taste showing in restraint as much as in moves.

Scoring & Weighting

Score each dimension 1–4 (Beginning = 1, Developing = 2, Proficient = 3, Professional = 4), multiply by its weight, and sum to a score out of 4.0.

Dimension Weight Why this weight
1. Technical Quality 20% Broken files disqualify everything they carry.
2. Translation 20% The book's working definition of professional.
3. Craft Decisions 20% Deliberateness is the skill being taught.
4. Process & Documentation 15% The career skill: repeatability.
5. Release Readiness 15% Where finished records go to fail quietly.
6. Identity & Taste 10% Real, but young — weighted gently because Chapter 40 takes years, not weeks.
Weighted score Verdict
3.5–4.0 Professional work. Release it, then reread Chapter 40 — this is the start line, not the podium.
2.8–3.4 Pass. Proficient, releasable craft. Non-gate flaws go on the version-2 list, where they belong.
2.0–2.7 Not yet. Every dimension below Proficient names its own chapters; revise against them and resubmit.
Below 2.0 Re-route. The project isn't the unit of failure — the stage is. Reopen the chapters the scores point to, rebuild from the earliest failing stage, and come back.

A worked example: Technical Quality 3, Translation 3, Craft Decisions 3, Process & Documentation 4, Release Readiness 3, Identity & Taste 2. Weighted: 0.60 + 0.60 + 0.60 + 0.60 + 0.45 + 0.20 = 3.05 — a pass, with the gently-weighted 2 doing exactly its job: not sinking a releasable record, while naming the next mountain.

And the floor rule, restated because it's load-bearing: one Beginning anywhere caps the verdict at "not yet." The weights describe importance, not interchangeability.

A Note on "Professional"

Read the top row of those tables again and notice what isn't there. No console. No treated facility with a name. No budget line. Nothing in the Professional descriptors requires anything beyond what this book assumed in Chapter 1: a DAW, modest gear chosen with Appendix D sanity, a room improved with Chapter 10 labor, and trained ears.

That's not encouragement-poster optimism; it's the book's founding, documented fact. The debut album that won Album of the Year was produced in a bedroom by someone whose monitoring chain cost less than a used car — and what made it professional wasn't the room, it was that every decision on it was deliberate and the record translated everywhere (Chapter 5). Those are Dimensions 2 and 3. They are skills, not purchases.

So here's the honest bar this rubric actually sets. Professional means translation plus deliberateness: the work holds up on systems you didn't choose, in rooms you've never been, and every audible element is where it is on purpose — and you can say why. That's the whole test. Gear can make passing it more comfortable. It cannot pass it for you, and its absence cannot stop you.

Two honesty notes to close. First: Professional on Identity & Taste is rare on a first capstone, and that's correct — it mostly arrives with reps, somewhere along Chapter 40's ten-year roadmap, which is why it's weighted gently instead of pretended into reach. Scoring Proficient across all six dimensions is a genuine achievement and a releasable record; do not let the existence of a fourth row convince you the third row is failure. Second: this rubric never retires. Run it on your next release, and your tenth — self-assessment first, outside ears second, gates always. The score that matters isn't this project's. It's the trajectory.