If you teach for a living, the volume of context you carry is genuinely impressive and a little inhumane. Twenty-five to a hundred students, each with their own running story. Lesson plans for five subjects or four periods. Standards documents you're supposed to be aligning to. Parent emails. IEP and 504 paperwork. Last year's plans you swore you'd reuse. The school's PD binder. A printer that's been broken since November.
Most of this lives in different drawers — paper folders, the LMS, your school email, a personal Google Drive, a spiral notebook, and the back of your brain. This guide is about putting the parts that matter into one searchable place where an agent can help with the boring lifting.
The problem with the way teaching notes usually live
A typical teacher's note system has three weaknesses. First, it's split across systems — your school's LMS won't talk to your personal Drive, and your personal Drive won't talk to your phone notes. Second, it's hard to search across years; last year's perfect lesson on the same unit is theoretically findable but practically lost. Third, the parts that need privacy (specific student observations, IEP details, parent communication) are jumbled together with the parts that don't.
The shape that helps: a single vault you control, organized by class and unit and student, with an AI agent that reads what's in it. Plain markdown files, so the agent is fast at searching, summarizing, and surfacing connections. No plugin assembly to do at the start of the year — the agent works on day one.
That's what we built Docapybara around. The rest of this guide is how that maps to actual teaching workflows. If you also design and refine the curriculum yourself, see AI notes for course creators and the more detail-oriented curriculum design guide — they cover the design layer that sits underneath weekly lesson planning.
Lesson plans that compound year over year
The biggest waste in teaching is rebuilding lesson plans from scratch every year because last year's are technically saved but practically inaccessible. They're in a Drive folder you can't quickly search, named with formats you can't remember, and the markdown of "what worked, what didn't" lives in your head, not in the file.
The fix is structural. One top-level page per subject. Sub-pages per unit. Sub-pages per lesson. After each lesson, a short reflection at the bottom — what landed, what didn't, what to change. There's no depth limit, so you can nest as deep as the structure needs.
Now next year, when you sit down to plan the same unit, you don't reinvent it. You ask the agent: "Pull last year's lesson plan for the photosynthesis unit. Give me the reflections I wrote at the bottom of each lesson — what worked and what I said I'd change." Five minutes of reading replaces an hour of remembering.
For the planning itself, the agent is good at the boring middle 70%. "Draft a five-day lesson plan for the unit on equivalent fractions for fourth grade. Use the structure from my last unit on adding fractions, and align it to these standards." The standards document was a PDF you uploaded last August; it got auto-converted to markdown via docstrange when you uploaded it, so the agent can quote from it directly.
Student observations: capture quickly, find them again later
Behavior, academic, social — observations matter most when they accumulate over time. The student who's been quiet for two weeks. The reader who shifted from struggling to confident over a month. The classroom dynamic that changed when one kid moved seats.
But observations are fragile. You scribble them on a sticky note. You meant to type them up Friday. You didn't. By Monday, the sticky is gone and the observation with it.
A workable pattern: a "Students" section in your vault, with a short page per student. After class, type a one-line dated observation into the relevant student page. Even a half-sentence is enough — "Tuesday: stayed after to ask about the test, first time he's done that." Over the year, those one-liners build into a real picture.
When parent-teacher conferences arrive, the agent earns its keep. "Read everything I've written about Maya this semester. Give me a one-page summary covering academic progress, behavior, and three specific anecdotes I can share with the parents." The agent reads the page, pulls out the patterns, and gives you a draft. You spend ten minutes editing it instead of two hours staring at scattered notes.
For privacy: the vault is single-user, cloud-hosted, scoped to your account. Treat student observations the way your district policy says to treat them — but at least they're now in one searchable place instead of on the back of an attendance sheet. (The single-user trade is part of the design — see our Notion comparison for context on when team-shaped tools fit better.)
Parent communication: a record you can actually find
Parent emails go in two directions and usually get lost in both. The thoughtful email you sent in October about a student's late work patterns? You wouldn't find it in February if you needed it. The parent's reply with the context about a family situation? Even harder.
A simple habit: every meaningful parent communication gets pasted into the relevant student's page in your vault, with a date. The original can stay in email — that's your transport, not your storage. The vault entry is what you'll find later.
When you sit down to write a hard email — a behavior concern, a grade explanation, a recommendation for additional support — ask the agent to draft from the record. "I need to email Liam's parents about his missing assignments. Read what I've written about him this quarter, and draft something that's specific, kind, and includes the three concrete steps we agreed on at the last conference." You get a draft grounded in the actual history, not a generic template.
Recordings: meetings, observations, and the agent that reads transcripts
Teachers sit through a lot of meetings — IEP teams, PLCs, departmental, faculty, parent conferences. The note-taking burden is real, and most of it lands in a notebook that gets flipped past.
When the meeting is one you'd normally take notes in (and where recording is appropriate and policy-compliant), drop the audio into a page in your vault. Transcription with speaker labels happens automatically — you don't have to babysit it. Now you have a searchable record of who said what, which matters most for IEP and 504 meetings where the specifics legally matter.
After the meeting, ask the agent: "Pull every commitment made in today's IEP meeting. Who said they'd do what, by when?" That list goes into a follow-ups database on the same page, and you have something concrete to chase instead of a vague memory of "I think we agreed Sarah would update the goals?" The general pattern for that move sits in our guide on how to capture action items so they actually get done.
Same pattern works for classroom observations you record for your own reflection — a lesson you taped to study your own pacing, for example. The transcript becomes searchable text the agent can read.
A grading and feedback loop that doesn't burn the weekend
The agent isn't going to grade for you (and shouldn't). But the boring middle work around grading — keeping track of which assignments are out, who's missing what, which patterns are showing up across the class — is a database problem, not a teaching problem.
An inline database in a class page, embedded directly in markdown via the :::database::: directive: one row per major assignment. Columns for due date, status, common patterns observed, and a link to your gradebook entry. The agent can pull "which assignments are open across all my classes right now?" or "which students have three or more missing assignments?" without you opening anything else.
For feedback writing, the agent helps draft. "Draft three sentences of feedback for this student's essay. Focus on the thesis structure and one strength to build on. Use the rubric I uploaded." The rubric was a PDF; it's now searchable text the agent can quote from. You edit, personalize, send.
The end-of-week routine that keeps the system honest
A workspace is only as useful as its currency. The teachers who get the most out of a vault setup tend to spend ten or fifteen minutes on a Friday afternoon doing three things:
- Add any observations from the week that didn't make it in during class.
- Skim the upcoming week's lesson plans and ask the agent to surface any missing pieces — "Read next week's plans for fifth-grade math. Note anything that needs a printable, a slide deck, or a reservation I haven't made yet."
- Reply to any parent communication that's been waiting, drafting from the record so the response sits in context.
The Friday loop is short because the system holds the context. You're not reconstructing your week from memory; you're skimming what the system already captured.
A calmer year
A few honest limits. This isn't a gradebook — you still need your district's gradebook for official records. It isn't an LMS — assignments and student-facing materials still go where your school posts them. It isn't a shared space for a teaching team — the vault is single-user, one person, one workspace. If your school uses a particular system for IEPs or behavior referrals, this complements it, not replaces it. What it is: the place your own working context lives. Your lesson archive. Your observations. Your parent records. Your meeting transcripts. The context that historically lived in your head, a desk drawer, and three different apps — now in one place an agent can read.
Teaching is going to be exhausting regardless of tools. But the cognitive load of remembering where things are, what you wrote down, and who said what at the last meeting — that part is fixable. Move that load out of your head and into a vault that holds it for you.
Try Docapybara free — sign up, drop in last year's lesson plan for one unit, this week's observation notes, and one PDF of standards or curriculum, and ask the agent for next week's plan grounded in all three.