Readiness assessment is the written analysis of whether a setting can actually absorb the change you intend to prepare, and at doctoral level it is an organizational analysis rather than a description of enthusiasm. The graded reasoning covers who holds authority over the process you want to alter, what competing work is already consuming the same staff minutes, what the setting's recent history with change has taught its workforce to expect, and where the change would be structurally supported or structurally resisted. Written honestly, it is the section that most often prevents a project from failing later. Your section may print this as NR 705A or NR705A; 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-705A Week 2 asks for
The most common sentence in a weak readiness section is that leadership is supportive. It is almost always true and it is almost never useful. Supportive means somebody said yes in a meeting. What a doctoral readiness assessment needs to establish is narrower and harder: who can change the standing document, who can add an item to a nursing assistant's shift routine, who has to be told before an existing report is modified, and whether any of those people have said yes to the specific thing rather than to the general idea. Support in principle and authority over a workflow are different objects and a project that confuses them discovers the difference in week six.
Consider a long-term care organization where a DNP student proposed a structured handoff step before transfer to the emergency department. Executive leadership endorsed it warmly. The step required the transfer packet to be assembled fifteen minutes earlier than it currently was, which required a change to the evening medication pass sequence, which was controlled by a pharmacy services agreement and not by nursing at all. Nobody had concealed this. It simply had not been asked, because the readiness conversation had happened at the wrong altitude.
The written work at this stage typically takes the form of an organizational or site assessment section within your project documentation, sometimes accompanied by a stakeholder analysis. Some sections carry a posted discussion in which the cohort compares settings. Hold posted work to the same standard as submitted work, since posts do not reopen once submitted in Canvas and doctoral faculty read them.
Two analytic instruments raise this section above description. The first is capacity accounting: expressing the change's demand in the same currency the setting is short of, which in nursing is almost always minutes per staff member per shift rather than dollars. The second is change history. A workforce that has absorbed three initiatives in eighteen months, two of which were quietly abandoned, will respond to yours in a way that has nothing to do with its merits, and a readiness assessment that names that history is doing organizational analysis rather than optimism.
The placement boundary, stated plainly
Everything in this assessment must come from work you actually did. The 128 clinical hours, the hour log, activity records, mentor or preceptor evaluations, site agreements and any signature the facility or university verifies are your own record and are never drafted, reconstructed, estimated or completed with help of any kind. Observations of a unit, conversations with a director of nursing, and time spent watching an evening transfer are things you must have genuinely done before you write about them, and no manual and no tutor can supply them. What can be taught is the written layer: how to organize a readiness analysis, how to convert what you observed into an argument a committee can follow, how to describe an organizational constraint without editorializing about colleagues. De-identify every person who appears in the writing. Refer to roles rather than individuals, remove dates and unit names where they would identify someone, and never include resident or patient detail beyond what an aggregate figure requires.
The NR-705A Week 2 method, step by step
Six moves for writing a readiness assessment that survives contact with the setting.
-
Reduce the rubric rows to verbs and locate the analysis row
Describe and assess sit at different altitudes. An assess row wants a judgment about whether the setting can absorb the change, supported by evidence, and a section that only describes the organization will not satisfy it.
-
Map authority to each element of the change
For every component of the intended change, name the role that controls it. Standing document, staffing routine, electronic record field, existing report, purchasing. Authority frequently sits in more than one place and finding the second one early is the point of the exercise.
-
Price the change in staff minutes
Estimate the time the change adds per occurrence, multiply by frequency, and say whose shift absorbs it and what it displaces. A cost expressed in minutes and displacement is credible; a cost expressed as minimal is not.
-
Write the change history of the setting
What has been introduced recently, what stuck, and what quietly stopped. Describe this factually and without blame, because it predicts the workforce's response to your change more reliably than any stated attitude.
-
Separate the willing, the affected and the deciding
Three distinct groups that readiness sections routinely merge. Enthusiasm from people the change does not touch is not readiness, and resistance from people whose shift absorbs the cost is information rather than obstruction.
-
Close with a readiness judgment and the conditions attached to it
State whether the setting is ready, conditionally ready, or not yet ready, and name the specific conditions that would move it. A judgment with conditions reads as doctoral analysis; a summary paragraph does not.
A layout and word budget for a site readiness assessment
Our frame for a readiness and organizational assessment section, sized for roughly 1,400 to 1,700 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 profile | Type of facility, size, population served, staffing model, and the structural features that bear on this specific change. | 180 to 220 |
| Authority map | Each element of the change with the role that controls it, and where control is shared or sits outside nursing. | 230 to 280 |
| Capacity accounting | Minutes added per occurrence, frequency, whose shift absorbs it, and what the change displaces. | 220 to 270 |
| Change history | Recent initiatives, which persisted, which lapsed, and what the pattern suggests about how this change will be received. | 200 to 250 |
| Stakeholder positions | The deciding, the affected and the willing separated, with what each controls and what each would need to agree. | 240 to 290 |
| Readiness judgment | Ready, conditionally ready or not yet, with the specific conditions and the actions that would satisfy them. | 190 to 240 |
Evidence craft for organizational assessment writing
Use a named readiness or implementation framework and keep its vocabulary. Established models exist for assessing organizational readiness and implementation context, and adopting one lets a committee check your analysis against a recognized structure. Attribute it with its year and use its own domains as your headings rather than inventing private categories.
Label the provenance of every claim about the setting. Observed across shifts, reported by a role, or drawn from a document. Three different weights of evidence, and a committee reads the distinction as methodological care. Anything you cannot label belongs to the fourth category, assumption, and should be written as one.
Describe constraints structurally, never personally. The evening medication pass sequence is controlled by an external services agreement is analysis. Pharmacy is difficult to work with is a sentence that damages both the document and the relationship, and it will be read by faculty who have managed such relationships themselves.
Quantify wherever a number exists. Staffing ratios, average daily census, transfer volume per month, turnover rate over the past year. Readiness arguments built on figures are far harder to dismiss than readiness arguments built on characterization, and most settings already report several of these.
Five mistakes that cost points in this week's territory
- Leadership support presented as readiness. Endorsement in a meeting says nothing about whether the person who controls the workflow has agreed to the specific change.
- Cost described as minimal. Every added step costs somebody time, and a section that cannot say how much and whose has not done capacity accounting.
- Barriers listed generically. Time constraints, staff resistance and competing priorities appear in every weak assessment and describe no setting in particular.
- Change history omitted. Ignoring what the workforce has already lived through leaves out the single best predictor of how your change will land.
- No judgment at the end. An assessment that describes without concluding has not performed the graded task, which is to decide whether the setting can carry this.
Before you submit
- Every element of the change has a named controlling role attached
- The time cost is stated in minutes with the frequency and the displacement
- Each claim about the setting is labelled observed, reported, documented or assumed
- Recent change history at the site is described factually
- Constraints are written structurally rather than as characterizations of people
- The section closes with a readiness judgment and its conditions
Writing your NR-705A readiness section?
Send the rubric and your scope document out of Canvas. A premium original draft comes back in 24 to 48 hours with authority mapped, the cost priced in staff minutes, and a readiness judgment that holds. Revisions run until the grade lands, and your hours, logs and site documentation stay entirely yours.