PHLT 8044 Week 8 Data Collection Schedule Plan Example

Advanced Program Evaluation Walden University Free custom sample in 24 to 48h

This PHLT 8044 Week 8 data collection plan example decides who supplies each record for a composite school water access evaluation, under what agreement and in which month, scheduled against the school calendar. Walden PHLT 8044 expects collisions worked out in advance, so a schedule table runs from a May baseline recall in 24 schools, timed around state testing, through monthly sales extracts, maintenance logs and meter readings, to site visits in September and February, a follow-up recall and cost records in July, with the collision each task must avoid. The plan describes data sharing agreements, family opt-out notice, review requirements, roles and training for the recall script, data handling for differing point-of-sale systems, respect for those who supply data and contingencies for late data, withdrawn schools and delayed installation, a working template for PhD in Public Health evaluators.

CoursePHLT 8044 Advanced Program Evaluation
WeekWeek 8
Paper typeData collection plan
LengthAbout 1,050 words, 6 pages
FormatAPA 7 student paper
SchoolWalden University
ProgramPhD in Public Health
UpdatedOctober 2026

Free sample paper for PHLT 8044 Week 8

1

Data Collection Plan for the School Water Access Evaluation: Who Supplies Each Record, When, Under What Agreement, Scheduled Against the School Calendar Before the Collisions Happen

Student Name

Walden University

PHLT 8044: Advanced Program Evaluation

Instructor Name

Month Day, Year

What this page is doingThe title frames data collection as a scheduling problem against the school year, which is where these plans usually fail.
2

Data Collection Plan for the School Water Access Evaluation: Who Supplies Each Record, When, Under What Agreement, Scheduled Against the School Calendar Before the Collisions Happen

Purpose

The measurement plan names six primary indicators and their sources. This plan decides who supplies each record, under what agreement, in which month, and what could go wrong in getting it. Data collection in schools collides with fixed calendars: testing weeks, holidays, summer closure and the start-of-year rush when principals have no time for evaluators. A survey scheduled during state testing will not happen; a sales extract requested after a district changes its point-of-sale vendor may never arrive. The plan works those collisions out in advance and assigns a named role to every task, following the evaluation framework's emphasis on feasibility as a standard for sound evaluation (Centers for Disease Control and Prevention [CDC], 1999).

What this page is doingOpening with the specific ways school calendars break data collection shows the plan is built around real constraints.
3

Sources, Suppliers and Agreements

Five suppliers provide the data. District food service directors in the 70 program and waiting-list schools' districts supply cafeteria sales extracts. The program's field staff supply maintenance logs and meter readings. Principals grant access for site visits and in-class surveys. Families receive notice of the student recall survey and may opt their child out. The state health department supplies results from its student health survey.

Two agreements are needed before anything else. The first is a data sharing agreement with each district covering sales records, which contain no student identifiers but are district property. The second covers the student recall survey: it collects no names, but it involves students in class time, so it requires district research approval, notice to families with an opt-out, and review by the evaluator's institutional review board. Because the recall records no names or student numbers, it does not create education records under federal student privacy law (Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g), but districts may still apply their own review rules.

The Schedule

Table 1

Data Collection Schedule by Month, Evaluation Year

MonthTaskSupplierResponsible roleCollision to avoid |
May (prior year)Baseline recall survey in a sample of 12 program and 12 waiting-list schoolsStudents, with family opt-out notice sent in AprilEvaluation field coordinatorState testing in late April and early May |
JunePull two prior years of sales data for all 70 schoolsDistrict food serviceData analystFiscal year close in late June |
AugustConfirm installation dates; site visit checklist finalizedProgram managerLead evaluatorTeacher return week |
SeptemberFirst site visits to program schools; station distance measuredPrincipals and facilitiesField coordinatorFirst two weeks of school |
Monthly, October to MaySales extracts; maintenance logs; meter readingsFood service; program field staffData analystWinter break and spring break gaps |
JanuaryMidyear check with waiting-list principals on any water changesPrincipalsField coordinatorSemester exams |
FebruarySecond site visits; trust-in-water surveyStudents and principalsField coordinatorMidwinter break |
MayFollow-up recall survey in the same 24 schoolsStudentsField coordinatorState testing window |
JulyProgram budget and cost records for the efficiency questionProgram officeData analystNone |

Note. Months reflect a typical school year in the composite state; testing windows will be confirmed with each district by August.

What this page is doingA schedule column naming the collision for each task turns the calendar into a risk register.
4

Roles and Training

Three roles carry most of the work. The field coordinator schedules site visits and surveys, administers the recall in classrooms using a fixed script and checks forms for completeness before leaving each school. The data analyst requests and maps sales extracts, maintains the master dataset and logs every data problem with its date and resolution. The lead evaluator approves any change to the schedule or procedures and keeps the record that the analysis plan will rely on. Before the baseline survey, the field coordinator and two assistants will practice the recall script together and administer it in a pilot classroom outside the sample, comparing their recorded answers to make sure they ask follow-up questions the same way. Station distances at site visits will be measured with the same tape and recorded from the same point at each cafeteria entrance.

Data Handling

Sales extracts will arrive in different formats from different districts, since districts use different point-of-sale systems. Each district's beverage item codes will be mapped once, at the start, to a common list of sugary drinks, plain water, milk and flavored milk, and the mapping will be reviewed with food service staff. Any mid-year change in a district's system will be logged, since a change in coding is an instrumentation threat to the comparison. Survey forms will be scanned, entered twice and stored without identifiers. Maintenance logs will be checked monthly against meter activity, so that a station logged as working but showing no use is flagged for a visit.

