A Superintendent's Guide to Vetting Curriculum Vendors

A vendor decision that works cleanly for one building doesn't automatically work at the district level. The questions change once you're thinking about consistency across campuses, equity of access, and a procurement process that has to hold up to scrutiny beyond your own office. This is a vetting guide written for that level, not a repackaged single-school checklist.

What Changes at the District Level

Three things shift once a decision moves from one principal's building to district-wide:

Multi-campus consistency. A resource that one school adopts informally creates uneven access if it doesn't roll out the same way everywhere. At the district level, the question isn't just "is this good," it's "can every campus actually get and use this the same way."

Equity across schools. Differences in staff size, budget flexibility, or IT capacity between campuses can turn an apparently simple decision into an uneven rollout, where some schools get full access quickly and others lag for reasons that have nothing to do with instructional need.

Procurement policy. District-level purchases typically face more formal scrutiny, board visibility, and documentation requirements than a single building's discretionary spend. That changes what "vetted" needs to mean before you move forward.

Vendor Vetting Criteria Specific to Superintendents

Beyond the standard content and pricing questions any building-level administrator would ask, a district-level vetting process should specifically weigh:

• Standards alignment across the district, not just for one grade band or one school's curriculum map. Does the vendor's content span the full range your district needs, consistently labeled?
• Vendor stability. Is this a business likely to still exist, and still be maintaining its content, three years from now? Small vendors aren't automatically a risk, but it's worth understanding who's behind the product and how they support it.
• Data handling. What student or staff data, if any, does the platform touch, and how is it handled? A printable resource library that doesn't require student logins or collect student data is a simpler answer here than a platform where students sign in directly, though this is worth confirming directly with any vendor you're evaluating, ClassWeekly included.

How District-Tier Licensing and PO Billing Typically Work

At 75+ teachers or across multiple schools, a vendor relationship usually shifts away from self-serve card billing toward a custom quote and purchase order process. With ClassWeekly, that's the District tier specifically: a custom quote with PO billing available, requested through "Request a quote" rather than a card checkout used at smaller tiers. That shift matters for your procurement timeline, since PO-based purchases typically need to start earlier in a budget cycle than a same-day card purchase would.

Rolling Out Consistently Across Multiple Schools

Once a district-level license is in place, consistency across campuses depends less on the vendor and more on how the rollout itself is managed. A few things that help:

1. Communicate the decision the same way to every building, rather than letting individual principals introduce it inconsistently.
2. Confirm that access doesn't require per-school IT setup. With ClassWeekly, there's no LMS integration required, which removes one common source of uneven rollout timing between campuses with different IT capacity.
3. Set a shared expectation for content requests. If a teacher at one school requests something that doesn't exist yet, the resulting content should be available district-wide once built, not siloed to the requesting school.

A district-level decision carries more weight and more scrutiny than a single-building purchase, which is exactly why it's worth a more formal vetting process than "does this look good in a demo."

---

Ready to evaluate a District-tier rollout across your schools? Request a quote for purchase order billing, or get started to pilot at a single school first.