The second half of a fiscal and project management course turns from money to method. Chartering is the written act of defining a piece of work before it begins: its purpose, its measurable objectives, its boundary, its deliverables, its sponsor and its authority. Scope definition is the other half of the same document, and its most important sentences are the ones about what the project will not do. A charter is short, plain and binding rather than eloquent, and the doctoral skill is compressing a complicated practice change into a page that a sponsor could sign without asking what any of it means. Your section may print this as NR 711 or NR711; 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-711 Week 6 asks for
An assisted living organization convenes a meeting to launch a medication reconciliation project for residents returning from hospital stays. Everyone in the room agrees it is needed. By the end of the hour the work has acquired an electronic record request, a family education pamphlet, a pharmacy contract review and a proposal to standardize transfer forms with two hospital partners, and nobody has written down which of those the project is. Six weeks later the work has no completion condition, because it never had a boundary. Chartering is the discipline that prevents this, and it is a writing task before it is a management task.
A charter answers a fixed set of questions. Why does this work exist, stated as a problem with a magnitude. What will be true when it is finished, stated as objectives with measures. What will the project produce, stated as deliverables that could be handed to someone. What is inside the boundary and what sits outside it. Who sponsors it and what authority does the lead actually hold. Who are the stakeholders and what does each need. What must be true for the work to succeed, and what would stop it. When are the milestones. What resources are committed.
Objectives are where most students lose points, because a purpose written as improving medication safety at transitions cannot be completed, only pursued. An objective needs a direction, a subject, a magnitude, a measure and a window: reducing unreconciled admission medication lists from the current level to a stated target, measured by an audit method you name, across a defined period. That construction forces you to know your baseline and to have decided how the outcome will be measured, and it also gives the evaluation stage something to evaluate.
The scope exclusion list deserves as much care as the inclusion list. In post-acute settings a project touching transitions attracts adjacent problems immediately, because everyone at the table has one. Writing that the project will not modify the electronic record, will not renegotiate the pharmacy contract and will not extend to the memory care unit in this phase is not defensive. It is what makes the timeline honest, and it gives you the sentence you will need in week four when someone asks for one small addition. Expect a written charter, often with a table of deliverables or milestones, and sometimes a peer critique of a classmate's charter on the discussion board. Posts do not reopen once submitted in Canvas.
The NR-711 Week 6 method, step by step
Six moves from an agreed problem to a signable charter.
-
Compression of the problem into a purpose statement
Three or four sentences carrying the setting, the gap with its magnitude, the consequence and the intent. If the purpose runs past a short paragraph, the project is probably two projects.
-
Conversion of intent into measurable objectives
Two or three objectives, each with a direction, a baseline, a target, a measurement method and a window. Anything a reader could not verify as achieved is a hope rather than an objective.
-
Specification of deliverables as nouns
A revised transfer checklist, a training package, an audit tool, a run chart, a final report. Deliverables are things that can be handed over, which is what makes completion observable rather than negotiable.
-
Definition of scope by inclusion and exclusion together
State the units, populations, processes and shifts inside the boundary, then the adjacent items explicitly outside it. The exclusion list is the part that protects the schedule.
-
Identification of stakeholders with their interests and influence
Name each group, what they need from the project, what they can withhold, and how they will be engaged. Consulting families, direct care staff and the receiving pharmacy are different tasks with different cadences.
-
Decomposition of the work into a hierarchy of tasks
Break each deliverable into work packages small enough to estimate and assign. A package nobody can size in hours is still too large, and unsized packages are where schedules quietly fail.
A layout and word budget for a project charter
Our frame for a charter with supporting narrative, sized for roughly 1,300 to 1,700 words including the tables. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever the two disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Purpose and business case | The problem with its magnitude, its cost, and one sentence on the evidence supporting the intended change. | 200 to 260 |
| Objectives | Two or three, each with baseline, target, measure and window, written so completion is checkable. | 180 to 240 |
| Deliverables and milestones | The artifacts the project will produce and the dates or stage markers at which each appears. | 200 to 250 |
| Scope boundary | Units, populations and processes included, followed by an explicit list of what is excluded from this phase. | 200 to 260 |
| Stakeholders and governance | Sponsor, project lead, team roles, decision rights, and the interest and influence of each stakeholder group. | 240 to 300 |
| Assumptions, constraints, risks | What must hold true, what limits the work, and the early risks with their proposed responses. | 200 to 260 |
Evidence craft for charter writing
Write in the flat register of a document that gets signed. Charters are not persuasive essays. Short declarative sentences, no adjectives carrying the argument, and no rhetorical questions. The persuasion happened in the business case; this document records the agreement.
Attach a baseline to every objective. A target without a current level cannot be evaluated and usually reveals that the measurement method has not been settled. Cite where the baseline came from, even if it is your own week two analysis.
Name the sponsor by role and state the authority. Say who can commit staff time, who approves spend, and what decisions the project lead may make alone. In post-acute organizations these often sit with different people, and unstated authority is the most common cause of stalled projects.
Ground the intervention in cited evidence in one clause. A charter is a practice document, not a literature review, but a single sentence naming the evidence base for the change signals that this is translation rather than improvisation.
Keep the charter about the written and organizational work. The project's clinical activity, the resident care itself and any hours a student logs toward a program requirement belong to the student and the site, and they are documented by the people who performed them. The charter plans work; it never stands in for anyone's record of practice.
Five mistakes that cost points in this week's territory
- Objectives without baselines or measures. Improve, enhance and increase awareness cannot be completed, which means the project can never be declared finished.
- An empty exclusion list. A scope section that only says what is included has not defined a boundary and will absorb every adjacent request that arrives.
- Deliverables written as activities. Educate staff is an activity. A training package with an attendance record is a deliverable, and only one of them can be handed over.
- Stakeholders listed without interests. A roster of departments tells the reader nothing about what each group needs or can block.
- Charter written as an essay. Flowing paragraphs where a structured document belongs make the sections hard to locate and read as unfamiliarity with the form.
Before you submit
- The purpose states a magnitude, not just a concern
- Each objective carries a baseline, a target, a measure and a window
- Deliverables are nouns that could be handed to someone
- The scope section includes an explicit exclusion list
- Sponsor, lead and decision rights are named by role
- Assumptions, constraints and early risks each appear with a response
- Every reference appears in the text and every in-text citation appears in the list
Drafting the NR-711 charter this week?
Send the rubric and your project idea out of Canvas. A premium original draft comes back in 24 to 48 hours with measurable objectives, a real exclusion list and governance named by role, and revisions run until the grade lands.