-admin cost of centralization.
-efficiency gain in distributed admin. Build the system to thrive as more admins are promoted, but can be run by one person, or full auto mode for emergency. collaboration to be driving innovative organizational principles.
-new organizational opportunities between teachers and substitutes
-new social metrics for matching system and performance based pay scale.
-create a more legitimate "career" to retain subs for longer periods; offering both teaching experience and [(drupal)website] admin skills.
-possible model for student teaching career teaching track, bringing the teacher education closer to the schools where they will eventually work.
-possible model for school-wide administrative system; integration of electronic systems.
-try and avoid the implementation of another data silo, so look to implement a system that is pure infrastructure that can potentially be used ubiquitously within the district. Drupal will offer that path if it should come to pass. very flexible with APIs and openess.
-a system that strives to expand website administrative capacity for "ordinary" people; ie being able to easily build custom reports or collections of data from the system.