Services

Empathetic editing

I definitely think there are certain elements of editing that I excel at. One is empathy. I am able to “put myself in the knitter’s shoes” and when I’m editing for clarity, I’m always thinking of the knitter first. I view my role as a tech editor as the middle woman between you and your customers. So even though something might make sense to me as an experienced knitter, I’m also thinking through the areas that I think could trip someone up.

I think this empathy also extends to my editing process. I’ve worked as a writer and editor at an online magazine and news site (non-knitting related) for the past five years so I understand first-hand how hard it is to get edited, and even more so when you’ve spent so much time on your pattern already. I always try to be as constructive as possible in my suggestions.

What gets checked

Typically when I tech edit a pattern, there are a number of things I check for:

  • Use the given gauge to make sure finished measurements are correct
  • All measurement conversions are correct
  • Yarn information is correct (fiber type, yardage, company name, etc.)
  • All information a knitter needs to successfully make an item as intended is included in the pattern (notions, abbreviations, supplies, etc.)
  • Charts match written instructions¬†
  • All abbreviations are used and none are missing
  • Stitch counts are correct and that rows flow into each other correctly
  • Compare the sample photos with the instructions
  • Things within your pattern are displayed consistently
  • If you have a style guide, I will check your pattern against it
  • Grammatical errors

Depending on the pattern, there may be more things to check as well, and I will adjust my workflow accordingly.

If there are any specific areas in your pattern that you have concerns about, let me know at the start and we can work through those together.

My process

I work either with PDFs, directly adding my notes onto the document for you to see, or using Google Docs where we can make use of Suggestions mode / comments.

After you have looked at my first edit and updated your pattern, you’ll send it back to me for a second round of editing so that I can give it a final look to ensure it is ready for publishing. You can also opt to send it back to me again after test knitting if any changes are made during that process that you want me to take another look at.

Typically, my turnaround time for the first edit is 1 week. You will have the second edit back within a few days of me receiving the updated pattern. If you want to secure an editing slot for a particular week to ensure I have availability, you can book through my Calendly.

My specialties

I am comfortable editing most things, but if I come across a pattern I don’t feel I have the needed expertise to edit, I will be happy to recommend a fellow tech editor who might be a better fit.

My favorite things to edit include:

  • Shawls
  • Top-down sweaters
  • Lace
  • Cables
  • Textured stitch patterns

Pricing

My rate for new clients is $40/hour, charged in 15 minutes increments. If you are a new client I offer a 25% discount on your first edit to give you a chance to see how we work together. When you send me your pattern I will give you a quote based on my estimate of how long I think it will take to edit. If I start working and find an edit will take longer than expected, I will reach out to you for approval before proceeding.

I accept payment through PayPal, and invoices are due within 30 days of me sending them. I only invoice once per month, at the end of the month, so if your pattern is edited at the beginning of the month, don’t be surprised if you’re waiting on an invoice for a few weeks.

Here is an estimation of how long different items will take to edit:

  • Hats, scarves, and cowls: 30 minutes-1.5 hours
  • Shawls, socks, and simple sweaters: 2-4 hours
  • Complex sweaters (involved stitch patterns, complicated constructions, etc): 4-6 hours

Factors that contribute to editing time are the number of errors present, stitch pattern complexity, and the number of sizes/yarn weight options available.

Financial accessibility

I feel I can’t talk about pricing without also mentioning financial accessibility. The bottom line is that tech editing is expensive. I firmly believe that you get what you pay for, so while there may be cheaper tech editors out there, I set my rates based on my skills, experience, and knowledge. I work really hard to make this process as worth it as possible.

That being said, I understand that tech editing is a huge expense, and I don’t want cost to stand in the way of you being able to have a professionally edited pattern. If you have concerns about cost, let’s chat!

I am open to working with you to bring costs down, especially if you are new to designing. If this is your first knitting pattern, it could be a while before you’ve had enough pattern sales to justify your investment. Some first steps to take in bringing down costs include:

  • Signing up for my quarterly newsletter using the form below for a 10% discount on an edit in addition to the 25% off you get on your first edit
  • Following my pre-edit checklist to catch basic errors yourself and reduce the number of edits I need to make
  • Asking to delay your invoice until after your pattern has been released (if within a reasonable timeframe) so you can pay for your edit with pattern sales

If these starting points still don’t make the cost fit your budget, feel free to reach out with your concerns and we’ll see if we can figure something out that works for both of us.

Next steps…

I invite you to read my testimonials page to hear what my clients have to say about working with me, or check out a portfolio of patterns I’ve edited on Ravelry.

If you’re interested in working together to improve your pattern, please use either my contact form to get in touch or book an appointment through Calendly. You can also sign up for my mailing list using the form below to receive a 10% discount off a tech edit (in addition to my normal 25% off for new clients.

%d bloggers like this: