A protocol nobody has been prepared to run is a document, not a change. The written work in this part of a 192-hour block is the human layer: who has to agree, who has to be trained, what each group is being asked to do differently, and how you will know the preparation actually happened. Doctoral readers score this section on specificity of influence, not on enthusiasm. Your section may print this as NR 705B or NR705B; 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.
What NR-705B Week 3 asks for
Consider a family practice where the project adds a two-minute caregiver conversation at every well-child visit for children with a documented asthma diagnosis. The clinical case is settled and the protocol is written. The obstacle is entirely social. The senior partner believes the practice already does this. One medical assistant is on light duty and rotating. The front desk was never told the project exists and is the group whose schedule flags make the whole sequence possible. Nothing in your evidence set solves any of that, and the written work of this stage is where a doctoral student demonstrates that they know it.
Stakeholder writing at this level is analysis rather than a courtesy list. For each group you name three things: what they control that your project needs, what the change costs them in time or attention, and what would make the change worth it from where they sit. A practice manager whose measure is throughput does not care about screening rates; she cares whether the added step lengthens visits. Writing the same benefit sentence for every stakeholder is the surest sign a student has not done this analysis, and it is visible on the page in seconds.
The training layer is the other half. You are not writing a curriculum. You are writing what each role must be able to do afterwards, how that capability will be built in the time a working clinic can spare, and what artifact will show the preparation occurred. Fifteen minutes at a staff huddle with a one-page reference and a short competency check is a realistic plan for a small practice; a ninety-minute in-service is a plan that will be cancelled twice and then abandoned. Write to the clinic that exists.
Where the boundary sits. Everything in the practicum itself is yours. The 192 clinical hours, the log that records them, any activity or encounter counts, evaluations completed by a preceptor or site mentor, agreements and signatures are your own record and your own work, never drafted, reconstructed or estimated with outside help, and no honest service offers otherwise. What can be taught is the written layer around it: how to structure a stakeholder analysis, how to write a training plan a clinic could run, how to reflect analytically on interactions you actually had. When your writing draws on real conversations or real encounters, de-identify them fully - roles rather than names, no dates, no identifying detail about families. The relationships and the hours are yours to build; only the clarity of the writing about them is on offer here.
The NR-705B Week 3 method, step by step
Six moves for writing a stakeholder and training section that reads as doctoral analysis.
-
Map by control, not by seniority
List every role that can stop the change: whoever owns the schedule template, whoever owns the electronic record build, whoever staffs rooming, whoever answers when a caregiver complains. Influence in a clinic tracks control of a resource far more reliably than it tracks a title.
-
Price the change for each group in their own currency
Minutes per visit for rooming staff, interruption for providers, call volume for the front desk, coding questions for billing. State the cost before you state the benefit, because a stakeholder section that only lists benefits is advocacy rather than analysis.
-
Convert each stakeholder into one named ask
Not engagement. A specific request: approve a schedule flag, release fifteen minutes of huddle time, agree to review positive results before the family leaves. If you cannot write the ask in one sentence, you have not yet decided what you need from that person.
-
Write the training plan as capabilities, then as logistics
Start from what each role must be able to do unassisted afterwards. Then decide the shortest format that builds it inside a working clinic day. Capability first prevents the common inversion where a plan describes a meeting and never says what the meeting produces.
-
Build one competency check per role and keep it small
A rooming staff member who can locate the form, hand it over with the standard phrasing and record the result has demonstrated the capability. Two minutes, observed once. This is preparation for your own project, kept in your own project records, and it is a different thing entirely from any school or site evaluation of you.
-
Name the resistance you expect and what you will do about it
Write the specific objection you anticipate, from which role, and your planned response. Doctoral committees read an anticipated-resistance paragraph as evidence of implementation literacy; its absence reads as a student who has never changed anything in a real building.
A layout and word budget for a stakeholder and training section
Our frame for this stage's written work, sized for roughly 1,500 to 1,900 words. It is our own outline rather than anything the university issues, and your chair's guidance and your week's rubric outrank it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Setting and decision structure | How decisions actually get made in this practice, including where formal authority and practical authority diverge. | 170 to 210 |
| Stakeholder analysis table | Role, what they control, cost of the change to them, the single ask, and current status of that ask. | Table plus 120 of framing |
| Engagement narrative | What has already been discussed with whom, by role, and what was agreed - factual, dated, no adjectives about enthusiasm. | 250 to 300 |
| Capability requirements | What each role must be able to do unassisted once the change starts, written as observable actions. | 200 to 260 |
| Training logistics | Format, length, timing inside the clinic day, materials, and who delivers it, sized to what the practice can absorb. | 230 to 280 |
| Verification of preparation | How you will know each role is ready, and what your project records will hold as proof for your own later analysis. | 180 to 220 |
| Anticipated resistance and response | Two or three specific objections tied to specific roles, with planned responses that concede something real. | 220 to 280 |
Evidence craft for the stakeholder layer
Use a named change or implementation framework and let it do structural work. If you invoke a model of organizational change or an implementation determinants framework, apply its categories to your actual site rather than defining the model for two paragraphs. A framework used as a lens earns marks; a framework summarized and abandoned wastes the word count you need for analysis.
Report conversations as facts with dates and roles. The practice manager agreed on the fourteenth to release ten minutes of the Thursday huddle is a usable sentence. Leadership is enthusiastic about the project is not, because it cannot be checked and it will not be true in week six when the enthusiasm meets the schedule.
Cite the training literature when you make a training claim. If you assert that a brief huddle-based format with a job aid outperforms a single long in-service for sustaining a new step, support it. This is a well-studied area, and an unsupported assertion in a section adjacent to your evidence chapter is conspicuous.
Keep staff unidentifiable in written work. Rooming medical assistant rather than a first name, treating provider rather than an initial. Small practices are small; a description that identifies a colleague inside their own building is a real problem even when the sentence is complimentary.
Distinguish your project records from institutional records in every sentence. A brief competency check you designed for your own implementation lives in your project file. Your practicum hour log, your site evaluations and anything your program or site verifies are separate, are yours alone, and are not part of what any writing support touches.
Five mistakes that cost points in this week's territory
- One benefit sentence reused for every stakeholder. If the same value proposition serves the billing lead and the rooming staff, no analysis has been done.
- A training plan the clinic cannot absorb. Ninety-minute in-services and mandatory modules are the plans that get cancelled. Committees know it and so does your site.
- Adjectives standing in for status. Supportive, engaged and on board are not statuses. Agreed, declined, pending and not yet approached are.
- No anticipated resistance at all. A section describing universal cooperation reads as either naive or unwritten, and it removes your best opportunity to demonstrate systems judgment.
- Treating stakeholders as an audience rather than as operators. These people will run your intervention. The section should read as operational planning, not as a communications strategy.
Before you submit
- Every stakeholder row names something concrete that role controls
- Each role carries a cost line, not only a benefit line
- Each stakeholder has exactly one written ask
- Capabilities are written as observable actions before any logistics appear
- Status language is factual, dated and free of enthusiasm adjectives
- At least two specific objections are named with planned responses
- No staff member or family is identifiable anywhere in the document
Writing the NR-705B engagement layer?
Send the rubric, your protocol and your notes on the site out of Canvas. A premium original draft comes back in 24 to 48 hours with the stakeholder analysis built role by role and the training plan sized to a working clinic, revised free until it lands. Your hours, logs and evaluations are never part of the work.