This page holds a finished NR 612 Week 2 progress report, showing how a dated invitation ledger and a dated presence ledger are reported together without either becoming an account of effort. Searches like "nr 612 week 2 assignment example", "nr612 week 2 sample" and "nr 612 week 2 example" land here.
What a finished NR 612 Week 2 progress report looks like
Two tables and about a page of prose. The first table carries invitations: date, channel, how many went out, and to which list or which block, one row per batch. The second carries events: date, start time, setting type, the role of whoever was there to count, and the number recorded on the day. The prose retells neither. It states the period covered, how many rows each table holds, and the two or three points where the calendar moved, each with the date it moved and what it displaced. Rows for weeks when nothing went out stay in, because an empty stretch is the reason a later figure looks the way it does. Nothing is written in the future tense except the closing line.
How a NR 612 Week 2 example is structured
The period is fixed first, opening and closing dates given, because everything counted afterwards is counted inside it. The invitation ledger follows, ordered by date rather than by channel, so a reader sees the rhythm of the work instead of a tidy grouping made afterwards. The presence ledger comes next in the same order, and each row names by role the person who held the sheet, since a number with nobody attached to it cannot be checked. Reconciliation is third and short: which batches fed which events, and which events drew people no batch can account for. Deviations follow, each as a date, a cause and a displaced item. Revised dates come next, marked as revisions rather than quietly substituted. One closing line fixes the next action, the day it falls on, and which role has to be in the room.
Two ledgers, kept apart
Invitations and presence answer different questions, so they are recorded separately. Merging them early destroys the only comparison the reach summary will later be in a position to make.
Rows before prose
The tables carry the detail. Written paragraphs state the period, count the rows and point at dates, which keeps the report short and every claim checkable against a line.
Empty weeks stay in
A stretch with no rows shows the project queued behind somebody else, and deleting it removes the explanation a later figure will need before anybody can make sense of it.
Who held the sheet
Each presence row names by role the person doing the counting. A figure with nobody behind it cannot be defended once somebody asks how it was arrived at.
Deviations priced, not mentioned
Each change of date names what it displaced: a venue booking, a season, a group who can now only be reached after the sessions rather than before them.
Where marks go in NR 612 Week 2
The heaviest loss is effort reported as progress, where hours of preparation fill the page and no row records a member of the population being contacted. Second is a share of the plan described as complete, which needs a base nobody has written down and usually flatters the writer. Third is undated rows, since a ledger that cannot be sequenced cannot support the reach work depending on it. Then a channel logged only as outreach, with no list, block or medium named. Lower down: weeks with nothing in them deleted for tidiness, a deviation reported without saying what it displaced, revised dates written over the originals, a person counting who is never identified by role, and closing actions written as intentions with no day attached.
Get a NR 612 Week 2 example written to your instructions
Send your own instructions, the file your section posted, or a graded example you want matched, and a custom NR 612 Week 2 progress report gets written to it and returned inside 24 to 48 hours. The first costs nothing, and it comes back in the format your classroom asks for rather than a generic one.
NR 612 Week 2 questions, answered
Is a table acceptable in a graded report?
In this genre it is preferred. Many sections publish a template with the columns already fixed, and where they do not, a dated table plus a page of prose reads better than four pages of narrative. The written part earns its place by summarizing the period and naming deviations, not by restating rows a reader can already see.
What if almost nothing has happened this period?
Report the period as it was and say what was waiting on whom. A thin ledger with an honest cause beside it is worth more than a full one padded with meetings and reading. It also protects the later analysis, since a short delivery window is one of the few limits a marker accepts without argument when it was declared as it happened.
How do walk-ins get recorded before Week 3?
As their own rows, from the beginning. If somebody arrives who no invitation batch can account for, that row is written as an arrival with no matching batch rather than folded into the nearest one. Reconstructing this later is guesswork, and the reach summary depends on the two groups having been held apart while the memory was fresh.