Ongoing Thoughts

In a previous post , I discussed the need to slow down and breathe during tech adoption, especially while under stress.  Based on that post, I thought I would share some policies written in regards to software adoption in an educational environment. Several years ago, I was responsible for authoring my employer's Software Steering Review Committee policies and considerations for approval. In a time when the school district I work for was pushing hard on instituting personalized learning, it was difficult to maintain a balance between flexibility and appropriate review. The district already had the initial request process documented, so I was simply left with the review process documentation. Originally, there was a Software Steering Review Committee that met to evaluate requests. Unfortunately, that process was cumbersome and difficult to schedule, which resulted in many successful attempts to completely bypass review. (Please keep in mind, the purpose of this post is not to

As educators, parents and students around the world struggle to rapidly adapt to our changed environment, now seems like a good time for a reminder that it's ok (even necessary) to slow down and evaluate our technology adoptions.  As such, I'm taking this opportunity to review some points about Google Apps for Education (GAFE) and FERPA compliance. The G Suite Terms of Service for Education Agreement is not a terribly long document, it totals out at just over 12 pages.  When a school district signs up to use Google Apps for Education, someone authorizes this agreement.  In it, Google asserts that they will act as a "school official" with regards to the data they receive.  There are two very important things to remember about this agreement however: This agreement applies to Google's Core Services and does NOT apply to additional services (explicitly noted in the GAFE privacy policy .) It is still the responsibility of the district to configure the G Suite