This page holds a finished NR 702A Week 6 project charter draft, a one-pager carrying the problem, the aim, the sponsor, the boundaries and what the organization is asked to provide. Searches like "nr 702a week 6 assignment example", "nr702a week 6 sample" and "nr 702a week 6 example" land here.
What a finished NR 702A Week 6 project charter draft looks like
It looks like a form even when no form was supplied. A title block sits at the top with the project's working name, the service, the sponsor and the date of this version. Below it the problem gets one line and the aim is reproduced word for word from Week 5, not paraphrased. A scope section lists what the project covers and, in a second column or a second list, what it does not. There is a line for what the organization is being asked to provide, in people, access and time. Milestones run across four terms with dates against them. At the foot sit the approvals: who signs the charter, and how a change to it gets agreed.
How a NR 702A Week 6 example is structured
Charters are read top to bottom by people who will not read past the first half, so the order is a ranking of what matters. Identification first: the working name, the service, the version and its date, because a charter that gets amended twice needs to say which one a reader has. The problem and the aim follow in two lines, quoted rather than rewritten, so that the same words appear in every document of the term. Scope comes third, and the out of scope list is written before the in-scope one by most careful writers, since the exclusions are what make the inclusions credible. Then the request: what the writer needs from the organization, itemized. Then milestones with dates. The charter ends with approvals and an amendment line, without which the page is a description rather than a commitment.
The title block
Working name, service, sponsor, version and date. Trivial to write and the first thing a reader checks, since a charter with no version cannot be amended safely.
Problem and aim, quoted
Two lines lifted unchanged from the gap paper and the aim statement. Rewording them here is how a project ends up with three slightly different versions of itself.
What is out of scope
The list that earns the marks. Naming the neighboring service, the second shift or the wider population as excluded is what makes the rest of the page believable.
What the organization is asked for
People, access and time, itemized so the sponsor can see the cost. A request nobody can price is a request that gets agreed to and never honored.
Approvals and amendments
Who signs this version and how the next one gets agreed. Charters without an amendment line are abandoned by term three, which faculty have watched happen repeatedly.
Where marks go in NR 702A Week 6
A charter is marked down first for an empty exclusion list. Everything in scope and nothing out of it tells a reader the boundaries have not been thought about, and it is the fault faculty flag before they reach the milestones. Next is the sponsor named as a department rather than as a role with the standing to commit one: quality cannot approve anything, a person in quality can. A third deduction follows milestones with no dates, or dates that all fall in the final term. Charters also lose marks where the aim has been reworded from Week 5, where the request from the organization is vague enough to be refused politely, and where no amendment route is given, so the document cannot survive its first change.
Get a NR 702A Week 6 example written to your instructions
Give us the charter template your program circulated, or the assignment page if your section does not supply one, together with your aim as it currently stands. The sample comes back filled in at the level of detail a sponsor would expect, exclusions included. Turnaround is 24 to 48 hours and the first one costs nothing.
NR 702A Week 6 questions, answered
Is the charter the same as the proposal?
No, and confusing them costs time later. A proposal argues that a project should happen and is written for an academic reader. A charter records what has been agreed and is written for the organization, which is why it is short, dated and signed. Most programs want both eventually, and the charter is the one that gets pinned to a wall and referred to.
My sponsor has not agreed to anything yet. Can I still draft it?
Yes, and the draft is usually what makes the conversation possible. A charter written before the meeting gives the sponsor something concrete to accept, amend or refuse, which is easier than being asked to support a project in the abstract. Mark the version as a draft, leave the approval block unsigned, and say in the assignment that agreement is outstanding.
How long should a charter be?
Shorter than most first drafts. One page is the working target in many sections and two is common once milestones are listed, but length is not the mark: a reader should be able to find the aim, the exclusions and the request inside ten seconds. Anything that cannot be found that fast belongs in the proposal instead.