NR-709A Week 1 Scoping the Evaluation Term: How to Write It

What NR-709A Week 1 asks for

What does it feel like to arrive at the evaluation stage of a doctoral project? Usually like standing in a clinic hallway with a folder of numbers that do not quite match the question you asked eight months ago. A nurse who put a standing depression rescreening step into a community health center's chronic care visits arrived at this stage with three sources of truth about the same thing: a report her quality analyst runs monthly, a spreadsheet a medical assistant kept by hand because the report did not break out the visit type, and her own memory of the two weeks in March when the workflow quietly stopped because the room was being renovated. All three are real. None of them is an evaluation. Turning them into one is the work of this stage, and it starts on paper before it touches a single figure.

The opening written task in an evaluation term generally has three parts. First, restate the aim in the form it was implemented under, not the form you wish it had taken, because the evaluation must answer the question that was actually posed. Second, specify what counts as the answer: which measure, over which window, compared against which baseline, for which population. Third, scope honestly against your hour load. A 128-hour block is not a small amount of time, but it is a term in which you are also probably working, and it will not support an evaluation that requires a hundred chart reviews you have not started.

The intellectual posture of this stage matters more than at any other point in the sequence. You are evaluating a translation of existing evidence into practice at one site, not running a trial. Quality improvement evaluation asks whether a change was implemented and whether the thing you were trying to move moved, in a real setting where many other things were also moving. It does not establish causation, it does not generalize, and writing it as though it does is the fastest way to lose a doctoral reader who knows the difference. The honest version is more useful anyway, because a site deciding whether to keep your change wants to know what happened here.

The boundary that governs every page in this manual. Practicum hours, hour logs, encounter counts, site documentation, preceptor evaluations and signatures are your own record and your site's. They are never drafted, reconstructed, estimated or completed with help from anyone, and no tutor should ever perform, observe or document clinical activity on your behalf. What a manual supports is the written layer around work you genuinely did: scoping an evaluation, structuring an argument, presenting data honestly, writing a reflection that analyzes rather than narrates. Wherever your writing draws on real encounters or a real site, every patient detail is de-identified before it reaches a page, and the site is described by type and size rather than by name.

The NR-709A Week 1 method, step by step

Seven moves that turn a folder of numbers into an evaluation you can actually complete in 128 hours.

1. Split your week's rubric into administrative rows and scholarly rows

   Practicum rubrics mix hour requirements, site documentation and supervision with the written deliverable. Separate them in a working file. The administrative half is yours to satisfy directly with your site and faculty; the scholarly half is what your word budget applies to.

2. Retrieve your aim statement exactly as it was approved

   Copy it verbatim into your draft before you touch it. Aims drift during implementation, and an evaluation written against a remembered aim rather than the approved one produces a mismatch that a committee spots immediately.

3. Write the evaluation question as a single sentence with a comparison in it

   Did the proportion of eligible visits including the step change between a stated baseline period and a stated post-implementation period at this site. Comparison, population, measure and window all inside one sentence, or the sentence is not finished.

4. Inventory what data exists, where it lives, and who can get it

   List every source: a standing report, a registry extract, a manual tally, an audit you would have to run. Note who owns each and how long a request takes. This list is the real constraint on your term and it belongs on paper in week one.

5. Set the window boundaries and defend them

   Say where baseline starts and ends, where implementation starts, whether you are excluding a ramp-up period, and where the post period ends. Every one of those edges is a decision, and evaluations lose credibility when the edges appear to have been chosen after the results were seen.

6. Name what your hour block cannot carry, in writing

   A twelve-month sustainability window, a second site, a patient-reported outcome survey you have not fielded. Scope statements that say what is out of scope read as judgment rather than as limitation, and they protect you when a reader asks why something is missing.

7. Draft the sentence you would write if the result is null

   Write it now, while nothing is at stake. Knowing in advance how you will report no detectable change keeps the later analysis honest and stops the slow drift toward measures that happen to look better.

A layout and word budget for an evaluation scoping paper

Our frame for an opening evaluation-stage deliverable, sized for roughly 1,200 to 1,500 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree. Scale proportionally if your assigned length differs, and cut project background before you cut the measurement specification.

Evidence craft for the opening of an evaluation term

Operational definitions beat labels. Screening completed is a label. Documented completion of the instrument in the visit encounter within the same calendar day, among patients meeting the stated eligibility criteria, is an operational definition. Write definitions at that grain now, because the ambiguity you tolerate in week one becomes an unresolvable argument in week six.

Say where each number comes from, every time. A figure in a doctoral evaluation carries its source, its extraction method and its date range. Reports change specifications, analysts leave, and a number nobody can regenerate is a number that will not survive its first question.

Describe the determination your project operates under accurately. Institutions have their own processes for deciding whether a project is quality improvement or human subjects research, and the outcome is theirs to make rather than yours to predict. Write what determination governs your work and who issued it, and do not characterize a pending decision as settled or promise a particular outcome.

De-identify from the first draft. Work from de-identified extracts wherever the site permits, never carry identifiers into your academic document, and describe the setting by type and volume. A rural community health center with roughly 4,600 annual visits across two clinical pods tells a reader everything relevant and names nothing.

Cite the improvement literature for method, not for content. When you name a framework for evaluating an implementation, attribute it with author and year. Method choices in doctoral work are argued rather than assumed, and one well-placed methodological citation does more for the paper than three more sources about the clinical topic.

Five mistakes that cost points in this week's territory

• Evaluating a different aim than the one approved. Quiet substitution of an easier question is the most common and most damaging opening error in this stage.
• Research language on a QI evaluation. Hypothesis, subjects, treatment arm and statistical power signal that the practice-doctorate distinction has slipped, whatever the rest of the paper says.
• Windows with no stated boundaries. Before and after are not periods. Dates are, and a reader cannot judge an effect without them.
• An unbounded data plan. Committing to a manual review of every chart in a year is how a 128-hour term ends with an unfinished evaluation.
• No plan for a null result. Papers written on the assumption of improvement read defensively when the numbers do not cooperate, and the fix is planning rather than rhetoric.

Before you submit

• The approved aim appears verbatim, with any authorized change noted and dated
• The evaluation question carries measure, population, comparison and window in one sentence
• Every measure has an operational definition, not a label
• Each data source is named with its owner and retrieval route
• All period boundaries are dated and justified
• What 128 hours will not cover is stated explicitly
• Language is quality improvement language throughout, not research language
• De-identification and the governing determination are described accurately
• No sentence claims or implies help with hours, logs or site documentation

Questions students ask about this stage

Keep going