A new school signs in to an empty system, and the honest question is what to do first. The checklist answers it in order — classes, sections, subjects, students — and gets out of the way once the school is running.
In the order the work actually has to happen
Subjects cannot be mapped before classes exist, and attendance cannot be marked before students are on the roll. The list follows those dependencies rather than listing every screen in the product.
It disappears
Once the school is set up the checklist goes, replaced by quick actions for the daily jobs — admit a student, mark attendance, post a notice. It does not sit there for the next three years reminding you of a step you deliberately skipped.