Every FlexPath assessment has two documents attached to it: an instructions page describing the scenario or task, and a scoring guide listing the exact criteria an evaluator will check. Students who treat the instructions as the assignment and the scoring guide as an afterthought tend to write competent, well-organized documents that still come back for revision. Students who treat the scoring guide as the actual assignment, and the instructions as background context, pass more often on the first attempt. This guide walks through the method in detail.
Why the scoring guide has to come first
The instructions page is written to explain a scenario. It tells you who the audience is, what the business or clinical situation looks like, and roughly what kind of document to produce. It's useful context, but it isn't what gets scored.
The scoring guide is written to specify exactly what an evaluator will look for, criterion by criterion, at each performance level. It's the actual grading instrument. Reading the instructions first primes you to think about the scenario in general terms. Reading the scoring guide first primes you to think in terms of specific, checkable evidence, which is what actually determines your score.
A quick mental model
Think of the instructions as the prompt and the scoring guide as the answer key. You wouldn't study for a test by reading the topic list and ignoring the answer key. FlexPath works the same way, except the "answer key" is published upfront, before you write a single word.
The five-step scoring-guide-first method
This method applies to almost every FlexPath assessment, regardless of course or program. The specific criteria change, but the process for working with them doesn't.
- Download and read the scoring guide in full, before opening the instructions document. Don't skim it. Read every criterion at every performance level, including Non-Performance, so you understand exactly what "not meeting" a criterion looks like.
- Rewrite each criterion in your own words as a single-line checklist item. If a criterion is long or has multiple parts, split it into sub-items. This step alone catches most of the ambiguity that shows up later.
- Read the instructions document now, with your checklist already in hand. You're reading it to understand the scenario and gather any context you need, not to figure out what to write about.
- Draft your document with one labeled section per criterion, in the same order the scoring guide lists them. This isn't just an organizational preference. Evaluators read the scoring guide in order, so matching that structure makes your evidence easy to locate.
- Map your checklist against the finished draft, item by item, before you submit. For each one, point to the specific sentence or paragraph that satisfies it. If you can't point to it quickly, expand that section.
Turning criteria into a document outline
The scoring-guide-first method only works if you actually restructure your document around the criteria, not just keep them in mind while writing normally. A simple table helps translate scoring guide language into section headings.
| Scoring guide criterion (paraphrased) | Suggested section heading |
|---|---|
| Analyzes the problem using a relevant framework or model | "Problem Analysis Using [Framework Name]" |
| Recommends an evidence-based intervention | "Recommended Intervention and Supporting Evidence" |
| Evaluates potential risks or limitations of the approach | "Risks and Limitations" |
| Communicates clearly using professional, discipline-appropriate language | Not a separate section. Applied throughout, but reviewed last |
Not every criterion maps cleanly to its own section. Communication-quality criteria, for example, usually apply across the whole document rather than one part of it. Everything else, though, benefits from an explicit, labeled section that mirrors the scoring guide's own language.
How much to write per criterion
There's no universal word count per criterion, since scoring guides vary by course and assessment complexity. But a consistent pattern shows up across FlexPath assessments: criteria that get one or two sentences of treatment tend to score Basic, while criteria that get a full paragraph with specific, named evidence tend to score Proficient or Distinguished.
- A criterion asking for analysis needs actual analysis: naming the framework, applying it to the specific scenario, and stating the conclusion it leads to.
- A criterion asking for a recommendation needs a specific, actionable recommendation, not a general direction.
- A criterion asking for evidence needs named, cited sources directly tied to the claim they support, not a source list at the end of the document.
As a rough guide, if a criterion's dedicated section is shorter than three or four sentences, it's worth checking whether the requirement has actually been met or just gestured at.
A shortcut that backfires: writing to the instructions instead of the scoring guide
It's tempting to write a strong, well-organized response to the instructions document and assume the scoring guide criteria will naturally get covered along the way. This works sometimes, especially on simpler assessments. On assessments with specific, narrowly worded criteria, it frequently misses at least one requirement, because general good writing doesn't reliably produce the exact evidence a criterion demands.
Building a reusable criterion checklist
Once you've applied this method to two or three assessments, the process gets noticeably faster. Keep a simple running template you reuse every time:
| Checklist column | What goes here |
|---|---|
| Criterion (your own words) | A single, plain-language restatement of the scoring guide requirement |
| Section in my draft | The heading where this criterion is addressed |
| Evidence location | The specific sentence or paragraph satisfying the criterion |
| Confidence | Proficient / Distinguished / Not sure. Flag anything marked "not sure" for expansion before submitting |
This template takes a few extra minutes to fill in per assessment, but it consistently prevents the most common and most avoidable return reason: a requirement that's addressed in spirit somewhere in the document, but never stated explicitly enough for an evaluator to credit it.
Get a scoring-guide-matched draft, criterion by criterion
Send your scoring guide and assessment instructions. Your writer builds the document section by section against every criterion, so nothing gets missed or under-addressed.
Get FlexPath Help Common return reasonsApplying the method across different assessment types
Most FlexPath courses eventually include more than just standard written papers. The scoring-guide-first method adapts to each format, though the specifics shift slightly.
| Assessment type | How the method adapts |
|---|---|
| Standard written paper | Direct application: one labeled section per criterion, in scoring guide order |
| Presentation or slide deck | One slide or slide group per criterion, with speaker notes stating explicitly how that slide satisfies it |
| Discussion-style or reflective assessment | Criteria are addressed within a more conversational structure, but each one still needs an identifiable, explicit section |
| Case study or scenario analysis | Criteria typically map to case-specific sections (background, analysis, recommendation) rather than generic headings |
Whatever the format, the underlying discipline doesn't change: know exactly what's being scored before you start producing content, and make each criterion's evidence easy for an evaluator to find.
What this method does after a Basic score
Even careful application of this method doesn't guarantee every criterion scores Proficient on the first try. Evaluator interpretation has some natural variance, and occasionally a criterion you thought was clearly addressed gets flagged anyway.
When that happens, the checklist you built during drafting becomes valuable again. Pull up the exact section tied to the flagged criterion, compare it against the evaluator's specific comment, and expand only that section. Because your document is already organized by criterion, revision becomes a targeted edit instead of a full rewrite.
- Re-read the scoring guide language for that one criterion, word for word, ignoring the rest of the document.
- Compare it against what your section actually says, not what you meant to say.
- Add explicit, named evidence rather than lengthening the paragraph with restated points.
A worked example: applying the method start to finish
Suppose a scoring guide includes this criterion: "Evaluates the ethical implications of the proposed data collection method." Applying the five-step method looks like this in practice.
Step by step
Step 2 (checklist rewrite): "Explain the ethical concerns with how I'm proposing to collect data, and address them directly."
Step 4 (section heading): "Ethical Implications of the Proposed Data Collection Method"
Draft content: "This study's proposed use of anonymous employee surveys raises informed consent concerns, particularly around whether participants can meaningfully decline without professional repercussions given the direct reporting relationship between surveyed staff and their supervisors. To address this, data collection will be administered by a third-party platform with no manager visibility into individual responses, and participation will be explicitly voluntary with no tracking of non-completion by name."
Step 5 (checklist mapping): Confidence marked "Proficient." The section names a specific ethical concern (coercion risk via reporting relationships), not a generic one, and describes a specific mitigation (third-party anonymized platform), not a vague commitment to "ensure ethics."
Notice that nothing in this example is exceptional writing. It's ordinary, direct prose. What makes it score well is that it names the specific concern, ties it to the actual scenario, and states a specific response, exactly matching what the criterion asked for rather than a general statement about taking ethics seriously.
Common mistakes when applying this method
A handful of mistakes show up repeatedly even among students who are actively trying to follow a scoring-guide-first approach.
| Mistake | Fix |
|---|---|
| Copying scoring guide language verbatim as a heading, then writing generic content underneath | The heading should mirror the criterion, but the content underneath needs specific, scenario-tied evidence |
| Building the checklist after drafting, not before | Build it first. A checklist created after the fact just confirms what you already wrote instead of shaping it |
| Treating the checklist as optional for "easier" assessments | Simpler assessments still get returned for missed criteria; the checklist takes minutes and prevents this regardless of difficulty |
| Addressing a criterion once and assuming it's covered everywhere it's relevant | Some criteria (especially communication and formatting) apply throughout the document, not in one section |
Is the extra time worth it for every assessment?
Some students reserve the scoring-guide-first method for harder or higher-stakes assessments and write more casually on ones that feel routine. This trades a small amount of time saved for a real, measurable increase in return risk, since the assessments that feel "routine" are often exactly the ones where a specific, narrow criterion gets skimmed over.
The time cost of the method is front-loaded and shrinks fast with repetition. On your first assessment, expect the checklist and section-mapping steps to add perhaps twenty to thirty minutes. By the third or fourth time, most students report the entire process, reading the guide, building the checklist, and confirming coverage, taking under fifteen minutes total.
| Approach | Time cost | Typical outcome |
|---|---|---|
| No structured method, write to the instructions only | Lowest upfront time | Higher rate of at least one criterion scoring Basic or below |
| Scoring-guide-first, applied inconsistently | Moderate, only on "hard" assessments | Fewer returns overall, but routine-feeling assessments still get missed occasionally |
| Scoring-guide-first, applied every time | Highest upfront on the first few assessments, then drops sharply | Most consistent pass-on-first-submission rate across an entire program |
Weighed against the time cost of an actual revision cycle, which usually means waiting for evaluator feedback, re-reading the scoring guide anyway, and resubmitting, the upfront investment in this method is almost always the faster path overall, not just the safer one.
Adapting the method as you move through a program
The method doesn't stay static across an entire degree. Early courses tend to have more generously worded scoring guides with some room for interpretation. Later courses, and especially capstone or comprehensive assessments, tend to narrow the wording considerably and add criteria that reference earlier coursework directly.
- Early courses: focus on building the checklist habit itself. The stakes per assessment are lower, which makes it a low-risk place to get comfortable with the process.
- Mid-program courses: start paying closer attention to discipline-specific terminology in the scoring guide, since evaluators increasingly expect that exact vocabulary rather than a general paraphrase.
- Capstone and comprehensive assessments: treat every criterion as cumulative. Scoring guides at this stage often assume familiarity with frameworks introduced several courses earlier, so the checklist should note not just what the criterion asks for, but which prior course it draws on.
Students who carry this method consistently from their first course tend to find the transition to capstone-level scoring guides far less jarring, since the underlying discipline, read the guide first, map it to a checklist, structure the document around it, never changes. Only the complexity of what's being asked does.
Related guides
Scoring Guide Strategy FAQ
Read the scoring guide first. It tells you exactly what will be evaluated. The instructions provide scenario context, which is easier to apply once you already know what you're building toward.
Most criteria benefit from their own labeled section. Communication-quality and formatting criteria are the main exception, since they typically apply across the entire document rather than one specific part.
On your first assessment or two, expect it to take longer while you're learning the format. By the third or fourth assessment, most students complete it in under twenty minutes.
That's usually a sign the criterion hasn't been addressed yet rather than a structural problem. Add a new section specifically for it rather than trying to fold it into an unrelated one.
Yes, though the sections may look more like natural paragraph breaks than formal headings. Each criterion still needs to be explicitly, identifiably addressed somewhere in your submission.
Rarely. Evaluators are looking for identifiable evidence, and a clearly organized document makes that evidence easier to find, not harder. The risk of under-structuring is far more common than the risk of over-structuring.