ErrataDeskAll articlesPRICING & PRACTICAL GUIDES
How to Organize Knitting Pattern Customer Feedback
Organize pattern feedback by the question being resolved, not by the inbox where it arrived. One issue may appear in email, a project note, and a social comment. Keeping three unrelated notes makes it harder to see whether those reports concern the same file and size.
A useful feedback log connects each report to a pattern, file version, location, and next action. It should help you decide what to investigate without treating every customer question as a confirmed defect.
Ask for enough context
Request the pattern name, file version or download date, selected size, page or chart, and a short description of the problem. If the customer is working from a printed copy, the version printed in that copy is more useful than the current shop version.
Ask only for details needed to understand the issue. A focused reply can reduce another round of clarification without making the customer complete a long support questionnaire.
Sort feedback into actionable categories
| Category | Example | Next action |
|---|---|---|
| Possible error | Reported stitch-count mismatch | Review against the source |
| Clarification | A phrase is being read two ways | Consider clearer wording |
| Technique question | Reader needs help with a method | Point to appropriate guidance |
| Existing correction | Report matches known errata | Share the relevant correction |
| Future request | Suggestion for another size | Record separately from fixes |
Sister Mountain's account of managing feedback recommends categories and a record of how feedback is being acted on. This keeps useful suggestions from disappearing into message history.
Combine duplicate issues without losing reporters
If several reports refer to the same suspected error, link them to one issue record. Retain the affected sizes and versions from each report. Two similar questions may turn out to concern different instructions, so review the context before merging them.
Give the issue a status such as reported, under review, confirmed, corrected, or published. Store the contact reference privately; public errata needs the correction, not a list of customer names.
Review the log at a predictable time
Choose a review cadence you can maintain. Identify unresolved issues, decide the next action, and separate urgent corrections from optional future improvements. A small catalogue may only need a short review; the goal is a reliable habit rather than a complicated support system.
When an issue is confirmed, use the errata record template. When it is fixed, use the storefront release checklist to finish publication. Those are separate steps.
Keep the tool proportional to the work
A spreadsheet is enough if you can find open issues and complete updates reliably. Consider a dedicated tracker only when repeated copying and missed release steps justify it.
ErrataDesk is being planned around this correction workflow, with one pattern free and a $9 monthly designer plan. It organizes the record; you remain responsible for checking instructions and responding to customers. Early-access inquiries help confirm scope and availability. No payment is collected through the inquiry form.