This page holds a finished NR 720 Week 1 discussion post example: one cross-department failure named precisely, and replies that relocate the trouble rather than agree with it. Searches like "nr 720 week 1 assignment example", "nr720 week 1 sample" and "nr 720 week 1 example" land here.
What a finished NR 720 Week 1 discussion post looks like
Narrowness is the first thing a reader notices. It opens on a single occurrence rather than a category: one patient, one request, one interval where the work existed but sat on nobody's worklist. Then it does the move that earns points, which is to state what each department believes was true at that moment. Transport believes the request had not been released. The unit believes it went out well before that. Both are reading their own record correctly. The post ends by asking what would settle the question instead of proposing anything. Replies do not endorse. A useful one takes the same occurrence and puts the trouble a step further back, at the request rather than the delivery, and names what would show which reading is right.
How a NR 720 Week 1 example is structured
Order matters more than length. The opening move is the occurrence itself, loosely dated, with every detail that could point at one patient or one colleague taken out. Second comes the split: what each side's record says about the same minutes, reported as fact rather than as blame. Third is the naming, where the post says what the missing action actually is, and it is usually a verb rather than a department. Somebody has to release the request, confirm that it arrived, and decide it is no longer theirs. Fourth is the evidence the writer currently has, which in a first week is thin and reads better admitted than dressed up. Last is the open question, phrased so a classmate can take a position against it, because replies attach there.
One occurrence, not a category
The post that works starts from a single event with a time and a place, because a category like discharge delay contains a dozen different failures with a dozen different owners.
What each side logged
Both departments keep a record of the same minutes and the two records rarely agree. Setting those accounts down together is the entire analytical move of this week.
Name a verb, not a unit
The missing thing is usually an action nobody was assigned: releasing, confirming, deciding it is finished. Naming the action rather than the department keeps the post diagnostic.
Replies that relocate
A reply worth points takes the same occurrence and argues the trouble began earlier or later than the writer thinks, then says which record would settle it.
Where your evidence stops
An opening week post rests on one person's view of a process. Saying which half you witnessed directly reads as competence, while quietly filling in the other half reads as padding.
Where marks go in NR 720 Week 1
The most expensive post names a feeling. Frustration, poor teamwork and low morale are what people report about a bad transfer, not what happens during one. Nearly as costly is the post that casts a department as the villain, because an account that assigns fault stops looking the moment it starts feeling satisfying. After that comes scope: everything wrong with discharge cannot be argued in one post, and the ones that land pick a single transfer of a single item. A quieter loss is the missing second record, where the writer reports what their own department logged and never asks what the other side logged. Replies that restate the original in fresh words collect the participation points and nothing above them.
Get a NR 720 Week 1 example written to your instructions
Send the discussion prompt from your classroom along with any word count and reply requirement it sets, and a custom NR 720 Week 1 post written to it comes back inside 24-48h, first one free. If your occurrence involves your employer's own operational reports, those stay with you; describe the pattern instead.
NR 720 Week 1 questions, answered
Can I write about a failure at a workplace I have left?
Yes, and it is often easier, since distance makes the split between two departments visible in a way it is not while you are standing inside one of them. Keep the organization unnamed, describe it by size and type, and be plain that your version of the other department's record is secondhand. A post that says which half of the story it witnessed reads stronger than one that quietly supplies the rest.
How specific can I be about a real patient?
Not very, and the post is better for it. This week needs the shape of the event, not the person: a transfer between two departments, an approximate interval, a request that existed in one place and not the other. No age, no condition, no date closer than a month, no unit small enough that one person becomes obvious. Everything the argument actually needs survives all of that.
Does the post need a source?
Most classrooms expect one reference and the choice matters more than the number. Something on transfers between departments or on operational flow supports the framing, while a general leadership article supports nothing and reads as filler. Bring the source in after the occurrence rather than before it, so the reading explains what you saw instead of deciding in advance what you were going to see.