Best practices for district-wide rollout

While we typically recommend that schools and districts pilot Little SIS Sync prior to a large-scale rollout, the summer months are a great time to work out the kinks that would arise during a pilot - namely, cleanliness of data and change management. The advantages to rolling out Little SIS Sync during the summer are the creation of Classroom classes for all of your teachers, and the lessened chance that teachers have already created classes that you will need to manually link to in the interface. 


How do you get started with a large scale rollout of Little SIS Sync?

Review the Installation and Data Requirements sections in the Help Center to ensure that both your environment and your data are ready. Once your server and your data are good to go, you'll want to create the Jobs that you will run throughout the school year.

 Before setting up Jobs, we do recommend bulk-archiving all of the previous year's classes. The reason for this is to ensure that both the teachers' and the students' view in Classroom only contains information relevant to the current school year. You can find out more about bulk archiving classes here


Communicate to Your Teachers

We definitely recommend letting your teachers know about what kind of changes they can anticipate as you roll out Little SIS Sync. Further information about change management can be found here.

Additionally, we have a teacher email template available here


Setting Up Jobs for a Full Year Deployment

It is best practice that you set up your Jobs in a way that makes sense for your school or district. Smaller independent schools may find that Jobs according to grade level or term make the most sense. A small to medium-sized district might want to break up their Jobs per school site and term. A larger district might still find that site-level Jobs are helpful, but may want to organize their Jobs into larger chunks, like Elementary, Middle, High, in order to ease the setup process. But why wouldn't you want all of your sites in one Job, you ask?

The more Jobs that you create, the more granular control you have over the contents of the individual Jobs, including class naming convention and automation settings. For example, you may want to include period number in your middle school and high school class names, but for Elementary school, you only want to include the grade and the name of the teacher. Creating separate Jobs for each will allow you to accomplish this small difference. 

More about creating Jobs can be found here.    


What if I don't want my teachers to know who is enrolled in their class yet?

You can create classes without enrolling students - that way your teachers are still able to build out their course content in Classroom, but they are not able to see who is enrolled in the class until you are ready to reveal that information.

Within the Job settings, navigate to Update Preferences. Here you see the Roster Updates section first, where you can deselect the "Add" and "Remove" checkboxes, allowing you to provision Classroom classes for your teachers without letting them, or your students, know who is in which class. Just go back in to the job settings when you're ready to push the students out and reselect the Roster Updates, as shown below.