Skip to content

RoboticsMuse Curriculum

Purpose

RoboticsMuse provides a common training framework for teams that want technical rigor, clear progression, and consistent expectations across seasons. The curriculum is designed for:

  • middle school students preparing for FTC or entering an FRC pipeline
  • high school students contributing directly on an FRC team
  • mentors and student leaders who need a repeatable way to onboard, train, assess, and advance students

The system is intentionally structured so that one organization can use it across multiple teams while still adapting assignments to local tools, mentor capacity, and robot strategy.

Pathway Model

Every technical pathway uses the same five levels:

Level Name Typical Student Profile Team Expectation
0 Exposure New student with no prior experience Identify parts, vocabulary, safety, and workflow
1 Foundations Beginner ready to perform guided tasks Complete simple tasks correctly with supervision
2 Application Developing contributor Deliver a subsystem task on a real robot or training rig
3 Leadership Experienced contributor Plan work, review quality, and lead a subsystem effort
4 Mentor Veteran student or adult mentor Teach others, define standards, and improve the pathway

Age-Band Guidance

RoboticsMuse is designed to span FTC-prep through FRC:

  • Grades 6-8 / FTC-prep: emphasize Levels 0-2, simplified mechanisms, shorter build tasks, and safety-first supervised practice
  • Grades 9-10 / Early FRC: emphasize Levels 1-2 with selected Level 3 responsibilities
  • Grades 11-12 / Advanced FRC: emphasize Levels 2-4 with leadership, integration, and training responsibilities

Students do not need to progress at the same rate in every pathway. A student may be Level 3 in CAD and Level 1 in Electrical.

Shared Expectations Across All Pathways

Every RoboticsMuse pathway includes:

  • core concepts and theory
  • required skills and prerequisite habits
  • hands-on tasks tied to actual robot work
  • mini-projects or milestones
  • assessments that demonstrate mastery
  • common mistakes and troubleshooting habits
  • expected outcomes that describe what a student can do next

Cross-Disciplinary Competencies

These competencies are mandatory in every pathway, not optional add-ons.

Collaboration Between Subteams

Students are expected to:

  • attend design reviews with at least one adjacent subteam
  • ask for interface requirements early, not after fabrication or wiring
  • communicate constraints in terms other teams can act on
  • hand off work with enough detail that another student can continue it

Examples:

  • Electrical and Programming align on CAN IDs, sensor ports, and diagnostic data
  • Mechanical and CAD align on packaging, service access, and tolerances
  • Manufacturing reviews CAD before stock is cut or CAM is posted

Design Reviews and Iteration

Each major task should move through a lightweight review loop:

  1. define success criteria
  2. propose a concept or plan
  3. review risks and interfaces
  4. prototype or implement
  5. test and document what changed

Students should learn that revision is normal. The goal is controlled iteration, not a perfect first attempt.

Documentation and Communication

Every level requires students to maintain some form of record:

  • engineering notebook or build log
  • wiring diagrams or labeled photos
  • CAD naming conventions and revision notes
  • code comments, README files, and commit messages
  • meeting notes and action items

If a student cannot explain how something was built, wired, programmed, or revised, they have not fully mastered it.

Time Management During Build Season

RoboticsMuse aligns training with the season cadence:

Season Window Training Focus
Spring post-season Reflection, repairs, beginner exposure, mentor documentation
Summer Deep skill-building, tooling, software practice, CAD drills, shop certifications
Fall pre-season Pathway advancement, drivetrain projects, mock reviews, standards alignment
Kickoff to Week 2 Strategy, concepting, prototyping, architecture choices
Weeks 3-5 Integration, subsystem delivery, software bring-up, testing
Weeks 5-Competition Driver iteration, reliability, serviceability, scouting feedback loops

Implementation Principles

Teams using RoboticsMuse should keep four rules in place:

  1. Train on real tools and real interfaces whenever possible.
  2. Assess by demonstration, not attendance alone.
  3. Let students specialize, but require them to understand adjacent workflows.
  4. Promote students only when they can perform reliably under build-season pressure.

Pathways

Core Public References

RoboticsMuse builds on established public resources:

These references should supplement the RoboticsMuse curriculum, not replace local instruction, design reviews, or supervised practice.