Keep reading.
Drop your email to finish the piece. One-time — we'll remember you on this device.
© 2026 Swiftscore, Inc.
Swiftscore is teacher-evaluation software built around how principals actually spend their week. This blog is where we publish what we're learning from the districts using it.
CTO of Swiftscore. Writes about what we're learning from districts on the ground.
Drop your email to finish the piece. One-time — we'll remember you on this device.
Simplifies evaluation cycles and supports equitable teacher growth across multiple campuses.
Swiftscore is teacher-evaluation software built around how principals actually spend their week. This blog is where we publish what we are learning from the districts using it: what worked, what didn't, and what the numbers looked like on the other side. First case study lands later this month.
Two things, and only two things.
One. Stories from districts using Swiftscore. Named principals, named asst supts, named outcomes. How many hours came back into the week. How feedback to teachers changed. What the rollout actually looked like in month one versus month four. We will not publish anything a district leader has not read and approved.
Two. Short notes on the craft of instructional leadership when AI is in the room. Not "the future of education" essays. Specific operating questions: what to do with an observation note an AI helped you draft, how to compare a Marshall rubric score to a Danielson score without flattening either, how a coaching conversation changes when both people have the transcript.
If a post does not fit one of those two buckets, it does not go here. Broader sector commentary lives on our Medium publication. This site is for proof and craft.
For most of the last year we ran Swiftscore quietly. Small districts, founder-led sales, no marketing site to speak of beyond the product page. That was the right move at the time. Our job was to find out whether the product actually saved principals time and improved feedback to teachers, not to write about whether it did.
We have enough data now to talk about it. We also have enough live customers willing to talk on the record about what changed. Withholding that from the next round of districts evaluating Swiftscore is not modesty. It is friction we can remove.
Posts on our blog are written by people at Swiftscore who worked directly on the engagement they are writing about. If a case study covers a TIA rollout in a 4A Texas district, the post is written or co-written by the person who sat on the calls and read the observations. We will name them at the top of every piece.
For case studies, the district leader gets co-author credit if they want it. Several have asked for it. We think that is the right default.
A few things, on purpose.
Roughly two posts a month. One case study, one craft note. We would rather publish less and have every post defensible than publish more and dilute the bar.
We will iterate on that as we go. If a particular post format gets long thoughtful replies from the people we built Swiftscore for, we will do more of it. If it gets silence from them and applause from no one in particular, we will stop.
Swiftscore exists because teacher evaluation in most US districts is a paperwork job that crowds out the part principals went into the work to do. We are not the first to notice that. We are trying to be one of the few that builds for the operating reality, not the policy abstraction.
This blog is one way we plan to show our work. The other is Medium, where we will publish broader pieces about the field. Different audiences, different rules. Here on swiftscore.org, it is proof and craft. Over there, it is sector commentary.
If you are a principal or an asst supt thinking about whether this is worth your time: subscribe, read the first case study when it goes up, and tell us where the post falls short. We will fix it and write back.
Software that helps principals run teacher observations, draft feedback, and surface coaching patterns across a building or district. Built for principals first, district admin second.
People at Swiftscore who worked directly on the engagement being written about. Case study posts are co-authored or reviewed by the district leader involved before publication.
It is a proof blog. Posts cover real districts and real numbers. There is no demo ask in the body. If you want to talk with us, the contact link is at the bottom of each post.
Swiftscore's blog is for case studies and craft notes specific to Swiftscore customers. Our Medium publication is for broader sector commentary on teacher evaluation, instructional leadership, and AI in K-12.