Arguments given for this include:
- Defaulting a class to active may reduce the number of "DECLINED" classes in some contexts, increasing adoption of centrally-provisioned classes and reducing administrative frictions.
- This option could be allowed, but not set as the default in a job.
- Students in an "ACTIVE" class are able to see / enter / interact with the class immediately. This fact may not be known to Little SIS administrators, and may pose a risk of user error that puts students and/or staff at some risk. Allowing this option would require some strong warnings to be in place within the app.
- Provisioning classes directly to the "ACTIVE" state will make it harder for folks to distinguish classes a teacher actively engaged with from those that the teacher never bothered to touch. Cleanup of unused classes and monitoring of teacher engagement gets less clear / more complicated when fewer states are used to understand teacher engagement.
- Giving teachers "no choice" in adoption can have blowback from an IT change-management perspective, and should be approached carefully.