NR 300C Week 4 is commonly the design week: objectives written to be measured, a simple logic model linking inputs and activities to outcomes, and a named measure for each outcome before any service begins. Your section may print the code as NR300C; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog description; your section's rubric decides what your week actually asks.
What NR 300C Week 4 asks for
A three credit project is large enough that faculty expect a designed intervention rather than an improvised one. The design document usually includes objectives, a logic model and an evaluation plan, and it becomes the reference point for the rest of the session.
A logic model is a one-page picture of the project: inputs such as your hours and the partner's space, activities such as education sessions, outputs such as the number of sessions and attendees, and outcomes such as short-term knowledge or confidence. It is a common tool in public health and program planning.
Graders typically check alignment from left to right: every activity leads to an output, every output supports an outcome, and every outcome has a measure.
The NR 300C Week 4 method, step by step
Five moves for a design that can be evaluated at the end.
-
Write outcome objectives before activity objectives
Decide what should change for the community first, then the activities that produce it. Designing backward keeps activities purposeful.
-
Make each objective measurable
Specific, measurable, achievable, relevant and time-bound. A modest number with a clear date beats an ambitious target nobody can check.
-
Draw the logic model in a simple table
Four columns: inputs, activities, outputs, outcomes. One page is enough for a student project.
-
Choose a measure for each outcome
A short pre and post question, an observation checklist, a count of resources distributed, or partner feedback. Keep measures simple and acceptable to the partner.
-
Check privacy and feasibility for each measure
Every measure should avoid personal health information and fit the time participants have.
A layout and word budget for the design document
Sized for about 900 to 1,200 words plus a logic model table. This is our teaching frame; your rubric takes precedence.
| Section | What belongs in it | Word target |
|---|---|---|
| Problem recap | The Week 3 problem statement in brief. | 60 to 90 |
| Outcome objectives | Two or three objectives describing change for the community. | 150 to 200 |
| Activity objectives | The activities that will produce the outcomes. | 150 to 200 |
| Logic model | Inputs, activities, outputs, outcomes. | table |
| Measures | One measure per outcome and how it will be collected. | 200 to 260 |
| Feasibility and privacy | Why the design fits the hours and protects participants. | 120 to 160 |
Evidence craft for project design
Cite a source for the logic model approach if you use it. A public health program planning resource that describes logic models gives the design a credible basis.
Justify the intervention with evidence. One or two sources showing the chosen activity has worked in similar settings support the design choices.
Use validated items cautiously. If you borrow a published question, cite it. If you write your own, say so and keep it simple.
Five mistakes that cost points in this week's territory
- Activities designed before outcomes. Backward design keeps every activity tied to a purpose.
- Outcomes the project cannot reach. A few weeks of education will not change long-term health outcomes; aim for short-term outcomes.
- Missing measures. Every outcome needs a measure named in advance.
- Measures that collect personal health information. Keep measures anonymous and simple.
- A logic model that does not line up. Each column should connect to the next.
Before you submit
- Outcome objectives come first and are measurable
- Activities clearly produce the outcomes
- The logic model connects inputs to outcomes
- Each outcome has a named measure
- Measures are anonymous and acceptable to the partner
- The design fits about forty-eight contact hours
Designing the NR 300C project?
Send your problem statement, partner notes and the rubric. A premium original draft returns in 24 to 48 hours with measurable objectives, a logic model and a measure for every outcome.