Skip to content

Method

Run composition: difficulty, variety, execution, flow, amplitude where applicable

An overview of what judges look at in a run: difficulty, variety, execution, flow and amplitude where applicable.

GLOSSARY

A strong run combines hard tricks with variety in direction and type, clean execution, smooth flow between features and, in pipe and big air, height.

Context and distinction

Each criterion has its own entry; which ones apply depends on the discipline's rules.

Explore the glossary →

HOW TO DO IT

Run composition: difficulty, variety, execution, flow, amplitude where applicable

This page applies the competition knowledge and preparation framework to Run composition: difficulty, variety, execution, flow, amplitude where applicable. Treat the listed dimensions separately rather than assigning one universal cue to the whole topic. Different snowboard formats reward different performance and use different rules. A historical judges' definition can inform terminology without being the current event rule.

Preparation and setting

Use the setting and competence boundary below. This is a page-level learning/application text; use the exact linked movement for reproduction instructions.

Execution / application sequence

  1. State the page-specific task and the conditions in which it is being attempted.
  2. Separate difficulty, variety, execution, flow, amplitude where applicable as individual observations.
  3. Identify the actual discipline, organizer and season.
  4. Read the applicable current rulebook and event instructions.
  5. Separate judging categories from physical execution.
  6. Choose an existing controlled task for practice.
  7. Compare runs under recorded conditions.
  8. Review the result without treating one score as a universal rider level.

Learning and practice

Use dated rules and event-specific rehearsal. No numeric eligibility, equipment or penalty threshold is inferred here.

Errors, limits and corrections

Mixing pipe, big-air, race and freeride criteria creates false standards.

Observable checks

The page-specific task, conditions, known components and missing procedure can be explained. Successful application is checked in the actual task, not inferred from reading.

01

editorial review notes

Imported from the supplied editorial package; technical and coaching review remains required.