“At the same time” means that two sets of instructions overlap during part of the knitting. Individual actions may fall on different rows; only some rows may need both. Keep following each instruction from its own starting point until its stated stopping point.

Read the whole section for your chosen size before starting. The pattern’s notes and legend take precedence over general conventions. The Craft Yarn Council’s pattern-reading guide explains simultaneous shaping and reversing it for a matching piece.

A concrete example

Here is an illustrative flat-knitting exercise on 40 live stitches. Row 1 is the next row of this section, a wrong-side (WS) row; earlier rows and the cast-on are not included. The first decrease is explicitly on row 6, a right-side (RS) row:

“Continue in stockinette. On row 6, decrease 1 stitch at each end. Repeat these decreases every 6th row 4 more times: 5 decrease rows in total.”

  • Row 1 (WS): purl across.
  • Row 2 (RS): knit across.
  • Row 3 (WS): purl across.
  • Row 4 (RS): knit across.
  • Row 5 (WS): purl across.
  • Row 6 (RS): ssk, knit to the last 2 stitches, k2tog. 38 stitches remain.
  • Row 7 (WS): purl across.

Continue purling odd-numbered rows and knitting even-numbered rows in this example. Repeat the decrease row on rows 12, 18, 24 and 30; the counts after those rows are 36, 34, 32 and 30. Each decrease uses 2 stitches and produces 1, so each decrease row removes 2 stitches. The total is 40 − 5 × 2 = 30 stitches. Stop decreasing after row 30 and continue as the pattern directs.

There are five intervening rows between decrease rows. Five times in total includes row 6; five more times after row 6 would mean six decrease rows, ending on row 36 with 28 stitches. An isolated phrase such as “every 6th row” does not establish the first decrease row: find that starting point in the surrounding instructions.

Where this shows up

You may encounter overlapping armhole and neckline shaping. A pattern can start one at a row number and the other when the piece reaches a stated length. Measure from the specified point and follow any instruction about which side to finish on. A length alone does not identify a row: estimating rows needs row gauge and rounding to a suitable whole row, and does not replace checking the actual measurement. Once both schedules are running, some rows may have one decrease, both, or neither.

Also appears when stitch patterns change during shaping. A sweater body might transition from ribbing to cables at the same time as waist increases. Front bands too: “Continue in seed stitch. AT THE SAME TIME, work buttonhole on rows 4, 14, 24, and 34.” The seed stitch carries on. The buttonholes slot in at intervals.

A worked example with two overlapping schedules

This separate flat example follows just one front section with 30 live stitches, with an armhole edge at the beginning of an RS row and a neck edge at its end. Row 1 starts this section on the RS; even rows are WS. On row 1, decrease 1 stitch at each edge. Repeat the armhole decrease every other row 4 more times (5 total) and the neck decrease every fourth row 2 more times (3 total). Use ssk at the beginning and k2tog at the end here; purl the WS rows.

Row RS/WS Armhole Neck Both?
1 RS yes yes yes
2 WS – – –
3 RS yes – armhole only
4 WS – – –
5 RS yes yes yes
6 WS – – –
7 RS yes – armhole only
8 WS – – –
9 RS yes yes yes

The armhole decreases are on rows 1, 3, 5, 7 and 9; the neck decreases are on rows 1, 5 and 9. Both occur on rows 1, 5 and 9, not on multiples of 4. Stitch counts after rows 1–9 are 28, 28, 27, 27, 25, 25, 24, 24, 22. After row 9 both schedules are complete: 30 − 5 − 3 = 22 stitches. No stitches are held or bound off in this example.

These are counts for one section, not a whole garment or both fronts combined. After a neckline divides a piece, record each side’s live stitches and schedule separately. Record held stitches separately from bound-off stitches; held stitches still exist. Follow the pattern for working the sides with separate yarns and for the other side’s mirrored shaping.

Why patterns are written this way

Separating a stitch pattern from its shaping schedule keeps an instruction concise, especially across several sizes. A merged row-by-row plan can still be easier to follow while knitting.

Think of it as two tracks playing simultaneously. Melody and bass line. Each makes sense alone. You play both.

How to keep track

Write the starting row, interval, total occurrences, edge and ending condition for each instruction. A row labelled “next row” means the next row you will work; do not count the last completed row again. Mark setup rows separately and distinguish the garment’s row count from a count restarted at a section or shaping event.

For the table above, your list starts: “Row 1: knit with both decreases. Row 2: purl. Row 3: knit with the armhole decrease only.” Tick off each completed row and each shaping action. If you use two manual counters for intervals, advance both after every completed row while their schedules are active, including rows without shaping. Record completed decreases separately so you know when to stop.

KnitTools’ Row Counter includes multiple counters as a Pro feature. For this method, you can use separate, unlinked counters that you advance yourself. You still interpret the pattern, enter the starting counts and track which actions are due; this is not a promise that the app reads the instructions or creates this merged plan automatically.

Decrease type and symmetry

