This page holds a finished NR 304 Week 2 focused exam write-up, where the regions examined closely and the regions passed over both carry a stated reason. Searches like "nr 304 week 2 assignment example", "nr304 week 2 sample" and "nr 304 week 2 example" land here.
What a finished NR 304 Week 2 focused exam write-up looks like
Read down the finished document and it visibly narrows. The opening lines carry the complaint as reported and the hour of the day it started, then one sentence naming the systems that follow from it. Those systems are then worked in detail, each entry giving the site and the thing that entry is being judged by: the opposite limb, the same site an hour earlier, or the figure the form prints as ordinary. Regions outside the complaint take one compressed line each, naming what was inspected and what it produced. A closing block lists what was not done and why, which is what turns a short examination into a defended one rather than an unfinished one.
How a NR 304 Week 2 example is structured
Order comes from whatever form your section issues, and the example fills it in the printed sequence while adding one thing the form omits. Each region opens with the reason it is present: the complaint sent us here, or this is the opposite limb, or the row simply had to be answered. The complaint block runs first, with onset given as a clock time. Then the systems that complaint reaches, worked one at a time, each entry naming what was done, where, and what the result is being judged by. Paired structures share a line so the two figures can be read without turning back a page. The compressed regions follow, brief on purpose. The final section names each deferral with its reason, which is where a marker checks whether the narrowing was reasoned or merely convenient.
A reason at the top of every region
Each block states why it is present before it reports anything, so a marker can see the examination was aimed rather than assembled from the form alone.
Onset as a clock time
The hour something started rather than recently or a while back, because the whole examination is about to be judged by what came before that hour.
The opposite limb in the same line
Paired sites written together so the difference between them is a recorded finding, not something the writer noticed and expected the reader to assume.
Compressed regions kept in
Areas outside the complaint answered in a line each rather than dropped, since a missing row reads as an oversight and a short row reads as a decision.
Deferrals with their reasons
A closing list of what was not examined and why, which converts the choice at the heart of this week into something a rubric can actually award.
Where marks go in NR 304 Week 2
Top of the list is the narrow examination that has silently grown back to full width. Twelve regions at equal weight answers a different assignment, and it buries the finding the week was built around. Under that comes the narrowing nobody justified, where four systems are simply absent from the page and the reader cannot tell whether they were dropped or never thought of. The rest are smaller and add up quickly. An entry with a result and no site. A finding called high or reduced with nothing named that it is high against. Two paired structures reported as one line when only the accessible one was examined. Onset written as recently. A deferral listed with no reason next to it. And an interpretation slipped into a row that asked what was found.
Get a NR 304 Week 2 example written to your instructions
Give us the Week 2 instructions and the focused examination form your section posted, and a custom example is written into its rows inside 24 to 48 hours, with the complaint you were given driving which regions open up. The first one is free. Send the case text too where your prompt supplies one, since the narrowing has to follow what it actually says.
NR 304 Week 2 questions, answered
How do I know when a focused examination has gone too wide?
Ask what each region would change. If a positive finding there would alter what you do next, or would rule out something the complaint raises, it belongs. If it would only add a line to the page, it is padding and it dilutes the part being marked. Writing that test into the document as a short reason under each heading protects you when a marker disagrees with one of your choices.
The complaint could point at two different systems. Do I pick one?
Examine both and say so in the opening sentence. A complaint that reaches two systems is common, and a write-up naming both, then working each, reads as reasoning rather than as indecision. What loses marks is examining both while writing as though only one was intended, because the reader then cannot tell which regions were planned and which were afterthoughts added on the way through.
Do I still record the ordinary findings inside the focused region?
Yes, and they are worth real points here. A complaint region where three things were ordinary and one was not is a far stronger document than one reporting only the problem, because the ordinary entries are what show the region was actually covered. They also give the abnormal entry something local to stand against, which is the comparison this course keeps asking for.