Login counts are the easiest number to put in a board packet and the easiest number for a board member to dismiss. A slide that says “4,812 platform logins this year” tells the board that teachers touched a tool. It does not tell them whether instruction changed, whether the $70,000 coaching position produced anything a principal would notice, or whether the board should continue, adjust, or expand the role. When a board member asks “so what did that buy us?” a login count has no answer.
For a district of 1,000 to 10,000 students with a technology team of five people, the fix is not a bigger data system. It is a smaller, repeatable evidence set built around what the coach is actually supposed to do, presented in a structure the board can use to make a decision. This article lays out that structure, the evidence behind it, and the tradeoffs of each choice.
Start with the role the board already approved
The ISTE Standards for Coaches describe the role as capacity building and implementation support: “Because coaches have a unique role as capacity builders and implementation experts, these standards guide coaches in ensuring that learning with technology is high impact, sustainable, scalable and equitable for all” (ISTE Standards: For Coaches). That sentence is a gift for a board report, because it names the outcome the board should be evaluating: capacity, sustainability, scale, and equity — not tool contact.
The standards also give the coach a built-in evaluation obligation. Standard 4.5 says coaches “plan, provide and evaluate the impact of professional learning,” and 4.5.c says coaches “evaluate the impact of professional learning and continually make improvements to meet the schoolwide vision” (ISTE). Standard 4.6 addresses using qualitative and quantitative data. In other words, the coach’s own professional framework already requires the kind of evidence a board should see. The report is not an extra burden invented by the technology director; it is the coach’s job, documented.
Frame the report as a program evaluation, not a scoreboard
ISTE’s own guidance on coach evaluation defines program evaluation as “the systematic application of methods to assess the design, implementation and outcomes of a program,” and says its purpose “is to uncover whether the program is achieving its desired results” (Know the ISTE Standards for Coaches: PD and program evaluation). That same guidance lists what evaluation information is for: designing future professional development, managing resources, improving effectiveness, providing evidence of what is working, documenting accomplishments, and supporting funding decisions.
That list maps almost exactly onto what a school board does. A board decides whether to continue a position, adjust its scope, or expand it. A report framed as a program evaluation gives them the material for that decision. A report framed as a usage dashboard gives them a number to argue about.
The tradeoff is real: a program evaluation takes planning time in the fall, before the year gets busy. If the coach waits until April to think about evidence, the only data left will be whatever the platforms logged. The cost of doing this well is roughly two planning sessions in August and September and a standing 30-minute monthly review. The cost of doing it poorly is a board packet that cannot defend the position.
Use a cadence the school calendar can survive
The ISTE guidance describes a workable cycle: a coach conducts short lesson observations with all teachers twice a year and administers a survey twice a year, then uses that data to prepare professional development and evaluate whether it met teachers’ needs (ISTE). The same guidance notes that the typical one-off training approach does not work.
For a five-person team, the calendar version looks like this:
- Late August / early September: short needs-assessment survey (10 minutes, during a already-scheduled staff meeting, not a new one).
- October–November: first round of brief classroom visits or teacher self-reports, focused on two or three instructional practices the district already named in its technology plan.
- January: mid-year check — what professional learning was delivered, what teachers asked for next, what the coach observed.
- March–April: second survey and second observation round, using the same questions and the same look-fors so the comparison is honest.
- May: board report built from the fall-to-spring comparison.
The value is in the cadence and the stated comparison, not the volume. Two data points per teacher per year is enough to say “this moved” or “this did not move.” It is not enough to claim student achievement effects, and the report should say so plainly.
Build the evidence set a five-person team can actually produce
A defensible evidence set for a small district has four parts. The following is a hypothetical structure, not a record of any district’s results; each district must supply its own real counts.
- Activities delivered. Number of professional learning sessions, number of teachers attending, hours of coaching conversations, number of model lessons or co-taught lessons. These are counts of work, and they are legitimate — they just are not the whole story.
- Needs assessment results. What teachers said they needed in the fall, and how the professional learning plan responded. This is the design layer of the program evaluation.
- Practice indicators. What the coach observed in the fall versus the spring, using a short, fixed look-for list tied to the district’s own goals. Examples: frequency of a specific instructional routine, use of a district-approved accessibility feature, or a change in how teachers assign and give feedback on digital work. The look-fors must be chosen before the year starts, or the comparison is not credible.
- Teacher self-report. A short spring survey asking whether the coaching support changed a specific practice, and what would have helped more. Self-report is weaker evidence than observation, but it is honest about its limits and it gives the board the teacher voice that board members often ask for.
The tradeoff: observation data requires the coach to spend time out of classrooms’ daily support role, and some teachers will read observation as evaluation. The fix is to state in writing, before the first visit, that the visits are for program evaluation and not personnel evaluation, and to keep the notes aggregated in the board report. If the district cannot commit to that boundary, drop the observation layer and rely on surveys plus activity counts — a smaller report, but an honest one.
Separate what you did, what changed, and what you don’t know
The most common failure in a coach’s board report is overclaiming. A report that implies coaching raised reading scores will be challenged by any board member who has sat through a data presentation, and the challenge will be correct. The ISTE program-evaluation guidance is careful on this point: it describes evaluating impact on instructional practice and student learning as the standard, but the practical examples it gives focus on whether training met teachers’ needs and what future training is needed (ISTE).
A three-layer structure keeps the report credible:
- Layer 1 — Activities: what the coach did, with counts and dates.
- Layer 2 — Practice indicators: what changed in classrooms, with the fall-to-spring comparison and the method stated.
- Layer 3 — Not yet established: an explicit statement that the district has not linked coaching to student outcome data, and what it would take to try. This layer protects the report. It tells the board the technology team knows the difference between evidence of practice change and evidence of student impact.
This structure also gives the board a decision tool. If Layer 1 is strong and Layer 2 is flat, the recommendation is to adjust the coaching model, not to cut the position. If Layer 2 shows movement in the practices the district prioritized, the recommendation is to continue and scale. The report should end with one of those recommendations, stated in one sentence, with its cost.
Keep student data out of the board packet
Coaching evidence can drift into student data quickly — a coach reviewing assessment dashboards with a teacher, for example. Board reports should not include student-level data, and the coach should not be collecting it for reporting purposes. The U.S. Department of Education’s Student Privacy Policy Office maintains guidance on federal student privacy law at studentprivacy.ed.gov; district counsel and the district’s data governance policy should be consulted before any coaching report includes anything beyond aggregate teacher-level information. The practical rule for a small team: if a data element would identify a student, it does not belong in a public board packet.
A repeatable template for the spring
The template below is a structure, not a mandate. It is designed to be filled in by the coach and reviewed by the technology director in under two hours, using data the team already collected during the year.
- Purpose statement (2 sentences): what the board is being asked to decide — continue, adjust, or expand the coaching role.
- Role definition (1 paragraph): the coach’s role as capacity builder, citing the district’s own job description and the ISTE Coaches standards.
- Activities (table): sessions, participants, hours, dates.
- Needs assessment (short paragraph): what teachers asked for in the fall and how the plan responded.
- Practice indicators (table): fall versus spring, method stated, look-fors named.
- Teacher self-report (short paragraph): what teachers said helped and what did not.
- What is not yet known (short paragraph): the student-outcome link, stated honestly.
- Recommendation and cost (2 sentences): the decision requested and the dollar or staffing implication.
The cost of this template is the fall planning time described earlier. The benefit is that the spring report takes hours, not weeks, and that the board sees a program with a stated method rather than a platform with a login count.
Frequently asked questions
What if the board specifically asks for login counts?
Give them, in an appendix, labeled as usage data. Then explain in one sentence what usage data can and cannot show: it shows contact with a tool, not change in practice. Pairing the appendix with the practice indicators keeps the board’s question answered without letting the number become the report.
What if the coach does not have time to do observations twice a year?
Then do one round, or use teacher self-report only, and say so in the report. A smaller evidence set with a stated limitation is more defensible than a large set that was never collected. The ISTE guidance’s two-round cycle is a model, not a minimum requirement for every district.
Does this report format satisfy state or federal reporting requirements?
Not necessarily. State and federal reporting requirements vary, and this template is designed for local board communication, not compliance reporting. Check with district leadership on any separate reporting obligations before reusing the format.
Where does the ISTE framework fit if the district uses a different coaching model?
The framework is useful because it names the evaluation obligation, not because it is the only model. A district using a different coaching framework can still use the three-layer structure — activities, practice indicators, not yet known — and cite its own framework for the role definition.