Use Claude for lesson planning as a drafting step, not as an instructional authority. Give it an approved curriculum source, a measurable objective, classroom constraints, and the lesson format you need. Then check the draft mechanically, review it as the teacher, and store only the approved version for reuse.
For example, a Grade 7 science teacher planning a 50-minute food-web lesson can provide the objective, printed materials, no-device rule, vocabulary requirements, and preferred teaching sequence. Claude can propose activities and questions, but the teacher still verifies facts, standards alignment, accessibility, safety, pacing, and local feasibility.
This article presents a teacher-owned workflow with a structured output contract, deterministic checks, a human approval gate, and an optional ClickUp storage pattern. The ClickUp pattern is a configurable architecture, not a documented turnkey lesson-planning integration.
How to use Claude for lesson planning
A reliable workflow separates stable teaching context from the needs of one lesson. Use a Claude Project for recurring instructions and supplied reference documents when that feature is available to you. Use the individual lesson prompt for the objective, duration, student needs, materials, and constraints that change from lesson to lesson.
The basic sequence is simple: prepare the source pack, generate a structured draft, run mechanical checks, review the lesson as its teacher, and save the approved version. The source selection, instructional judgment, and release decision remain with the educator.
Prepare the context Claude needs
Before prompting, identify the grade level, subject, class duration, measurable objective, relevant standard, prior knowledge, available materials, technology limits, instructional model, and required lesson components. A useful objective describes what students will produce or demonstrate, not only what topic they will encounter.
Describe student needs in general instructional terms where possible. For example, specify that the lesson needs language scaffolds, additional processing time, or an extension task without including names or unnecessary personal details. Follow school and district policy before uploading student records, full IEPs, medical information, or sensitive accommodation details.
Claude Projects are self-contained workspaces with project instructions, chat histories, and supplied knowledge. Anthropic documents Projects for paid plans. They do not automatically connect Claude to school systems, so the teacher must supply the relevant material or use an approved connection.
Anthropic lists PDF, DOCX, CSV, TXT, HTML, ODT, RTF, EPUB, JSON, and XLSX among supported upload formats. Its current guidance states that chat uploads are limited to 30 MB per file and up to 20 files per chat. Project knowledge has separate context conditions, and non-PDF files are processed as text, so embedded images in those files are not interpreted. Check the current upload guidance before relying on a particular file.
The more consequential the instructional decision, the more important it is to preserve the source, the reviewer, and the reason for the final decision.
Prompt for a usable, structured lesson draft
Ask for observable fields rather than only a polished narrative. Include the audience, measurable objective, duration, standard and source, instructional model, available materials, constraints, and required segments. For each segment, request minutes, teacher actions, student actions, and a check for understanding. Ask Claude to flag assumptions or factual claims that need verification.
A lesson-specific prompt might say:
Draft a 50-minute Grade 7 life science lesson using the supplied district guide. Objective: students explain how matter moves through a simple food web using evidence from a diagram. Use a brief model, guided analysis, and an independent exit response. Materials are a projector and printed food-web diagram; students do not have devices. Include a vocabulary scaffold. For each segment, give minutes, teacher action, student action, and a check for understanding. Identify claims or assumptions the teacher should verify. Return the requested fields and mark the plan Draft.
The following output contract is an editorial example, not a built-in Claude feature. It includes separate fields for a lesson record, review metadata, and source provenance. If another system will receive the result, validate the JSON syntax and required fields before creating or changing records.
{
"lesson_key": "course-42_unit-3_lesson-2_curriculum-2026-27",
"lesson_title": "Matter in a Food Web",
"lesson_duration_minutes": 50,
"learning_objectives": [
"Explain how matter moves through a food web using diagram evidence."
],
"standards": [
{
"identifier": "Teacher to verify",
"source": "District science guide, 2026-27"
}
],
"materials": [
"Projector",
"Printed food-web diagram"
],
"lesson_segments": [
{
"segment_name": "Warm-up",
"minutes": 5,
"teacher_action": "Display a food-web question.",
"student_action": "Write an initial explanation.",
"check_for_understanding": "Scan responses for a starting idea."
},
{
"segment_name": "Model and guided analysis",
"minutes": 25,
"teacher_action": "Model tracing matter through the diagram.",
"student_action": "Annotate the printed diagram with guidance.",
"check_for_understanding": "Ask students to explain one connection."
},
{
"segment_name": "Independent response and exit check",
"minutes": 20,
"teacher_action": "Give the response prompt and review answers.",
"student_action": "Write an explanation using diagram evidence.",
"check_for_understanding": "Review the exit response against the objective."
}
],
"differentiation": {
"language_support": ["Provide a vocabulary bank and sentence starter."],
"accessibility_review_needed": true,
"extension": "Teacher to define after reviewing the core task."
},
"assessment": "Independent explanation using evidence from the diagram.",
"source_materials": [
{
"title": "District science guide",
"version_or_date": "2026-27"
}
],
"factual_claims_to_verify": [],
"review_status": "Draft",
"reviewer": null,
"reviewed_at": null
}One approved lesson is not the same thing as one generation attempt, citation, or review event. Keep a lesson record, generation_run record, citation records, and review records separate so repeated drafts and multiple sources do not overwrite the approved plan or distort later reporting.
Run checks, then review the lesson as its teacher
Start with rules that do not require instructional judgment. Add each segment’s minutes and compare the total with the stated class duration. Require non-empty objective, materials, assessment, and source fields when your format calls for them. Check that the activities do not ask students to use devices when the prompt says there are none. If software will read the response, validate JSON syntax, required keys, and values such as review status against an allowed list.
Then walk through the plan as the teacher. Check factual claims against the supplied curriculum or another trusted source. Verify the standard identifier and version. Consider developmental fit, accessibility, applicable accommodation procedures, safety, transitions, pacing buffers, and classroom routines. Ask what students will produce, what evidence shows understanding, what happens if technology fails, and what you will do if the class is confused.
Differentiation suggestions are prompts for professional adaptation, not evidence of IEP compliance. A polished plan can still contain unsupported claims, an unrealistic sequence, or an activity that cannot be delivered with the available resources.
Keep the plan in Draft until a named educator has reviewed it. If the school shares plans, record the reviewer and review date with the approved version. Escalate disputed standards, sensitive accommodation questions, or safety-critical activities to the appropriate curriculum or school reviewer.
- Segment minutes total the stated class duration and leave a workable transition buffer.
- Objectives, materials, assessment, source version, and required lesson fields are present.
- Claims and standards have been checked against the cited curriculum version.
- Activities fit available resources and include a response to likely technology failure.
- Accessibility, language support, accommodations, and safety have received the appropriate review.
- A named educator has approved the version and the review date is recorded.
Save and reuse approved plans without losing context
Choose one system of record for approved plans and use a consistent name based on course, unit, lesson number, and curriculum version. Keep the source document or a stable link with the plan. Add a source version or snapshot so a later curriculum edit does not silently change the evidence base for an older lesson.
ClickUp is one configurable option. A task can hold planning metadata and preparation work, while a linked Doc can hold the detailed lesson. Teams can configure Custom Fields for subject, grade, unit, duration, standards identifiers, source version, and review status. Subtasks can track materials or assessment preparation, and assigned comments can support a teacher review handoff. These are organization and collaboration capabilities; the team defines the lesson fields and approval process.
ClickUp’s Class Planning Template is an organizational template for class-planning tasks, fields, views, statuses, and resources. It is not documented as a Claude lesson generator, educational validation workflow, approval system, or duplicate-prevention mechanism.
For teams configuring a shared planning workspace, ClickUp consulting and workspace design may help with decisions about where lesson records, documents, and review work should live.
Use a safe identity and write process for integrations
If a compatible assistant is connected to ClickUp through its separately configured MCP option, ClickUp documents capabilities such as searching work, creating or enriching tasks, posting comments, and retrieving information. OAuth is required, and available tools, permissions, rate limits, plans, and model choices depend on the current setup. Verify the connection before relying on write-back, and keep generated edits as drafts or comments until a teacher approves them.
Do not define the lesson identity as only a title, calendar date, teacher name, prompt, or model name. Those values can repeat across drafts and curriculum versions. A proposed lesson key can combine the school or workspace identifier, course, unit, lesson number, and curriculum version:
lesson_key = hash(
school_or_workspace_id +
course_id +
unit_id +
lesson_number +
curriculum_version
)This key identifies the lesson record, not every event associated with it. A useful grain model is:
- lesson_record: one approved or archived lesson plan.
- generation_run: one Claude generation or revision attempt, with prompt and model details where permitted.
- citation_record: one source attached to a lesson or claim.
- review_record: one human review event with reviewer, outcome, and timestamp.
- usage_summary: an aggregate over a defined period, not a substitute for the underlying events.
A search-then-create sequence is not safe when two runs can execute concurrently. Use a database-enforced unique constraint or a transactional upsert in the integration layer. If the destination cannot provide that guarantee, maintain an external idempotency ledger that maps the lesson key to the destination record, generation run, and write status. Do not assume that MCP or a template supplies race-safe duplicate prevention.
For teams configuring fields, permissions, and review handoffs, ClickUp setup and automation support may be relevant. Treat the lesson schema, validation rules, approval statuses, provenance model, and idempotency control as proposed implementation design rather than vendor-provided lesson functionality.
Choose AI for drafting and rules for predictable checks
Use Claude for language and idea generation. Use ordinary rules for values that must be exact. Keep the teacher as the owner of instructional decisions.
- Draft questions, examples, or explanations: Claude can propose language using supplied curriculum context. The teacher checks content and fit.
- Confirm that minutes equal class duration: An arithmetic rule sums the segment fields. The teacher revises the pacing and buffer.
- Set grade, subject, date, or status: Controlled fields and allowed-value checks prevent inconsistent metadata.
- Detect an existing lesson record: A stable key plus a unique constraint or transactional upsert protects against concurrent duplicate creation.
- Approve standards fit, access, or safety: A teacher or designated school reviewer makes the decision, not an AI label.
ClickUp documents AI tools and models from Anthropic, OpenAI, and Google, including Claude, ChatGPT, and Gemini. Model availability depends on Workspace configuration, plan, role, region, and current product conditions. AI credit use also varies by feature, model, context, and actions, so do not convert vendor credit limits into a fixed number of lesson prompts.
A small pilot can measure missing fields, timing errors, infeasible material requests, factual corrections, review effort, revision count, and duplicate records. Define the sample and evaluation criteria before comparing results; do not promise a time saving in advance.
Frequently asked questions
Can Claude use curriculum files?
Yes. A Claude Project can use documents supplied to its knowledge base as context for project chats, subject to plan, file, and context conditions. This does not give Claude automatic access to school systems. See Anthropic’s Projects guidance and current file documentation for applicable limits.
Can Claude create an accurate lesson without review?
No. It can produce a structured draft, but a teacher must verify factual claims, standards, timing, access needs, safety, and classroom feasibility before approval.
Can ClickUp Brain use Claude?
ClickUp documents models from Anthropic, OpenAI, and Google, including Claude, ChatGPT, and Gemini. The choices available to a particular Workspace can vary, so check the current model selector, plan, role, and regional availability.
Does the Class Planning Template include AI checks?
The template page describes class-planning organization with tasks, fields, views, statuses, and resources. It does not document Claude generation, educational validation, approval, source versioning, or duplicate prevention.
How should I handle student information?
Use general instructional categories instead of names or unnecessary sensitive details. Do not upload full IEPs, medical information, behavior records, or identifiable student work unless the school has approved the tool, configuration, data handling, and applicable procedures.