Curriculum design is a long game. The first version is a draft. The second version is the one you'd actually want to teach, informed by what happened the first time. The third version is the one that holds — the one you can teach for two or three years before it needs serious revision. Most curricula never make it to the third version because the design notes from version one are gone by version two.
This guide is about putting curriculum design into a vault that holds for years. Source material, outlines, lesson scripts, the running log of what to revise — all in one place where the agent can read across them. The goal isn't perfect curriculum on day one. It's a curriculum that gets sharper every iteration because the iteration is informed.
What a curriculum's notes are actually for
A curriculum has design layers and operational layers. The notes need to hold both:
- Design layer: the learning objectives, the throughline, the sequencing rationale, the source material the lessons are drawn from.
- Lesson layer: each individual lesson — outline, script, slides, exercises, assessments.
- Revision layer: the running log of what's working, what's not, what to change next time.
- Source layer: the readings, the references, the artifacts the curriculum draws on.
A vault that holds all four together, with an agent that can read across them, lets the curriculum evolve coherently over years instead of getting refactored top to bottom every time you sit down to revise. For the operational side — running cohorts, tracking student feedback, drafting sales material — see our companion guide on AI notes for course creators.
The curriculum page — the design document
The top of the vault has a single curriculum page. This page describes what the curriculum is — for whom, doing what, over what time frame, with what prerequisites. It articulates the throughline: the central thing the learner should be able to do or understand at the end.
Module structure lives on this page. Each module has a one-paragraph description, the learning objectives, and a link to its sub-page. The sequencing rationale lives here too — why module three comes after module two, what dependency module four has on module three.
This page is a living document. As you teach and learn what works, you update the sequencing rationale. As learning objectives sharpen, you revise the descriptions. The page should reflect the current best understanding of the curriculum, not the original draft.
The agent helps with structural review. "Read the curriculum page and the module pages. Flag any place where a module's stated learning objective isn't actually delivered by its lessons." That's the kind of audit that's hard to do by reading the curriculum sequentially in your head, easy when the agent reads everything in one pass.
Module pages — design details and dependencies
Each module gets a page. The page holds the module's full design — the learning objectives, the lessons that compose it, the assessments, the time estimate, the prerequisite knowledge, and the dependencies on other modules.
For each lesson in the module, a sub-page underneath. Unlimited page nesting means the design can be as deep as it needs to be without going to a separate folder structure. The whole curriculum is navigable as a tree.
Dependencies are the load-bearing part. If module five assumes students have done a specific exercise from module two, that dependency lives on module five's page explicitly. When you revise module two and consider removing that exercise, the agent can flag the downstream impact: "If I remove the regression exercise from module two, what later modules reference it?" You don't break things you didn't know depended on the change.
Lesson pages — the unit of actual teaching
Each lesson lives on its own page. The page holds:
- The learning objective (one sentence)
- The outline or script
- Links to or embeds of any slides, videos, or external materials
- The exercise spec
- The assessment criteria
- A notes section that accumulates as you teach
When you record video lessons, drop the audio or video file in. It transcribes with speaker diarization. The transcript becomes searchable text — useful when you need to revise the script and want to start from what you actually said the last time, not what you thought you said. The same transcription pipeline backs every recording-heavy workflow on the platform — described more fully at AI meeting note taker with speaker labels.
The agent reads lesson pages in seconds. "Read every lesson page in module three. Identify any term used in a later lesson that hasn't been defined in an earlier one." You get a vocabulary audit. The lesson where you forgot to define "convex hull" before using it three times surfaces. You add the definition where it belongs.
Source material — the references the curriculum draws on
Most curricula are drawn from sources — readings, papers, textbooks, talks, datasets. Those sources usually live in a folder you opened during the design phase and then never opened again.
A "Sources" section in the vault, with a sub-page per source, keeps them accessible. Drop in PDFs of papers; they auto-convert to markdown via docstrange so the agent can search and quote from them. For online sources, save the page text and the URL. For datasets, a notes page describing the data and a link to where it lives.
Each source page has a "Used in" section listing which lessons reference it. The agent can populate or audit this on demand: "For each source in the sources section, list the lessons that cite it." When a source becomes outdated (a paper gets superseded, a dataset gets a new version), you can find every lesson that needs updating in seconds.
For the design phase of a new module, the sources section is the substrate. "Read every source tagged with [the module's topic]. Pull the three strongest cases for sequencing the topic in this order versus the alternative." You get a synthesis grounded in your actual references, not a generic AI take. That synthesis informs the design choice.
The revision log — where the next iteration starts
The single most important part of curriculum maintenance is the revision log. After each delivery, every lesson page gets a few notes — what landed, what fell flat, what students struggled with, what you'd change. The notes are dated so you can trace the curriculum's evolution.
These notes accumulate into the substrate for the next revision. "Read every revision note across all lessons from the last delivery. Group by theme. Tell me which themes are showing up across multiple lessons." You learn that students consistently struggle with the transition between a conceptual unit and an application unit — a structural issue you can address in the curriculum design, not just in individual lessons.
For the actual revision pass, the agent helps prioritize. "Based on the revision notes from the last three deliveries, what are the top five revisions I should make? Group by module. Estimate the size of each revision." You get a ranked revision agenda. You decide which revisions to take this cycle and which to defer.
Assessments and student outcomes
A curriculum's assessments tell you whether the design is working. Most assessment design ends after version one because reviewing assessment results is slow.
Drop the anonymized assessment results into the curriculum's vault. The agent reads across them: "For the final assessment in module four, what concepts did most students miss? What concepts did almost everyone get right?" You learn which lessons in module four are pulling weight and which are not. The revision focuses on the lessons whose assessments expose them.
For longer-running courses with multiple cohorts of assessment data, the trend line matters. "Compare the last three cohorts' assessment results on module five. Are students doing better, worse, or the same? What changes did I make between cohorts?" You can attribute or rule out the impact of specific revisions. The curriculum gets revised on evidence, not on hunch.
Updating across the whole curriculum at once
A common pain point is the cross-cutting update — a definition changes, a tool gets renamed, a source gets superseded. Touching every lesson manually is the kind of work that gets started and abandoned.
Ask the agent: "The framework we used to call 'GROW' is now being called 'GROWTH' in the latest edition of the source. Find every lesson that uses 'GROW' and propose the updated text." You get a list of lessons and the suggested edits. You review, accept, or reject each one. The cross-cutting update lands in twenty minutes instead of getting deferred for six months.
Same pattern for tone updates, terminology changes, or structural moves. The agent can read the whole curriculum and apply the change consistently. You stay the editor. The curriculum stays internally coherent.
Working with co-instructors
If the curriculum is co-taught, the vault is yours — single-user. For shared materials, what works is exporting the relevant pages or sections as markdown when you need to hand off, not trying to make the vault a collaboration platform. The vault is the design surface for the lead instructor; the artifacts that other people see are the published versions. (If team-based collaboration is a requirement, our Notion comparison covers when a different shape fits better.)
For incorporating co-instructor feedback, drop their comments or notes into a feedback page. The agent reads them: "Read the feedback from the spring cohort's TA notes. What patterns are they seeing that I should incorporate into the next revision?" You don't lose their observations to email threads.
The compounding return
A curriculum that's been through three revisions in a vault is a different document from one that's been through three revisions in scattered files. The vault version carries the rationale forward. You know why module three is sequenced the way it is, because the rationale is on the page. You know why a lesson was rewritten between cohort two and cohort three, because the revision note explains it.
Five years in, the vault is the institutional memory of the course. A new co-instructor can read it and understand the choices. You can teach it again after a long break and re-orient yourself. The curriculum stays sharper instead of slowly losing fidelity to its original intentions.
Try Docapybara free — sign up, drop in your current curriculum outline and the notes from your last delivery, and ask the agent what revision pattern it sees.