NR-621 Week 6 Building the Evaluation Plan: How to Write It

What NR-621 Week 6 asks for

Pull the evaluation file for almost any staff education program and the same document dominates it: a satisfaction form. Learners rated the session highly, would recommend it, found the presenter knowledgeable. None of that answers whether anybody can do anything differently, and the gap between what was collected and what was needed is usually invisible until somebody audits the program. An educator practicum project is graded partly on whether you can avoid producing that same file, which means designing evaluation from the objectives rather than from convenience.

The first distinction to hold is the level of evaluation. Reaction data captures what learners thought. Learning data captures what they can now do. Behavior data captures what they actually do back in practice. Results data captures whether anything downstream changed. Each level is harder and more informative than the one before it, and a project of this scale realistically reaches learning, sometimes reaches behavior with a small follow-up, and rarely reaches results. Say which levels you are targeting and why the higher ones are out of reach, because that reasoning is itself gradable.

The second distinction is formative versus summative. Formative checks happen during the session and exist to steer teaching in real time: a quick question, a show of hands, a two-minute paired practice you circulate through. Summative checks happen at the end and exist to establish achievement against the objective. A design carrying only the second gives you no way to rescue a session that is losing the room, and a design carrying only the first produces no evidence at all. Most strong plans include both and label them.

The third thing this stage asks for is alignment, checked explicitly. Every objective must have an evaluation method that measures the behavior at the level the objective specified. An objective demanding demonstration under simulated pressure cannot be evaluated by a multiple choice question, and one demanding recall of parameters does not need an observed scenario. Write the alignment as a table so the mismatch, if there is one, is visible to you before it is visible to a grader.

Where our help stops in a practicum course

Evaluating learners is your work, done inside your practicum under your mentor's supervision and within whatever permissions your site has given. Practicum hours, hour logs, attendance records, mentor evaluations, site documentation and signatures are your own record and are never drafted, reconstructed, or estimated with help. Nor can anyone score your learners, sit in your session, or produce evaluation data that was not collected. If a planned check could not be run, the honest written answer is that it was not run.

The written layer is where help belongs: aligning methods to objectives, drafting checklist criteria and item stems that measure the intended behavior, planning the timing of checks, and writing the section that explains and defends the plan. Learner evaluation data is sensitive, and de-identification is not optional. Report results in aggregate, never attribute a score or a comment to an individual, be careful with cohorts small enough that a described result identifies its owner, and follow your site's rules about what evaluation information may leave the department at all.

The NR-621 Week 6 method, step by step

Six moves that produce an evaluation plan aligned to the objectives it is supposed to test.

1. Build the alignment table first

   One row per objective, columns for the behavior, the level, the evaluation method and the timing. Any row where the method cannot capture the behavior is a defect you can fix now for free.

2. Choose the instrument from the behavior, not from availability

   Observed performance needs a checklist or rating scale with defined criteria. Application reasoning needs scenario-based items. Recall needs written items. Convenience is the usual reason a plan drifts to the wrong instrument.

3. Write the criteria at the level of the standard you set

   If the objective says all six steps in sequence, the checklist has six criteria and a rule about sequence. A rating scale of one to five with no anchors measures the rater's mood as much as the learner's performance.

4. Place at least one formative check inside the session

   Name what it is, when it happens, and what you will change if it shows learners are not with you. A formative check with no planned response is a pause, not a check.

5. Decide what counts as success for the group, not just the individual

   An objective sets the standard for a learner; the project needs a statement about the cohort. Say what proportion meeting the standard would represent success and be prepared to report it with its base.

6. Plan the follow-up you can actually run

   A short check at a defined interval, using the same criteria, on however many learners you can realistically reach. Modest and real beats ambitious and hypothetical, and the write-up should say which you have.

A layout and word budget for an evaluation plan

Our frame for the evaluation portion of an education project, sized for roughly 1,100 to 1,400 words plus the alignment table and any instrument in an appendix. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree.

Evidence craft for evaluation writing

Use a published evaluation framework and name it. Established models for training evaluation give you level vocabulary a reader already knows, and attributing the model with its year lets a grader check your classification. Apply the same labels throughout instead of alternating between terms.

Say where your criteria came from. Checklist steps drawn from an existing protocol, a published skill standard or a departmental competency document are defensible; steps invented for the occasion need an explicit rationale. Naming the source is one sentence and it is the difference between an instrument and a list.

Address rater consistency even in a small project. If you are the only observer and also the person who taught the session, say so and name the bias that creates. Where a second observer is possible for even a subset, mention it. A short honest paragraph about this outperforms an assertion that the observation was objective.

Keep every reported proportion attached to its base. Nine of eleven learners met the standard on the first attempt, not eighty-two percent. Small cohorts make percentages misleading, and in an evaluation plan the base is the information a reader most needs.

Five mistakes that cost points in this week's territory

• Satisfaction data presented as learning. A form asking whether the session was useful measures reaction and nothing above it.
• Method and objective misaligned. A written quiz cannot evaluate an objective written for observed performance under pressure, however well the quiz is constructed.
• Rating scales without anchors. A one-to-five scale with no description of what each point means produces numbers that cannot be defended.
• No formative check. A session with only an end-point measure cannot correct itself, and the plan misses the easiest available demonstration of teaching judgment.
• A follow-up nobody could run. Proposing a three-month behavior audit in an eight-week session with no access is a plan for a paper, not for learners.

Before you submit

• An alignment table pairs every objective with a method at the right level
• The evaluation levels targeted are named, along with the ceiling and its reason
• Instrument criteria are anchored and their source is stated
• At least one formative check has a planned response attached
• Success is defined for the individual and for the group
• Rater consistency and observer bias are addressed honestly
• No individual learner is identifiable in any reported result

Questions students ask about this stage

Keep going