NR 300C Week 6 often asks for a progress report: what has been implemented so far according to your log, how it compares with the design, and what midcourse corrections you are making and why. 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 6 asks for
Real projects rarely run exactly as designed. Faculty expect that, and many sections build in a progress report so students can show they monitor their work and adjust it thoughtfully.
The report usually compares plan and reality: sessions delivered against sessions planned, participants reached against expectations, materials used, problems encountered. Your implementation log is the source for every number.
The strongest reports treat corrections as decisions backed by evidence. A change because attendance was low at the morning session and the partner suggested evenings reads as good practice; an unexplained change reads as drift.
The NR 300C Week 6 method, step by step
Five moves that turn a log into a useful progress report.
-
Total what the log shows
Sessions, hours, participants, materials. Keep the numbers factual and the bases clear.
-
Compare each element with the design
A plan versus actual table makes gaps visible at a glance.
-
Explain each gap briefly
What caused it, in a sentence, without blame.
-
Describe the correction and its evidence
What you are changing, who agreed to it and what information supported the change.
-
Check that objectives still hold
If a correction affects an objective or measure, say how, and update the evaluation plan.
A layout and word budget for the progress report
Sized for about 600 to 900 words plus a plan versus actual table. This frame is ours; follow the rubric.
| Section | What belongs in it | Word target |
|---|---|---|
| Summary | Where the project stands in two or three sentences. | 50 to 80 |
| Plan versus actual table | Element, planned, actual, note. | table |
| Explaining the gaps | Reasons for differences, factually stated. | 150 to 200 |
| Corrections | Changes made, who agreed, what evidence supported them. | 150 to 200 |
| Effect on objectives and measures | Any updates to the evaluation plan. | 100 to 140 |
| Next steps | What remains before the dissemination product. | 60 to 90 |
Evidence craft for progress reporting
Use the log, not memory. Every number in the report should trace to a log entry with a date.
Report partner input by role. The program coordinator suggested moving the session keeps people unidentifiable and attributes the decision accurately.
Cite if a correction follows evidence. If a change follows a published approach, such as shorter sessions for a particular audience, cite the source.
Five mistakes that cost points in this week's territory
- Hiding gaps. Faculty expect gaps; hiding them undermines the report.
- Unexplained changes. Every correction needs a reason and an agreement.
- Numbers without bases. State totals and the expected figures they are compared with.
- Blaming the partner or participants. Describe causes neutrally.
- Forgetting the evaluation plan. If the project changed, the measures may need to change too.
Before you submit
- Totals come from dated log entries
- A plan versus actual table shows the gaps
- Each gap has a brief, neutral explanation
- Corrections name who agreed and why
- Any effect on objectives or measures is stated
- Next steps lead toward dissemination
Writing the NR 300C progress report?
Send a summary of your log, the design document and the rubric. A premium original draft returns in 24 to 48 hours with plan versus actual laid out and corrections justified. The log itself stays your own record.