MPH-507 Week 7 asks whether the program was delivered as designed, which is a separate question from whether it worked. Process evaluation measures reach, dose delivered, dose received, fidelity and context, and without it a null result is uninterpretable: you cannot tell whether the idea was wrong or the delivery was. Written work here is graded on whether each construct has an indicator, a data source and a collection point rather than a promise to monitor. Your section may print this as MPH 507 or MPH507; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
What process data lets you conclude
A quality audit of a program in its third month is the scene this stage prepares you for. The auditor pulls the session records and finds that eight sessions were scheduled and five ran. The attendance sheets show a median of four participants against a design of twelve. The facilitator checklists show that two of the six core components were skipped in most sessions because the room was booked for only an hour. And the referral log shows that ninety percent of enrollments came from one clinic, meaning the intended population was reached in one neighborhood only. None of that tells you whether the program works. All of it tells you why the outcome data are about to look disappointing, and none of it would exist if somebody had not designed the collection in advance.
The constructs are distinct and the vocabulary matters. Reach is the proportion of the intended population that participated, which requires a denominator and is the construct most often reported as a raw count instead. Dose delivered is how much of the program was actually provided. Dose received is how much participants actually took in or used, which is different and usually lower. Fidelity is whether the components were delivered as designed. Context covers what else was happening that could affect delivery or outcomes, from a staffing change to a competing initiative to a policy shift.
The second layer is what process data are for. They serve three purposes and a strong section says which one each indicator serves. They allow mid-course correction, which requires collection frequent enough to act on. They allow interpretation of the outcome results, which requires the data to exist before the outcome analysis. And they allow replication, because a program described only by its design cannot be repeated, whereas a program described by what was actually delivered can.
Deliverables at this stage are usually a process evaluation plan, often with an indicator table, sometimes a monitoring schedule. Canvas posts do not reopen after submission, so verify any indicator definition before posting it in a thread where classmates will test whether it is measurable.
A method for building monitoring that gets used
Six moves that turn intentions into a measurement system.
-
Take the indicator set from the logic model's activity and output columns
Process indicators belong to what the program does, not to what changes in people. Working from the model rather than from imagination keeps the set complete and stops outcome measures leaking into the process section.
-
Define reach with an explicit denominator
Participants over the eligible population in your defined area, stated as a proportion. Then break it by segment, because a program that reaches its overall target while missing the segment carrying the burden has a finding to report, not a success.
-
Separate dose delivered from dose received and measure both
Sessions offered against sessions run for delivered; attendance, completion, materials actually used or messages actually seen for received. The gap between the two is where most program effect is lost and it is invisible if only one is collected.
-
Operationalize fidelity as a checklist somebody can complete
List the core components and define what counts as delivered for each. A fidelity measure that requires interpretation will not be completed consistently, and a checklist that takes more than a few minutes at the end of a session will not be completed at all.
-
Attach a source, an owner, a frequency and a threshold to every indicator
Where the number comes from, who records it, how often, and the value at which someone acts. Monitoring with no action threshold produces reports that are filed rather than used, which is the most common fate of process data.
-
Write the response plan for drift before it happens
If reach falls below the threshold in a segment, what changes. If fidelity drops in one site, who retrains. Deciding responses in advance is what makes the system a management tool rather than a record, and it is a scored distinction.
A layout and word budget for a process evaluation plan
Our frame for this deliverable, sized for roughly 1,200 to 1,500 words alongside an indicator table. It is our own outline rather than anything the university issues, and your section's scoring guide outranks it wherever the two disagree. The indicator table is the centrepiece here and will absorb around 280 words of the budget, which should come out of the narrative rather than out of the response-plan section.
| Section | What belongs in it | Word target |
|---|---|---|
| Purpose and questions | The three or four process questions this plan answers, and which decisions each one informs. | 140 to 180 |
| Reach | The definition, the denominator, the segment breakdown, the source and the collection frequency. | 190 to 230 |
| Dose delivered and received | Both measures defined separately, with the records that produce them and who maintains those records. | 210 to 260 |
| Fidelity | The core components, what counts as delivered for each, who completes the check and how it is verified. | 200 to 250 |
| Context monitoring | What else could affect delivery or interpretation, and how those conditions would be documented as they occur. | 160 to 200 |
| Thresholds and response | The action value for each indicator, who is notified, what changes, and how the change is recorded. | 210 to 260 |
Evidence craft for monitoring design
Name the record that produces each number. Attendance sheets, enrollment logs, facilitator checklists, referral records, an existing information system or a short participant survey are all specific answers. Data will be collected is not, and it is the phrase that most reliably marks an evaluation section written without thinking about who does the work.
Cost the collection honestly in staff time. Every indicator consumes somebody's minutes, and monitoring that is too heavy stops happening in month two. Say roughly how long each collection takes and who absorbs it, then defend the set as proportionate. Reviewers with implementation experience read a lean, well-chosen indicator set as more credible than an exhaustive one.
Report process findings with counts and denominators, not just proportions. Eleven of the eighteen scheduled sessions ran is a usable finding. A sixty-one percent delivery rate conceals whether the program was small or large, and this course reads for the base throughout.
Cite implementation frameworks where you use their language. Reach, dose, fidelity and their relatives come from published implementation and evaluation frameworks, and naming the framework you are working within lets a reader check your structure against a standard rather than against your invention. Use its actual categories rather than renaming them.
Five mistakes that cost points in this week's territory
- Attendance counted and nothing else. A single output measure cannot distinguish a program that was never delivered from one that was delivered and did not work.
- Reach reported without a denominator. A number of participants tells you nothing about coverage of the population the program exists for.
- Outcome measures placed in the process section. Knowledge and behavior change belong to outcome evaluation; mixing them makes both sections harder to score and confuses the interpretation.
- Fidelity described without a checklist. A general commitment to monitor quality gives nobody anything to record and produces no data.
- Monitoring with no threshold or response. Data collected and never acted on is administrative burden, and a plan that never says what would trigger a change has not built a management system.
Before you submit
- Process indicators come from the activity and output columns of the model
- Reach is defined as a proportion with a stated denominator and a segment breakdown
- Dose delivered and dose received are measured separately
- Fidelity has a component checklist with a definition of delivered
- Every indicator names a record, an owner and a frequency
- Each indicator carries an action threshold and a stated response
Building the process evaluation?
Send the prompt, the scoring guide and the intervention and logic model you already built. A premium original draft comes back in 24 to 48 hours with every indicator carrying a record, an owner, a frequency and an action threshold, and revisions run until the grade lands.