| Course | ADM 630 Introduction to the Nonprofit and NGO Sector |
|---|---|
| Topic | Topic 7 |
| Paper type | Logic model and evaluation |
| Length | About 1,000 words, 2 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | Individual classes |
| Updated | October 2026 |
Free sample paper for ADM 630 Topic 7
The Arrow From Matches to Graduation: Building a Mentoring Program's Logic Model and Testing the Assumption Six Years of Data Never Checked
[Author Name]
College of Humanities and Social Sciences, Grand Canyon University
ADM-630: Introduction to the Nonprofit and NGO Sector
Topic 7 Logic Model and Evaluation
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
The Arrow From Matches to Graduation: Building a Mentoring Program's Logic Model and Testing the Assumption Six Years of Data Never Checked
The Program and the Change It Exists to Produce
A composite youth mentoring nonprofit matches volunteer adult mentors with students in grades six through eight at four middle schools in a mid-sized city, chosen because their students graduate from high school at rates well below the district average. Mentors meet their students weekly at school and join monthly group outings. The program's materials state its purpose plainly: to raise high school graduation among the young people it serves. A logic model sets out how that is supposed to happen, from resources to results (W. K. Kellogg Foundation, 2004).
Inputs, Activities and Outputs
The inputs are a budget of about 900,000 dollars a year, six staff, about 120 trained volunteer mentors and space provided by the schools. The activities are recruiting and screening mentors, matching them with students, supporting matches through monthly check-ins with each mentor, and running group outings. The outputs, which the program already collects and reports, are about 140 active matches a year, about 3,200 hours of mentoring and an average match length of about ten months. For six years these figures have been reported faithfully to funders.
Table 1
The Mentoring Program's Logic Model and Its Evidence
| Component | What the program records | Status of evidence |
|---|---|---|
| Inputs | Budget, staff, mentors, school space | Recorded |
| Activities | Recruitment, matching, support, outings | Recorded |
| Outputs | About 140 matches, 3,200 hours, 10-month average length | Recorded yearly |
| Short-term outcome | Engagement in school: attendance, course passing | Not measured |
| Long-term outcome | High school graduation | Not measured |
The Outcome Claimed and the Arrow to It
The outcome the program claims is higher graduation. Between the outputs and that outcome sits an arrow, and the arrow carries the program's theory: that a sustained relationship with a caring adult raises a student's engagement in school, measured by attendance and course passing in middle school, and that greater engagement makes graduation more likely four or five years later. Logic models that stop at outputs leave this arrow unexamined, and this program's has never been tested.
The Assumption the Arrow Carries
The most important assumption is that matches last long enough to matter. Research suggests duration is critical. Grossman and Rhodes (2002) found that youth in mentoring relationships lasting a year or more showed improvements, while those whose relationships ended within a few months showed declines on some measures compared with youth who were not matched. A review of many mentoring programs found modest positive effects on average, varying with how programs were run (DuBois et al., 2011). The program's average match lasts about ten months, and its records show that about a third of matches end within six months, usually because a mentor's availability changes. If short matches do harm, the program's average could conceal a group of students left worse off. In six years the program has produced no evidence on whether its matches change attendance, course passing or graduation at all.
An Evaluation the Program Can Afford
A randomized trial is beyond the program's means. A feasible design uses data the program can obtain. The program has a waiting list every year, because it receives more referrals than it has mentors, and students are matched in the order mentors become available. Under a data-sharing agreement with the district, the program could compare attendance and course passing for matched students with those still waiting, over the same school year, at a cost of about 15,000 dollars for an analyst's time. It should also compare students whose matches lasted a year or more with those whose matches ended early. The design has limits: waitlisted students may differ from matched ones in ways the comparison cannot fully correct, and graduation would take years to observe. But it would produce the first evidence on the arrow.
Acting on the Assumption Now
The program need not wait for the evaluation to act on what the research already suggests. If duration matters, then reducing early endings is the most promising change. Mentors could be asked to commit to a full school year before matching, with a frank conversation about schedules at screening. Staff check-ins could be weekly rather than monthly in the first three months, when most early endings occur. And when a match must end, a planned closing meeting, rather than a mentor simply stopping, may limit harm to the student. Each change can be tracked in the program's existing records through the share of matches lasting a year.
Choosing the Measures
The evaluation should measure what the arrow claims in the order it claims it. Attendance and course passing are available every term and respond within a year, so they test the short-term link. Graduation should be tracked for each cohort as it reaches twelfth grade, which requires keeping student identifiers under the data-sharing agreement for several years. Survey measures of students' sense of connection to school could be added cheaply, since mentors already meet students weekly, but should be collected by staff rather than mentors to reduce bias.
What the Program Should Claim Until Then
Until outcome data exist, the program should describe what it can show: the number of matches, their length and the share lasting a year or more. It should present graduation as the purpose the program is designed to serve, not as a result it has demonstrated. Funders increasingly ask for outcome evidence, and a program that has claimed graduation effects it never measured faces an awkward question the first time one asks.
Conclusion
The mentoring program's logic model is complete up to its outputs, which are carefully recorded, and silent after them. The arrow from matches to graduation depends on matches lasting long enough, an assumption the research supports as important and the program's own records call into question. A waitlist comparison using district data would test it at a cost the program can afford. Until then, the honest claim is about matches made and sustained, with graduation stated as the aim.
References
DuBois, D. L., Portillo, N., Rhodes, J. E., Silverthorn, N., & Valentine, J. C. (2011). How effective are mentoring programs for youth? A systematic assessment of the evidence. Psychological Science in the Public Interest, 12(2), 57-91. https://doi.org/10.1177/1529100611414806
Grossman, J. B., & Rhodes, J. E. (2002). The test of time: Predictors and effects of duration in youth mentoring relationships. American Journal of Community Psychology, 30(2), 199-219. https://doi.org/10.1023/A:1014680827552
W. K. Kellogg Foundation. (2004). Logic model development guide. W. K. Kellogg Foundation.
The ADM-630 Topic 7 assignment instructions
Topic 7 of ADM-630 asks students to build a logic model and plan an evaluation. Strong models set out inputs, activities and outputs with the figures the program already collects, state the outcome claimed and the arrow connecting outputs to it, and name the assumption that arrow carries. Students should test that assumption against research and the program's own records, propose an evaluation the organization could actually resource, choose measures in the order the model claims and say what the program should claim until evidence exists. Changes suggested by existing research can begin before the evaluation reports. Short-term outcomes should be measured before long-term ones are claimed.
How the ADM-630 Topic 7 example is put together
The finished example builds a model and then interrogates its weakest joint. Inputs, activities and outputs are straightforward and countable: hours delivered, people served, sessions run. The outcome is a change in participants' circumstances, and the arrow between output and outcome carries an assumption, which is that attending the sessions produces the change. Six years of operation have produced output data and no outcome data at all, so the assumption remains untested. The example is direct that this is the normal situation rather than a scandal, and proposes the cheapest available test, which uses a follow up the program already conducts and currently discards. Each element of the model names the data the program already collects for it, or states that none exists.
ADM 630 Topic 7 rubric: what Excellent looks like
Faculty reward the arrow to outcomes examined. An Excellent paper tables the model with the status of evidence at each stage, following the Kellogg guide. Credit goes to naming match duration as the key assumption, with Grossman and Rhodes on duration and DuBois and colleagues on average effects. The rubric values an affordable waitlist comparison and measures chosen in the model's order. Strong papers act on the assumption now by reducing early match endings. Top marks go to an honest statement of what the program can currently claim. Faculty also value measures collected by staff rather than mentors.
Common ADM 630 Topic 7 mistakes, and how to avoid them
Logic models that stop at outputs are the standard submission, and the arrow to outcomes goes unexamined. A second failure is claiming an outcome the program has never measured, which is common and becomes a problem the first time a funder asks. Marks also go for proposing an evaluation the organization could not resource, since an unaffordable design produces no data at all. Models with no assumptions named present every link as equally solid. Papers treating the absence of outcome data as negligence misread the incentives that produced it. Evaluations proposed with no use of existing contact points ignore the cheapest data available. Models built with no figures against any element cannot show where the evidence stops.
Get an ADM-630 Topic 7 example written to your instructions
Send the ADM-630 Topic 7 instructions and the rubric your classroom posts, with the program your section assigned. We write a custom example to those criteria, building the model, naming the untested assumption and proposing a test the organization could actually run, in 24 to 48 hours. The first is free.
More ADM 630 papers and Individual classes samples
- ADM 630 Topic 1: Sector Scope Analysis
- ADM 630 Topic 2: Formation and Exempt Status
- ADM 630 Topic 3: Mission Statement Analysis
- ADM 630 Topic 4: Board and Executive Analysis
- ADM 630 Topic 5: Revenue Mix Analysis
- ADM 630 Topic 6: Capacity and Staffing Analysis
- ADM 630 Topic 8: NGO Accountability Analysis
- ACC 614 Topic 7: Research Memo to File
ADM 630 Topic 7 questions, answered
Why do logic models stop at outputs?
Because outputs are what funders require and what programs therefore collect. Hours delivered and people served are countable, reportable and available. Outcomes require follow up nobody funds, so the arrow between the two carries an assumption that goes untested for years. Naming that assumption is the most useful thing this topic asks for.
Is it bad that outcomes were never measured?
It is ordinary, and treating it as a scandal misreads the situation. Every incentive in the funding relationship rewards output reporting and none requires outcome evidence. The productive response is not criticism but the cheapest available test, which is usually attached to a contact the program already makes.
What makes an evaluation affordable?
Using something that already happens. If the program calls participants three months afterward and records nothing, that call is a free data collection point waiting for two questions. Designs requiring new surveys, new staff or new systems compete with delivery and lose. The cheapest workable test produces data; the ideal one produces a proposal.
Where can I find a free ADM 630 Topic 7 sample paper?
The logic model paper is shown here complete: the program, inputs to outputs, the claimed outcome, the assumption, acting now, choosing measures, an affordable evaluation, what to claim and the conclusion. Describe your program and a logic model with an evaluation plan follows free.
Why does match length matter in ADM 630 Topic 7?
Research suggests mentoring relationships lasting a year or more help, while very short ones may harm. A third of this program's matches end within six months.