| Course | PU699 Master of Public Health Capstone |
|---|---|
| Unit | Unit 6 |
| Paper type | Seminar reflection |
| Length | About 850 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | Master of Public Health (MPH) |
| Updated | October 2026 |
Free sample paper for PU699 Unit 6
A Flowchart Is Not a Loop: A Unit 6 Seminar Reflection Recording Which of Three Weak Competency Claims in a Beach Advisory Capstone Held, Which Became Conditional and Which Was Withdrawn
[Student Name]
Purdue University Global
PU699: Master of Public Health Capstone
Unit 6 Seminar Reflection
[Instructor Name]
[Date]
The seminar, the classmates and the Port Alder project are composite; the competency framework, the systems concepts and the research cited are real.
How I Use Three Words
Held means the claim stands as written. Conditional means it stands only if a named condition is met before the portfolio. Withdrawn means the claim is removed from the map.
Claim One: Systems Thinking
What the map asserted: competency 22 on the accreditation list, the systems thinking competency (Council on Education for Public Health [CEPH], 2016), carried by a diagram of the advisory system. The challenge: my diagram ran left to right in boxes, rain to runoff to creek to beach to sample to laboratory to advisory. A classmate who works in a state chronic disease program asked where the loop was, and when I said there was none, she said that what I had drawn was a process flowchart. A flowchart shows a sequence. A systems tool should show how parts of the system feed back on each other over time. My reply: I tried to name a loop on the screen and could not, which settled the matter. What I drew afterward: when advisories describe yesterday's water, swimmers see signs posted on clear days and no signs on days after a storm. They learn that the signs are often wrong. As trust falls, fewer people obey the signs, including on the days when they are right. Because compliance is low and nobody complains about a missing advisory, there is little pressure on the department to change its method, so advisories stay late and trust keeps falling. That is a reinforcing loop, and it matters for the project because it means a better model alone will not restore compliance quickly; the department will also have to tell the public that the method has changed. Systems thinking in public health is useful precisely because it shows these feedbacks, which a linear diagram hides (Trochim et al., 2006). Verdict: conditional. The claim holds if the revised diagram, with the trust loop and a balancing loop for staff workload, goes into the portfolio with a paragraph on what it changed in the protocol. I had mapped the competency to a picture of the problem's plumbing. The competency asks for a picture of how the problem keeps itself going.
Claim Two: Stakeholders and Coalitions
What the map asserted: competency 13, proposing strategies to identify stakeholders and build coalitions, carried by what the parks staff and the head lifeguard said about the draft and what it led me to change. The challenge: a classmate who manages a coalition for a county tobacco program asked what I had actually done. I had sent three emails to the parks director and had one phone call with the head lifeguard. She said that was outreach, not a coalition, and that the competency asks for strategies to build one. My reply: the lifeguards had changed something real. The head lifeguard pointed out that the draft protocol had me posting advisories at 9 a.m., an hour after lifeguards open the beaches, which would mean taking down flags people had already seen. Verdict: conditional. The claim will be rewritten as a strategy, naming who must be involved, what each gains and how they will be kept involved through the pilot season, with the lifeguard change as evidence. If the parks department meeting in Unit 8 does not happen, the claim will be withdrawn.
Claim Three: Budget and Resource Management
What the map asserted: competency 10, carried by the protocol's fiscal note. The challenge: a classmate with a finance background read the draft note and found that it priced the rapid testing pilot in detail but left out the staff time needed to run the model every morning, check its inputs and log its calls. My reply: she was right. I had treated the model as free because the software is free. The Chicago comparison of monitoring approaches had already warned that models need local refitting and testing to stay useful (Nevers & Whitman, 2011), and refitting is staff time. Verdict: held, after correction. The fiscal note now includes 20 minutes a day for 70 sampling days, about 23 hours a season, at the specialist's hourly rate, plus four hours each winter to refit and validate the model.
What the Hour Changed
The systems thinking paragraph is the longest because it holds my real change of mind. I had thought of the advisory problem as a technical delay. I now see it partly as a trust problem that a technical fix starts but cannot finish, and I have added a public explanation of the new method to the protocol's launch plan. I also learned to ask, of every competency claim, what the artifact would look like to someone who reads the competency's wording literally.
References
Council on Education for Public Health. (2016). Accreditation criteria: Schools of public health and public health programs. Council on Education for Public Health.
Nevers, M. B., & Whitman, R. L. (2011). Efficacy of monitoring and empirical predictive modeling at improving public health protection at Chicago beaches. Water Research, 45(4), 1659-1668. https://doi.org/10.1016/j.watres.2010.12.010
Trochim, W. M., Cabrera, D. A., Milstein, B., Gallagher, R. S., & Leischow, S. J. (2006). Practical challenges of systems thinking and modeling in public health. American Journal of Public Health, 96(3), 538-546. https://doi.org/10.2105/AJPH.2005.066001
Reading the PU 699 Unit 6 instructions
In Unit 6 you are generally asked to reflect on how the seminar tested your capstone work, often your competency claims. Present what you brought, the challenges raised and your response, organized so a reader can see the outcome for each item. Use consistent terms for outcomes, such as held, conditional or withdrawn, defined at the start. Explain any real change of mind in detail, with what it changed in your deliverable. Name conditions that must be met before the portfolio. Cite sources for concepts you rely on. Write in first person and keep classmates anonymous. If no one challenged a claim, test it yourself with the questions the session raised. Two to three pages is typical.
Inside the PU699 Unit 6 example
The reflection defines its three verdict words, then takes each claim in turn. The systems thinking section quotes the challenge, admits the writer could not name a loop, describes the redrawn diagram with a trust loop and cites systems thinking literature, ending conditional; a highlighted line names the error. The stakeholder section records a coalition manager's challenge and the head lifeguard's correction about posting time, ending conditional with a withdrawal condition. The budget section shows a missing staff-time line, supported by evidence that models need refitting, and ends held after correction. A margin note explains the verdict format, and a closing section describes changes to the protocol and to how the writer reads competencies.
Where the points sit in the PU699 Unit 6 rubric
Seminar reflections in this capstone are usually graded on the quality of self-assessment. Points go to a clear account of each challenge and response and to verdicts that follow from the exchange. Credit rises for a genuine change of mind, explained and connected to a revision of the deliverable. Instructors value conditions stated for unresolved claims and accurate use of competency language. Organization by claim rather than by speaker helps graders. APA citations for concepts and professional, first-person writing complete the rubric. Reflections that defend every claim unchanged, or that summarize the discussion without verdicts, tend to score lower. Defined verdict words, used the same way for every claim, let a grader scan the outcome of the hour in seconds.
PU699 Unit 6 help from the desk
A frequent weakness is narrating the seminar in order without saying what happened to each claim. Organize by claim. Another is defending claims that the discussion showed to be weak; withdrawal or a stated condition reads better. Students also describe changes vaguely; name the revised artifact. Do not attribute comments to classmates by name. Support concepts such as feedback loops with a source. If you have notes from your capstone seminar, send them with your competency map and we will draft a reflection that records each verdict. Keep each claim to one paragraph built in the same order, so the reader can compare what happened to each. Close with what the session changed in the deliverable itself.
Get a PU699 Unit 6 example written to your instructions
Bring your current competency map, the claims you suspect are weakest, the comments those claims drew, spoken or written, and the Unit 6 prompt and rubric. Every claim receives a verdict, held, conditional or withdrawn, in the free first custom sample, returned within 24-48h and written to those instructions, plus what would restore any that fall. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More PU699 papers and MPH samples
- PU699 Unit 1: Discussion Board Post
- PU699 Unit 2: Problem Definition Paper
- PU699 Unit 3: Competency Mapping Document
- PU699 Unit 4: Evidence Synthesis
- PU699 Unit 5: Data Analysis Section
- PU699 Unit 7: Deliverable Draft
- PU699 Unit 8: Stakeholder Presentation
- PU699 Unit 9: Reflection on Practice
- PU699 Unit 10: Capstone Portfolio
- PU501 Unit 6: Smoke-Free Housing Seminar Reflection
- PU685 Unit 6: Seminar Reflection
- PU508 Unit 6: Lifestyle Drift Seminar Reflection
- PU650 Unit 6: Seminar Reflection
PU699 Unit 6 questions, answered
What if nobody in the seminar challenged my competency claims?
Then the reflection can test them itself, using the questions the session raised about other projects. Apply the strongest challenge heard that day to your own weakest claim and report the result. Where a section provides written work in place of the live hour, that assignment usually asks for the same kind of test. A reflection that finds every claim intact deserves a second look.
What counts as a systems thinking tool?
Programs differ, but reviewers generally expect a visual tool that shows how parts of a system interact, not only a sequence. Causal loop diagrams, stock-and-flow models and system maps are common choices. A flowchart can serve elsewhere in a capstone, but a systems thinking claim resting on one alone often draws the challenge described here. Check the exact wording your program uses.
Should the reflection admit that a claim was withdrawn?
Yes. A withdrawn claim, explained, shows the judgment the capstone is meant to demonstrate, and it protects the final portfolio from a claim a reviewer would reject anyway. Say what evidence would restore the claim and when it will exist. Instructors tend to grade the quality of the reasoning, and a withdrawal is often the clearest reasoning in the whole reflection.
Where can I find a free PU699 Unit 6 sample paper?
The complete Unit 6 reflection on the beach advisory competency claims, with all three verdicts, can be read here.
Why is a flowchart not enough for the systems thinking competency?
A flowchart shows steps in sequence. A systems tool such as a causal loop diagram shows how parts feed back on one another over time.