Attendance, Outcomes, and a Funder Deadline

The program can report the 64% as a descriptive finding: among students for whom teachers reported a reading level, 64% improved one level. It cannot claim that the program caused the improvement or that the program is proven effective. There was no pre-test, no comparison group, and no standardized measure; teacher reports may be inconsistent across schools. Attendance was low, with only 58% meeting the 120-day threshold, so many students did not receive the intended dose. Missing data for 30 students weakens the denominator and may bias the result if those students differed systematically. The program also cannot call the figure proof of success to the foundation without overstating the evidence. A defensible report would describe the finding, state limitations, explain attendance and staffing challenges, and present it as preliminary evidence to be tested with a stronger design. The board should resist the director's framing because overclaiming risks credibility and renewal more than an honest improvement story.

In the next six months, the program should establish a baseline and improve data quality rather than launch a new component. First, define the outcome clearly: reading comprehension measured by a consistent, validated or locally standardized assessment at pre and post. Second, track attendance daily by student and site, with a target and early-warning follow-up for students missing sessions. Third, if feasible, create a comparison group of similar students who do not attend, or at minimum compare participants with different attendance doses. Fourth, train staff on consistent data collection and assign one person to manage missing data. Fifth, collect qualitative data from teachers and families to explain results. The robotics idea should be deferred or piloted separately; adding it now would dilute the reading focus and make attribution harder. The board should approve an evaluation plan with a timeline: baseline in the first month, mid-year attendance review, post-test at the end, and a report that separates findings from interpretation. This plan is credible because it fits the program's capacity and addresses the specific weaknesses in the current data.

The director should communicate early, not wait for the year-end report. A short mid-year update should state the attendance challenge, the missing data issue, and the corrective actions already underway. The report should distinguish outputs (students served, attendance) from outcomes (reading improvement) and explicitly note that the 64% figure is preliminary and not causal. The foundation is more likely to respect a credible improvement plan than a sudden claim of proof. The director should ask whether the foundation will accept a revised target or a learning report if attendance remains below 75%, and should propose a realistic evaluation design for the remaining months. The board should receive the same facts and approve the message. If the board wants to add robotics, it should treat that as a separate pilot with its own attendance and outcome measures, not as a substitute for reading results. The reasoning is that renewal depends on trust and learning, not on presenting weak data as strong evidence.