Traditional grading uses points per question, weighted averages, and a syllabus that tells you a B+ is good enough. Capella's FlexPath competency model works nothing like that, and it feels disorienting at first. FlexPath doesn't grade your work. It certifies whether you've demonstrated a defined competency. That distinction should shape how you approach every assessment you submit, from your first course to your capstone.
The four score levels, and why there's no "close enough"
Every FlexPath assessment is evaluated criterion by criterion against a scoring guide unique to that assessment. Most assessments include four to seven criteria. Each one is scored at one of four levels:
| Score level | What it means |
|---|---|
| Non-Performance | The criterion isn't addressed at all, or the response is fundamentally off-topic or missing required elements. |
| Basic | The criterion is addressed, but incompletely, vaguely, or without the depth the scoring guide requires. |
| Proficient | The criterion is fully met. This is the minimum passing level for every criterion on the assessment. |
| Distinguished | The criterion is met with additional depth, synthesis, or insight beyond what's strictly required. |
Here's the part that surprises most new FlexPath students: you must score at least Proficient on every single criterion to pass. There's no averaging. If six criteria score Distinguished and one scores Basic, the assessment is returned for revision. The five strong criteria don't offset the one weak one. This is fundamentally different from a weighted rubric, where a strong section can compensate for a weak one.
Who scores your work, and what they're actually looking for
Your assessment is evaluated by a faculty evaluator, not the course mentor you may have been communicating with throughout the course. Course mentors help you understand material and plan your approach, but they don't score assessments. The evaluator's only reference point is the scoring guide text itself, applied consistently across every student who submits that assessment.
This matters because the evaluator isn't grading your effort, your improvement, or how well you understood the broader course material. They're checking whether specific, identifiable evidence for each criterion exists in your submission.
Consider a criterion that reads "analyzes the financial impact of the proposed intervention using at least two credible sources." It needs exactly that: a financial analysis, explicitly framed as such, supported by two identifiable credible sources. Vague or implicit treatment of a requirement, even when the underlying thinking is sound, typically scores Basic rather than Proficient.
The scoring guide is your entire assignment brief
- Download the scoring guide for your specific assessment before you start writing. Skip the general course description.
- Turn every criterion into a heading or clearly labeled section in your draft
- Address each criterion explicitly, using close to the same terminology the scoring guide uses
- After drafting, go criterion by criterion and confirm you can point to the exact sentence or paragraph that satisfies it
- If you can't quickly locate the evidence, expand that section. A reviewer won't go looking for it either.
Distinguished vs. Proficient: what actually separates them
Most students target Proficient, since it's the passing threshold. But aiming only for Proficient leaves very little margin. A slightly weak paragraph that an evaluator reads more strictly than expected can tip a criterion down to Basic. Writing toward Distinguished on every criterion builds in a buffer, and it's usually a smaller lift than students expect. The difference is almost always specificity and synthesis, not additional length.
| Criterion area | Proficient | Distinguished |
|---|---|---|
| Use of evidence | Cites relevant sources to support each claim | Synthesizes multiple sources, addresses any conflicting evidence, and explains why the sources chosen are the right ones for this specific context |
| Analysis | Describes the situation and identifies relevant factors | Connects each factor explicitly to the outcome, using a named framework or model rather than general reasoning |
| Recommendations | Proposes a reasonable next step | Proposes a specific, resourced, time-bound action with an explanation of anticipated obstacles and how they'd be addressed |
| Professional communication | Writing is clear and organized | Writing uses precise discipline-specific terminology and reads as a document a practitioner in the field would actually produce |
Get scoring-guide-matched FlexPath help
Share your specific assessment brief and scoring guide. Your writer builds the submission around every criterion at the Distinguished level, so nothing gets returned for a preventable reason.
Get FlexPath Help Scoring guide strategyWhat happens when an assessment is returned
A returned assessment isn't a failure in the traditional sense. It's a request for revision. You'll receive evaluator comments tied to the specific criterion or criteria that scored Basic or Non-Performance, and nothing else about your submission needs to change.
The most common mistake at this stage is rewriting the entire document instead of surgically expanding the flagged sections. Doing so risks accidentally weakening a section that already passed.
| Why assessments commonly get returned | How to fix it |
|---|---|
| A criterion is addressed implicitly but never stated directly | Add an explicit sentence naming the criterion's requirement and pointing directly to how your work satisfies it |
| Sources don't meet the discipline-specific quality bar | Replace general web sources with peer-reviewed or professionally recognized sources appropriate to your field |
| A required framework or model is mentioned but not actually applied | Reference the framework by name in each section where it's relevant, and connect it explicitly to your specific analysis |
| Recommendations are generic rather than situation-specific | Name specific resources, timelines, and stakeholders rather than describing next steps abstractly |
How this compares to traditional course grading
If you've taken traditional online courses before, a few adjustments will help the transition:
- No rounding up. An 89% "close enough" doesn't exist in this system, because there's no percentage at all.
- No penalty for resubmission. FlexPath is built around revise-and-resubmit, so a returned assessment doesn't lower your standing the way a bad grade would on a transcript.
- No moving on until you pass. You can't advance in the course until the current assessment clears, which makes early, careful attention to the scoring guide more valuable than it would be in a traditional class.
One more adjustment matters: a traditional professor's running commentary gives you a sense of where you stand before the final grade lands. FlexPath doesn't work that way. You get evaluator feedback only after you submit, and only on the assessment you turned in. That makes the scoring guide itself, read carefully before you write a word, your only reliable preview of what "acceptable" looks like. Students who treat the scoring guide as an afterthought, something to check after drafting, consistently score lower than students who treat it as the outline for the document itself.
A worked example: turning one weak criterion into a passing one
Abstract advice about "being specific" is hard to apply without seeing it in practice. Here's a single scoring guide criterion, along with a response that would likely score Basic and a revised version of the same content that would likely score Proficient or better.
Sample criterion: "Recommends an evidence-based intervention appropriate to the identified problem"
Basic-level response: "Based on the research, implementing a new training program would help address the communication issues identified in the case. Staff should receive additional training on effective communication techniques to improve outcomes."
This response names an intervention (training) but doesn't identify which specific training model, doesn't cite the evidence base for it, and doesn't explain why this intervention fits this specific problem rather than any other plausible one.
Distinguished-level response: "The identified communication breakdown between shift teams aligns with gaps documented in structured handoff literature (Smith & Alavi, 2022; Chen et al., 2021). Implementing the SBAR (Situation-Background-Assessment-Recommendation) framework, validated across comparable clinical settings, directly targets the specific failure points identified in this case: incomplete background context and unclear recommendation ownership. Unlike general communication training, SBAR provides a standardized structure that can be audited for compliance, making the intervention's impact measurable rather than anecdotal."
Notice what changed. The intervention is named specifically, tied to cited evidence, and connected back to the exact problem described earlier in the document, not just "communication issues" in general. That specificity is almost always the difference between Basic and Proficient, far more often than raw writing quality.
Common misconceptions about competency scoring
A few misunderstandings show up repeatedly among students new to FlexPath, and each one tends to cost unnecessary revision cycles.
| Misconception | What's actually true |
|---|---|
| "A longer response is a safer response." | Length has no direct relationship to score. A tightly focused paragraph that explicitly hits a criterion outperforms three unfocused paragraphs that dance around it. |
| "If most of my assessment is strong, one weak section won't sink it." | Each criterion is scored independently. A Basic score on one criterion returns the whole assessment, regardless of how the others scored. |
| "The evaluator will infer what I meant." | Evaluators score what's on the page, not what you intended. If a requirement isn't explicit, it's treated as not met. |
| "Distinguished just means more references." | Distinguished reflects depth of analysis and synthesis, not citation count. Ten shallow citations score lower than three sources genuinely integrated into the argument. |
| "A returned assessment means I'm behind schedule for good." | Revision cycles are a built-in, expected part of FlexPath. Most students have at least one assessment returned during a program; it isn't a sign of falling behind. |
Building a repeatable scoring-guide workflow
Every FlexPath assessment follows the same underlying scoring logic, even though the specific criteria change from course to course. It's worth building one consistent process instead of approaching each assessment as a brand-new puzzle. A workflow that holds up across an entire program looks like this:
- Read the scoring guide in full before reading anything else about the assessment, including the instructions document.
- Write out each criterion as a single-line checklist item in your own words.
- Draft your document with a heading or labeled subsection matching each criterion, in the order the scoring guide lists them. Evaluators read the same guide in the same order, so matching that structure makes your evidence easy to find.
- Before submitting, go through your checklist item by item and mark exactly where in your document each one is satisfied.
- Expand any section where you can't quickly locate the evidence. Do this before you submit, not after you get feedback.
This process takes longer on your first assessment or two, mainly while you're still learning Capella's scoring guide format. By your third or fourth assessment, most students complete the checklist-and-mapping step in under twenty minutes. It consistently prevents the most avoidable return reason: a requirement addressed in spirit but never stated in a way an evaluator could point to directly.
Keep a personal log of any criterion that scores Basic, along with the specific evaluator comment. Patterns tend to emerge. A student who consistently loses points on "analysis depth," for example, benefits from deliberately over-explaining connections between evidence and conclusions in every later assessment, even where it feels excessive. What feels like over-explanation to the writer is usually just adequate explicitness to the evaluator.
Related guides
FlexPath Scoring FAQ
No. Every criterion is scored independently, and every criterion must reach at least Proficient. There's no averaging across criteria within an assessment.
No. It means that specific assessment needs revision before you can move forward. You'll get evaluator feedback and can resubmit. It doesn't appear on a transcript as a failing grade the way a traditional course grade would.
Yes, the Non-Performance/Basic/Proficient/Distinguished scale is used consistently across FlexPath courses and programs. What changes between assessments is the scoring guide content: the specific criteria being measured, not the scoring scale itself.
Proficient passes the assessment, so it's not required. But because there's no partial credit and evaluator interpretation has some natural variance, writing toward Distinguished gives you a buffer against a criterion being scored more strictly than you expected.
Scoring guides exist specifically to minimize this, but some interpretation variance is unavoidable across any evaluation system with human reviewers. This is exactly why writing toward Distinguished, rather than the bare minimum for Proficient, matters: it creates margin against that variance.
Most assessments list somewhere between four and seven scored criteria, though this varies by course and assessment complexity. Some scoring guides also include one or two "non-scored" competencies related to writing mechanics or APA formatting, which are still worth meeting even though they don't carry an independent pass/fail weight.