This page holds a finished MPH-507 Week 7 data collection plan in submission form, with the reasoning behind each choice marked. Searches like "mph 507 week 7 assignment example", "mph507 week 7 sample" and "mph-507 week 7 example" land here.
What a finished MPH-507 Week 7 data collection plan looks like
The plan is operational rather than aspirational. Each measure from the evaluation design appears with the instrument that produces it, who administers it, when in the program cycle, from whom, and where the result is stored. The realism test runs through the whole document: a plan asking front-line staff to complete a lengthy instrument at every session has committed somebody to hours nobody costed. Data quality appears as procedures rather than intentions, covering training, checking and what happens to missing responses. Consent, privacy and storage are addressed as they apply to this program, and the plan says who will analyze the data, which is often the question nobody has answered.
How a MPH-507 Week 7 example is structured
These plans are usually tabular with a narrative attached, so build to whichever template your section supplies. Each measure is entered with its source in the evaluation design, so nothing is collected that no question needs. The instrument follows, named and, where it is an existing validated one, cited. Administration comes next: by whom, to whom, at what point, in what mode and how long it takes. Frequency and sample follow. Storage and access are stated. Data quality procedures come after, covering training, verification and missing data rules. Consent and privacy are addressed as this program would handle them. The plan closes on who holds responsibility for the analysis, and on the burden the whole scheme places on staff and on participants.
Every measure traced to a question
Each item entered with the evaluation question it serves, so nothing is collected because it seemed interesting at the time.
Instruments named and cited
Existing validated tools referenced rather than described, since building a new instrument is work the plan would have to account for.
Who administers, and when
The person, the point in the cycle and the mode, because an instrument with no administrator attached will not be administered.
Quality as procedures
Training, verification and a rule for missing responses, rather than an intention to maintain data quality throughout.
Consent, privacy and storage
How this program would handle each, sized to a program evaluation rather than to a research study unless the section says otherwise.
Burden counted
What the whole scheme costs staff and participants in time, which is the check that stops a plan committing to uncollectable data.
Where marks go in MPH-507 Week 7
The predictable loss is the plan nobody could execute: several instruments at every contact, administered by staff with no time allocated and analyzed by nobody named. The second is data collected for no question at all, where the plan gathers demographics and satisfaction items that not one evaluation question ever asked for. Beyond those: instruments invented from scratch where validated ones already exist, no timing given so the measurement points are anybody's guess, missing data unaddressed, storage and access left unstated, consent handled as though this were a research study when it is a program evaluation or the other way round, and no analysis responsibility assigned to anybody at all.
Get a MPH-507 Week 7 example written to your instructions
Send the Week 7 instructions with the template your section uses and your evaluation design, and a custom example is built into that format and returned inside 24 to 48 hours. The first one is free. Any real collection from participants stays yours to arrange.
MPH-507 Week 7 questions, answered
Do I need ethical approval for a program evaluation?
It depends on whether the activity is evaluation or research, which is a determination your organization makes rather than you. Program evaluation for internal improvement is often treated differently from research intended for publication. Say which yours is and what determination you would seek, since assignments frequently test whether you know the distinction exists.
Should I build my own survey?
Rarely, if a validated instrument covers what you need. Existing tools have known properties, comparability with other programs and no development cost. Where nothing fits, say so and describe how you would develop and pilot one, since a plan that quietly assumes a new instrument will appear has skipped substantial work.
How do I know if the burden is too high?
Add up the minutes. Multiply the instrument length by the number of contacts and the number of participants, and then ask who has that time. Plans fail on this more often than on design, and a document that counts the burden and then trims the collection reads as far more competent than one that lists everything worth knowing.