Tech Editing vs. Test Knitting: What’s the difference?

The first time I ever test knit a pattern I had so much fun. I got a free pattern, got to chat with fellow knitters who were all working on the same thing, and I got to be a grammar nerd. Since my day job is writing-related, being a grammar nerd is my default state, and proofreading is one of my favorite parts of the job.

When I first started test knitting for designers, their questionnaires would sometimes have a space to list any typos or errors found. I often gave a long list of all the grammatical errors and formatting issues I saw, and, for a while, I thought that’s what test knitting was.

Then I discovered tech editing and realized I had been encroaching more into tech editing than test knitting.

Of course, I learned there’s much more to tech editing than correcting grammar, but I still felt like I had been blurring the lines between the two without even realizing it.

Now that I’m also a tech editor, I think the difference is clearer. I will attempt to explain the differences here.

What does a test knitter do?

Test knitters go through a pattern and physically knit the piece up. By working through the pattern, they can provide useful information on the user experience of the pattern and help the designer understand how their customers will experience the pattern.

Test knitters often are volunteers, and their compensation is that they get the pattern for free. Some designers even offer an extra pattern from their catalog as a thank you.

Test knitters are also often used as part of a designer’s marketing strategy because they’re able to guarantee photos of their design being shared on social media on launch day by testers, and testers will often create a Ravelry project for the test as well.

In summary, a test knitter:

  • Gives feedback on the experience of knitting the pattern

  • Finds the parts of a pattern where knitters might struggle

  • Helps with pattern promotion by sharing photos of their WIPs/finished objects

What does a tech editor do?

Tech editors are trained professionals who go through a pattern, checking for several different things. Knitting patterns are like a recipe, so it’s important that all the elements of that recipe are correct so that a knitter can replicate what the designer made.

Perhaps most importantly, they will check all of the math in the pattern. For example, when I edit a pattern I’ll plug the row instructions into a spreadsheet and make sure the number of stitches that row is worked across matches the number of stitches from the end of the previous row.

They will also go through and check that the gauge listed combined with the pattern’s stitch/row counts would produce an item of the size specified in the pattern.

In addition to making sure all the technical elements of a pattern are correct, tech editors also go through a pattern and edit it for clarity, make sure things are consistent throughout, make sure the pattern includes all the information needed to actually knit the pattern, and point out any grammatical errors.

Unlike test knitters who are volunteering their time, tech editors charge for their services, typically between $30 and $45 per hour.

In general, tech editors:

  • Ensure that the math is correct

  • Make suggestions on improving clarity

  • Make sure all necessary information is in the pattern (all abbreviations used are defined, gauge is listed, materials are all there, etc)

  • Correct grammatical errors

  • Ensure consistent style within the pattern and with the designer’s catalog as a whole

  • Ensure pattern information adheres to industry standards

Are both needed?

Yes, I believe both bring value to the design process. Tech editors ensure that everything is technically correct, that style is consistent, and that the grading makes sense and the item will fit properly.

In theory, a tech editor should catch everything and verify that the instructions are clear, and a designer should be good to publish at that point.

However, tech editors aren’t knitting the pattern, and testers can provide valuable feedback on what it’s like to physically knit the item. And because testers often range in their experience and expertise in knitting, they might share perspectives that a tech editor can’t, as they’re an expert in their craft and might not be thinking like a beginner would anymore.

And because tech editors aren’t perfect, test knitters act as the final line of defense for any errors that somehow slipped through the editing process.

Testers can also provide other benefits, like creating hype around a pattern by sharing photos of their work on social media or creating a Ravelry project.

In conclusion, both test knitters and tech editors are important as they serve different functions.

Hopefully, this clears up some of the confusion you might have had between these two steps in the pattern design process!


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

Excel functions to use when designing knitting patterns