| Course | PUBH 9101 Completing Doctoral Capstone I |
|---|---|
| Week | Week 7 |
| Paper type | Contingency note |
| Length | About 540 words, 4 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | PhD in Public Health |
| Updated | October 2026 |
Free sample paper for PUBH 9101 Week 7
If the Main Source Closes, Then What? A Contingency Note Fixing a Switch-Over Week, a Stand-In Source and the Claims a Pool Inspection Records Study Would Give Up
Student Name
Walden University
PUBH 9101: Completing Doctoral Capstone I
Instructor Name
Month Day, Year
If the Main Source Closes, Then What? A Contingency Note Fixing a Switch-Over Week, a Stand-In Source and the Claims a Pool Inspection Records Study Would Give Up
Purpose
The capstone examining Alder County's tiered inspection schedule for pools and spas has two strands, each dependent on something outside my control. This note sets out, for each strand, the trigger that activates a fallback, the fallback itself, the reduced question it could answer and the claims the study would give up. Writing these now prevents a late, rushed decision made under pressure.
Records Strand
Trigger. If the data use agreement is not signed by the end of Week 9 of the coming term, the full timeline cannot hold, because analysis and writing need at least eleven weeks after the extract arrives.
Fallback. The county's public inspection results site, which lists each permitted pool's recent routine inspections and the violations found. It requires no agreement. It shows only the two most recent seasons and does not show risk tiers.
Reduced question. Across all facilities together, did repeat critical findings at back-to-back routine visits differ between the season before and the season after each district's switch, across all facilities combined?
Claims given up. The study could no longer report results by risk tier, which is the heart of the original question, since the switch was meant to change inspection frequency differently by tier. It could not adjust for the trend before the switch, because two seasons are too few for an interrupted time series; the comparison would become a simple before-and-after contrast, open to any change that happened at the same time (Shadish et al., 2002). It also could not check pairing against complete records. The study would say plainly that it describes a change, not an effect.
Interview Strand
Trigger. If fewer than six inspectors agree to be interviewed by the end of Week 6, the planned range of perspectives cannot be reached.
Fallback. Interviews with the two district supervisors, plus a review of the division's written guidance on assigning tiers and scheduling inspections.
Reduced question. How did the division intend tiers to be applied, and how do supervisors describe their application?
Claims given up. The study could not describe how frontline inspectors apply tiers in practice or whether their accounts differ across districts. With few participants, it could not claim to have reached the point where new interviews add little; a commonly cited study found that most themes appeared within about twelve interviews in a fairly homogeneous group (Guest et al., 2006), and two would fall far short.
What Stays the Same
In both fallbacks, the outcome definition, the pairing rules and the use of district switch dates remain unchanged, so results from a reduced study could still be compared with the full design later. A time series study needs several seasons before and after the switch if change is to be told apart from trend (Lopez Bernal et al., 2017), and the fallback would be presented as a preliminary step toward that design rather than a substitute for it.
Decision Point
The chair and I will review both triggers at the Week 6 and Week 9 meetings, and whatever we decide goes into that meeting's notes.
References
Guest, G., Bunce, A., & Johnson, L. (2006). How many interviews are enough? An experiment with data saturation and variability. Field Methods, 18(1), 59-82. https://doi.org/10.1177/1525822X05279903
Lopez Bernal, J., Cummins, S., & Gasparrini, A. (2017). Interrupted time series regression for the evaluation of public health interventions: A tutorial. International Journal of Epidemiology, 46(1), 348-355. https://doi.org/10.1093/ije/dyw098
Shadish, W. R., Cook, T. D., & Campbell, D. T. (2002). Experimental and quasi-experimental designs for generalized causal inference. Houghton Mifflin.
PUBH 9101 Week 7 instructions, in plain terms
Contingency assignments ask candidates to identify the most likely threats to completing their capstone and plan responses in advance. Prompts usually require a trigger that activates each fallback, a description of the fallback, the revised question it could answer and the limits it would impose. Instructors expect triggers to be specific, often tied to dates. Notes that describe fallbacks without saying when they apply, or that claim a fallback would answer the original question equally well, typically lose credit, since the purpose is to make a hard decision easier by settling it before pressure arrives.
Inside the PUBH 9101 Week 7 example
The note opens by explaining why contingencies are set now. A section for the records strand gives a trigger tied to the week the agreement must be signed, a public fallback, a reduced question across all facilities combined, and a list of claims given up, including tier results and trend adjustment. A section for the interview strand gives a trigger tied to the number of inspectors agreeing, a fallback to supervisors and guidance, a reduced question and the claims lost. A section on what stays the same and a decision point at two chair meetings close the note. Both strands use identical headings, which makes the two fallbacks easy to compare. The note also lists what stays the same in a fallback, such as the outcome definition, so that a reduced study could later be extended.
Where the marks sit in the PUBH 9101 Week 7 rubric
Graders generally assess the specificity of triggers, the realism of fallbacks, the honesty of reduced questions and the completeness of claims given up. Dated triggers earn credit because they remove ambiguity about when to switch. Stating that a fallback produces a description rather than an effect demonstrates methodological honesty. Linking lost claims to design principles, such as the need for multiple time points, shows understanding. Keeping definitions constant across fallbacks so results remain comparable shows foresight. Notes that schedule the decision with the chair are typically judged ready to use. Graders often look for a fallback framed as a preliminary step toward the full design rather than a substitute, since that framing protects the candidate's original contribution while being honest about the reduced one.
PUBH 9101 Week 7 help: mistakes that cost marks
Identify the two things most likely to derail your capstone. For each, choose a date or threshold after which you will switch plans, and write it down. Find a fallback source or method that you can reach without the thing that failed. Rewrite your question so the fallback can answer it, and list honestly what you could no longer claim. Keep definitions the same so results stay comparable. Agree the decision points with your chair. If you have not yet faced what happens if your data never arrive, we can draft a sample note for your study.
Get a PUBH 9101 Week 7 example written to your instructions
Describe the one source your study cannot do without, what else could partly stand in, and the Week 7 prompt and rubric. The note fixes a trigger, a fallback with its limits, the smaller question and the claims surrendered, strand by strand. No charge for a first note, back in 24 to 48 hours; this county's public inspection site is made up.
More PUBH 9101 papers and PhD in Public Health samples
- PUBH 9101 Week 1: Status Memo
- PUBH 9101 Week 2: Decision Sweep
- PUBH 9101 Week 3: Procedure Draft
- PUBH 9101 Week 4: Source Access Plan
- PUBH 9101 Week 5: Dependencies Plan
- PUBH 9101 Week 6: Sizing Arithmetic
- PUBH 9101 Week 8: Out-of-Scope Statement
- PUBH 9101 Week 9: Peer Stall Test
- PUBH 9101 Week 10: Promise Audit
- PUBH 9101 Week 11: Working Document
- PUBH 9102 Week 7: Description Pass
- PUBH 8546 Week 7: Standardization Note
- PUBH 9103 Week 7: Practice Brief
- PUBH 8503 Week 7: Evidence Standard Memo
PUBH 9101 Week 7 questions, answered
Where can I find a free PUBH 9101 Week 7 sample paper?
The Week 7 contingency note is reproduced above, with fallbacks for a pool inspection capstone.
What triggers the records fallback?
The data use agreement remaining unsigned at the end of Week 9.
What is the records fallback?
The county's public inspection results site, which shows recent routine visits and violations but not tiers.
What claims would the study give up?
Results by risk tier and adjustment for the trend before the switch.
What triggers the interview fallback?
Fewer than six inspectors agreeing to be interviewed by the end of Week 6.