Strong submission
Weak submission
- States exactly what is changing.
- Explains why the change is educationally or operationally necessary.
- Identifies impacts on students, other courses, and implementation.
- Considers impacts on dependencies.
- Includes student transition plan where needed.
- Shows evidence of consultation where appropriate.
- Relies on shorthand such as “modernize”, “clean up”, or “everyone agrees”.
- Assumes reviewers already know the background.
- Ignores other impacted courses/plans and student implications.
- Omits downstream consequences.
- Leaves others to discover implementation issues later.