An Assistant Principal's Checklist for Resource Planning

You're often the one handling the operational side of a resource rollout, whether or not you were the one who signed off on the purchase itself. Coordinating staff access, training, and the inevitable mid-year staffing changes usually lands on your desk. Here's a checklist built for that specific job.

Where Assistant Principals Typically Fit in Resource Decisions

The purchasing decision and the rollout are often two different jobs, handled by two different people. A principal, curriculum director, or district office might make the actual purchase call. What frequently falls to an assistant principal is everything that happens after that: making sure staff actually know the resource exists, know how to use it, and can access it on day one, plus handling the staffing changes that happen throughout the year that a one-time announcement doesn't account for.

If that's your role here, this checklist is built around the operational side specifically, not the buying decision.

A New-Year Resource Planning Checklist

• Confirm access is live before the first staff day, not scrambling to set it up once the year has already started.
• Prepare a short, specific announcement, not a general email. Staff respond better to "here's a worksheet for the first unit you're teaching, here's how to find more like it" than to "we have a new resource, check it out sometime."
• Identify who to route access or login questions to, if any come up, even for resources like ClassWeekly's site license that don't require individual account setup for each staff member.
• Check whether any staff need materials before day one (for early planning periods, orientation, or pre-service days), so the resource is genuinely useful from the very first week, not just eventually.

Anticipating Pushback From Staff Who've Seen Tools Come and Go

Not every staff member greets a new resource announcement warmly, especially if they've watched two or three tools get rolled out and quietly abandoned in past years. That skepticism is reasonable, not a discipline problem, and it's worth addressing directly rather than hoping enthusiasm covers for it. Naming it plainly in the announcement, something like "we know new tools have come and gone before, here's specifically why this one doesn't require you to change how you already plan," tends to land better than a purely upbeat pitch. The fact that a School Site License requires no new login system, no LMS integration, and no individual account setup is a genuine answer to that skepticism, not just a feature to mention in passing.

A Worked Example: Rolling Out Access for a 40-Teacher Staff

Say your building has 40 teachers. Access under a School Site License is already live for everyone the moment the license is active, no individual invitations to send, no waiting on 40 separate signups. What takes actual coordination is the communication layer: a five-minute mention at the first staff meeting, a one-page handout with a direct link and a short "search by grade and topic" instruction, and a named point of contact for questions. That's a task that fits inside a single prep period, not a multi-week rollout project.

Coordinating Staff Access and Training

With a School Site License like ClassWeekly's, there's no IT setup or LMS integration required, which removes most of the coordination burden you'd otherwise carry for a typical new tool rollout. What's left is mostly communication, not technical setup:

1. A short announcement or staff meeting mention at the start of the year, ideally with one concrete example already loaded and ready to show.
2. A quick reference (even a one-page handout) pointing staff to where the resource lives and how to search it by grade and topic.
3. A follow-up check-in a few weeks in, since adoption at week one doesn't always predict adoption at week six. A quick "is everyone finding this useful" nudge catches teams that quietly stopped using something they never fully got comfortable with.

A useful follow-up check-in isn't just "is everyone using it." It's specific: has anyone found a grade or subject where materials feel thin, has anyone hit a search or access issue, and does anyone still not know it exists. Those three questions surface real adoption problems faster than a general status update ever does.

Handling Mid-Year Staff Changes

New hires, long-term substitutes, aides brought on mid-year, and specialists added to a caseload all need the same access as everyone else, and this is where a per-teacher licensing model creates real friction: someone has to notice the gap, request a new seat, and wait for it to be provisioned.

A School Site License avoids that problem structurally. Since the license covers the whole staff under one purchase, a new hire in October has the same access as a teacher who started in August, with no separate signup, no waiting on a purchase order, and no gap while paperwork catches up. That's one less thing on your list during a part of the year that already has enough moving pieces.

---

Ready to simplify staff access for the year ahead? Get Started with a self-serve School Site License, or request a quote for a District-level rollout.