
Build a sequence in the order a picture is built, not the order a stepsheet is read. Block the counts first as a rough pass, settle the count and the walls, then add the detail of arms, styling and timing. Detail added before the shape is settled is the part you have to undo.
A stepsheet is read from the top down, one line at a time, and that reading order tempts you to write the dance the same way. A dance is not built that way. Think of how a painting is built up: the painter blocks the whole canvas in rough shapes before any small mark is made, because a small mark placed on a wrong shape has to be removed. A sequence behaves the same. The rough pass is the whole dance in counts, held loosely, before any of it is polished.
In which order should you build a sequence?
Build it in three passes, in this order: rough pass, then count, then detail.
The rough pass is a block of counts. You write the eight counts of a wall as a shape, not as a finished phrase. You are asking whether the weight changes on the right count, whether the turn lands on a wall, whether the tag fits at the end. Nothing in this pass is meant to be danced well. It is meant to be danced at all, so you can feel where it breaks.
The count pass is where the shape becomes a dance. You fix the counts against the music, check the walls, and confirm that the restart falls where the phrase restarts. This is the pass that decides whether the sequence works. Most of the work lives here, and it is quiet work: counting, walking, counting again.
The detail pass comes last. Arms, head, styling, the small hold that makes a phrase feel finished. These are real decisions, but they are decisions about a shape that already stands. Add them earlier and you are decorating a wall that may move.
The order matters because each pass answers a different question. The rough pass asks whether the dance can exist. The count pass asks whether it fits the music. The detail pass asks whether it looks like anything. Answer them out of order and you answer the last question first, which is the most expensive way to work.
What is the rough pass that comes before detail?
The rough pass is the whole sequence written in counts only, with no styling and no polish, held together well enough to walk through from the first wall to the last.
It is rough on purpose. In the rough pass you allow yourself to write counts you are not sure about, because the point is to see the whole shape at once. A rough pass of thirty two counts tells you immediately whether the dance has a beginning, a middle and an end. A polished eight count tells you nothing about the other twenty four.
The rough pass is also where the rewrite happens. When a block of counts does not survive, you replace the block, not the dance. The record of a sequence shows this clearly: the rough block of counts is often the part that survives a rewrite untouched, while the detail around it is what changes. The counts are the load bearing structure. The styling is the plaster.
Keep the rough pass short. Write it in a notebook, on the back of a stepsheet, in a phone note. Do not format it. Formatting is a detail pass in disguise, and it slows down the part of the work that needs speed.
Why does detail added too early have to be undone?
Because detail depends on the shape, and the shape is not final until the count pass is done.
If you set the arms on count three and then move the turn to count five, the arms are wrong. If you style the tag before you know the tag is needed, the styling is wasted. If you teach the detail to a class before the counts are settled, the class learns a version that will change, and changing a learned version is harder than teaching it once.
There is a second cost. Detail is persuasive. A phrase with good arms feels finished, and a phrase that feels finished is hard to question. Dancers stop counting and start performing, and the fault in the counts hides under the styling until a wall goes wrong in front of an audience. The rough pass has no such hiding place. It is ugly, and ugliness is honest.
The practical rule is simple. If a change would alter the counts, it belongs to the count pass. If a change would only alter how the counts look, it belongs to the detail pass. When you are unsure which pass you are in, you are in the count pass.
How do the three passes survive a rewrite?
A rewrite touches one pass at a time, and the rough block of counts is usually the last thing to move.
Start a rewrite at the top. Walk the rough pass again and ask whether the shape still works. If it does, the rewrite is a count problem, and you work inside the count pass. If it does not, you are back in the rough pass, and the detail you had built is set aside rather than defended. Setting it aside is not losing it. Most of it returns once the new shape is settled, and the parts that do not return were never load bearing.
This is why a written record helps. Keep the rough pass, the count pass and the detail pass as separate notes rather than one finished sheet. When a rewrite comes, you can see which layer moved. A single finished sheet hides its own history, and a hidden history makes every change feel like starting again.
Walls are the clearest test. A sequence that changes walls in the count pass will change its tags and restarts too. Do that work before the detail pass and the detail pass is short. Do it after and the detail pass is a second rewrite.
Where does the music fit in the order?
The music belongs to the count pass, and it is the reason the count pass exists.
The rough pass can be counted aloud without music. That is its advantage: you hear the shape of the counts, not the shape of the track. Once the rough pass holds, bring in the music and fit the counts to the phrase. This is where you discover that a block of eight counts sits across a musical break, or that the chorus starts one count earlier than you assumed.
Do not fit detail to the music before the counts fit. Styling that follows a lyric is pleasant, and it is the first thing to break when the counts move by one. Fit the counts, then fit the styling to the counts, and let the music carry both.
A short routine for building in layers
Write the rough pass in counts only, thirty two counts or sixty four, and walk it once without music.
Fix the counts against the track, check the walls, and mark where the tags and restarts fall.
Add detail last, one phrase at a time, and only after the phrase before it is settled.
Keep the three passes as three notes. When something breaks, return to the pass that owns the problem, not to the finished sheet.
The order is the method. Rough pass, count, detail. A sequence built in that order is easier to teach, easier to fix and easier to hand to another dancer, because the shape underneath it was never in doubt.
01
Notice the pattern
Build a sequence in the order a picture is built, not the order a stepsheet is read. That is why the useful question is not whether you look like everyone else. It is whether you can describe the next action in a way that lets you repeat it. A step sheet may use a compact token, while a teacher may use a spoken cue. The Step Decoder keeps both close to the physical action.
02
Try one clean version
Block the counts first as a rough pass, settle the count and the walls, then add the detail of arms, styling and timing. Begin at a pace that allows you to hear your own count. Keep enough clear space to stop, reset and begin again. If a local instructor gives a different convention, their room-specific direction wins for that class.
03
Check the next foot
Before moving on, pause and identify your facing direction, supporting foot and next count. This is a better self-check than rushing through a longer sequence. It also makes the weight-transfer guide useful even when the term first feels technical.
For a first class, pair this page with what to expect in the room. For home practice, use the four-week practice route to keep the next decision manageable.
Source consulted for this note: vam.ac.uk.
Sources and scope
Source note: terminology and level guidance are compared with Linedancer, CLDAA, Kickish and canonical step-sheet metadata. Wording here is an original explanation.
Last reviewed 16 September 2026. Read the full method and sources, or email a terminology correction to [email protected].