PAC 499 Module 5 Gathering and Organizing Evidence Example

Reviewed by Frances Ledbetter, MA Aspen University Updated October 2026

This PAC 499 Module 5 sample paper reports midway through Jordan's pilot at Bluegrass Recovery Services, an invented Lexington outpatient program where a peer recovery specialist rings each new client the day after admission. In Aspen University's Senior Capstone, this module is about gathering evidence and putting it in order before analysis. Perla, Provost and Murray explain how to read a run chart, with rules for shifts and trends that keep a team from reacting to noise. McCarty and colleagues describe NIATx, in which treatment agencies used rapid change cycles to shorten waits and keep clients. Braun and Clarke guide the first round of interview coding. The report covers August and September data, a change made after the first cycle, a codebook and the remaining tasks.

CoursePAC 499 Senior Capstone
ModuleModule 5
Paper typeCapstone progress report
LengthAbout 1,110 words, 7 pages
FormatAPA 7 student paper
SchoolAspen University
ProgramPsychology and Addiction Studies
UpdatedOctober 2026

Free sample paper for PAC 499 Module 5

1

Two Cycles In: Organizing Retention Data and Interview Codes for the Bluegrass Peer Call Pilot

Student Name

Psychology and Addiction Studies Program, Aspen University

PAC 499: Senior Capstone

Instructor Name

Month Day, Year

What this page is doingThe title tells the reader where the pilot stands as the report is written. APA 7 student title page.
2

Two Cycles In: Organizing Retention Data and Interview Codes for the Bluegrass Peer Call Pilot

Jordan's capstone pilot at Bluegrass Recovery Services, the outpatient program in Lexington, Kentucky, invented for this course along with Jordan, began on August 1. Each new client receives a call from one of three peer recovery specialists the day after intake. This report, written in mid-November, describes the evidence gathered through two of three monthly cycles, how it is organized and what has changed so far.

Evidence Collected Against the Plan

Planned evidenceStatusNotes
Thirty-day retention, January to June intakesComplete148 intakes; received from the intake coordinator in August
Thirty-day retention, August intakesComplete24 intakes
Thirty-day retention, September intakesComplete23 intakes
Thirty-day retention, October intakesPendingAvailable in early December, when the last October intakes reach day thirty-five
Peer call logsCurrentUpdated weekly by peers
Client interviews, up to tenFive completedThree more scheduled; two clients declined
Peer interviews, threeNot startedPlanned for the final two weeks of November
What this page is doingListing every planned source, including what is late, keeps the report honest about what the analysis will rest on.
3

How the Data Are Managed

The intake coordinator prepares a monthly file listing each client by a study number, intake date, whether the client came to any scheduled appointment in the window from day twenty-five to day thirty-five and whether the peer call was completed. Names and other identifiers stay with the coordinator, in keeping with the special protection federal rules give addiction treatment records. Jordan keeps the files received unchanged in one folder and works only on copies. Each month, Jordan checks the file against the peers' call logs, using the study number; in September, two records showed a completed call that the log did not record, and the coordinator corrected one entry and confirmed the other. Every correction is noted in a data log with the date and reason. Interview recordings are kept on the program's secure computer, transcribed without names and then deleted.

Retention by Month

Month of intakeIntakesRetained at thirty daysPercent retainedCalls completed
January251352None
February231252None
March261350None
April241354None
May251352None
June251352None
August24145818 of 24
September23156520 of 23

Reading the Run Chart

Jordan plotted monthly retention on a run chart, a line graph of a measure over time with the median drawn across it. Perla et al. (2011) explain that run charts help improvement teams tell real change from ordinary variation, provided they read them with rules rather than by eye. They describe four signals. For Bluegrass, a shift would mean retention landing above fifty-two percent, or under it, for six straight months. A trend would mean five months that each improve on, or each fall short of, the month before. Runs are the unbroken stretches a chart makes on one side of its middle line, and a chart with unusually few or unusually many of them points to change. An astronomical point is a month so unlike the rest that it stands out on sight. The baseline months sit tightly around a median of fifty-two percent. August and September are both above it. Two points cannot meet any of these rules, so the chart so far is encouraging but not evidence of change. If October is also above the median, the pilot will still be short of a shift, a limit Jordan will state in the final report.

What this page is doingTwo months above the median looks like progress, and it may be, but the rules exist because two months often turn out to be noise.
4

The First Cycle and What Changed

McCarty et al. (2007) describe NIATx, a network in which addiction treatment agencies made small changes, tested them in rapid cycles and kept what worked, with the aim of reducing waiting times and improving continuation in treatment. Participating agencies reported shorter waits and better continuation, and the authors credited the approach of quick, small tests led by staff. Jordan's pilot follows the same logic. Before August, Jordan predicted that peers would reach nine of ten new clients. They reached eighteen of twenty-four, three in four. The call logs showed why: most missed calls went unanswered, and peers said several clients later told them they ignore calls from numbers they do not know. In the act step, the supervisor and peers agreed that intake staff would tell each new client to expect a call the next day from a named peer and hand them a card with the peer's name and number. In September, peers reached twenty of twenty-three. For October, Jordan predicted that the reach rate would stay above eighty-five percent.

Building the Interview Codebook

Jordan followed the early phases set out by Braun and Clarke (2006), reading each of the first five client transcripts twice before coding and noting first impressions in a memo. Coding then labeled every passage relevant to the research questions, staying close to what clients said. The codes were gathered into a working codebook, which will grow as the remaining interviews are coded.

