A district SpEd director, a site admin, and a provider all open Speddy and see something different — because each of them has a different job. Here's how the pieces fit together.
District SpEd directors get a read-only view across every site in the district, plus the access controls to add, remove, and re-role users as your team changes. You don't have to build schedules or log sessions yourself — but you can see how it's all going, at any moment, without asking anyone for a status update.
Site admins do the one part of Speddy that providers can't easily do alone: load the structural scheduling data — bell schedules, specials, lunches, blackouts. It's data you're already maintaining somewhere (usually a spreadsheet you share each August). Speddy turns it into a reusable foundation that every provider on your site builds against.
Site admins don't have to participate for Speddy to be useful. If you don't load the structural data, your providers can enter it themselves and still get the full benefit. But it's substantially better — for everyone, including you — when site admins contribute the foundation.
Providers do the most in Speddy — and get the most out of it. You build your weekly schedule against the structural data the admin loaded (or load it yourself if they haven't). You log attendance and lessons in a few clicks. You keep your referral queue organized so nothing falls through the cracks. And when something changes — and something always changes — you adjust once, in one place.
Districts give the team the tool. Site admins lay the foundation. Providers do the daily work. Each one does the part they're best positioned to do — and nobody has to do anyone else's job to make it work.
A pilot at one or more sites is the easiest way to see whether Speddy fits your team. We'll handle setup, your providers use it through the pilot window, and we review together at the end.