Collision choices without guesswork

Make duplicate file decisions clear before a batch continues

Explain whether a choice affects one collision or the rest of the batch, with evidence that preserves the distinction.

  • ✓Single and batch actions blur
  • ✓Distinguishing suffixes disappear
  • ✓Final summaries omit skipped items

A more precise duplicate-file report

Visible conflict scope

Document the exact control that changes a single-file decision into a batch policy.

Filename context that matters

Keep suffixes and dates available when similar names represent different contents.

Careful consequence wording

Describe observed prompts without inventing an overwrite or a successful recovery.

Build a collision that reveals the choices

Duplicate file dialogs often compress several different decisions into a few buttons. Prepare an authorized test upload in your product with two matching filenames, different modified dates, and a third file that has no conflict. Use harmless contents. Capture the destination list before upload, the first collision, and the next collision after choosing an action. Note whether the expected contract is replace, keep both, skip, or ask for every conflict.

Record the scope of each decision

Show the checkbox or control that applies a choice to remaining conflicts. An example issue is Skip this file becomes Skip all after opening file details. Record the initial wording, the details expansion, and the next prompt so reviewers can see whether the scope changed visibly. Include long filenames that differ only at the suffix. A clipped filename and a changed action scope need different acceptance boundaries even when they appear in the same modal.

Review the draft before calling it destructive

Upload supported screenshots or recordings to Retick, or use its browser capture. Compare AI candidate issues with the actual choices, edit any invented overwrite outcome, reject claims not demonstrated, and annotate the scope control. Example acceptance criteria: expanding details preserves the selected conflict policy; applying a choice to remaining files requires an explicit selection; and the full distinguishing filename is available before confirmation. Product must approve the intended batch policy rather than leaving the reviewer to infer it.

Check the next conflict as well

After a change, manually repeat with one duplicate, several duplicates, and a cancellation halfway through the batch. Check that the remaining prompt and final summary use consistent terms. Verify retained file contents and collision handling separately through your application's tests and authorized storage checks. Retick does not simulate uploads, guarantee against overwrites, or recover replaced files. Capture no real confidential documents, and do not expect automatic removal of filenames from media.

Download the accepted findings for manual file handoff, or export selected issues from the individual media item to Trello using an accessible board and list. Include the observed policy and unresolved storage questions so the task does not imply a data loss diagnosis that nobody established.

Review a file conflict decision

Capture the policy control and the prompt that follows it.