CodeDefinitionExample from a transcript
Same roadClient describes the peer as someone who understands from experience"He got it. He'd sat in that same lobby."
Practical answersCall resolved a concrete question about attending"She told me the group runs late, so I could plan my ride."
ExpectedClient describes feeling that the program was waiting for them"Somebody knew my name before I walked in Thursday."
Almost did not come backClient describes doubts after the first visit"I was halfway out already."
Unknown numberClient discusses screening or missing calls"Unknown caller goes straight to voicemail on my phone."
Call felt scriptedClient describes the call as routine or impersonal"Felt like a survey, honestly."
What this page is doingThe codebook keeps a negative code, "call felt scripted," so the analysis can report what did not work as well as what did.
5

Work Remaining and Risks

Three client interviews and all three peer interviews remain, as do October retention data and the analysis. The main risk is time: the semester ends in mid-December, and October data arrive in early December. To protect the schedule, Jordan will finish coding all interviews before the October data arrive and will draft the method and context sections of the final report now. A second risk is that the remaining clients interviewed may be those most positive about the call. Jordan has asked the supervisor to invite clients who were not reached as well as clients who were.

Conclusion

After two cycles, the evidence is organized and checked, the call has already changed in response to what the first cycle showed and the interview data are coded with a defined codebook. Retention in August and September sits above the baseline median, but read with Perla and colleagues' rules, two points are not yet a signal. The remaining work is planned, and the risks to finishing are known.

References

Braun, V., & Clarke, V. (2006). Using thematic analysis in psychology. Qualitative Research in Psychology, 3(2), 77-101. https://doi.org/10.1191/1478088706qp063oa

McCarty, D., Gustafson, D. H., Wisdom, J. P., Ford, J., Choi, D., Molfenter, T., Capoccia, V., & Cotter, F. (2007). The Network for the Improvement of Addiction Treatment (NIATx): Enhancing access and retention. Drug and Alcohol Dependence, 88(2-3), 138-145. https://doi.org/10.1016/j.drugalcdep.2006.10.009

Perla, R. J., Provost, L. P., & Murray, S. K. (2011). The run chart: A simple analytical tool for learning from variation in healthcare processes. BMJ Quality & Safety, 20(1), 46-51. https://doi.org/10.1136/bmjqs.2009.037895

PAC 499 Module 5 instructions, in plain terms

The fifth module of PAC 499 typically asks you to report how evidence gathering is going and how you are organizing what you have collected. Treat the Module 5 instructions in your Aspen course as the authority; the project here is invented. Say what you have collected so far against what you planned. Explain how data are stored, cleaned and protected. Present early numbers in a simple table or chart without overstating them. Record what each improvement cycle taught and what you changed. Show how qualitative data are being coded. List what remains and any risks to finishing on time, and cite your methods sources in APA 7. Where a cycle changed the intervention, say exactly what changed and when, because the final analysis has to account for it.

Inside the PAC 499 Module 5 example

Jordan has retention figures for August and September intakes and five client interviews. Perla, Provost and Murray's BMJ Quality and Safety article supplies the run chart rules, including the shift (a run of at least six months clear of the median line) and the trend (at least five steady climbs or drops). McCarty and colleagues' Drug and Alcohol Dependence article on NIATx models the rapid cycles. After August, when peers reached three in four clients, intake staff began telling clients to expect the call. A codebook table lists six codes with definitions and examples. Remaining work includes October data, three more interviews and the peer interviews. A data log records the two September records that disagreed with the call logs and how each was resolved.

Reading the PAC 499 Module 5 grading rubric

Progress reports earn credit for honest accounting of what has been collected, careful data management and early results presented without overclaiming. This example compares collected evidence against the plan, including the interviews still outstanding. It explains how de-identified records are checked for errors. The run chart is read with stated rules, so a rise over two months is not treated as proof. The cycle log shows learning from the first cycle and a specific change, which is the point of the method. The codebook defines each code with an example, so the coding can be checked. Clear next steps and risks complete the report, including a plan to invite clients who were not reached so the interviews do not hear only from the satisfied.

PAC 499 Module 5 help: mistakes that cost marks

Progress reports often present early numbers as findings. Describe them as early and read charts with rules, not by eye. Account for every planned data source, including those behind schedule. Explain how data are cleaned and protected. Record each improvement cycle: what you predicted, what happened and what you changed. Define codes clearly with examples so another person could apply them. List what remains with dates. Raise problems early with your supervisor and instructor. Keep raw data separate from cleaned data so errors can be traced, and write down every decision about excluding or correcting a record. If you are behind, say so now; instructors can help adjust a plan in Module 5 far more easily than in the final week.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official Aspen University document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.

More PAC 499 and Psychology and Addiction Studies sample papers

PAC 499 Module 5 questions, answered

What does PAC 499 Module 5 usually ask for?

Aspen's PAC 499 covers gathering and organizing evidence in this module, so reporting what has been collected, how it is managed and early results is typical. Check your Module 5 prompt.

How do you read a run chart?

With rules: Perla, Provost and Murray treat half a dozen or more points in a row above the median, or in a row below it, as a shift, and five or more steady rises or falls as a trend.

What is NIATx?

The Network for the Improvement of Addiction Treatment, in which agencies used rapid change cycles to reduce waiting times and improve continuation in treatment, as McCarty and colleagues report.

Where can I find a free PAC 499 Module 5 sample paper?

This page holds the full progress report: two months of pilot data, a run chart, a cycle log and an interview codebook.

What is a codebook in qualitative research?

A list of codes with definitions and examples that guides how data are labeled, so coding is consistent and can be checked by others.