Why you should get your pattern edited before test knitting

A common question new designers have when starting with pattern design is the order in which everything in the pre-publication process happens. One big question is whether you need to get your pattern edited before sending it off for test knitting, or do you get it test knit and then edited at the end?

I’m here to tell you definitively that you always want to do tech editing BEFORE testing.

I think the argument for testing before editing is that you might think that changes suggested by testers will be made during the process. But that’s okay. You can always have your tech editor do a final check of anything that has been changed before you publish.

Here are the reasons why I believe tech editing should happen first.

Your testers are likely volunteers, donating their time to you. To be respectful of their time, you should give them a pattern that is free of errors.

If you were to go through testing first, the errors will be caught by someone who is actively knitting, and they will have to rip back their progress if there are issues. A tech editor on the other hand checks for mistakes on a computer, in a spreadsheet, so it’s much easier to spot mistakes and correct them and no one has to frog their knitting.

Even if you think you’ve given your pattern the most thorough look, I can almost guarantee you’ve missed something. I can think of maybe five to 10 tech edits I’ve done where there hasn’t been a single math error. I’ve edited about 100 patterns, so let’s say around 5-10% have zero errors. And I’m not talking about minor errors like a missing comma or a simple typo. I mean incorrect stitch counts, wrong measurements, a stitch that’s in the wrong spot or missing that throws off the whole stitch patterning, repeats that don’t add up across the cast on number, etc.

Beyond catching the errors, there are also a lot of other changes made during the tech editing process. This varies from client to client, but I’d say oftentimes the majority of my markups on the page are suggestions to improve clarity or style inconsistencies. This means the pattern text may change significantly after tech editing.

And because test knitting is a process that tests the usability of a pattern, testers can let you know if something is confusing to them. That’s why you want to give them the most final version you can. If testers knit the item and then the wording changes afterwards, it’s kind of like not testing it in the first place.

You will also get better feedback by providing a clean and error-free pattern. You don’t want your feedback form to be cluttered up with pointing out errors, you want it to include valuable information on the process of knitting the pattern and if there are any areas for improvement.

There is also your brand image to consider. I used to test knit a lot, and once I started tech editing it became very clear to me which patterns had not been tech edited. It’s not fun signing up for a test and then having a miserable experience because you’re knitting through all of these mistakes that shouldn’t be in the pattern at this point of the process.

I know a lot of designers use test knitting as part of their marketing strategy as well. You will probably get a lot more positive reviews of your pattern, and thus positive social media posts, if the knitter actually enjoys making the pattern.

And finally, editors aren’t perfect. I’ve missed things in patterns before that a test knitter notices and points out. For all the errors I do catch, I know that there’s always the chance that I will miss something. It feels less stressful for me if I know there’s a team of testers providing that final level of quality control.

If you make significant changes to your pattern as a result of testing feedback and you want it checked before publishing, reach out to your tech editor. Those final passes usually only take about 15-30 minutes if you’re able to highlight what changes you’ve made, so they’re very easy for us to fit into our schedule. I also recommend this because sometimes a tester thinks they’ve found an error and it’s just that they’ve counted their stitches wrong or some other user error. Keeping your tech editor involved helps you verify you’re not accidentally adding a new error to your pattern!


Ready to take your knitting patterns to the next level?
As a knitting tech editor, I can work with you to ensure your patterns are clear, accurate, and easy to follow. Visit my Tech Editing Services page to learn more and get started today!

Jenna Barron

Jenna Barron is a knitting tech editor specializing in accessories.

Previous
Previous

Do you REALLY need to knit a gauge swatch? Mostly yes, but not always.

Next
Next

How to find a knitting tech editor