A Quarterly Audit for Your Media Favorites
A quarterly decision ledger reviews purpose and identity before any bulk cleanup, preserving unresolved and unavailable favorites safely.
In short: Freeze the list scope, preserve a before snapshot, and review each item by exact identity, owner, original intent, last useful retrieval, current availability, and future action. Choose keep, move, merge, investigate, or remove. Resolve uncertain versions and missing items before bulk cleanup, then verify favorites, history, and progress separately.
Quarterly is a practical rhythm for durable favorites because it is frequent enough to catch drift without turning curation into weekly maintenance. Temporary lists should use much shorter expiry dates.
Create the quarterly decision ledger
| Item identity | Owner | Original intent | Last useful retrieval | Availability | Exception | Decision | Next review |
|---|---|---|---|---|---|---|---|
| Keep / move / merge / investigate / remove |
Date the audit and identify the account, confirmed profile, or shared list scope.
Freeze and sample before changing
Capture list count, active filters, visible sort, and representative screenshots without private credentials. Select five items and test whether they reopen the intended entity. If retrieval or scope is unreliable, pause cleanup and investigate first.
Norva may retain favorites across supported devices under the same account. Confirm current synchronization and profile behavior before assuming one removal is local.
Review exceptions first
Prioritize:
- duplicate-looking cards;
- unavailable items;
- favorites that appear missing on one device;
- items attached to the wrong version;
- scope conflicts between household members;
- unreadable or incomplete identity.
Use the duplicate-favorite workflow before merging. Similar artwork is not enough evidence.
Apply the five decisions
Keep
The original future action remains useful and retrieval works. Update the next review only if needed.
Move
The item has value, but its intent belongs in next-up, tonight, a themed shortlist, or a private reference note. Moving should not erase history.
Merge
Two entries represent the same intended entity and one can be safely retained. Preserve the version that matches the purpose and any meaningful state.
Investigate
Identity, scope, availability, or synchronization is unresolved. Do not delete while evidence is incomplete.
Remove
No future action remains, the item is correctly identified, and removal scope is understood. Record a reason only if it helps future admission decisions.
Review intent and last use together
An old favorite can remain valuable as a stable reference. A recently added favorite can already be irrelevant. Use age as context, not an automatic removal rule.
Measure useful retrieval: watched, compared, recommended, or used for discovery. If an item was never used, ask whether its review trigger was too distant or its admission reason too vague.
Handle unavailable entries carefully
Current source unavailability does not erase title identity or personal preference. Apply the unavailable-favorite decision tree and decide whether to keep the reference, find another authorized version, or remove it because the intent ended.
Run a manageable-list test
After the first review pass, use the retrieval-capacity budget. Time a few searches and compare unresolved share with the previous baseline. The audit succeeds when decisions become easier, not merely when the count falls.
Apply changes in small batches
Change five to ten items, leave the page, reopen favorites, and confirm:
- intended items remain;
- removed items are absent only from favorites;
- history and progress remain intact;
- another supported device reflects the expected scope;
- filters have not hidden unresolved entries.
W3C notification guidance supports confirmations that state what changed and offer recovery where possible.
Record audit outcomes
Count each decision class and the reasons for investigation. Use the pattern to improve admission. Many “remove—no purpose” outcomes suggest the initial save rule needs tightening; many wrong-version cases suggest identity is not visible enough.
Common mistakes and limitations
- Starting with a bulk remove action.
- Reviewing age without intent.
- Merging cards by artwork.
- Deleting unavailable items automatically.
- Assuming account or profile scope.
- Counting removals as the only outcome.
Frequently asked questions
Must the audit happen exactly every three months?
No. Quarterly is a useful default. Adjust based on list inflow, review capacity, and temporary-list expiry.
Should every item have a note?
Only capture information that supports retrieval or the next decision. Avoid unnecessary personal data.
What if removal cannot be undone?
Preserve a private identity list first and apply changes in smaller verified batches.