Errata/Erratum: It’s Still an Error

The other day I got an e-mail from a designer whose pattern I purchased months ago.  The designer apologized because an error had been found in the pattern, and she attached a corrected version of the pattern. This was the second time in just a few weeks that I had received e-mails telling me about errors in patterns and that included new versions of the patterns. That’s one of the reasons I like getting patterns from designers. They have the ability–should they choose to use it–to contact those who have downloaded their patterns and let them know about errors.

There seems to be alot of errors going around these days, based at least on what I’m reading on many of the social networking sites. While many of the comments have been understanding, others have been down-right snarky. Sadly, I’ve found some of the snarkiest comments coming from seasoned designers with books of patterns under their belt. Uh, they’re not immune from pattern errors. When I first learned to knit socks, I bought a pattern book by a well-known designer of socks and other things. It had been recommended to me by many knitters, because it was extremely well illustrated, it gave instructions for 3 different knitting methods for every pattern, and it was well-written. When I kept running into problems, I thought it was my fault. I was destined to never knit socks. Well, I finally checked the publisher’s site for errata, it there were many corrections for the patterns in this book. And this was not this book’s first printing. Now I know to check for errata whenever I start a pattern.

I have a 20+-year career in publishing. I can tell you from that experience, it is almost impossible to publish a book or an article completely free of errors. And that’s with a book that goes through every publication stage. There are, however, things that can be done to minimize errors. Here are some designers might want to consider.

Provide a finished first draft of the pattern to testers and editors

This may seem obvious, and I thought it was standard procedure. But, I was communicating with a designer of a mystery project, who said she was designing as the clues were sent out. That might work if you’re doing squares that will be joined for an afghan or such, but I imagine it could open up a whole can of worms for other types of projects.

Engage test knitters

You know what you want your finished project to look like, so it’s easy to overlook errors and mentally–and almost unconsciously–make the adjustments in the pattern to get what you want. A test knitter is going at the pattern “blind,” so he or she has to take the pattern at its face value. They can provide you with invaluable help and feedback.

Usually, the test knitter will use yarn in his or her stash. If you want it tested using a specific yarn, please provide it.

I’ve mentioned before that I don’t think knitter’s should get caught up in experience levels, but they do have their place. If you’re labeling your pattern beginner or easy, make certain it really is. Have your patterns test knit by knitters of various skill levels. Here are the levels as published by the Craft and Yarn Council:

Skill levels for knitting
1		Beginner	Projects for first-time knitters using basic knit and purl stitches. Minimal shaping.
2		Easy	Projects using basic stitches, repetitive stitch patterns, simple color changes, and simple shaping and finishing.
3		Intermediate	Projects with a variety of stitches, such as basic cables and lace, simple intarsia, double-pointed needles and knitting in the round needle techniques, mid-level shaping and finishing.
4		Experienced	Projects using advanced techniques and stitches, such as short rows, fair isle, more intricate intarsia, cables, lace patterns, and numerous color changes.

Involve a tech editor
A tech editor and a test knitter do not do the same things. Though that might seem obvious, there is a lot of confusion about these tasks. The tech editor will not knit the entire project, though he or she might knit a section or two. The tech editor will check your math, provide feedback about yarn selection (for example, will it work with the needles, techniques, and desired outcome), edit the pattern for sense and correctness, and make sure sizing, etc., comply with industry standards. And if the pattern is part of a book or collection of patterns, the tech editor will check for consistency between patterns.

A tech editor should be well versed in yarns, techniques, and industry standards.

Proofread the finished pattern
After the pattern has been edited, and when you think it’s in its final form, proofread it. And have someone else proofread it as well. Again, you know what you want it to say, so your eye and mind will likely automatically correct minor errors.

Before you think that this will cost you money you don’t have, there are some who will do this work for you for free. Well, it might cost you a copy of the finished pattern and/or an acknowledgment, but that’s a small price to pay for customer satisfaction. There are some groups on Ravelry for tech editors and test knitters.

A Word to Knitters

Yes, it is extremely frustrating to come upon an error in a pattern. And yes, you should expect the same level of professionalism whether the pattern was free or you had to pay, or if it was a standalone pattern downloaded on line or from a slickly produced book.

That being said, the simple fact of the matter is that the design and publishing process involves humans. And where there are humans, there is the potential for errors. It’s a simple fact of life. When you run across an error, be sure to let the designer or publisher know. There’s no reason to be rude about it, and the truly professional designer and publisher will welcome the opportunity to make a correction.