NR-667 Week 6 usually foregrounds the course's second identity: preparation for the FNP national certification exam. The written work is a readiness self-assessment and study plan, your practice scores read domain by domain, gaps ranked, hours protected, and a routine that survives the capstone's deadlines. Your section may print this as NR 667 or NR667; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
One line stays fixed under everything this week: the certification seat has your name on it and no one else ever sits in it, at any stage, in any form. Study structure, drilling and planning can be coached; the exam and its practice sittings are yours alone.
What NR-667 Week 6 asks for
Expect the territory to cover the anatomy of honest readiness: baseline performance from practice question banks read at the domain level rather than as one comforting total, the certification blueprints published by the certifying bodies as the map of what the exam weights, the difference between knowledge gaps and test-taking gaps, and the conversion of all of it into scheduled hours that the capstone's writing deadlines cannot raid. The week's hidden subject is self-honesty, because a study plan built on an inflated self-image is a schedule for the wrong student.
Deliverable shapes here commonly include a readiness self-assessment essay, a structured study plan with hours and checkpoints, or a reflective inventory pairing each exam domain with evidence of current standing. If your section runs a discussion this week, it often asks which domain worries you most and what you are doing about it, a prompt that grades the plan more than the worry.
Your week's rubric will likely pay for the machinery: numbers as baselines, rankings with reasons, hours attached to calendar slots, and checkpoints where the plan itself gets re-scored.
The NR-667 Week 6 method, step by step
Six moves from a raw score report to a plan that adjusts itself.
-
Score yourself by domain, in numbers
Pull your practice-bank performance apart into the exam's content domains and record the percentage for each, with the date and the number of questions behind it. A domain score built on twelve questions is a hint, not a baseline, and your write-up should say which it has.
-
Rank gaps by size times weight
Read the certifying body's published blueprint for how the exam distributes its content, and rank your weak domains by the product of the gap and the domain's share. A modest weakness in a heavily weighted area outranks a large one in a thin slice, and showing that arithmetic is the section's core.
-
Split knowledge gaps from test-skill gaps
Wrong because you did not know is a content problem; wrong because you misread, rushed or second-guessed is a different problem with different drills. Classify a sample of your misses and let the split steer the plan's mix.
-
Convert rankings into protected calendar hours
Assign weekly hours to each ranked gap and put them on real days at real times, marked as immovable against capstone deadlines. An hour that can be donated to a paper will be, and the plan should show you know it.
-
Build the question routine with an error log
A daily or near-daily block of practice questions, each miss logged with its domain and its reason category. The log is what turns practice into data, and two weeks of it will re-rank your gaps better than intuition ever will.
-
Set checkpoints that can change the plan, then format
Name the dates you will re-score by domain and the thresholds that trigger reallocating hours. Close with the mechanics: current APA for anything cited, the plan formatted to your section's template, headings in your rubric's wording.
A readiness plan, section by section
Targets assume roughly 1,150 words for a self-assessment with an attached plan. If your section wants a table-first document, keep these blocks as its row groups.
| Section | What belongs there | Word target |
|---|---|---|
| Baseline by domain | Each content domain with its dated score and the question count behind it | 180 to 220 |
| Gap ranking with arithmetic | Weak domains ordered by gap times blueprint weight, with the numbers shown | 160 to 200 |
| Knowledge versus test-skill split | What the classified misses revealed and what each half implies | 150 to 190 |
| The weekly hour map | Hours per gap on named days, marked protected, with the capstone's deadlines beside them | 180 to 220 |
| Question routine and error log | The daily block, the logging fields, and how the log feeds the checkpoints | 150 to 190 |
| Checkpoints and reallocation rules | Re-scoring dates and the thresholds that move hours between domains | 140 to 180 |
The strongest single line a plan can contain is a reallocation that already happened: evidence you re-scored once and moved hours proves the plan is an instrument rather than an assignment.
Citing blueprints and your own numbers
The exam blueprints are published documents, so cite them like documents: the certifying body, the document, the year, checked against the body's current site because blueprints get revised. Where the two certifying bodies' exams differ in emphasis, plan against the one you will actually sit, and name it.
Your own performance data deserves the same denominators you would demand from a study. A domain percentage means little without its question count and date, and a trend claim needs at least two dated points. Practice-bank scores also come from a vendor's question pool, not from the exam itself, so treat them as a proxy and say so; the honesty costs one clause and buys credibility for every number that follows.
If you cite pass rates or preparation research, attach the source, year and population, and keep the verbs associational; preparation studies are almost never randomized. And resist quoting any figure you cannot trace, because a readiness document is exactly the wrong place to model unsourced confidence.
Five mistakes that cost points in a readiness week
- Planning from the total score. One overall percentage hides the exact information the plan needs; domains are the unit of work.
- Hours listed without protection. A plan that never says how its hours survive the capstone's deadlines is a plan already half-donated.
- All questions, no content, or the reverse. Drilling without repairing knowledge, or reading without testing retrieval, each starves half the preparation.
- No error log. Without logged reasons, every miss teaches nothing twice: once when made, once when repeated.
- Confidence standing in for measurement. "I feel strong in this area" is the sentence readiness documents exist to replace.
Before you submit
- Every domain has a dated score with its question count
- The gap ranking shows its gap-times-weight arithmetic
- Misses are classified into knowledge and test-skill piles
- Hours sit on named days, marked protected, beside the writing deadlines
- The error log's fields and review rhythm are specified
- Checkpoints carry thresholds that can actually move hours
Review plan losing to the capstone calendar?
Send your domain scores and deadlines. A structured readiness plan with protected blocks and checkpoints returns inside 24 to 48 hours, floor-checked like everything else.