Kept, weakened or broken: PUBH 9101 sets a promise audit in Week 10, and this example checks a risk-tier study's first chapter against the working document it now introduces. Searches like "pubh 9101 week 10 assignment example", "pubh9101 week 10 sample" and "pubh 9101 week 10 example" land here.
What a finished PUBH 9101 Week 10 promise audit looks like
Every sentence in chapter one that commits the study to something is extracted into a table: the problem statement, the purpose, the question, the significance claims and the promised contributions. Each row carries the sentence, its location, the part of the current plan meant to deliver it, and a verdict. Three promises are broken outright: an effect on foodborne illness risk, perspectives from inspectors across the whole division, and findings about complaint-driven visits. Two are weakened, since the purpose still says the study will determine the effect of the switch, which a before-and-after design with a comparison tier cannot claim, and the significance section implies results reaching statewide. Each broken or weakened row has replacement wording drafted beside it. Promises that held are listed at the end, so the audit also records what the revisions protected.
How a PUBH 9101 Week 10 example is structured
Sentence-level extraction is the method, because promises hide in single clauses: a significance paragraph can be accurate overall and still commit the study to one thing it will not do. Three verdicts instead of two let the audit separate a promise needing a qualifier from one needing deletion, and the repairs differ accordingly. The delivering-part column is what makes the verdicts checkable; a promise marked kept should point to a section of the working document, and one pointing nowhere is broken however it sounds. Replacement wording sits beside each problem so the audit produces a revision rather than a to-do list. The verb in the purpose statement gets extended treatment, since determine the effect claims a causal reach the design lacks. Listing kept promises last is deliberate: it confirms the audit read everything, not only the sentences expected to fail.
Every commitment extracted
Problem, purpose, question, significance and contribution sentences pulled into one table, each with its location.
Where it should be delivered
The section of the working document meant to honor each promise, or a blank where no such section exists.
Three broken, two weakened
Illness risk, division-wide perspectives and complaint visits gone; the purpose verb and the reach of significance overstated.
Replacement wording
Revised sentences drafted beside each problem row, ready to drop into chapter one.
What held
Promises that survived the revisions, listed so the audit's coverage can be seen.
Where marks go in PUBH 9101 Week 10
Most credit here comes from promises caught in unlikely places. Finding that the purpose statement overreaches is expected; finding that a significance clause quietly commits the study to statewide relevance takes a sentence-by-sentence read, and that is the reading faculty reward. The delivering-part column carries a large share because it converts impressions into verifiable links. Separating weakened from broken is credited for proportion, since deleting a promise that needed only a qualifier throws away legitimate ground. The purpose-verb treatment earns a notable portion by showing the author understands what the design supports. Drafted replacements are rewarded as evidence the audit will change the document. The kept list is worth a little on top. Audits disappoint when they paraphrase instead of quoting, when they skip significance, or when every broken promise is patched with hedging instead of rewritten.
Get a PUBH 9101 Week 10 example written to your instructions
Send chapter one as it currently reads, your latest working document, and the Week 10 prompt and rubric. Each commitment is extracted, linked to the part of the plan meant to deliver it and judged on whether it still holds, with replacement wording drafted. Free for a first audit, due in 24 to 48 hours; the chapter audited here is a composite.
PUBH 9101 Week 10 questions, answered
What counts as a promise in chapter one?
Any sentence a reader could later hold against the study: what it will examine, determine, compare, describe or contribute. Significance claims count, as do phrases like this study will inform. Background sentences describing the problem usually do not, unless they imply a measurement the study will make. When unsure, include the sentence; a promise marked kept costs nothing.
Should I delete broken promises or rewrite them?
Rewrite where the study still delivers something close; delete where it delivers nothing related. A broken promise about inspectors across the division might become one about inspectors in two districts. A promise about illness outcomes, with no illness data at all, is better removed and, if relevant, moved to recommendations for later work.
Does the audit replace the final check before submission?
No. This audit tests chapter one against the plan; later, once results exist, the opening has to be checked against what was actually found. The two catch different mismatches. Keeping this audit's table helps, because the later reconciliation can start from promises already verified here instead of from a blank page.