AI Skill Report Card
Managing Online Embroidery Course Programs
Quick Start13 / 15
To document or set up an online class program, produce these core pieces:
- Program overview - what the online format includes (lessons, schedule, discussion forum, teacher access)
- FAQ organized into: Before you register / After you register / Technical issues
- Two-list catalog structure: "Open Registration or Coming Soon" and "In Progress or Previously Offered"
- Per-class page template (see below)
- Skill level definitions (Basic/Intermediate/Advanced/All levels)
Recommendation▾
Add more concrete examples with actual input/output text pairs (e.g., a full sample FAQ entry, a complete filled-out class page) rather than mostly describing the structure abstractly
Per-Class Page Template
Online Studio Class [#]: [Title] with [Teacher Name]
[Status badge: Open Registration | Coming Soon | Closed Registration | Previously Offered]
Taught by [Teacher Name] (view bio)
[2-4 sentence teacher bio: credentials/certifications, teaching
history/venues, specialty, notable achievements or publications,
optional teaching philosophy quote, website link]
[1-3 sentence project hook - what it is, why it's appealing]
[2-4 sentence project description: technique(s) taught, materials/
fabric/thread specifics, customization options (colorways, sizing),
what's included if kitted]
Registration dates: [Month Day, Year - Month Day, Year]
Class schedule: [Month Day, Year - Month Day, Year, or lesson posting dates]
Workflow13 / 15
Progress:
- Define program mechanics (lesson delivery, discussion forum, access rules)
- Write FAQ in three sections (pre-registration, post-registration, technical)
- Define skill level categories
- Build class catalog split into active/upcoming vs. closed/past
- For each class: status, teacher bio, project description, dates
- Cross-link: class page → discussion group → lessons → teacher bio
- Add membership/eligibility gating notes (e.g., active membership required)
Recommendation▾
Include an example of the 'bad outcome' - e.g., a poorly written ambiguous class status or date range - to contrast with the good version
Key Structural Rules
- Status drives visibility: every class has exactly one status — Open Registration, Coming Soon, Closed Registration, or Previously Offered. Never leave status ambiguous.
- Registration window is always separate from class schedule window and both are always stated as explicit date ranges, never relative ("next month").
- Membership gating: state plainly that an active account/membership is required both to register AND to retain access throughout the class run — note the consequence (lost access) if membership lapses.
- Non-refundable policy (if applicable) gets its own explicit FAQ line, not buried in terms.
- Teacher access window is finite and explicit: state start trigger (e.g., "first lesson posted") and end trigger (e.g., "two weeks after last lesson").
- Discussion/community access window is longer than teacher-active window — state both separately (e.g., community access runs to two months post-final-lesson; teacher stops answering at two weeks post-final-lesson).
- Kit shipping timing is relative to class start, not registration ("kits ship 1-2 weeks before class start"), and shipped by teacher, not org, if that's the actual logistics.
Examples12 / 20
Example 1: Input: A teacher bio draft that's just a list of credentials. Output: Rewritten into flowing bio: credentials → teaching venues/history → current specialty/focus → notable recognition (awards/publications) → optional philosophy quote → website. Keep to 3-5 sentences max; link full bio separately via "(view bio)".
Example 2: Input: "We need an FAQ for people confused about when they can see lessons." Output: Two FAQ entries:
- "When do I get access to the lessons?" → Lessons post per the schedule on the class page; discussion group access begins immediately upon registration so students can start interacting before lesson 1 drops.
- "Where will I see the lessons?" → Course Content section at the bottom of the class page, once posted.
Recommendation▾
The niche focus on embroidery specifically limits reuse; consider whether this should be genericized to 'craft course programs' or lean further into embroidery-specific terminology (stitch counts, fabric types) for added value
Best Practices
- Always pair a project's required skill level with the Basic/Intermediate/Advanced/All-levels rubric — don't invent new tiers.
- When a class has no kit, explicitly say so and clarify what the student must source themselves (fabric count, thread type/size, color freedom).
- Use "Coming Soon" classes to capture interest: offer a "sign up for reminder" mechanism rather than leaving the page static.
- Keep teacher-answers-question window and discussion-group-open window as two distinct, clearly different durations — don't conflate them.
- Always state login/membership status requirement next to any "where do I find X" instruction, since access errors are the top support issue.
Common Pitfalls
- Don't merge registration dates and class schedule dates into one ambiguous range — these are different windows and both must appear.
- Don't describe kit shipping relative to registration date; it's relative to class start date.
- Don't forget to state the non-refundable policy explicitly if it exists — silence here creates support tickets.
- Don't let "Closed Registration" and "Previously Offered" collapse into one status — closed-but-upcoming (already full/past deadline, not yet run) is different from fully completed/archived.
- Don't bury the membership-required-to-register-AND-to-maintain-access rule inside a long paragraph; it needs to be its own clear FAQ answer.