A homeschool co-op planning committee doesn't reject a class idea because it's boring. Most of the time they table it because the proposal answers the wrong questions - it describes what the class is about, when what the committee actually needs to know is whether it's logistically workable: how many families can fit, what it costs, who's supervising, and what a family walks away with. A proposal that leads with excitement about the topic and never gets to those four things gets a "let's revisit next semester," which is a polite no.
What a committee is actually evaluating
Every co-op has slightly different priorities, but almost every planning committee is running the same checklist in their head, whether they say so out loud or not:
1. Capacity - minimum and maximum students, and what happens if enrollment falls short
2. Cost - materials fee per family, and whether it's collected by you or the co-op
3. Space and supervision - what room or setup it needs, and whether a second adult is required
4. Deliverable - what a family can point to at the end (a project, a skill, a portfolio piece) that justifies the semester
A proposal that's three paragraphs about why the topic matters and never states a max enrollment number is asking the committee to guess the answer to the question they actually care about most.
Structuring the packet so it's skimmable in two minutes
Most co-op committees are volunteers reviewing proposals in a single evening alongside a dozen others. A packet that requires a full read to find the enrollment cap will get set aside for one that puts it in a header. Lead with a one-line summary block - grade range, class size, cost, and day/time - before a single paragraph of description. Committees approve what they can evaluate fast.
Drafting the packet with AI
Once you know the four questions to answer, a model is genuinely useful for turning your rough notes into a structured packet in the co-op's expected format. Try:
- "I want to propose a [topic] class for our homeschool co-op. Here's what I'm thinking: [rough notes on grade level, format, materials]. Write a one-page proposal with a summary header (grade range, class size, cost, schedule) followed by a short description, a materials list, and what students will have produced by the end of the semester."
Build it out inside the [co-op class tool](/coop-class), and if the class doubles as something you'd want to eventually offer beyond this one co-op, keep your notes structured the same way you would in the [course curriculum tool](/course-curriculum) - a proposal you write once for internal approval is most of the way to a standalone course description later.
A quick before/after
Before: a paragraph about why 3D printing is a great skill for kids to learn, with the class size and cost buried in sentence four.
After: "Intro to 3D Printing — Grades 6-9 — Max 8 students — $35/semester materials fee — Tuesdays 1-2pm — Students design and print one original object per month, portfolio of 4 by December."
What still needs your judgment
- Read the room first. A co-op that's tight on classroom space will weigh the space/supervision line heavier than cost - ask a committee member informally what's blocked past proposals before you submit.
- Don't overpromise the deliverable. A vague "students will learn a lot" is weak, but promising four finished projects you can't realistically deliver in a semester is worse - commit to what's actually achievable.
- Resubmit, don't abandon. A tabled proposal usually just needs the missing logistics answered, not a whole new topic - go back with the specific numbers the committee was missing.
