A schedule is an argument about time, and this stage asks you to make it in writing. The work is to sequence the tasks a project requires, identify which of them cannot slip without moving the finish, load real people onto them at realistic availability, and register the risks that would derail the plan along with what you would do about each. The most common failure is not optimism about individual tasks but blindness to dependency and to the fact that the people doing the work already have jobs. Doctoral writing here is operational and unsentimental. 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 7 asks for
A hospice organization plans to redesign its transfer documentation across four branch offices, and the plan on paper says twelve weeks. It takes nine months. Nothing in the plan was unreasonable in isolation. What the plan missed was that the education could not start until the form was approved, that approval required a committee meeting held monthly, that the clinical manager who was to lead training covered two branches and was on call every third weekend, and that the last branch was scheduled to convert during the same window as an annual survey. Every one of those was knowable in advance, and a schedule is the document that makes them visible.
Three concepts carry the week. Dependency is the first: which tasks must finish before others can start, and which can run in parallel. Writing the dependency out is what converts a task list into a sequence, and the longest chain of dependent tasks through the project is its critical path, meaning the set of tasks where a day lost is a day lost off the end date. Tasks off that path carry float, and knowing where the float sits tells a project lead where to absorb a delay and where to refuse one.
Resource loading is the second. A task estimated at sixteen hours does not take two days when the person assigned to it is available four hours a week, and health care projects run on people whose primary work is clinical. Loading means checking, task by task, whether the assigned person has the hours in the calendar window, and it routinely reveals that the plan requires one manager to do three things in the same fortnight. In post-acute settings the constraint is often sharper still, because a single director of nursing sits on the critical path of everything.
Risk is the third, and it is a written register rather than a paragraph of worry. Each entry names the risk as a condition that might occur, estimates likelihood and impact, states the response, and gives it an owner and a trigger. Responses come in recognized types: avoid by changing the plan, mitigate by reducing likelihood or impact, transfer to another party, or accept with a contingency held. Expect a written plan containing a schedule, a responsibility assignment and a risk register, usually with tables, and often a discussion post on a planning tool. Posts do not reopen once submitted in Canvas.
The NR-711 Week 7 method, step by step
Six moves from a list of tasks to a schedule that survives contact with a real building.
-
Decomposition to estimable tasks
Break each deliverable down until every task can be estimated in hours by the person who would do it. Anything still described in a phrase like roll out the change is a container, not a task, and containers hide the work.
-
Establishment of the dependency network
For each task write what must finish first and what cannot start until it ends. Approval gates, committee cycles and vendor lead times are dependencies even though nobody on the team performs them.
-
Identification of the critical path
Trace the longest dependent chain from start to finish and mark it. Those are the tasks that get your attention, your buffer and your escalation route, and the rest of the plan can absorb small slips without a conversation.
-
Loading of named people at real availability
Assign each task to a role, then check the hours against what that person actually has free in the window, allowing for their clinical schedule, leave and existing commitments. Fix the overloads by resequencing rather than by hoping.
-
Assignment of responsibility across the team
Build a simple matrix showing, for each deliverable, who does the work, who is accountable for it, who must be consulted and who is informed. Ambiguity here produces the two most common project failures, duplicated effort and orphaned tasks.
-
Registration of risks with responses and triggers
Write each risk as a conditional, rate likelihood and impact, choose a response type, name an owner and state the observable event that would activate the response. A risk without a trigger is never acted on until it has already happened.
A layout and word budget for a project plan
Our frame for a schedule and risk deliverable, sized for roughly 1,300 to 1,700 words plus the schedule, matrix and register 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 |
|---|---|---|
| Planning assumptions | The window available, the organizational calendar constraints, and the availability assumed for each role. | 160 to 210 |
| Task breakdown | Deliverables decomposed into estimable tasks with durations and the basis of each estimate. | 240 to 300 |
| Sequence and critical path | Dependencies stated, the critical chain identified, and where float exists in the rest of the plan. | 240 to 300 |
| Resource loading | Who is assigned to what, at what weekly availability, with the conflicts you found and how you resolved them. | 220 to 280 |
| Responsibility matrix | Doer, accountable owner, consulted parties and informed parties for each major deliverable. | 160 to 210 |
| Risk register and monitoring | Risks with likelihood, impact, response type, owner and trigger, plus how progress will be tracked and reported. | 280 to 340 |
Evidence craft for planning documents
State the basis of every duration estimate. Say whether a figure came from a prior project, a vendor's stated lead time, an expert judgment from the person who will do the task, or an assumption. Estimates with a stated basis can be argued with; estimates without one can only be believed or dismissed.
Write availability as hours per week, not as percentages of a person. Saying a manager is fifty percent allocated means nothing in a building where she is also on call. Six hours a week in the Tuesday and Thursday windows is a statement someone can check against a calendar.
Put the organizational calendar in the plan. Survey windows, budget cycles, holiday coverage, open enrollment and committee meeting schedules all constrain a health care project and none of them appear in a task list. Name the ones that touch your window.
Phrase risks as conditions, not as topics. Staffing is not a risk. If two of the four licensed staff trained in the new process leave before go-live, coverage falls below the level the process requires, is a risk with a likelihood, an impact and a response.
Keep clinical work outside the plan's writing help. A schedule can plan when education happens and when an audit is run. The care delivered, the hours a student accrues toward any program requirement, and the site's own documentation belong to the people who performed them and are recorded by them alone.
Five mistakes that cost points in this week's territory
- A schedule with no dependencies. A list of tasks with dates attached is a calendar. Without sequence there is no critical path and no way to know what a delay costs.
- Full-time assumptions for part-time people. Plans built as though clinical staff can give a project eight hours a day fail in the first fortnight and are visibly unrealistic to any reader who manages a unit.
- Risks without owners or triggers. A register that lists concerns and responses but names nobody produces no action when the condition actually occurs.
- No buffer anywhere. Every task estimated at its optimistic duration guarantees a late finish, because delays accumulate and early completions do not.
- Monitoring described as ongoing communication. Say what will be reported, to whom, how often and in what format, or the tracking plan is decoration.
Before you submit
- Planning assumptions and the available window appear before the schedule
- Every task has a duration with the basis of the estimate stated
- Dependencies are written and the critical path is identified
- Resource loading uses hours per week and names the conflicts found
- A responsibility matrix distinguishes doing from being accountable
- Each risk carries likelihood, impact, response, owner and trigger
- Every reference appears in the text and every in-text citation appears in the list
Building the NR-711 project plan?
Send the rubric and your task list out of Canvas. A premium original draft comes back in 24 to 48 hours with dependencies mapped, the critical path marked and a risk register that names owners, and revisions run until the grade lands.