Getting outside help with an assessment doesn't remove the normal FlexPath cycle of evaluator feedback and revision, it just changes who does some of the drafting work. If a delivered assessment is returned by your evaluator rather than accepted at Proficient or above, that's exactly the situation a revision policy exists to cover. This guide explains, in plain terms, what's included, what to send us, and what a realistic turnaround looks like, so an evaluator return feels like a normal, manageable step rather than a setback.
What a revision policy is actually for
A revision policy exists for one specific situation: you submitted work you received help with, your actual Capella evaluator scored it, and one or more criteria came back at Basic or Non-Performance rather than Proficient or Distinguished. In that situation, the writer who worked on your assessment revises the flagged sections based on what the evaluator said, at no extra charge, within the terms of your original order. It is not a general rewrite service for work you've simply changed your mind about, and it is not the same thing as Capella's own resubmission policy, which governs how the university itself handles returned assessments. Those are two different processes running in parallel: Capella decides whether your work meets the scoring guide, and our revision policy governs how we support you in responding to that decision.
Two policies, two different owners
Capella's resubmission policy governs the academic side: how many revision cycles the university's own process allows, what resets between attempts, and how your course pacing is affected. Our revision policy governs the service side: what we do, at no extra cost, to help you respond to evaluator feedback on work we helped deliver. Understanding this distinction avoids a common confusion where a student assumes a service revision request is the same as, or a substitute for, actually resubmitting through Capella's own coursroom.
What triggers a covered revision
A revision is covered when three things are true: the assessment was delivered through an order with us, it was submitted to your actual Capella evaluator, and it came back with a genuine evaluator return, meaning at least one scoring guide criterion scored below Proficient. This is different from a student simply preferring different wording after reading the delivered draft, or wanting an unrelated topic explored instead. Those requests are handled as change requests rather than covered revisions, since they aren't tied to actual evaluator feedback.
| Situation | Covered as a revision? |
|---|---|
| Evaluator scored one or more criteria Basic or Non-Performance | Yes, within the policy window |
| Evaluator feedback asks for more specific evidence or a missed requirement | Yes, this is exactly what the policy covers |
| You simply want different phrasing with no evaluator feedback involved | No, handled separately as a change request |
| You want an entirely different topic or approach after submission | No, this is a new order rather than a revision |
| The assessment was never actually submitted to Capella | No, revisions apply to delivered work that reached an evaluator |
What you should provide to get a fast, accurate revision
The single most useful thing you can send us is the evaluator's own written feedback, ideally the exact comments tied to whichever specific criterion or criteria scored below Proficient, rather than a general summary in your own words. Evaluator comments are usually specific about what was missing or insufficient, and specific feedback lets a writer target exactly the right section instead of guessing which part needs to change or, worse, revising a section that already scored well.
- The returned scoring guide, if you have it. Seeing which specific criteria scored below Proficient, alongside ones that already passed, tells the writer precisely where to focus.
- The evaluator's written comments themselves. Paraphrased feedback loses detail. The evaluator's own words are more precise than a summary, even a good one.
- Any updated instructions or resources. Occasionally a course adds a resource or clarifies an expectation between the original submission and the return. Anything new should come along with the request.
- Your own deadline for the resubmission. If you're working inside a tight subscription-term window, telling us that upfront helps prioritize the turnaround appropriately.
Why the exact feedback matters more than a summary
A student might reasonably write "the evaluator said my analysis needed more depth," but the evaluator's actual comment might specifically ask for named financial figures, or a comparison to a particular framework covered in the course, or evidence tied to one particular scenario detail. That specificity is exactly what determines what the revision needs to contain. Sending the evaluator's own words, screenshots or copy-pasted text both work fine, consistently produces a faster, more accurate revision than a paraphrase does.
What a covered revision does and doesn't include
A covered revision targets the specific criteria the evaluator flagged. Sections that already scored Proficient or Distinguished are generally left alone, both because they already met the bar and because touching them unnecessarily introduces a real risk of accidentally weakening something that was already working. This mirrors the same discipline Capella's own resubmission process rewards: precise, targeted revision rather than a ground-up rewrite.
| Included in a covered revision | Not included in a covered revision |
|---|---|
| Expanding or correcting the specific flagged criterion or criteria | A full rewrite of sections that already scored Proficient or Distinguished |
| Incorporating evaluator-cited resources or requirements you send us | Adding entirely new scope the evaluator never mentioned |
| Adjusting formatting or citations if the return specifically flagged them | General style preference changes unrelated to the evaluator's feedback |
| A follow-up check if the same criterion is flagged again on a second pass | Open-ended, unlimited revision requests unrelated to evaluator feedback |
Get your revision built around the evaluator's exact words
Share the returned scoring guide and the evaluator's own comments. We'll target precisely what was flagged, without touching what already scored well.
Get FlexPath Help Common return reasonsRealistic turnaround expectations
Turnaround on a covered revision depends mostly on how much of the assessment the evaluator flagged and how quickly you can get us the feedback after it lands. A revision touching one narrowly scoped criterion in an otherwise-passing assessment typically turns around considerably faster than a return involving several criteria, or one where the evaluator's comments point to a more substantial gap in the underlying approach. As a general pattern, smaller, narrowly scoped revisions move fastest, while returns touching several criteria, or requiring genuinely new research the original draft didn't include, understandably take longer.
| Scope of the return | General turnaround pattern |
|---|---|
| One criterion flagged, narrow and specific feedback | Fastest, since the writer knows exactly what to change and where |
| Several criteria flagged across the assessment | Longer, proportional to how much of the document is affected |
| Feedback pointing to a deeper gap in approach or missing research | Longest, since new research or a restructured argument may be needed |
Because your own subscription term and course pacing keep moving regardless of revision timing, it's worth sending evaluator feedback as soon as it's available rather than waiting. The sooner a writer has the specific comments in hand, the sooner a revised draft can be turned around and resubmitted through your own coursework, keeping your term timeline intact.
How the revision process actually runs, step by step
- You receive the evaluator's return. Capella's own system notifies you, with the assessment marked returned rather than complete.
- You send us the feedback. The scoring guide, the evaluator's specific comments, and any new resources or deadline context, through your dashboard or the same channel as your original order.
- The original writer reviews it. Wherever possible, the same writer who worked on the original draft handles the revision, since they already understand the assessment's context and prior approach.
- Targeted revision happens. Only the flagged sections are addressed, mapped directly to the specific criteria the evaluator called out.
- You review the revised draft. Before resubmitting anything to Capella, you read through the revision yourself to confirm it genuinely addresses the feedback and that you understand the changes made.
- You resubmit through your own coursework. The revised assessment goes back to your evaluator through Capella's normal resubmission process, described in detail in our resubmission policy guide.
Why reviewing the revision yourself still matters
Even with help on both the original draft and any revision, the assessment is ultimately submitted under your own name, and you remain the one accountable for understanding it. Reading through a revised draft before resubmitting, rather than forwarding it straight through, serves two purposes at once: it gives you a chance to catch anything that doesn't sound like your own voice or reasoning, and it means you actually absorb the material the evaluator asked you to demonstrate competency in, which tends to pay off in later, related assessments in the same course or program. Treating delivered work as something to engage with and learn from, not just a file to submit, is consistent with using outside support responsibly rather than as a way to avoid the coursework entirely.
Common questions about coverage windows and eligibility
Students sometimes ask how long a revision request stays eligible for coverage after delivery, and whether a second evaluator return on the same assessment is still covered. In general, a revision request tied to genuine evaluator feedback on a delivered assessment stays eligible for a reasonable window following delivery, intended to comfortably cover normal FlexPath evaluation turnaround rather than an indefinite, open-ended period. If a second return happens on the same assessment after an initial covered revision, that follow-up is typically covered as well, provided it's tied to actual evaluator feedback and falls within the same reasonable window, rather than being an unrelated new request arriving long after the original order closed.
What to do if you're unsure whether something qualifies
If you're not sure whether a specific request counts as a covered revision or a separate change request, the simplest path is to just ask, with the evaluator feedback (or lack of it) in hand. Sharing exactly what happened, whether there's an actual evaluator return involved or just a change of mind, gets a clear answer quickly and avoids any wasted back-and-forth.
A worked example: a returned criterion, start to finish
An abstract description of a policy is harder to picture than a concrete walkthrough. Here's what a typical covered revision looks like from the moment a return lands to the moment a resubmission goes back to Capella.
Scenario: a business analytics assessment
Day 1: The delivered assessment is submitted, covering a proposed data strategy for a case-study organization, with five scored criteria.
Day 4: The evaluator's return arrives. Four criteria scored Proficient or Distinguished. One, tied to "justifies recommendations using the case's own data," scored Basic. The evaluator's comment notes that the recommendation section discussed data-driven decision making in general terms without referencing the specific figures given in the case scenario.
Day 4: The student forwards the returned scoring guide and the evaluator's exact comment, unedited, along with a note about the remaining time left in the subscription term.
Day 5 to 6: The original writer reviews the flagged section, pulls the specific figures from the case materials, and rewrites that section to tie the recommendation directly to those numbers. The other four sections are left untouched.
Day 6: The revised draft is delivered back to the student for review.
Day 6 to 7: The student reads through the revision, confirms it genuinely addresses the evaluator's comment and that the reasoning makes sense, then resubmits it through Capella's own coursework.
Notice how narrowly the actual revision work was scoped: one section out of five, addressed with a specific, named fix rather than a general rewrite. This is the shape a covered revision takes when the evaluator's own comments are shared exactly as written, rather than summarized secondhand.
How revision requests interact with your subscription-term timing
Because FlexPath itself runs on subscription terms rather than a fixed semester calendar, timing matters on both sides of a revision request. On our side, a revision request submitted promptly after a return gives the writer the most room to work within any deadline you're facing. On Capella's side, a resubmission still has to clear before you can move to the next assessment in that course, so a revision cycle that drags on unnecessarily can compress the rest of your term's pacing plan. For that reason, it's worth treating the moment a return lands as a prompt to act quickly rather than something to set aside, even if the rest of the week is already busy.
| Good practice | Why it helps |
|---|---|
| Sending evaluator feedback the same day it arrives | Maximizes the writer's available time before your own deadline |
| Flagging your remaining subscription-term time upfront | Helps prioritize the request appropriately against other work |
| Reviewing the revised draft promptly once delivered | Keeps the resubmission from sitting unsubmitted and eating into term time |
| Waiting several days before forwarding feedback | Compresses the time available for both the revision and Capella's re-evaluation |
Related guides
Revision Policy FAQ
A genuine return from your actual Capella evaluator on a delivered assessment, meaning at least one scoring guide criterion scored below Proficient. Simple preference changes with no evaluator feedback aren't covered the same way.
The evaluator's own written comments, ideally tied to the specific criterion that scored low, along with the returned scoring guide itself if you have it.
Wherever possible, yes. The original writer already understands the assessment's context and approach, which usually makes the revision faster and more consistent.
No. These are two separate things. Our revision is the service-side response to evaluator feedback. Resubmitting the revised work to your evaluator through Capella's own coursework is still a separate, required step.
It depends on scope. A single flagged criterion with specific feedback usually turns around fastest. Returns touching several criteria, or requiring genuinely new research, take longer.
Generally yes, provided it's tied to actual evaluator feedback and falls within a reasonable window following the original delivery, rather than an unrelated request much later.