| Course | PUBH 9101 Completing Doctoral Capstone I |
|---|---|
| Week | Week 3 |
| Paper type | Procedure draft |
| Length | About 580 words, 5 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | PhD in Public Health |
| Updated | October 2026 |
Free sample paper for PUBH 9101 Week 3
From One Vague Line to Eleven Steps: A Procedure Draft Turning "Inspection Records Will Be Extracted" Into Instructions With an Owner, a System and an Output File for a Pool Inspection Capstone
Student Name
Walden University
PUBH 9101: Completing Doctoral Capstone I
Instructor Name
Month Day, Year
From One Vague Line to Eleven Steps: A Procedure Draft Turning "Inspection Records Will Be Extracted" Into Instructions With an Owner, a System and an Output File for a Pool Inspection Capstone
The Line Being Replaced
My capstone plan said: "Inspection records will be extracted and prepared for analysis." That sentence cannot be followed. It does not say who extracts, from which system, which records, or what the result looks like. The procedure below replaces it for the Alder County pool study, set in an invented county. Each step begins with the role that carries it out and ends with the file it produces.
The Procedure
Table 1
Extraction and preparation steps
| Step | Who | Action | System | Output | |
|---|---|---|---|---|
| 1 | Division data analyst | Export all inspections of permitted pools, spas and splash pads from three seasons before the earliest district switch to two seasons after the latest | Inspection database | inspections_raw.csv | |
| 2 | Division data analyst | Export the violation table for the same inspections, with violation code and critical flag | Inspection database | violations_raw.csv | |
| 3 | Program manager | Provide each district's switch date from policy memos | Internal memos | switch_dates.csv | |
| 4 | Program manager | Provide the risk tier assigned to each facility, with dates of any tier changes | Tier spreadsheet | tiers.csv | |
| 5 | Division data analyst | Replace facility names and addresses with study identifiers and keep the key inside the division | Division secure drive | All files above, de-identified | |
| 6 | Author | Keep routine inspections only; set complaint and follow-up visits aside in a separate file | Analysis software | routine.csv; other_visits.csv | |
| 7 | Author | Order each facility's routine inspections by date and form consecutive pairs, ignoring any non-routine visit between them | Analysis software | pairs.csv | |
| 8 | Author | Flag a pair as a repeat when both inspections show at least one critical violation | Analysis software | pairs_flagged.csv | |
| 9 | Author | Attach the facility's tier at the date of the second inspection and the district's switch date | Analysis software | pairs_analysis.csv | |
| 10 | Author | Assign each pair to the season and to before or after its district's switch | Analysis software | pairs_analysis.csv, updated | |
| 11 | Author | Run checks: counts by season and district against the division's annual report, and a random sample of 30 pairs compared with the source records | Analysis software and database read access | checks_log.txt | |
File names are working names; every output is stored on the division's secure drive.
Decisions Embedded in the Steps
Step 6 settles a deferred choice: only routine inspections form pairs, because complaint and follow-up visits are triggered by problems and would inflate repeat rates. Step 7 settles another: a follow-up visit between two routine inspections is ignored for pairing, so the pair still compares two routine visits. Step 8 uses any critical violation at both inspections rather than the same violation, since pools often show different critical problems at different visits; in multistate data, disinfectant problems and missing or faulty safety equipment were each cited at roughly one routine inspection in eight (Hlavsa et al., 2016).
Why Step 11 Matters
Errors in pairing or flagging would bias the outcome without any visible sign. Comparing totals with the division's own annual report catches gross errors, and checking a random sample against source records catches subtler ones. Recording these checks also allows the procedure to be repeated, which is what makes a quasi-experimental result credible to others (Shadish et al., 2002). Because outcome definitions can drift when record systems change, the check also compares violation code lists across seasons (Lopez Bernal et al., 2017).
References
Hlavsa, M. C., Gerth, T. R., Collier, S. A., Dunbar, E. L., Rao, G., Epperson, G., Bramlett, B., Ludwig, D. F., Gomez, D., Stansbury, M. M., Miller, F., Warren, J., Nichol, J., Bowman, H., Huynh, B.-A., Loewe, K. M., Vincent, B., Tarrier, A. L., Shay, T., . . . Beach, M. J. (2016). Immediate closures and violations identified during routine inspections of public aquatic facilities: Network for Aquatic Facility Inspection Surveillance, five states, 2013. MMWR Surveillance Summaries, 65(5), 1-26. https://doi.org/10.15585/mmwr.ss6505a1
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.
The Walden PUBH 9101 Week 3 instructions
Procedure assignments in capstone courses ask candidates to turn general methods statements into instructions that could be followed by someone else. Prompts usually require numbered steps with responsible roles, systems, inputs and outputs, along with any rules applied along the way. Instructors often ask candidates to explain choices built into the steps and to include quality checks. Procedures written as intentions, or that skip the transformations between raw records and analysis files, tend to lose credit, because a study's credibility depends on whether its data preparation could be repeated and checked.
How the PUBH 9101 Week 3 example is put together
The page opens by quoting the vague sentence being replaced. A table lists eleven steps, each with a role, an action, a system and an output file, covering exports, de-identification, filtering to routine inspections, pairing, flagging repeats, attaching tier and switch status, and checks. A section explains three decisions embedded in the steps: routine inspections only, ignoring non-routine visits when pairing, and counting any critical violation at both visits. A closing section explains why the checks matter and how they also watch for changes in violation codes over time. File names are given for every output, and the page notes that all files stay on the division's secure drive. The vague original sentence is quoted at the top so the reader can see how much the procedure adds.
PUBH 9101 Week 3 rubric: what earns full marks
Graders typically evaluate completeness, clarity of responsibility, explicitness of rules and inclusion of checks. Steps that each name a role and an output earn credit because they show the work can be divided and audited. Explaining embedded decisions, such as how pairs are formed, demonstrates methodological reasoning. Quality checks against an independent total and a random sample show rigor. Attention to de-identification and secure storage shows ethical awareness. Procedures that could be handed to a new analyst without further explanation typically earn the highest marks. Graders also respond well when the procedure states which decisions it settles, since a procedure that silently makes choices is harder to defend. Checks that compare violation code lists across seasons show awareness that record systems change over time.
Common PUBH 9101 Week 3 mistakes, and how to avoid them
Take the vaguest methods sentence in your plan and ask: who does this, in which system, starting from what and ending with what file? Break the work into steps small enough that each has one role and one output. Write down every rule you apply along the way, such as which records are excluded. Add at least two checks, one against an outside total and one by sampling records. Store everything securely and say where. If your data preparation exists only in your head, we can prepare a sample procedure from your description. Name every file and where it is stored.
Get a PUBH 9101 Week 3 example written to your instructions
Choose the line in your plan you most dread someone else having to carry out, and send it with the method chapter and the Week 3 prompt and rubric. It returns as numbered instructions, each opening with a role and ending in a named output. No fee for a first draft, delivered within 24 to 48 hours; the analyst and database shown are fictional.
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 4: Source Access Plan
- PUBH 9101 Week 5: Dependencies Plan
- PUBH 9101 Week 6: Sizing Arithmetic
- PUBH 9101 Week 7: Contingency Note
- 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 3: Deviation Log
- PUBH 8546 Week 3: Data Source Appraisal
- PUBH 9103 Week 3: Objection Register
- PUBH 8503 Week 3: Candidate Designs
PUBH 9101 Week 3 questions, answered
Where can I find a free PUBH 9101 Week 3 sample paper?
The Week 3 procedure draft appears above, with eleven steps for extracting pool inspection records.
What sentence does the procedure replace?
Inspection records will be extracted and prepared for analysis.
Why use only routine inspections?
Complaint and follow-up visits are triggered by problems and would inflate repeat rates.
How is a repeat flagged?
When both inspections in a consecutive pair show at least one critical violation.
How is the output checked?
Against the division's annual report totals and by comparing 30 random pairs with source records.