Recent chats

How can I keep notes on changes I make to a craft pattern or set of instructions?

Quick answer

Keep a dated change log beside the original pattern or instructions. For each change, note the step or location, what the instructions said, what you did instead, why you changed it, and what happened. Record quantities or measurements when relevant, and mark anything you still need to check. This gives you a clear record to use when resuming, repeating, or revising your version.

LET’S WORK THROUGH IT

The question, the details, the next step.

Question

I often change a craft pattern while I’m working, then forget what I did. What should I write down?

Geez

Make a small project-change log and fill it in when you make a departure from the instructions. Preserve both versions: what the pattern asked for and what you actually did. A note such as “changed row 4” may not be enough to help you later.

For each entry, record:

  1. The step, row, section, or location.
  2. The original instruction, briefly or in your own words.
  3. Your change, including a count or measurement if relevant.
  4. Why you changed it, or “reason not noted.”
  5. The result and anything you want to check next time.

Keep the pattern’s name or version with the log. Date entries or identify which section they apply to, especially if you restart the project.

Follow-up question

Can you show me how to write one? I’m worried I’ll just make vague notes.

Geez

Here’s a hypothetical example. The details are placeholders, not instructions for a real pattern:

Project: [project name] Pattern or instruction version: [name/version] Date: [date]

Location: Step 6 Original: [follow the specified repeat for 8 rounds] My change: [worked 7 rounds] Reason: [adjusted to fit my planned size] Result: [piece measures ___; appearance ___] Next time: [check the measurement before deciding whether to use 7 or 8 rounds]

This is more useful than “made it smaller” because it identifies where the change happened and what you would check. If you do not know the result yet, write “not checked” rather than guessing.

Follow-up question

What if I make several changes, or I’m not sure which one caused the result?

Geez

Give each change its own entry, even if several happen in the same section. For example, list a measurement change separately from a change to the order of steps. That way, you can see what you altered without assuming which change caused a later difference.

If you check the result after making several changes, say so: “Result checked after changes A, B, and C; individual effects not separated.” Treat the outcome as uncertain. If you want to compare versions later, label them simply—such as [Version A] and [Version B]—and record the differences rather than relying on memory.

Follow-up question

How do I make the notes easy to use when I come back to the project months later?

Geez

Put a short project summary at the top: project name, pattern or instruction version, materials or tools if they matter to your changes, and the last step completed. Number change entries in the order they occurred, and use the same location labels as the instructions. Keep unresolved questions visible under “check next” instead of burying them in a long note.

Copyable entry:

Entry [number] — [date] Where: [step/row/section] Original instruction: [brief note] What I did: [specific change and amount] Why: [reason or not noted] Observed result: [what I noticed / not checked] Next time: [repeat, revise, or check]

Before starting again, read the original instructions and your log together. The log records your choices; it does not replace the pattern or show that a change will work in a different project.

A practical checklist

  • Write down the pattern or instruction name and version.

  • Identify the exact step, row, section, or location for every change.

  • Record the original instruction and what you did instead.

  • Include relevant counts or measurements, and note why you changed it.

  • Describe the result or mark it as not checked.

  • List open questions or checks for the next session.

A few more useful answers

Should I rewrite the whole pattern to include my changes?

A change log can preserve the original while recording only your departures. If you make a clean personal copy, label it as your modified version and keep the original available for comparison.

What if I notice a change only after I’ve moved on?

Add an entry when you notice it. If you do not know when the change happened, mark the date as the date recorded. Be clear about uncertainty rather than presenting a reconstructed detail as certain.

What should I record if I haven’t finished the project?

Record the last completed step, the next step, and any change whose effect is still unknown. That gives you a restart point without implying that an unfinished result has been checked.

YOUR QUESTION. YOUR DETAILS.

Let’s work through your situation.

Get a tailored answer or help with your next task. Starts at $1, with a quote before you pay.

Ask your own question
← Back to Geez at Work