A finished PD 121 Unit 1 time audit: one week logged as it happened, totaled by category, with the recoverable hours named and the fixed ones left alone. Searches like "pd 121 unit 1 assignment example", "pd121 unit 1 sample" and "pd 121 unit 1 example" land here.
What a finished PD 121 Unit 1 time audit looks like
The artifact is a log rather than an essay about time. Seven days run down the page in blocks of an hour or a half hour, and every block carries an entry, including sleep, commuting, meals and the stretches where very little happened. Shifts, class meetings and caregiving appear as fixed, because the exercise exists to show what remains after them. Entries are specific enough to be checked against a phone or a posted schedule: reading the chapter for one course rather than studying, a grocery run rather than errands. Category totals sit directly beneath the grid. A short read follows, and it refers only to figures already on the page. In a sample the logged week belongs to a composite person, since nobody else can supply the hours of your own.
How a PD 121 Unit 1 example is structured
The grid comes first and the interpretation last, because a reader handed conclusions before data has no way to test either one. Fixed hours go in before anything else, since the shape of a week is set by the blocks a writer cannot move, and whatever survives them is the only part a plan can touch. Categories are defined before any totaling, so the same hour does not land in two of them and the arithmetic means something. Totals sit under the grid they came from rather than in a separate section, which lets an instructor trace a figure back to the blocks that produced it. The closing paragraph stays arithmetic: it names hours that exist in the log, not hours the writer wishes were there, and it stops before it becomes a page of resolutions.
Every hour carries an entry
Blank blocks read as hours nobody tracked, and an audit with gaps in it cannot support any claim about the capacity that is left.
Fixed blocks entered before the rest
Shifts, classes and caregiving are logged first because they set the week's real shape, and negotiable time is only whatever survives them.
Categories defined ahead of the totaling
A stated rule for what counts as study keeps one hour from being counted twice, which is the whole basis of a defensible total.
Totals a reader can trace
Each figure sits beneath the grid that produced it, so an instructor checking the arithmetic against the blocks above never has to take it on trust.
A closing read, not resolutions
The last paragraph interprets numbers already logged and stops short of promising a routine that nothing in the record would support.
Where marks go in PD 121 Unit 1
Time audits lose points for being tidy. A week in which every evening holds two clean study hours and nothing ever overruns has been written backward from its conclusion, and instructors read a great many of them. Blank blocks cost marks by themselves, because untracked hours are exactly where recoverable time hides. Categories broad enough that most of the week lands in personal or other yield totals that carry no information. The commonest deduction is commentary detached from the log: a paragraph about discipline attached to a grid it never cites. An audit of an imagined typical week, rather than a specific one with dates, misses the assignment outright. Padding the log with hours nobody actually spent is a small invention, and everything reasoned from it inherits the flaw.
Get a PD 121 Unit 1 example written to your instructions
Send the Unit 1 instructions your PD 121 classroom posted, with the rubric if your section attaches one, and say which category scheme is required. We write a custom example logged across seven dated days, with totals traceable to the blocks above them and a closing read built from those figures. First one free, back in 24-48h.
PD 121 Unit 1 questions, answered
Do I have to log my own actual week?
Yes, and no example can supply it, because the hours are yours and nobody else holds them. What a finished sample shows is the shape the artifact takes: block size, the rule for each category, where totals belong, and what a closing read is allowed to claim from them. The grid itself you fill from your calendar, phone and shift schedule.
My employer sets my hours. How much of that goes in?
Log the hours and leave the workplace out. A block reading shift, 7am to 7pm carries everything this assignment grades, while the company name, the department, customers or colleagues add nothing to a total and travel into a file that leaves the building. Anything your workplace treats as its own stays out. De-identified, the week still adds up exactly the same.
Which categories should the audit use?
Most instructions supply a scheme, and where yours does, use it rather than a neater one found elsewhere. Where the choice is open, categories earn their place by separating time you control from time you do not, since the closing read depends entirely on that split. Four or five well-drawn categories beat a dozen overlapping ones that push every borderline hour into miscellaneous.