Opening promise against arrived finding: PUBH 9103's Week 10 promise reconciliation example adjusts a practice capstone's chapter one to the study actually done, and logs each change. Searches like "pubh 9103 week 10 assignment example", "pubh9103 week 10 sample" and "pubh 9103 week 10 example" land here.
What a finished PUBH 9103 Week 10 promise reconciliation looks like
A table pairs each promise from chapter one with the corresponding finding from chapter five. Columns record the promise's wording, the finding's wording, the relationship, whether matched, exceeded, narrowed or unmet, and the resolution. Most promises are narrowed rather than broken: the question promised change within each tier, and the finding is clearer for the high tier than for the low. The interview promise delivered a theme the opening never mentioned, coaching during longer visits, so the opening is extended to name it. The code change forced the outcome's name to shift, and chapter one's definitions are updated to match. Each resolution states which text changed and why, and a short log lists every edit with its date. A closing paragraph confirms that no finding was bent to fit the opening.
How a PUBH 9103 Week 10 example is structured
Pairing promise and finding in one row makes every mismatch visible without reading two chapters side by side. The four-way relationship is finer than match or mismatch, because a narrowed promise needs a different repair from an unmet one. Resolutions favor changing the opening, since the opening ought to describe the work as it happened; the rare exception is a conclusion that drifted past its evidence, which is corrected instead. Recording the new interview theme as an extension of the opening shows reconciliation also captures findings nobody promised. Updating definitions for the outcome's changed name keeps a reader from meeting two vocabularies. The dated edit log serves the reviewer who compares versions and asks what moved. The closing confirmation addresses the obvious risk in this exercise, adjusting findings to fit promises.
Promise beside finding
Chapter one's wording and chapter five's wording in one row each.
Matched, exceeded, narrowed, unmet
Four relationships, each calling for a different repair.
Which text moves
Usually the opening; the conclusion only where it had outrun its evidence.
A theme nobody promised
Coaching during longer visits, added to the opening instead of left unannounced.
Dated edits
Every change logged, so a reviewer comparing versions can see what moved.
Where marks go in PUBH 9103 Week 10
The direction of repair is what faculty check first. A reconciliation that edits findings to match the opening has reversed the logic and loses most of the available credit; favoring changes to the opening, with the exception reasoned, earns the central share. The four-way relationship is rewarded for precision. Capturing the unpromised theme draws credit because reconciliation that only trims misses what the study added. Updating definitions for the outcome's new name earns a share for consistency across the document. The dated edit log is valued because a reviewer will ask what changed. The closing confirmation adds a smaller portion. Reconciliations disappoint when promises are paraphrased instead of quoted, when narrowed promises are treated as fully met, or when chapter one is rewritten so thoroughly that its original intent can no longer be traced.
Get a PUBH 9103 Week 10 example written to your instructions
Send chapter one, your conclusions chapter and any earlier audit of promises, with the Week 10 prompt and rubric. Each promise is paired with the finding that arrived, the relationship named, the text that should move identified and every edit logged. A first reconciliation costs nothing, 24 to 48 hours; the chapters paired here come from a made-up capstone.
PUBH 9103 Week 10 questions, answered
Is it legitimate to change chapter one after the results are in?
Yes, and expected, provided you change it to describe the work actually carried out and keep a record of what moved. What would not be legitimate is changing the research question to fit an unexpected result while presenting it as the original aim. The record is what makes that difference visible.
How does this differ from the promise audit in the first capstone course?
That audit checked the opening against a plan, before any data existed. This reconciliation checks it against actual findings. Promises that survived the audit can still fail here, because the data may not deliver what the plan could. The earlier audit's table is a useful starting point for this one.
What if a finding exceeds what was promised?
Report it, and decide whether the opening should announce it. An unexpected theme or result deserves a mention in chapter one if it forms part of the conclusions, so readers are not surprised later. If it is minor, a sentence in the discussion may be enough to place it.