The short answer
Define collisions, missing dates and unsupported files. Official examples describe file processing, but real records still need a backup and a small trial.
Try it in three steps
- Copy a few non-sensitive files into a practice folder.
- Request old name, proposed name and reason.
- Approve changes only for the practice copies.
A practice prompt
Before you start
Place two same-topic notes in a practice folder and preview names only.
Practice material (fictional)
Both a.txt and b.txt contain 2026-10-01, sample receipt. Rule: date_subject, keep extensions and flag collisions.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
Preview names as date_subject. Mark missing dates and collisions without moving, deleting or renaming files.What to look for (not a recorded test result)
Both map to the same target, so flag a collision without overwriting or substituting creation time for the stated date.
If it goes wrong
If creation time is treated as a business date, require the date source and do not assume equivalence.
Check your result
Every file has a traceable mapping with conflicts and skipped items visible.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.