NR 300B Week 7 usually asks for the outcome report: the results of your evaluation plan, objective by objective, with the data summarized clearly and the limits of a small project stated honestly. Your section may print the code as NR300B; 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 300B Week 7 asks for
The evaluation method you named in the Week 2 proposal now produces its result. The outcome report presents that result. For a two credit project this typically means simple counts, short knowledge checks or feedback themes, summarized in a table or a few paragraphs.
Graders look for alignment and honesty. Alignment means each objective is reported using the data source you promised. Honesty means small numbers are reported as small, unmet objectives are reported as unmet, and limits are named.
The report is not the reflection. Keep interpretation of what the experience meant for you for the final paper, and keep this week focused on what happened and what the data shows.
The NR 300B Week 7 method, step by step
Five moves for a clear, credible outcome report.
-
List objectives and data sources side by side
Start with a table: objective, promised data source, what you actually collected. Gaps between promised and collected are findings in themselves.
-
Summarize numbers simply
Counts and simple percentages with the base stated, such as fourteen of twenty attendees answered the check question correctly. A two credit project rarely needs anything more complex.
-
Summarize feedback as themes
If you collected comments, group them into two or three themes and give a short de-identified example of each.
-
Rate each objective against its data
Met, partly met or unmet, with one or two sentences of explanation.
-
Name the limits plainly
Small numbers, a single site, self-reported answers and short timeframes all limit what the data can show. Say so.
A layout and word budget for the outcome report
Sized for about 600 to 900 words plus a results table. Our outline; your rubric decides.
| Section | What belongs in it | Word target |
|---|---|---|
| Overview | What was delivered and over what period. | 60 to 90 |
| Results table | Objective, data source, result, rating. | table |
| Quantitative results | Counts and simple percentages with bases. | 130 to 180 |
| Qualitative results | Feedback themes with de-identified examples. | 130 to 180 |
| Limits | What the data cannot show and why. | 90 to 130 |
| Implications for the agency | What the agency might continue or change. | 80 to 120 |
Evidence craft for reporting results
Always give the base. A percentage without its denominator is not interpretable. Write the count and the total next to every percentage.
Do not generalize beyond your project. Results from one site over a few weeks describe that project. Avoid claims about the community as a whole.
Connect back to your evidence review. If your results resemble or differ from what the Week 4 sources reported, a sentence comparing them shows synthesis.
Five mistakes that cost points in this week's territory
- Reporting data you did not plan to collect, while skipping what you promised. Report the promised data first, then anything extra.
- Percentages with no base. Small projects make this especially misleading.
- Over-claiming impact. A short session can show reach or short-term knowledge, not long-term behavior change.
- Mixing in personal reflection. Keep it for the final paper.
- No limits section. Every small project has limits worth naming.
Before you submit
- Each objective is reported with its promised data source
- Every percentage shows its count and base
- Feedback is summarized as themes with de-identified examples
- Each objective has a rating with a reason
- Limits are stated plainly
- Implications for the agency are practical
Writing the NR 300B outcome report?
Send your evaluation data, the proposal and the rubric. A premium original draft returns in 24 to 48 hours with results aligned to objectives, bases stated and limits named. The data you collected stays yours.