This page holds a finished NR 669 Week 2 immersion objectives review, each objective carried forward, tested against what the site can now supply, and either kept or renegotiated. Searches like "nr 669 week 2 assignment example", "nr669 week 2 sample" and "nr 669 week 2 example" land here.
What a finished NR 669 Week 2 immersion objectives review looks like
Item by item is how this one reads, and the items are the objectives you brought in rather than fresh ones. Each gets three things: the evidence that it is running, the specific feature of the setting supporting or blocking it, and a decision. Keep, narrow, or exchange. The blocked ones carry the most weight, because a block explains something real about the place: the clinic runs one half day a week, the group you needed meets quarterly, the department that owns the work sits in another building. The running ones take less space and still get their evidence, because on track asserted is not on track shown. Exchanges are named as exchanges and argued on what the replacement will demonstrate, never slipped in as though nothing had moved.
How a NR 669 Week 2 example is structured
Some sections supply a table for this and others want prose; where a table is published, fill it and put the reasoning underneath. Either way the movement holds. A short opening states where the immersion stands in hours and in weeks, without commentary. Then each objective in turn, in the wording it was given during the earlier part, so a reader holding both documents matches them without interpretation. Under each one, evidence first: what you have actually done toward it, named as work rather than as intention. Then the site condition acting on it, described concretely enough that somebody who has never visited understands the obstacle. Then the decision and what it costs the remaining weeks. A closing paragraph gathers the changes into one request the preceptor can answer.
The wording, unchanged
Each objective reproduced exactly as it was written in the earlier part, so a reader holding both documents can match them without having to interpret anything.
Evidence, then verdict
What has actually been done toward each objective, named as completed work with dates, before any judgment about whether it is running to time.
The site condition
Whatever in the setting helps or blocks each objective, described concretely: opening hours, meeting cycles, access rules, and who has to agree before anything happens.
Exchanges, argued
Any objective swapped out named as a swap, with a sentence on what the replacement will demonstrate that the original one was going to.
One request at the close
The changes gathered into something the preceptor can answer in a sentence, which is what turns a review into a working document rather than a status page.
Where marks go in NR 669 Week 2
An objectives review with a tick against every item is the version faculty trust least, since an immersion that has satisfied all of them by its midpoint either aimed low or is going unexamined. Next is the objective restated in fresh wording, which stops a reader matching it to the document it came from and reads as history being tidied. Third is a block described as bad luck rather than as a property of the setting, when staffing, geography, meeting cycles and access rules are all open to analysis and disappointment is not. A further cost is the exchange made without argument, and another is an exchange proposed without naming who at the site has to approve it. Least expensive, and simple to supply, is a review carrying no hours at all.
Get a NR 669 Week 2 example written to your instructions
Send the review instructions, any objective table your section supplies and the objectives you carried in, and a custom example is written to them and returned inside 24-48h, the first one free. It arrives with the blocked objectives fully argued, since that is the part carrying the marks.
NR 669 Week 2 questions, answered
My site cannot deliver one of the objectives I brought in.
Write it up as the finding it is. Name the objective, name the feature of the setting that blocks it, and propose the exchange with a sentence on what the replacement demonstrates instead. Faculty read a documented renegotiation as evidence that you are managing the immersion. What marks badly is an objective that vanishes between two documents with nothing said about it.
Does my preceptor have to agree before I submit?
Practice differs by program and your faculty will tell you. The example works either way: proposed changes stay phrased as proposals until somebody agrees to them, and the document marks which are settled and which are pending. That distinction costs one word per objective and protects you if the site later declines the exchange you assumed.
Nothing has changed since my objectives were set.
Then the review is short and it is still analytic. Evidence that an objective is running is not the same as an assertion that it is, so each one gets the work behind it named and dated. A review that says on track five times with nothing underneath reads as unexamined, which is exactly what this week exists to prevent.