8.2 — Time-Block + Sunday Reset + Schedule Layers | AI for Real Life

"I have so much to do, I don't know where to start." That's a planning problem, not a time problem.

You're going to create a weekly time-block. You decide on Sunday what each chunk of time is for, then you stop deciding for the rest of the week. Claude builds the template fast if you give it the right inputs.

What we're building in this lesson

Three things: (1) a weekly template you'll reuse most weeks of the semester: classes, study blocks, work, sleep, meal/movement, social/recharge; (2) a Sunday Reset that adapts the template to the actual upcoming week using the calendar from Lesson 8.1; and (3) the Activity Schedule Layer for the stuff that's not on any syllabus: sports practice, club meetings, work, away games, last-minute schedule swaps. Same prompt pattern as the Module 7 weekly refresh, with logistics-specific anchors. By the end of this lesson, you have a real schedule and a re-run-this-every-Sunday ritual that keeps it from drifting.

The weekly template prompt.

Run this prompt once at the start of the semester. It gives you a default Mon–Sun grid you'll modify each Sunday rather than rebuild from scratch.

The Weekly Template Prompt

Build me a weekly time-block template: Monday through Sunday: for a [high school junior / college sophomore / etc.] taking [N] classes this semester. My fixed inputs: CLASSES (course code + day + time): - [e.g. BIO 201:MWF 10:00–10:50] - [...] OTHER FIXED COMMITMENTS (job shifts, practice, club meetings, recurring family stuff): - [e.g. Barista shift: Tue/Thu 4–8pm] - [...] NON-NEGOTIABLES: - Sleep: at least [7.5] hours/night, lights-out by [11:30] - Meals: 3 protected meal slots + flexible snacks - Movement: [3x/week, 30–45 min] OR [tied to my sport practice schedule above] GOALS for the week: - [~25 study hours / ~15 study hours / etc., honest with yourself] - One protected social block per weekend - One protected do-nothing block (yes, on purpose) Output a 7-day grid in 30-minute increments from 7am to 11pm. For each block, label one of: CLASS, STUDY [course], WORK, SLEEP-PREP, MEAL, MOVEMENT, BUFFER, SOCIAL/REST, ADMIN. Then below the grid, give me a "Logic notes" section (3–5 bullets) explaining: where you put the heaviest study blocks and why, where you protected rest, and what the most fragile point in the week is (the day where one curveball will break the whole schedule).

Why "Logic notes" matters

Without it, Claude gives you a grid and you accept it. With it, you see Claude's reasoning ("I put the BIO study block Tuesday afternoon because the lab is Thursday morning") and can argue with the parts that are wrong for you ("actually I'm dead after Tuesday work shifts, move that to Wednesday"). The logic notes are also what you'll edit each Sunday: the underlying structure stays, the assignment of blocks shifts.

The Sunday Reset.

The template tells you the shape of a normal week. The Sunday Reset tells you what this week actually is: what's due, what's heavy, what to protect, what to drop. Run it Sunday late afternoon, before the week starts. It's a quick ritual, not a long planning session.

The Sunday Reset Prompt

Sunday Reset for the week of [date]. I'm pasting: 1. The next 7 days of dated items from my semester calendar (from Lesson 8.1): [paste the relevant rows of the table] 2. Anything new since last Sunday: assignments added, plans changed, things I committed to: [short list] 3. My energy honestly going into this week (1–10): [N], because [one sentence]. Walk me through a 5-minute Sunday Reset: A) **What's the heaviest thing this week?** Pick the single highest-stakes item. That's where the heavy STUDY blocks anchor. B) **What's slipping from last week?** Anything I haven't started that I should have. Don't roast me, just name it. C) **What can I drop or downgrade?** Realistic look: if energy is a 4/10 this week, what's the lowest-stakes thing on the list, and is it okay to do it B-effort instead of A-effort? D) **The one priority.** If I only get one big thing done this week, which one is it? (One. Not three.) E) **Edits to the template.** Suggest 2–4 specific changes to my standard weekly template for THIS week: e.g., move the Wednesday study block earlier, add a Thursday catch-up block, swap Saturday's social for Sunday's so I can rest Saturday after the exam. Keep it short. Five minutes of reading max.

🪨

The "rocks first" rule

The big rocks (heaviest item, group-project deadline, exam) get placed first in the week. The small stuff (readings, problem sets, discussion posts) fills the gaps around them. Claude will default to "fair distribution":push back if your week has a real anchor and ask for the schedule built around it.

🔁

The "honest energy" input

The 1–10 energy line is a key field. A schedule built for a 9/10 energy week and run on a 4/10 energy week is how students implode. Telling Claude "I'm at a 4 this week" lets it actually downgrade things instead of giving you a perfectionist plan you'll fail.

The Activity Schedule Layer.

Lesson 8.1 builds your calendar from syllabi. The template above builds the weekly rhythm from classes and study. Both miss the things that, in real life, are way more likely to blow up your schedule: an away game that means you're on a bus until 11pm Tuesday, a club meeting moved to Thursday at the last minute, a coach calling a Sunday-morning practice the day before your midterm, a manager texting you to swap into a Friday night shift.

You probably get your sport schedule as a PDF or a screenshot of a team app. Your club schedule lives in a Discord. Your work schedule lives in 7shifts or a Google Doc. None of them talk to each other. The whole problem is fixable with one prompt.

The Activity Schedule Layer Prompt

I'm adding my non-academic commitments to my semester calendar. I'll paste/upload everything I have. For each one, pull out every dated event and add it to my unified calendar. INPUTS: [Sport / activity #1:paste schedule, screenshot, or describe pattern: e.g. "Volleyball: practice MWF 3:30–5:30, games most Saturdays, season runs Aug 25 – Nov 2, here's the game schedule PDF"] [Sport / activity #2] [Club: e.g. "Debate club: Thursdays 6–8pm, tournaments first Saturday of each month, see attached Discord export"] [Job: e.g. "Barista at [shop]:typical schedule Tue/Thu 4–8pm, but it changes weekly via 7shifts. Here's the next 4 weeks I have."] OUTPUT: A unified table: same format as my semester calendar from Lesson 8.1: | Date | Day | Time | Activity | Type (sport/club/work) | Travel? | Conflicts with academic items I've already shared (Y/N) | Then a "CONFLICTS" section listing every date where one of these activities runs against an academic deadline, exam, or major project from the semester calendar. For each conflict, suggest one of: "shift the assignment earlier," "talk to coach/manager about that day," "this week needs special handling: flag for the Sunday Reset." Don't tell me to quit anything. Just make me see what's coming.

Spotting conflicts early

Three months in, you'll have an away game on the day a paper is due. You can't always change either. The point of building this layered calendar is to see it three weeks early instead of three days early. Three weeks gives you options: ask the prof for an extension, write the paper before the trip, study on the bus, swap a shift. Three days gives you only one option, which is the all-nighter. The Sunday Reset above is the weekly check that catches these.

Up next: 8.3: The Group Project Survival Kit

You've got a calendar (8.1). You've got a weekly rhythm and your activities layered in (8.2). The next lesson is the one for the worst kind of student stress: group projects. Kickoff messages, role-splitting, the polite-but-firm nudge for the unresponsive teammate, conflict scripts that don't burn the relationship. Five screens. Templates you'll actually use this semester.

Continue to 8.3 → Group Project Survival Kit