When two shaping actions happen on the same row, follow the decrease types named in the pattern. If the pattern leaves the choice to you, pair the leans deliberately.

K2tog is a right-leaning decrease. Ssk is a left-leaning decrease. For visible shaping, use the same logic on matching edges so the shaping lines mirror each other instead of drifting in different directions.

When the decreases overlap, work them in the order they appear across the row. Handle the shaping at the first edge, knit across, handle the shaping at the other edge. If both shaping actions are near the same edge, do exactly what the pattern says and check the stitch count before moving on.

Binding off is a different operation from decreasing. In ordinary flat knitting, edge bind-offs are generally worked at the beginning of a row, so matching edges may be bound off on successive RS and WS rows. Do not replace this with decreases at both ends of one row. After turning, the beginning is the opposite physical edge. For neckline or shoulder shaping, follow the specified edge, working direction and method; “left” and “right” garment pieces refer to the wearer.

When intervals collide

Intervals alone do not tell you where actions coincide: their first rows matter too. In the table, both start on row 1, so the 2-row and 4-row schedules coincide on rows 1, 5 and 9. Different starting rows can change or prevent that overlap.

Work the specified operations in the order you reach them across the row. If they are near the same edge, check which stitches each uses; do not assume you can use the same stitches twice. Keep any established stitch pattern aligned, including its edge stitches and any incomplete repeats, as the pattern directs.

When the schedule falls on a WS row

In ordinary flat knitting without short rows, RS and WS alternate. Repeating a decrease four rows after the previous decrease keeps it on the same side, with three rows between the decreases. This depends on the first decrease row, not just where you began counting. Odd rows are not universally RS: row 1 is WS in the first exercise and RS in the table.

If a schedule conflicts with an instruction to shape only on RS rows, check the starting point, notes and errata, or ask the designer. Do not silently move the decrease to the next RS row. For a WS decrease, use the specified method, such as p2tog or ssp. In ordinary knitting in the round the RS stays facing you, so the flat examples’ alternating knit/purl rows do not apply.

When the actions don’t start together

Sometimes armhole shaping starts first and neckline shaping starts later. The instructions overlap for only part of the work, and one may finish first. Record each actual starting row and stopping condition; do not restart the first schedule when the second begins.

This is where a merged row-by-row plan pays off most. Map the armhole rows. Overlay the neck rows. Mark which rows have only armhole, which have only neck, which have both. Knit from the merged plan. If you’re also untangling the rest of the pattern’s structure, that guide covers sizes, repeats, and abbreviations.

Buttonholes in front bands

A common variation is: “Continue in seed stitch (or ribbing). AT THE SAME TIME, work buttonholes on rows 6, 16, 26, 36 and 46.”

These numbers describe five buttonhole rows, 10 rows apart, with nine intervening rows. The earlier example, rows 4, 14, 24 and 34, describes four buttonhole rows with the same spacing. Count from the start of the band in these illustrative schedules, excluding any preceding setup row. Here row 1 is WS, so the listed even rows are RS. That is an explicit assumption for these examples, not a universal rule.

These are timing examples, not complete button-band patterns: they do not specify the initial stitch count or the hole’s position across the band. For a simple yarn-over buttonhole, a yarn over adds 1 stitch and k2tog removes 1: the starting count is restored within that row. Work the other stitches in the established pattern. A buttonhole made by binding off and casting on may temporarily change the count, so track both steps on the specified rows. Follow the pattern’s buttonhole method and placement rather than treating every hole as one interchangeable action.

Mark the rows and completed holes on paper or in manually maintained notes. If a published pattern gives exact rows or a different counting origin, follow those instructions.

Cross-checking with Ravelry

If a section remains unclear, other knitters’ Ravelry project notes may help you identify a question to check. Compare the same size, pattern version and any modifications, and verify proposed corrections against the designer’s notes or errata. A project note is not an authoritative correction by itself.

Common questions

Can you forget one of the actions for a few rows and recover? Check which action was missed, on which row, and how it affects the shape and stitch pattern. An extra decrease later restores a count but does not restore its original position or the intended slope. Working back to the error is the way to reproduce the written sequence; an alternative needs to be checked for that particular pattern.

Can you do the actions separately instead of together? No. The timing is intentional. Armhole and neckline shaping overlap because the decreases need specific intervals for the correct shape. Finishing one then starting the other changes the proportions.

Does this only show up in garments? No. Accessories can combine a stitch or colour pattern with shaping too, such as a hat motif continuing while crown decreases begin. Follow round numbers if the piece is worked in the round.

Why don’t patterns write every row out? Some do, especially beginner-friendly patterns. Separating repeated instructions saves space across multiple sizes. You can write out your selected size without changing its sequence.

What’s the fastest way to draft a merged row plan? Use a row-number column and one column per action. First enter each action’s actual starting row, then its interval and total occurrences. For the table here, mark the armhole on 1, 3, 5, 7, 9 and the neck on 1, 5, 9. Include the intervening rows and stop each schedule after its specified total, even if the other continues.