Track outfit repeats to learn which pieces you use

Define a wear record before counting anything

Choose a small observation window and a rule you can apply consistently. For this worksheet, an item worn on one recorded day counts once, even if it appears in two outfits that day. This is our bookkeeping convention, not a universal clothing standard. Keep the original date and item identity so the same photograph does not create a second wear.

Record the pieces actually worn, not merely saved or suggested. A planned combination may change because of weather, comfort, laundry or a different activity. Keep that change visible instead of copying the plan into the wear history. An unrecorded day is unknown, not proof that nothing was worn.

Add a brief context and readiness note: work, walk, dinner, repair needed or waiting for care. Follow the garment’s own care instructions rather than using a wear count to prescribe washing frequency. The FTC’s US care-label guidance concerns instructions for covered apparel; it does not establish a number of wears before cleaning.

Worked week: five recorded days and two unknown days

Fictional closet IDs are T01 blue shirt, B01 dark trousers, J01 jacket and S01 shoes. The owner recorded Monday, Tuesday, Thursday, Friday and Sunday. Wednesday and Saturday were not logged. The worksheet preserves those gaps.

Within the five recorded days, T01 appears on two, B01 on four, J01 on two and S01 on five. These are item-day counts, not four complete-outfit repeat counts and not a percentage of the entire closet. Do not divide by seven and pretend the two unknown days were checked.

The complete listed combination T01+B01+S01 repeats on Monday and Thursday. Tuesday and Sunday both include J01 and S01, but their full outfits are not established as identical. Sunday explicitly leaves another top outside this sample. A shared pair of items does not prove the whole outfit repeated.

The shirt’s absence on Friday has a recorded care reason. That is different from disliking it. A formal outfit not observed in one ordinary week may still serve an important occasion. Keep the observation bounded to its dates and activities before making a purchase or disposal decision.

Use the pattern to ask one useful next question

Choose a practical follow-up: does a frequently used piece need a repair, is a favorite combination worth planning again, or was a low count explained by the season? Keep the decision separate from the count so a later reader can understand the reason.

If you add earlier wears from memory, mark them as estimates rather than mixing them into the checked week. If two closet records describe the same garment, resolve the identity before adding their counts. Keep similarly colored but physically different items separate.

No carbon saving, cost saving, lifetime durability, body-fit accuracy or style score is calculated here. Those would require other evidence. The weekly wardrobe guide helps choose future outfits; this guide compares future intent with what was actually observed after the week.

Clovio organizes owned pieces and outfit ideas

Clovio’s current listing describes clothing photos, editable detected attributes, outfit combinations, color explanations, shop matching and optional AI try-on previews after adding a body photo. Free users start with three shared AI uses across the listed AI actions. Premium expands use within subscription plan limits; check the installed allowance and terms.

We publish Clovio. Saved outfit ideas and AI previews are not a verified wear calendar. Use this separate CSV to record actual wear; saved suggestions do not automatically supply that history. AI suggestions do not guarantee fit or exact measurements.

Use Clovio’s stable closet item names or your own IDs to relate observations to owned pieces. Review optional photo sharing and avoid including unrelated people or private backgrounds. The CSV does not import into the app, track you automatically or validate a shopping recommendation.