NR-718 Week 2 Scope of Practice on Paper: How to Write It

What NR-718 Week 2 asks for

A multistate group standardizing its onboarding paperwork built a comparison table of what its advanced practice providers were permitted to do in each state where it operated. The table had four columns and it exposed a mess that the organization had been absorbing for years. In one state the practice act placed no supervisory requirement on the activity in question, but the group's own credentialing policy imposed one anyway, copied from a template written for a different state a decade earlier. In another, the state permitted the activity and the dominant payer would not recognize the resulting claim, so the service was performed and billed under a different provider's identifier, which meant the organization's own utilization data understated what its advanced practice workforce was doing by a large and unmeasured amount. Nobody had built this table before. Building it took two weeks and changed three policies.

That table is the shape of this stage. The written work usually asks for an analysis of the regulatory and organizational environment governing your role, often with comparison across jurisdictions or against a national picture, and often with an argument about the consequences for practice, workforce or patient access. Sections differ in how they frame it, but the discipline is constant: name the system, read the primary document, state what it actually says, and keep the five systems distinct.

Those five are worth setting out plainly because the distinction carries most of the marks. Licensure is granted by a state board and defines the legal boundary of practice in that state. Certification is granted by a national certifying body and attests to specialty knowledge, and it is often required by the state but is not itself the license. Regulation is the board's rulemaking that gives the practice act operational detail. Credentialing and privileging happen inside an organization and can lawfully be narrower than the state permits, never broader. Payer recognition determines whether the work generates revenue under your own identifier, which shapes what an organization will let you do regardless of what the law allows. A paper that keeps these five straight is already scoring above the middle of the pile.

The doctoral layer is the consequence analysis. You are not writing a summary of regulations; you are writing about how the arrangement affects access, workforce deployment, cost and outcomes for a population, and what a leader could change about it. That is the practice-doctorate contribution: reading the regulatory structure as something that produces measurable effects and can be acted on.

The NR-718 Week 2 method, step by step

Six moves for writing a scope analysis that would survive a compliance review.

1. State the specific activity, not the role in general

   Scope questions are answerable only about particular acts: prescribing a class of medication, ordering a category of test, signing a specific form, admitting, supervising. Pick the activity that matters to your practice and hold it constant across every system you examine.

2. Read the practice act and the board rules as primary documents

   Go to the statute and the administrative rules themselves, note the citation and the effective or revised date, and quote only where wording carries the argument. Summaries drift and secondary sources age badly, particularly in a field where rules change between legislative sessions.

3. Separate what the state permits from what your organization permits

   Write both, side by side, and mark the gap. Organizational policy narrower than state law is lawful and extremely common, and it is often the real constraint on practice. Finding that gap is frequently the most useful thing your paper does.

4. Follow the payment path for the activity

   Who can bill for it, under whose identifier, at what recognition, and what that means for how the organization deploys the role. Payment shapes practice as forcefully as regulation and is left out of most student papers, so including it visibly raises the analytic level.

5. Build a comparison that carries an argument

   Two or three jurisdictions, or your state against a national pattern, arranged so the comparison shows something: variation with no clinical justification, a constraint that tracks nothing in the evidence, an access consequence in underserved areas. Comparison without an argument is a table nobody needs.

6. Close with the reachable change and its instrument

   Say what could actually be changed, by which body, through which process, and what evidence would move it. An organizational policy revision, a board interpretation request, a credentialing committee proposal and a legislative amendment are four different asks with four different timelines, and naming the right one is the leadership judgment being assessed.

A layout and word budget for a scope and regulation analysis

Our frame for this paper, sized for roughly 1,500 to 1,800 words plus a comparison table. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.

Evidence craft for regulatory writing

Preserve modal verbs exactly. Shall, may, must and should are not interchangeable in a statute or a rule, and converting one into another inside a paraphrase is a factual error rather than a stylistic choice. When the distinction carries your argument, quote the phrase and cite it.

Date every regulatory claim. Practice acts and board rules are amended, sometimes annually. Give the citation and the version or effective date you consulted, because a claim about what a state permits is a claim as of a date and a reader in this field will check.

Distinguish what is required from what is customary. Many organizational practices exceed what any rule requires, having been adopted out of caution that hardened into assumed obligation. Write both the requirement and the practice, and treat the gap as a finding rather than as noise.

Say when a question is genuinely unsettled. Some scope questions have no clear published answer, and some are answered differently by a board's formal opinions than by its statute. Writing that the documents available do not resolve the question, and naming what would, is stronger than an assumption stated with confidence. Doctoral readers reward that honesty and mark the alternative severely.

Five mistakes that cost points in this week's territory

• Merging licensure and certification. They are issued by different bodies for different purposes, and a paper that conflates them cannot analyze either accurately.
• Citing a secondary summary as the rule. Advocacy maps and trade articles are useful for orientation and are not the regulation. Cite the primary document.
• Undated regulatory claims. A practice act cited without a version makes a claim about the present from an unknown point in time.
• Ignoring the payment layer. Leaving out payer recognition removes the constraint that most often determines how the role is actually deployed.
• Advocacy in place of analysis. Full practice authority is a defensible position and it still needs evidence, a named instrument and an honest account of the counterargument.

Before you submit

• One specific activity is defined and held constant throughout
• Licensure, certification, regulation, credentialing and payment are kept distinct
• Primary documents are cited with dates or versions
• Modal verbs in paraphrases match the source
• The gap between what is permitted and what the organization allows is stated
• The comparison carries an argument about access, workforce or outcomes
• The closing names an instrument, a body and a realistic process

Questions students ask about this stage

Keep going