A week-by-week back-to-school checklist for teachers, covering the room, the syllabus, your AI-use policy, and the first week of lessons, with a free generator linked at each step.
A back-to-school checklist works best broken into four parts: the room, the paperwork, the first week of lessons, and the routines that carry the rest of the year. In the guides we publish here, the checklist that actually gets finished is short enough to clear in a weekend, not a list of forty small tasks nobody starts.
Start with the two things students notice in the first thirty seconds: where they sit and whether you know their name. A seating chart set before the first bell saves the awkward five minutes of students picking their own spots and you re-shuffling them by day three. The seating chart generator builds one from your roster in under a minute, and you can re-run it once you know which students need to sit apart.
Names come next. A roster you can read fluently by day two changes how the whole room feels, because a teacher who already knows names does not spend the first week scanning a seating chart mid-sentence. If a class list runs past 25 or 30 students, a random name picker doubles as a low-stakes way to drill names out loud during the first week's warm-ups, calling on students by name instead of pointing.
A syllabus written the week before school starts is a syllabus you can actually explain clearly on day one, instead of reading from a draft. The syllabus generator turns your grading scale, late-work policy, and course outline into a printable document in a few minutes, which leaves you time to actually think through the policies instead of just formatting them.
One policy line gets skipped more than any other: what students may and may not do with artificial intelligence (AI) tools on their assignments. Writing that line in August, before the first assignment is due, avoids the harder conversation of explaining a new rule mid-semester after a student already used AI on a paper. The AI syllabus statement guide has copy-ready language for allowing, limiting, or prohibiting AI use, sorted by how strict you want to be. If your school or district has not published its own AI policy yet, the U.S. Department of Education's Office of Educational Technology publishes federal guidance on classroom AI use that is worth reading before you write your own version, and our AI policy for schools guide breaks down what a school-level policy usually needs to cover.
A strong first day and a weak second day undoes most of the good will a strong opener buys. Plan the whole first week as one unit: an icebreaker or diagnostic on day one, a real lesson by day two, and a full routine by day five. The lesson plan generator drafts a full week from your grade level and topic, which gives you a working plan to edit rather than a blank page to fill five nights in a row.
Build in a warm-up and an exit ticket from day one, even before you have graded anything. Both signal to students that the class has a rhythm, and both give you fast information about who is following along. An exit ticket generator turns a single learning target into a two-minute check you can read that same night.
Routines set in week one and never repeated are not routines. Pick two or three you can run identically every day for a month: how students enter the room, how you form groups, and how you get quiet fast. Responsive Classroom, a research-based approach to classroom management, teaches the first six weeks of school as the window where a routine either becomes automatic or falls apart, because that is the stretch where students are still watching to see whether you actually enforce what you announced on day one.
Two tools make the daily version of this easier to keep up. The group generator splits a roster into random or balanced groups in seconds, so grouping students never eats five minutes of class time. The classroom timer puts a visible countdown on the board for transitions and independent work, which cuts down on the "how much longer" questions that break your focus mid-lesson.
Grading systems built after the first stack of papers arrives are usually built in a rush, at 9 p.m., with a headache. Build the rubric before you assign the work. The rubric generator turns a list of criteria into a printable, gradeable rubric, so the first assignment of the year comes with clear expectations attached instead of a vague prompt and a promise to "grade it fairly."
Decide your turnaround time now, too. Telling students on day one that work comes back within a week, and holding yourself to it for the first month, sets an expectation that is much harder to establish once you are three weeks behind on a stack of essays.
A short first-week email that covers your grading scale, your communication policy, and your classroom's AI-use line heads off most of the individual questions you would otherwise field one at a time in September. Keep it to what a parent actually needs to act on: how to reach you, when grades post, and where the full syllabus lives. A long email restating your entire philosophy of education gets skimmed and forgotten. A short one gets read.
This checklist assumes a general education classroom setting up a normal course load. A teacher inheriting a highly structured, district-mandated curriculum with its own pacing guide and required materials has already had several of these decisions made, and should treat this as a shorter list: mostly the room, the roster, and the routines, since the syllabus and pacing are set elsewhere. It also is not written for a first-year teacher building a classroom management system from nothing. That work takes a mentor and a season, not a checklist.
A one-to-one device rollout, a new learning management system, or a district-wide AI tool adoption announced right before the year starts would move the syllabus and AI-policy steps earlier, since those decisions then depend on tools you may not have used yet. A shortened first week, common in districts that start with a half-day or a staggered entry schedule, compresses the "first week of lessons" step into the room and roster steps instead of treating it as its own phase.
Start with the room and the roster this week, since those are the two things ready before students arrive changes how the first day actually feels.
Join the Chalkbox list for free printable packs and new tools — no spam, unsubscribe anytime.
Start about two weeks before the first day: the room and roster in week one, the syllabus and policies in week two, and the first week's lesson plans in the final few days. Doing all of it the weekend before leaves no time to fix a rough draft.
A seating chart, a printed or posted syllabus, and a plan for the first day's opening activity. Everything else, the full first week of lessons and your grading rubrics, can come together over the following days as long as day one is covered.
Start from copy-ready language rather than a blank page. The AI syllabus statement guide linked above has wording for allowing, limiting, or banning AI on assignments, sorted by how strict a policy you want, so you can pick a version and adjust the details for your course.
Pair a seating chart with a short daily routine of calling on students by name during a low-stakes warm-up. Most teachers who commit to this for the first two weeks have the roster down cold by the start of week three.
Plan the whole first week as one block, not day by day, so day two already has a plan when day one runs long or short. A rough draft finished the weekend before the first day still leaves time to adjust once you see how the actual class moves.
This guide is general information for educators, not legal advice. AI tools and school policies change quickly — verify specifics against your own school’s rules and the tools’ current documentation before acting.