Your kid spent the last three weeks obsessed with how bridges don't fall down, building models out of popsicle sticks and asking increasingly specific questions about tension and compression. That's exactly what unschooling is supposed to look like. Then your state's annual portfolio review or your umbrella school's reporting form shows up, asking for something that maps to "subjects" and "objectives met" — and suddenly the thing that worked because it followed your kid's real curiosity has to get translated into language that sounds like a school district wrote it.
The tension isn't imaginary
Unschooling works because it doesn't start from a predetermined scope and sequence. State reporting requirements, even the loose ones, usually want to see evidence of progress against something. Trying to force the bridge-building weeks into a rigid subject-by-subject curriculum document after the fact often kills the thing that made it work in the first place — you start planning for the report instead of following the kid.
Documenting after the fact, not planning ahead of it
The fix isn't picking a curriculum. It's building a habit of translating what already happened into the language a reviewer needs, without changing how the learning actually happened.
1. Keep a running, low-effort log as things happen, not a lesson plan. A few sentences a week — what your child got into, what they made, what they asked about — is enough raw material. Ask AI to help you draft this log entry from a couple of bullet points if writing it out feels like a chore; the goal is capturing it while it's fresh, not writing beautifully.
2. Translate after, not before. Once you have a few months of log entries, ask AI: "Here's what my child actually did this quarter. Map this to [your state's required subject areas] and identify what's genuinely covered versus what's thin." This tells you where a real gap exists versus where the requirement is just asking for different vocabulary.
3. Fill genuine gaps with more interest-led material, not workbooks. If the mapping shows almost nothing under "written expression," that's useful information — look for a way to fold writing into whatever your child is already into, rather than bolting on an unrelated worksheet just to check a box.
4. Write the formal report last, from the log. The document a reviewer sees should be a faithful translation of what happened, generated from your actual notes — not something written from scratch to sound impressive, which is both more work and less true.
What a good log entry actually needs:
- What the child was doing (specific, not "science")
- What they asked or figured out on their own
- Anything they made, wrote, or explained to someone else
Where our tools fit
Our [unschooling / interest-led plan](/unschooling-plan) tool is built around this same follow-the-interest structure, helping turn what a child is already curious about into a documented plan without imposing a curriculum on top of it. For the state-specific reporting side, our [homeschool planning](/homeschool-plan) tool covers what's actually required versus optional so you're not over-documenting to be safe.
What still needs your judgment
- Your state's actual rules, not a general template. Requirements vary widely by state and even by umbrella school — confirm what's genuinely required before assuming a template covers you.
- Not over-translating. It's tempting to dress up every activity in academic language for the report; keep the log honest so the translation stays honest too.
- Protecting the actual learning. If documentation starts changing what your child does day to day, the paperwork has started running the show — the log should describe the learning, not direct it.
