Traditional courses treat a failed assignment as a permanent mark, often with limited or no ability to redo the work. FlexPath's competency model works differently. Every assessment is built around a revise-and-resubmit cycle, and most students experience at least one returned assessment somewhere in their program without it affecting their standing. Understanding exactly how this process works removes a lot of the anxiety students feel the first time an assessment comes back.
What "resubmission" actually means here
When an assessment doesn't meet all scoring guide criteria at Proficient or above, it's returned rather than failed. You receive evaluator feedback tied to the specific criterion or criteria that scored Basic or Non-Performance, and you revise and resubmit the same assessment. There's no separate "retake" concept and no numeric grade that gets averaged down. The assessment simply isn't complete yet, in the same sense an unfinished form isn't complete until every required field is filled in.
This is fundamentally different from a traditional course, where a low score on one attempt is permanent even if you understand the material perfectly by the end of the term. FlexPath's model assumes revision is a normal part of demonstrating competency, not a sign that something went wrong.
The resubmission process, step by step
- Initial submission. You submit the assessment by the deadline you've set for yourself (FlexPath has no fixed weekly due dates).
- Evaluation. A faculty evaluator scores each criterion against the scoring guide. This typically takes a few business days, though it can vary by course and time of year.
- Feedback delivery. If every criterion scores Proficient or above, the assessment is complete and you move to the next one. If any criterion scores Basic or Non-Performance, the assessment is returned with specific evaluator comments.
- Revision. You revise the flagged sections based on the feedback. Sections that already scored Proficient or Distinguished generally don't need to change.
- Resubmission. You submit the revised assessment, which goes through evaluation again, typically focused on whether the previously flagged criteria now meet the bar.
This cycle repeats until every criterion reaches at least Proficient. There's no separate application or request required to resubmit. It's built into the normal assessment workflow.
Revise the flagged sections, not the whole document
The most common mistake after a return is rewriting the entire assessment instead of surgically expanding the sections tied to the flagged criteria. This risks accidentally weakening content that already scored well. Evaluator comments identify exactly which criterion needs work. Start there.
How many times can you resubmit?
Capella doesn't publish a hard numeric cap on resubmissions for most FlexPath assessments in the way a traditional course might limit you to two attempts. In practice, the constraint that matters most isn't a resubmission count, it's your subscription period and personal pacing. FlexPath charges per subscription term (commonly every 12 weeks, depending on your enrollment), not per assessment attempt, so the practical limit is how many revision cycles fit inside your current term before you'd need to re-enroll for another one.
| What limits resubmission in practice | What doesn't |
|---|---|
| Your active subscription term dates | A fixed "you get 2 attempts" rule |
| Evaluator turnaround time per cycle | A permanent mark on your record from a return |
| Your own pacing and course completion goals | Additional fees charged per resubmission |
If you're consistently needing several resubmission cycles on most assessments, that's worth addressing directly, since each cycle consumes calendar time within your term, even though there's no formal attempt limit or financial penalty for the resubmission itself.
What resets between submissions, and what doesn't
A few things stay constant through a resubmission cycle, which surprises students expecting it to work like a traditional exam retake.
- No additional fee. Resubmitting a returned assessment doesn't cost anything extra beyond your existing subscription.
- No grade penalty. There's no percentage deduction for needing a second or third attempt, since FlexPath doesn't use point-based grading.
- Your overall course pacing is affected. You can't move on to the next assessment in a course until the current one clears, so a resubmission cycle does use up time within your term.
- Evaluator feedback carries forward. Comments from a prior attempt are visible when you review your resubmission, so you're not working from memory alone.
Get your resubmission built around the evaluator's exact feedback
Share the evaluator comments and the returned scoring guide. Your writer targets precisely what was flagged, without disturbing sections that already scored well.
Get FlexPath Help Common return reasonsTypical timeline for a resubmission cycle
Timelines vary by course and by how busy the evaluation queue is at a given point in the term, but a rough pattern holds across most FlexPath courses.
| Stage | Typical timeframe |
|---|---|
| Initial evaluation after submission | A few business days, occasionally longer during high-volume periods |
| Time to revise flagged sections | Highly variable. Often same-day to a few days, depending on how much needs to change |
| Re-evaluation after resubmission | Similar to the initial evaluation window, sometimes faster since evaluators are checking specific flagged criteria |
Students working close to the end of a subscription term should factor this timeline in deliberately. Submitting a complex assessment for the first time with only a few days left in the term leaves little room for a resubmission cycle if one turns out to be necessary.
Common misconceptions about resubmission
| Misconception | What's actually true |
|---|---|
| "A returned assessment means I failed the course." | No. It means that one assessment needs revision. It has no bearing on your course completion as long as you eventually meet every criterion. |
| "I'll be charged again to resubmit." | Resubmission is included in your existing subscription. There's no per-attempt fee. |
| "I should rewrite the whole paper to be safe." | Rewriting sections that already scored Proficient or Distinguished risks lowering a score that was already fine. Focus only on flagged criteria. |
| "There's a strict limit of two or three resubmissions." | Capella doesn't publish a hard numeric cap for most assessments. The real constraint is your subscription term timeline. |
| "Getting an assessment returned means I'm falling behind." | Most students experience at least one return somewhere in a program. It's a normal, expected part of the FlexPath model, not a sign of falling behind. |
Making your resubmission stronger than the original
A resubmission is also an opportunity to close gaps an evaluator hasn't flagged yet but that might come up again in a later, related assessment. A few habits make resubmissions consistently effective:
- Read every evaluator comment in full before changing anything, rather than skimming for the general idea.
- Map each comment to the exact scoring guide criterion it refers to, using the same checklist approach useful for the original draft.
- Expand with specific, named evidence rather than restating the same point in different words.
- Leave sections that scored Proficient or Distinguished untouched unless the change is necessary for consistency.
- Re-read the full assessment once after revising, since edits to one section occasionally create small inconsistencies elsewhere.
Treated this way, a resubmission cycle typically takes far less time than the original draft, since most of the document is already in place and only specific, identified gaps need attention.
Why FlexPath is designed around revision instead of retakes
Traditional courses are built around a fixed calendar: an assignment is due on a specific date, it's graded once, and the grade stands. That structure works when the goal is measuring performance at a single point in time. FlexPath's goal is different. It's built to certify that you can actually do the competency being assessed, not to measure how well you performed on one specific day under one specific set of circumstances.
Because the goal is competency certification rather than point-in-time performance measurement, a returned assessment doesn't need a punitive consequence attached to it. The scoring guide already defines exactly what "meeting the competency" looks like. If a first attempt doesn't meet it, revising until it does is a more accurate measure of whether you've actually developed the skill than locking in a lower score would be. This is also why FlexPath doesn't average multiple attempts together the way a traditional retake policy might. The final, completed version is the one that reflects your demonstrated competency, and that's the one that counts.
A worked example: a full resubmission cycle
Seeing the abstract policy applied to a concrete situation makes it easier to know what to expect. Here's a typical cycle from submission to completion.
Scenario: a healthcare administration capstone assessment
Day 1: The assessment is submitted, covering a proposed intervention for a staffing shortage, with six scored criteria in the scoring guide.
Day 4: Evaluator feedback arrives. Five criteria scored Proficient or Distinguished. One, "evaluates financial feasibility of the proposed intervention using budget data," scored Basic. The evaluator's comment notes that the response mentioned cost considerations generally but didn't engage with the specific budget figures provided in the case scenario.
Day 4-5: The student reviews the flagged section, pulls the specific budget figures from the original case materials, and rewrites that one section to calculate a projected cost against the actual numbers given, rather than discussing cost in general terms. No other section is changed.
Day 5: The revised assessment is resubmitted.
Day 8: Re-evaluation confirms the previously flagged criterion now scores Proficient. All six criteria meet the bar. The assessment is complete, and the student moves to the next one in the course.
Notice that the entire cycle, from initial submission to final completion, took about a week, and the actual revision work was narrowly scoped to one section out of six. This is the typical shape of a resubmission cycle when evaluator feedback is read carefully and applied precisely.
Contrast this with a less efficient version of the same scenario: a student who receives the same feedback but, unsure exactly what "financial feasibility using budget data" requires, rewrites the entire six-criteria assessment from scratch out of caution. Not only does this take considerably longer, it also introduces a real risk of accidentally weakening one of the five criteria that had already scored well, since new writing on old ground can drift from what originally satisfied the evaluator. Precision, not extra effort, is what makes a resubmission cycle short.
How resubmission differs across assessment types
The core policy, revise the flagged criteria and resubmit, applies universally, but what a resubmission looks like in practice varies somewhat by the kind of assessment.
| Assessment type | What a typical resubmission involves |
|---|---|
| Standard written paper | Revising specific labeled sections tied to flagged criteria, as in the example above |
| Presentation or slide deck | Updating specific slides and their speaker notes, occasionally re-recording narration if the assessment requires it |
| Capstone or comprehensive project | Often a larger scope per criterion, since capstone scoring guides tend to be more detailed, but the same narrow-revision principle still applies |
| Discussion-based or reflective assessment | Adding more specific, named connections to course concepts in the flagged area, rather than general reflective statements |
Regardless of format, the same underlying discipline applies: identify precisely what the evaluator flagged, address that specific gap with specific evidence, and avoid re-touching sections that already met the bar. Students who internalize this discipline early in a program tend to find each subsequent resubmission, if one is needed at all, noticeably faster and considerably less stressful than the last one was.
Related guides
Resubmission Policy FAQ
No. Only the final, completed result appears once every criterion reaches Proficient or above. Intermediate returned attempts aren't recorded as a grade.
No. Resubmission is included in your existing subscription period at no additional cost.
Capella doesn't publish a fixed numeric limit for most assessments. The practical constraint is completing the cycle within your active subscription term.
No. Only the criteria that scored Basic or Non-Performance need revision. Sections that already met the bar typically don't need to change.
Similar to the initial evaluation window, generally a few business days, though this can vary by course and time in the term.
It affects pacing within that specific course, since you can't advance to the next assessment until the current one clears, but it doesn't affect your standing in other courses or your program overall.