With every new software package, there can be unique implementation challenges, and learning how to drive your new Communication and Data Analysis Tool is no different! There are important decisions to be made, tasks to be assigned and a learning curve for all involved. No need to worry though, we’re SchoolStatus, and we're here to help!
Challenge #1: Your district doesn’t know what to do first.
Overcome this by creating an implementation guide.
Planning is the key to success. Use our handy implementation guide to help you figure out what you need to do along the way.
Challenge #2: You feel overwhelmed.
Overcome this by making a to-do list and assigning tasks.
You are great! You can do anything- but that doesn't mean you have to do everything. Here are some ways your team can help:
- Technology Director: review SchoolStatus System Requirements
- District Test Coordinator: provide access to assessment sources
- SIS or Payroll Administrator: compile a user list with emails and job titles
- Professional Development: Schedule training dates and get the word out
- Curriculum Director: confirm which users see students through assigned courses besides teachers (librarians, interventionists, speech pathologists, counselors, SPED teachers and other "special case" educators)
Challenge #3: Your team doesn't want to share data access.
Overcome this by reviewing our security procedures with them.
Look, we get it. We are DATA NERDS, after all. For those who are sharing-shy, here's some nerd-security speak for you: Our framework is housed in an SOC 1/ISAE 3402 facility, using banking-grade encryption technology. We have designed SchoolStatus with strict FERPA compliance as the baseline rule. Just as you might have an administrator who is nervous about sharing access, we've also seen an administrator or two who... um... really, really... aren't. SchoolStatus has designed very specific procedures for districts to use when transferring credentials and files to us. For security purposes, please advise your staff that we will never recommend that you send usernames, passwords or student details by email.
For full details, email us at email@example.com.
Challenge #4: You don’t know how long it will take to set up.
Overcome this by creating a schedule.
Once you've signed your terms of service, we ask you to gather your team for a kickoff call, where we talk about next steps. After that, you'll need to gather, test and submit your credentials; then we will integrate them. In theory, it *might* be possible to go from zero to full display in just a day or so. Realistically, we ask for about two weeks, because we want to make sure everything is working properly. Then we will verify the data with the SPOC and give a brief tour of the new digs. That's when we like to schedule your training dates. Then we help you create your user accounts, and get you ready to roll!
Challenge #5: You don’t know how to create User Accounts.
Overcome this by creating a list of Admin-level employees with email addresses and job titles.
Once you've shared a list of potential users with us, we'll work with you to review the list of job titles, learn how they need to work with students, if they should be limited by school, if they have assigned courses with students enrolled in them- that sort of thing. This step might seem a little tedious, but in the long run, you'll be so glad you've established a protocol up front for account creation.
We can usually automate the creation of accounts for teachers (those with students enrolled in courses assigned to them.)
Challenge #6: You don’t know how (or when) to engage your users to get them excited about it.
Overcome this by scheduling training dates, and then using an email sequence.
It's really important to get training for your users BEFORE they dive in. A few training steps in the beginning will make the product more enjoyable and more effective for them. Think of your training dates like parties. Not only do you want people to attend, you want them to get excited, enjoy it, and talk about it the next day!