Start of semester. Kid comes home with 6 syllabi. Some printed, some digital, some "on the class website somewhere." Three weeks in: "I didn't know that was due." Missed assignment. Grade dropped. THE TEENAGER TIME MANAGEMENT CRISIS Each class has different format. Some teachers list due dates clearly. Some bury them in paragraphs. Some just say "weekly quizzes" with no specific dates. Asking "do you have homework?" gets a shrug. Checking the syllabi requires actually reading them. Nobody reads them after day one. Teachers assume students track their own deadlines. Students assume they'll remember. Nobody remembers. THE SYLLABUS ORGANIZER I BUILT Start of each semester, syllabi go into folder. Workflow processes each one. Extracts course name, teacher info, grading breakdown, office hours. Most importantly: every single assignment, project, exam with due dates and point values. Sorts everything chronologically. Not by class, by DATE. What's due soonest at the top regardless of which class. Generates a master calendar. Every deadline visible in one place. Weekly summary: "This week: History essay (50 pts), Math quiz (20 pts), Science lab report (30 pts)." THE GRADE PROTECTION Before: Missed assignments, "I didn't know," scrambling at last minute, stress for everyone. After: Deadlines visible, no surprises, actually can plan ahead. First semester with this system: No missed assignments. First time ever. Kid still complains about the weekly summary notifications. "I know, mom." But hasn't missed anything since. The extraction struggles with syllabi that are images instead of real PDFs. Some teachers scan handwritten documents. Those need manual entry. Worth the effort. Fighting over missed homework was exhausting for everyone. This is the workflow here i want to share How do you help students actually track what's due?

If AI feels “mid” to you, it’s probably because you’re using it like a vending machine. You type: “Write me a landing page” or “Make me a content plan.” It spits out beige. Then you blame the model. The fix isn’t a smarter prompt. You need better context. Here’s a simple way to feed context that actually changes the output in one go. Copy this and fill it in. Keep it saved as your “Context Card” and paste it before any real request: 1) What you’re making (one sentence) Example: “A landing page for a 2-week onboarding sprint for busy founders.” 2) Who it’s for (pick one person, not a market) Example: “A founder who has 12 tabs open, 40 Slack pings, and keeps pushing onboarding ‘to next week’.” 3) The moment they’re in (what happened right before they found you) Example: “They just hired their first ops person and realized nothing is documented.” 4) What they already tried (and why it didn’t work) Example: “They tried a Notion template dump. It turned into a graveyard.” 5) Your taste rules (3–7 bullets max) Example: - Short sentences. No hype. - Practical, not philosophical. - Assume they’re smart and tired. - Give examples, not frameworks. 6) Proof you can actually claim (real, plain) Example: “Includes a 30-minute kickoff, 5 docs, and a weekly review checklist.” 7) The one action you want them to take Example: “Book a call” or “Start the sprint” or “Reply with ‘ONBOARD’.” Then ask for the thing you want: “Using the Context Card above, write a landing page with: headline, subhead, 3 sections, FAQ, and a final CTA. Write v1. Leave placeholders where you need specifics.” Two important notes: - “Taste rules” is where your voice lives. Most people skip it. That’s why everything sounds the same. - Let AI write v1 on purpose. Your job is v2–v10: cut half, add one real example, remove anything you wouldn’t say out loud. If your outputs keep sounding generic, don’t prompt harder. Describe the person, the moment, and your taste. That’s the whole difference.