Why you should get your pattern edited before test knitting
A common question new designers have when they’re getting started with pattern design is the order in which everything in the pre-publication process happens. The big question is do you need to get a pattern tech edited before you send it off to test knitters, or do you wait until it’s been test knit to send it off to a tech editor?
I’m here to tell you definitively that you always want to do tech editing BEFORE testing.
I think the argument for testing before tech 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.
Here’s why tech editing should happen first.
Use a template to design knitting patterns
I'm all for systems and processes that will make life easier, so I try to make templates for just about everything. When I get a request from a new designer to tech edit their pattern, typically my response is a templated response I have saved in Gmail, with some minor alterations. I have my invoices saved as a template in PayPal too so that I don't have to put my business info and rate in every time I create a new invoice. The list goes on. Templates just make life so much easier.
And you can do this to your patterns too. You may be asking: what is the difference between a template and a style sheet? How I see it is a style sheet is a document with every possible note you may need to use when designing future patterns and making sure everything conforms to your style. A template is basically an empty version of my pattern that I can fill in with details.