During the summer break, we transitioned from Education Edge to Veracross. There is a long list of reasons why we decided to do this, but I won’t go into that in this post. Veracross provides more support than Education Edge to a number of roles across the school, from the receptionist to the registrar to the admissions team to the faculty. But with this additional support comes additional responsibilities. As a result, some roles have had to take on extra responsibilities. The following document details the current SIS roles and responsibilities at my school. We are only two months into the implementation of Veracross and I expect this document to go through a few versions before the end of the academic year.
We’re about to begin the process of redesigning our website at my school. Before we start I thought it would be a good idea to redefine the current roles dealing with the website and while I’m at it define a few new roles. The end result is the following document.
In the Technology Department at Saint Maur, we’re currently meeting with school information system (SIS) vendors who are demonstrating their products to us. We’re meeting with vendors because the system we’re currently using to manage student and other information, Blackbaud’s Education Edge, falls short in a number of areas that are important to us. These areas include: parent portal; admissions portal; and medical, alumni, human resource and asset information management. (I won’t go into details about where exactly Education Edge falls short in these areas as this is implied in the checklist below.) Anyway, after spending several hours meeting with vendors I realised that rather than them showing me what their systems are capable of, it would be far more time effective to, well, flip things and have them complete a checklist of what their systems can and can’t do. Below you’ll find this checklist. Please feel free to copy it and make adjustments where need be.
Spring at Saint Maur (Mar 27, 2012), a set on Flickr.