Respecting the People Who Supply Data

The Program Evaluation Standards include propriety, which concerns the rights and burdens of people involved in an evaluation (Yarbrough et al., 2011). Three choices follow. The recall survey takes under ten minutes and replaces no instructional time scheduled for testing preparation. Families receive notice in the languages spoken in each school, with a simple way to opt out. Principals receive a one-page school report after each site visit, so the data they help collect also serve them.

Contingencies

Three problems are likely enough to plan for. If a district cannot provide sales data on time, the analyst will request the missing months in the next extract and the analysis will note the gap; if a district cannot provide any data, its schools will be dropped from the primary comparison and the loss reported. If a survey school withdraws, a replacement will be drawn from the same group and income stratum before the baseline survey, but not after, since a replacement without baseline data would weaken the comparison. If installation in a program school is delayed past October, that school will be analyzed separately, because it would receive less than a full year of the program.

What This Plan Delivers

By July of the evaluation year, the plan delivers three years of sales data for 70 schools, two rounds of recall data in 24 schools, monthly implementation data, site visit findings and cost records, each collected under a documented agreement and on a schedule built around the school calendar.

References

Centers for Disease Control and Prevention. (1999). Framework for program evaluation in public health. MMWR Recommendations and Reports, 48(RR-11), 1-40.

Family Educational Rights and Privacy Act, 20 U.S.C. § 1232g (2024).

Yarbrough, D. B., Shulha, L. M., Hopson, R. K., & Caruthers, F. A. (2011). The program evaluation standards: A guide for evaluators and evaluation users (3rd ed.). SAGE.

PHLT 8044 Week 8 instructions, in plain terms

The eighth assignment usually asks for a data collection plan that turns the measurement plan into a schedule of tasks. Faculty expect each data source tied to a supplier, an agreement, a month and a responsible role, with attention to the constraints of the setting, which in schools means testing windows, holidays and the start of the year. Agreements and ethical review should be identified before collection begins. The plan should describe how data will be handled, cleaned and stored, how people supplying data will be respected and what will happen if data arrive late or not at all. Training for anyone administering instruments is often expected. A schedule table plus discussion of roles, handling and contingencies is common, typically three to four pages.

Inside the PHLT 8044 Week 8 example

A purpose section explains how school calendars break data collection. A section names five suppliers and two required agreements, a district data sharing agreement and the approvals for the recall survey, and notes how federal student privacy law applies. A schedule table lists each month's task, supplier, responsible role and collision to avoid. A roles and training section assigns work to a field coordinator, analyst and lead evaluator and describes script practice in a pilot classroom. A data handling section covers mapping item codes across point-of-sale systems and checking logs against meters. A section describes respecting families, students and principals, and contingencies cover late district data, school withdrawal and delayed installation, before a summary of what the plan delivers by July.

Reading the PHLT 8044 Week 8 rubric

The strongest plans read as instructions a field team could carry out, with obstacles foreseen. A schedule without suppliers, agreements or responsible roles, or one that ignores the school calendar, loses credit. The collision column distinguishes strong plans, since it shows specific risks were considered. Agreements and ethical review should be addressed before data collection, and privacy obligations should be described accurately. Credit goes to data handling procedures that protect comparability, such as mapping item codes and logging system changes, and to training that standardizes survey administration. Contingency plans that preserve the design's integrity, for example not replacing schools after baseline, show methodological judgment. Respect for participants' time and rights connects the plan to evaluation standards and earns credit.

PHLT 8044 Week 8 help: mistakes that cost marks

Data collection plans fail when they ignore the setting's calendar. Map every task to a month, a supplier, a responsible person and the conflict it must avoid. Secure agreements and approvals first. Train anyone who administers instruments. Decide how you will handle data that arrive in different formats. Plan for late data and withdrawals in ways that protect your design. Keep the burden on participants small. Share the schedule with each supplier early so conflicts surface while dates can still move. Evaluations in clinics or workplaces need the same calendar-first planning.

Get a PHLT 8044 Week 8 example written to your instructions

Send the Week 8 prompt and rubric together with your measurement plan, and each indicator is given a collection route and a date. Delivery runs 24-48h, and there is no fee the first time. District calendars and agreements from your setting are not reproduced; the sample shows where they slot in.

More PHLT 8044 papers and PhD in Public Health samples

PHLT 8044 Week 8 questions, answered

Where can I find a free PHLT 8044 Week 8 sample paper?

The full Week 8 data collection plan is reproduced on this page, scheduling every task in a school water evaluation against the school calendar with suppliers, roles and collisions.

Does an anonymous student survey need family notice?

Districts usually require notice and an opt-out for in-class surveys even when no names are collected, and evaluator review boards expect it, so the plan sends notice in families' languages.

Why not replace a school that withdraws after baseline?

A replacement without baseline data would weaken the before-and-after comparison, so replacements are drawn only before the baseline survey.

Why map cafeteria item codes at the start?

Districts use different sales systems with different item codes, and a common list of sugary drinks, water and milk keeps purchases comparable across schools and over time.

What if a district cannot provide sales data at all?

Its schools are dropped from the primary comparison and the loss is reported, rather than filled with estimates that could bias the result.