A technical editor is an essential part of the knitting design process. A knitting technical editor reads a pattern and checks that the pattern can be knitted correctly and that what is produced is accurate. They will proof read and help correct mistakes within the pattern, including:

• The order of instructions and if they are complete
• Consistency of language and terms used through the pattern, including measurements
• Details of the yarn and gauge
• Ensure all the needles and notions are correct
• Abbreviation list are present and correct
• That all the mathematics included is correct
• If photos are included they are consistent with the design
• Check sizing
• Ease of reading

Proof reading your own work can be very difficult to do and mistakes can be missed easily. The fewer mistakes in a pattern, the more professional the impression it makes on the person using it (and the better the result). As a knitter there is nothing more annoying than working with a pattern that is littered with mistakes or that is difficult to read; this will often result in me not returning to that designer to buy more patterns.

Technical Editor Versus Test Knitter

So how does a test knitter differ from a technical editor?

A test knitter knits up the pattern and sees whether it works. Some will point out mistakes in the pattern and help ensure that, if there are multiple sizes, that the pattern works. They will probably not pick up on mistakes in the instructions which a technical editor will be looking for. It also helps you get a range of of opinions on how your design is to actually knit. A technical editor will not knit the garment (though if you had a design element – e.g. a cable design – they may knit this to ensure the instructions work). They may also leave feedback and pictures of how your design works which can be useful in selling a pattern.

So, a test knitter helps the design process but there focus is the finished item, whereas a technical editor looks at the finer detail of the actual pattern.