Build and Standardize Your Swim School Curriculum

A swim-school curriculum is more than a list of skills. It explains how swimmers move through a program, what readiness looks like, how instructors introduce and develop each skill, and how lessons create enough practice for progress. When that information is scattered across documents, the curriculum may be clear to its author but difficult for the wider team to apply.

SmartMoves gives the curriculum an explicit structure. A school can create programs for different audiences or purposes, divide each program into levels, connect skills to those levels and attach lesson plans, activities, teaching notes, videos and resources where they are needed. The hierarchy can reflect the school’s existing terminology rather than a universal template imposed by the software.

Making the structure visible also exposes gaps. A level may contain too many unrelated outcomes. Two skills may describe the same expectation in different language. A lesson sequence may not provide enough opportunities to observe a key skill. Those are curriculum decisions, not software errors, but a connected system makes them easier to see and discuss.

Each level should have a reason to exist. Its name may be playful or operational, but the team needs a plain-language purpose: who the level is for, what swimmers are expected to bring into it and what meaningful change they should demonstrate before moving forward. A level with an unclear purpose tends to accumulate unrelated skills and becomes harder to teach consistently.

Skill statements should describe something an instructor can observe. “Water confidence” is an important aim, but it is broad. Supporting statements might describe entering the water with an agreed level of assistance, placing the face in the water while breathing out, or maintaining a supported body position. The exact wording depends on the school’s teaching model and should be reviewed by experienced aquatics staff.

Progression does not need to imply that every swimmer develops in a perfectly linear way. A useful curriculum can show prerequisites and relationships while allowing instructors to respond to individual needs. SmartMoves provides a place to record the approved structure and the evidence language your team uses; it does not replace instructor observation.

Keep the hierarchy as simple as the program allows. Deep nesting can make content harder to find, while an overly flat structure hides relationships. A practical test is whether a new instructor can locate the next class plan and understand why its activities belong there without a separate explanation from the curriculum author.

A skill ladder tells the team where swimmers are heading. Lesson plans describe how the school creates appropriate practice on the way there. Connecting the two prevents lesson planning from becoming a separate library of entertaining ideas with no clear relationship to the program.

A lesson guide can identify its focus skills, activity order, equipment, teaching cues and adaptations. Reusable activities can appear in more than one plan when they serve a clear purpose. Videos and supporting resources should sit close to the point of use so instructors do not need to search a separate training library while preparing for class.

The connection also improves curriculum review. If a skill rarely appears in lesson plans, the team can ask whether the sequence provides enough practice. If an activity is used often but produces inconsistent results, managers can clarify its description, add a demonstration or observe how different instructors deliver it.

SmartMoves includes public lesson examples that show this relationship in practice. They are examples of one program structure rather than a universal prescription. Your own school can keep its preferred terminology, teaching methods and approval process.

Standardization does not mean freezing a curriculum forever. Good programs improve as teams observe swimmers, coach instructors and review outcomes. The operational question is how an idea becomes an approved change. Without ownership, several versions can circulate at once and instructors may not know which one to follow.

Define who can propose, review and publish changes. Record enough context that future managers understand why a decision was made. Larger organisations may keep core level outcomes centrally controlled while allowing locations to contribute activities or local notes. Smaller schools may use a simpler approval process, but the responsibility should still be clear.

When an update is published, instructors need practical communication: what changed, why it matters and when to use the new version. Instructor development should reinforce significant changes rather than assuming that access equals understanding. SmartMoves keeps the updated material in the teaching workflow so the approved version is easier to find.

Review the curriculum on a deliberate cycle and also when evidence suggests a problem. Repeated confusion about a skill, frequent ad hoc lesson changes or inconsistent progress decisions can all indicate that the written structure needs attention.

Keep a short decision record for material changes. Note the issue, the people consulted, the agreed update and any instructor support required. This gives future program managers useful context and prevents the same debate from restarting when staff change. It also distinguishes an intentional curriculum decision from an accidental edit.