This manual is for RSCH-FPX7868 Assessment 1, start to submission. An opening deliverable in this course is normally an analysis plan: the analytic approach named and cited to whoever built it, the coding path shown from raw segment to code to category to theme, and the four trustworthiness criteria met with specific actions rather than promised in a paragraph. The assessment usually asks for a procedure somebody else could follow, and your scoring guide decides which sections it wants. Below is the method our tutors use for it, a structure that maps to the criteria, and an annotated sample excerpt from interviews with first-generation graduate students. Prefer to hand it off? A premium original sample for this exact assessment comes back in 24 to 48 hours, revised free until it meets the guide. Your courseroom may print this as RSCH FPX 7868 Assessment 1 or RSCH7868 Assessment 1; it is the same deliverable, and RSCH-FPX7868 Assessment 1 is what this manual walks through.
One honesty note before the manual: Capella revises courses and scoring guides over time, so always write to the exact scoring guide attached to your assessment in the courseroom. The course identity above is verified on capella.edu; the method and structure below are our tutors' approach to it, not Capella's official rubric text.
How RSCH-FPX7868 Assessment 1 is scored
Every criterion in the guide is placed at one of four levels rather than converted to a mark, and the top level is the instruction for the section beneath it:
| Level | What it means on a coding and trustworthiness plan |
|---|---|
| Distinguished | The path from segment to theme is traceable and cited to the method's own author, themes carry a subject and a verb, and credibility, transferability, dependability and confirmability each arrive with the action taken, including a deliberate search for cases that do not fit. |
| Proficient | The approach is named correctly and the coding steps are described in order. Sound, and one level short, because the themes are still topics and the rigour is still general. |
| Basic | Coding described in the abstract, themes printed as single nouns, and trustworthiness claimed by naming the four words. The commonest landing spot in this course. |
| Non-performance | A required element is absent, most often the analytic approach's citation, or any statement of how codes became themes. |
One verb costs more credit here than anything else. An analysis section reporting that themes emerged has told the evaluator nothing about how, and the criteria are grading the procedure that passive construction hides. Every finding needs a derivation somebody else could repeat.
The RSCH-FPX7868 Assessment 1 method, step by step
-
Name the analytic approach and cite the person who built it
Reflexive thematic analysis, a codebook approach with two coders, and grounded theory coding rest on different assumptions about where themes come from. Choose one, cite its own author, and describe the phases you will actually perform rather than the phases the textbook lists.
-
Argue the sample in the language of information power
No power calculation applies here. A narrow aim, participants selected for direct experience of the phenomenon, strong theoretical grounding and rich dialogue all let a smaller sample carry more. State the purposive strategy, whether criterion, maximum variation or snowball, and give its rationale.
-
Write a protocol that does not tell the participant the answer
Six to eight open questions with planned probes, ordered from the concrete toward the abstract, nothing double-barrelled. Asking what it was like to contact an advisor produces data; asking how the advisor's silence frustrated the student produces frustration.
-
Show the coding path on real material
Take one stretch of transcript and carry it up the ladder in the draft: the segment, the code close to the participant's own words, the category the code joins, and the theme the set will support. A described procedure with no worked example is a claim about coding rather than evidence of it.
-
Make each theme a sentence, not a noun
A theme needs a subject and a verb, it has to hold in more than one participant's data, and it should survive an attempt to disprove it from the transcripts. If your theme can be printed as one word, it is still a category and the findings row will say so.
-
Set the trustworthiness actions and the stopping rule in advance, then self-score
Decide now what your audit trail contains, who debriefs you, how negative cases get hunted, and what saturation will mean, such as no new codes across three consecutive interviews. Then place every criterion at one of the four levels on your own reading and rebuild whatever sits under the top one.
A structure that maps to the criteria
Planning targets our tutors use for a graduate qualitative analysis plan, not Capella rules; expand whichever section your own guide weights hardest.
| Section | What it must do | Guide word target |
|---|---|---|
| Aim and why it needs words | The question, and the argument that numbers could not answer it, which is itself graded. | ~200 words |
| Sample and information power | Setting, participants, purposive strategy, inclusion criteria, and the richness argument for the size. | ~280 words |
| Data collection | The protocol, its probes, the sequence, recording method and field notes. | ~250 words |
| Coding procedure | The named approach with its citation, the phases performed, and one worked example up the ladder. | ~350 words |
| Trustworthiness | Credibility, transferability, dependability and confirmability, each with the action taken. | ~300 words |
| Ethics and references | Consent for recording, identifiability in a small sample, storage, primary methodologists cited. | ~200 words |
Annotated sample excerpt
An original model paragraph from our team, written to show a coding path that can be audited. Take the moves, then build the version your own data needs.
Open coding of the first six interviews produced segments labelled close to the participants' wording: rehearsing the email before sending it, waiting for permission that never arrives, asking a classmate what a deadline meant rather than asking the advisor.1 Those codes gather into a category I have called checking before asking, which is still a filing decision rather than a finding, so the analytic claim is written as a sentence: first-generation students treat uncertainty about a norm as evidence of their own unreadiness, which routes their questions sideways to peers and away from the person holding the answer.2 The claim held in eleven of fourteen transcripts, and the three that did not fit are reported rather than set aside, since all three participants had a sibling who had already completed a graduate degree, and that contrast is what the theme now rests on.3
- 1Codes stay close to participant language, which keeps the first rung of the ladder auditable instead of interpretive.
- 2Says the category is only a category and then writes the theme as a claim with a subject and a verb. This is the move that separates a findings section from a filing system.
- 3Reports the cases that did not fit and lets them sharpen the theme, which is negative case analysis doing work rather than appearing in a list of rigour terms.
The full premium sample for your exact assessment, written fresh to your scoring guide and issue, is free to request. Study it, revise it into your own voice, and submit work you understand.
The five mistakes that cost Distinguished
- Themes that emerged. Passive discovery language hides the procedure being graded, and no credit exists for a finding whose derivation is invisible.
- Topics presented as themes. A one-word heading with quotations stacked beneath it has organized the data without interpreting it.
- Frequency used as proof. A code appearing in twelve transcripts is not more true than one appearing in two, and counting themes imports a logic from the other half of the research core.
- Rigour claimed by vocabulary. Naming the four trustworthiness criteria without an audit trail, a debriefing or a negative case is a paragraph of terms.
- Traditions mixed without noticing. Bracketing your assumptions in one paragraph and sampling theoretically in the next borrows from two incompatible logics.
Pre-submission checklist
- The analytic approach is named and cited to its own author
- Sample size argued from aim, richness and direct experience rather than from a rule of thumb
- Protocol questions open, sequenced, and free of wording that supplies the answer
- One worked example carries a segment up to a code, a category and a theme
- Every theme written as a sentence, with negative cases reported
- Four trustworthiness criteria each matched to a specific action, and a stopping rule defined
Analysis plan due this week?
Send the guide, the aim and any transcripts or protocol drafts you have. One pass on the eight-person pipeline exists purely to confirm that every claim in the findings can be traced back to something in the data. The premium original sample returns within 24 to 48 hours and is revised without charge until each criterion is met.