It means what it says, which is exactly why it’s confusing. Two different things happen on the same rows, and the pattern describes them separately even though you do them together.
“At the same time” in a knitting pattern means two sets of instructions happen simultaneously over the same rows, typically one shaping action layered on top of an ongoing stitch pattern. This shows up most in garment shaping. The pattern can’t easily describe both in a single line, so it describes one action, then says “at the same time” and describes the other.
A concrete example
A typical instance from a sweater pattern:
“Continue in stockinette stitch. AT THE SAME TIME, decrease 1 st at each end of every 6th row, 5 times.”
Keep knitting stockinette (knit on RS, purl on WS), but on every 6th row, work a decrease at the beginning and end of that row. The decreases happen within the stockinette rows. You don’t stop one to do the other.
- Row 1: knit across
- Row 2: purl across
- Row 3: knit across
- Row 4: purl across
- Row 5: knit across
- Row 6: ssk, knit to last 2 sts, k2tog (decrease row, still stockinette)
- Row 7: purl across
- Continue the same way, decreasing every 6th row, for 5 decrease rows total.
The stockinette never stops. The decreases layer on top of it.
Where this shows up
Most commonly: armhole and neckline shaping at the same time. The pattern describes armhole decreases, then says “at the same time, when piece measures X inches, begin neck shaping.” Both sets of decreases happen on the same rows once the neckline starts. You end up decreasing at both edges simultaneously, but on different schedules. Armhole every other row, neckline every 4th row, say.
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
To see how this looks in practice, imagine armhole decreases every 2nd row and neck decreases every 4th row, both starting on the same row.
| 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 |
Every 2 rows, the armhole gets a decrease. Every 4 rows, the neck gets one. Every 4 rows, both happen on the same row. The grid is the whole trick. Once you see the overlap, the knitting becomes a set of decreases.
Writing the grid out before starting takes 5 minutes. It saves hours of confusion mid-row.
Why patterns are written this way
The alternative is worse. Writing every row with both actions merged makes the instructions long, repetitive, and harder to follow for anyone past the beginner stage. Separating the actions and telling you to combine them is cleaner once you understand the convention.
Think of it as two tracks playing simultaneously. Melody and bass line. Each makes sense alone. You play both.
How to keep track
The knitting isn’t hard. Remembering which row needs which action (or both) is the hard part.
Simplest approach: write it out before you start. Merge the two instruction sets into a single row-by-row list. “Row 1: knit, decrease at armhole edge. Row 2: purl. Row 3: knit, decrease at neck edge.” Takes a few minutes but kills the mental load while you’re actually knitting.
Two counters work too. One tracks the armhole interval, the other the neckline. When both hit their trigger on the same row, you do both actions. Some knitters mark the pattern directly, annotating which rows have armhole decreases, neck decreases, or both. Different colored highlighters help.
KnitTools’ Row Counter supports multiple concurrent counters for exactly this situation.
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.
When intervals collide
When the two actions run on different schedules, some rows will have both. Armhole decreases every 2nd row, neckline every 4th means every 4th row gets two sets of decreases.
Work them separately across the needle. Start with whichever decrease belongs at the beginning of the row, knit across, do the other at the far end. If both happen at the same end (rare, but possible in asymmetric construction), work them in sequence.
When the schedule falls on a WS row
Most visible shaping is written for RS rows because the decreases are easier to read on the right side. But row-count language can still trip you up. If a “decrease every 4th row” schedule starts on a RS row, the next decrease rows stay on RS rows. If the count starts from a WS row, the trigger rows stay on WS rows.
Don’t quietly move a decrease because the row feels inconvenient. First check the pattern notes, stitch counts, and any errata. If the pattern calls for a WS decrease, use the WS decrease it gives, such as p2tog or ssp. If the pattern says shaping happens on RS rows only, keep the decrease on the next RS row and mark the count clearly.
The important part is not guessing. The total number of decreases must still match the pattern, and the shaping line should stay consistent.
When the actions don’t start together
Sometimes it’s staggered. “Begin armhole shaping” and then three rows later “at the same time, begin neck shaping.” The two overlap for part of the work. One starts first, both run simultaneously for a while, then one finishes before the other.
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: “Continue in seed stitch (or ribbing). AT THE SAME TIME, work buttonholes on rows 6, 16, 26, 36, and 46.”
Different from shaping in two ways. Buttonholes don’t accumulate (each one is a discrete event, not a cumulative reduction in stitches). And the spacing is often fixed by exact row numbers. The cleanest approach is to mark those row numbers in advance with sticky tabs on the pattern or notes in a row counter app.
If you’re planning your own spacing, decide whether the buttonholes belong on RS rows and mark them before knitting the band. If the published pattern gives exact rows, follow those rows unless the pattern notes say otherwise.
Cross-checking with Ravelry
If a section of a pattern keeps confusing you, search the pattern on Ravelry and check the project pages. Other knitters often flag where they hit timing issues, especially around “at the same time” sections. Notes like “armhole and neck overlap is tricky, I wrote out the rows ahead” are common, and so are corrections to ambiguous wording.
A complex pattern with no Ravelry projects gives you less outside evidence. That doesn’t make it bad, but it does mean your row plan and stitch counts matter more.
Common questions
Can you forget one of the actions for a few rows and recover? If you catch it within a row or two, rip back. Several inches past, you might add an extra decrease on the next scheduled row. One missed decrease: usually fine to adjust. Multiple: ripping is safer.
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? Mostly. Occasionally in accessories (hat colorwork changing at the same time as crown decreases) or complex stitch patterns. Garment shaping is by far the most common context.
Why don’t patterns write every row out? Some do, especially beginner-friendly ones. But for complex garments with multiple sizes, row-by-row instructions for every size would add ten pages. The convention saves space, and experienced knitters expect it.
What’s the fastest way to draft a merged row plan? A small spreadsheet or a column of row numbers on paper with ticks for each action. Number rows 1 through 60 (or however many you need), put a checkmark in the armhole column on every 2nd row, the neck column on every 4th row, and circle the rows that have both. Five minutes of prep saves a lot of mental load.