Sort Repeat Requests by Decision Not by Product Name

Build folders around the question being answered

Instead of saving every repeat request under a product name alone, group files by the decision that still needs review: wording, layout, reference image, or customer approval. It makes the next action obvious when a request returns after a pause.

Keep a compact status line

Add one short note that states what is confirmed and what remains open. The note reduces guesswork for a small team and avoids treating an old exploratory sample as current evidence. Browse /updates/ for other repeatable workflow habits.