NR-524 Week 3 is the week where a single word decides whether a design can be graded. An objective built on understand cannot be measured, and everything downstream, the teaching strategy and the assessment, inherits that failure. This stage asks you to write outcome statements at two levels and to keep the verbs honest. Your section may print this as NR 524 or NR524; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
What NR-524 Week 3 asks for
Two levels of statement operate here and they are not interchangeable. Program level outcomes describe what a graduate can do at the end of the whole experience, written broadly and evaluated across years. Course or unit level objectives describe what a learner can do at the end of a much smaller stretch, written narrowly and evaluated within it. A design that mixes the grain sizes, putting a graduate level statement inside a three week unit, produces an objective nothing in the unit could ever demonstrate.
The verb carries the measurement. Classification systems for learning objectives arrange verbs by the kind of thinking they demand, from recall through application to evaluation and creation, and they exist so that a designer can pitch a statement at the right level deliberately. Identify, explain, apply, analyze, evaluate and design ask for different performances and different evidence. Understand, know, appreciate and be aware of ask for nothing observable at all.
Beyond thinking, nursing education deals in skilled performance and in attitude, and the same discipline applies. Perform, demonstrate and calibrate belong to skilled performance. Statements about professional attitude are the hardest to write honestly, because valuing something is invisible; what can be observed is behavior that would be expected of someone who valued it, and writing the behavior is what makes the statement assessable.
Deliverables at this stage are usually a set of outcome statements with a rationale, sometimes with a map showing how course level statements roll up to program level ones. If your section runs a discussion this week, remember Canvas posts cannot be edited once submitted, so check every verb before posting.
The NR-524 Week 3 method, step by step
Six moves that produce statements a later assessment can actually measure.
-
Start from the gap, not from the content
Each statement should close part of the difference your needs assessment documented. Writing objectives from a topic list produces statements that describe coverage rather than ability, and the alignment rows will find the mismatch.
-
Write the performance before the verb
Describe in plain words what you would watch a learner do to be satisfied they had it. Then find the verb that names that performance. Choosing the verb first tends to pull the statement toward whatever the verb list suggests.
-
Set the level deliberately
Decide whether this ability is recall, application, analysis or creation, and pitch the verb there on purpose. A program full of identify and describe has quietly committed itself to graduates who can recite, which is rarely the intention.
-
Add condition and standard where they matter
Given a deteriorating patient scenario, escalate using a structured communication format within a stated interval. The condition says where the performance happens and the standard says how good is good enough, and both make assessment design far easier later.
-
Keep the levels separate and show the roll up
Program statements in one list, course statements in another, then a short map from the small to the large. That map is usually the fastest way to feed the alignment row without adding prose.
-
Test each statement against an imagined assessment
For every objective, name in one phrase how you would measure it. Any statement that resists this test is either unmeasurable or pitched at a level your setting cannot evaluate, and it should be rewritten now rather than in week six.
A layout and word budget for an outcomes document
The frame below suits a deliverable of roughly 1,100 to 1,500 words with a separate statement list or map. It is our tutoring outline rather than an official structure, and your week's rubric overrides it on contact. Scale each target to your assigned length.
| Section | What belongs in it | Word target |
|---|---|---|
| Frame | The program or course, the learner group, and the gap the statements are written to close. | 110 to 150 |
| Program level outcomes | Three to five broad statements about the graduate, each with the source or standard behind it. | 240 to 300 |
| Course or unit objectives | Narrow statements at the right grain, each with a verb chosen deliberately and a condition where useful. | 280 to 360 |
| Level rationale | Why each statement sits at the thinking level it does, argued from the learner profile and the gap. | 230 to 300 |
| The roll up | How the small statements feed the large ones, usually as a short map with a paragraph explaining it. | 150 to 200 |
| Assessability check | One line per objective naming how it would be measured, then a close on the hardest one to write. | 150 to 200 |
Evidence craft for outcome statements
Cite the classification system to its own source. Verb taxonomies for learning objectives were published by identifiable authors and later revised, and the revision differs from the original in both naming and order. Say which version you are using and cite it accordingly.
Anchor program statements to a current standard. Professional and licensure documents are revised on published schedules, and a program outcome aligned to a superseded edition is aligned to nothing. Name the edition year in the sentence.
Do not quote another program's outcomes as evidence. A published outcome set from another school is an example of practice, not proof that the approach works. Use it to illustrate and cite research separately for any claim about effect.
Keep effect claims out of the rationale. This statement is written at the analysis level because the gap involves judgment rather than recall is a design argument and needs no study. Analysis level objectives improve retention is an empirical claim and needs one, with its design and sample named.
Five mistakes that cost points in this week's territory
- Unassessable verbs. Understand, know, appreciate and be familiar with cannot be observed, and every assessment attached to them will be measuring something else.
- Grain size mixed. A graduate level statement inside a short unit cannot be demonstrated in the time available, and the misfit runs through every later section.
- Two abilities inside one statement. An objective joining assess and manage with an and cannot be scored, because a learner may do one and not the other.
- Objectives written from the topic list. Statements that describe what will be covered rather than what a learner will be able to do break alignment before the design has started.
- Everything at the recall level. A whole set built on identify and list commits the program to graduates who can recite, which almost never matches the philosophy stated in week one.
Before you submit
- Every verb names something an observer could see a learner do
- Program level and course level statements are in separate lists
- No statement contains two distinct abilities joined by and
- Each statement traces to part of the documented gap
- The thinking level of each statement is deliberate and defended
- Each objective has a named way it would be measured
Outcomes and objectives due in NR-524?
Send the prompt and the rubric from Canvas. A premium original draft comes back in 24 to 48 hours with assessable verbs, deliberate levels and a roll up map a grader can check in one glance.