> For the complete documentation index, see [llms.txt](https://help.onform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.onform.com/sports/golf-analysis/beginners-guide-to-kinematic-sequence.md).

# Read a kinematic sequence

What a golf kinematic sequence shows, the order the pelvis, torso, arms and club should speed up in, and how to open and read the Kinematic Sequence chart in Onform on iPhone and iPad.

Works on: iPhone and iPad, for golf swings filmed face-on. It works best on newer-generation iPhones and iPads; on older ones it still works but may be slow to create.

A kinematic sequence shows how fast each part of the body rotates through the swing, and in what order. In a powerful, efficient swing, speed builds from the ground up: the pelvis speeds up first, then the torso, then the arms, then the club, each one faster than the one before. Onform draws this chart from the 3D it makes of your swing, so you can see the sequence without sensors.

## How it works

### Four lines, one for each body part

The chart has four colored lines:

| Line          | Color  | What it shows                    |
| ------------- | ------ | -------------------------------- |
| **Pelvis**    | Blue   | How fast the hips rotate.        |
| **Torso**     | Purple | How fast the upper body rotates. |
| **Arm**       | Orange | How fast the arms rotate.        |
| **Club Head** | Green  | How fast the club rotates.       |

The height of each line is rotation speed in degrees per second, not ball or club speed in miles per hour. The bottom of the chart is **Swing Phase**, from the start of the swing (0) to the end (1).

### Swing positions

Gray dashed lines mark positions in the swing:

* **P3:** lead arm parallel to the ground in the backswing.
* **P4:** the top of the backswing.
* **P5:** lead arm parallel to the ground in the downswing.
* **P7:** impact.

### The order of the peaks

Each line has a peak, the moment that part of the body is rotating fastest. Onform marks each peak after the top of the backswing with a letter: **P** for pelvis, **T** for torso, **A** for arm and **C** for club. The top corner of the chart shows the order they peaked in, such as **P - T - A - C**.

### Reading the chart

* **The ideal order is P - T - A - C.** Each part peaks a little after the one before it, and each peak is higher than the one before. That's the body passing speed up the chain, like cracking a whip.
* **Peaks out of order** suggest a part is starting too early, for example the arms or torso firing before the hips have led the way.
* **Peaks that barely rise** from one part to the next mean that part isn't adding much speed. For example, a torso peak only just higher than the pelvis peak means the torso isn't adding much.
* **Play the video** to see the values at each moment: a line on the chart follows the playhead and shows each part's speed.

Use the chart to compare swings over time, or before and after a change, rather than as a single score. For a longer introduction, see the [beginner's guide to the kinematic sequence](https://onform.com/blog/beginner-guide-kinematic-sequence/) on the Onform blog.

## Open the kinematic sequence in Onform

1. Open a golf swing filmed **face-on** at 120 fps or higher.
2. Tap the **AI tools** button (the sparkles icon) at the top.
3. Tap **Show Kinematic Sequence (FO only)**. If the swing has no 3D yet, Onform makes it first.

You can also tap the small button at the left of a panel and choose **Kinematic Sequence**. The panel then shows **KS**.

## What it needs

* **A face-on full swing**, filmed at 120 fps or higher, with the golfer's whole body in the picture. Down-the-line swings don't have a kinematic sequence.
* **The club head in the picture for the whole swing**, for the club line. If the club leaves the frame, the club line can be missing or off.
* **A plan with 3D**: Coach Pro or Individual Premium. If you see **Kinematic Sequence is locked**, see [3D questions and problems](/sports/golf-analysis/3d-faqs.md).

If you see **Kinematic Sequence Unavailable**, the message underneath says why. The most common reason is a swing filmed from another angle.

## What this means for you

* **For coaches:** the sequence shows *why* a swing looks the way it does on video. Pair it with the video and the body metrics, and record a Voice-over to walk your golfer through it.
* **For golfers:** look for the order first, then how much each peak builds on the last. Your coach can tell you which part to work on.

## Related

* [Analyze a swing in 3D](/sports/golf-analysis/using-3d-data-and-visualization.md)
* [3D questions and problems](/sports/golf-analysis/3d-faqs.md)
* [About Onform's 3D model](/sports/golf-analysis/model-card.md)
* [Record a Voice-over](https://github.com/Onform-Inc/onform-docs/tree/main/coaching/analyze/how-to-record-a-voiceover.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.onform.com/sports/golf-analysis/beginners-guide-to-kinematic-sequence.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.