ContextCleaner: see every entry in the Windows 11 right-click menu, and which app added it — on the Microsoft Store.
Workflow ScanRoute Local

A File Naming Convention for Scanned Documents: Dates, Order, and Characters Windows Will Not Accept

Published October 17, 2026 Updated October 17, 2026 8 min read

A good file naming convention for scanned documents puts the same fields in the same order every time, writes dates as YYYY-MM-DD so files sort by date, and avoids the characters and names Windows does not allow. A pattern such as Client\2026-10-17_INV_10452.pdf is readable, sorts correctly and survives copying between systems. ScanRoute Local can apply a convention like this automatically, building each name and folder from a template and fields read from the page, and showing every name before anything is written.

Apply one naming convention to every scanned document, with names read from the page.

Get it from Microsoft

Why do scanned documents need a naming convention?

Scanners and copiers name files by timestamp or counter, such as SCAN_0047.pdf. A folder of those tells nobody anything, and searching it means opening each file. When several people scan, each invents a format: one writes Smith invoice Oct, another 10-17 smith inv. Six months later nobody can find anything, and duplicates pile up.

A convention fixes that by agreeing, once, on what goes in a name and in what order.

What should a scanned document’s name contain?

Pick the fields that someone searching would use. For most offices that is four:

FieldExampleWhy
Date2026-10-17Sorts files by date and separates repeats
TypeINV, RCT, LTRTells you what it is without opening it
Identifier10452Invoice, claim, policy or matter number
Client or partySmithUsually better as a folder than in the name

Put the client in the folder and the rest in the name: Smith\2026-10-17_INV_10452.pdf. The folder groups a client’s papers, and the name stays short.

How should dates be written in file names?

Use ISO 8601: year, month, day, written YYYY-MM-DD. ISO’s own page on ISO 8601 gives the format and points out that a date like 01/05/22 is ambiguous, since it can be read as different days depending on the country. Checked on 17 October 2026.

YYYY-MM-DD has two practical benefits for files:

  1. It sorts. Alphabetical order and date order are the same, so File Explorer lists files in date order with no extra work.
  2. It is unambiguous. 2026-03-04 is 4 March to everyone. 03/04/2026 is not.

It also avoids the slash, which Windows does not allow in file names at all.

Which characters and names does Windows not allow?

Microsoft’s Naming Files, Paths, and Namespaces lists the rules. The ones that matter for a convention:

RuleDetails
Reserved characters< > : " / \ | ? *
Reserved namesCON, PRN, AUX, NUL, COM1 to COM9, LPT1 to LPT9, also with an extension such as NUL.txt
EndingsDo not end a file or folder name with a space or a period
BackslashSeparates folders in a path, so it cannot appear inside a name

Source: Microsoft Learn, checked on 17 October 2026.

This matters for scanned documents because the fields often come from the page. An invoice number like INV/2026/104, a client called Smith: Holdings, or a date written 17/10/2026 all contain characters that cannot go into a name as they are.

What separators and case work best?

  • Underscore between fields, hyphen inside dates. 2026-10-17_INV_10452 keeps fields and date parts visibly different.
  • Avoid spaces if files travel. Spaces are allowed on Windows, but they become %20 in links and need quoting in scripts.
  • Use fixed codes for type. INV, RCT, LTR, CRD. A short fixed list beats free text.
  • Keep names short. Long paths cause trouble with some tools, and a client folder carries part of the meaning.

How do I roll out a convention in an office?

  1. Write it on one page. Fields, order, date format, type codes, and two examples.
  2. Decide the folder level. Client, matter or year: pick one and stick to it.
  3. Agree the type codes and print them by the scanner.
  4. Test on one week of scans before renaming the archive.
  5. Automate it where you can, because people under time pressure will not type long names consistently.

Let ScanRoute Local apply the convention to each scan, with the free trial in the Microsoft Store.

Get it from Microsoft

How does ScanRoute Local apply a naming convention?

ScanRoute Local splits combined scans and builds each name from the page.

  1. Split the scan at barcode separator sheets, blank pages, or every N pages.
  2. Draw one zone over the line that carries the identifying details, such as the invoice header.
  3. Set a pattern that pulls fields such as date, client, type and number from that zone and checks each one.
  4. Write the template in your convention, for example {Client}\{Date}_{Type}_{Id}.pdf. The part before the backslash becomes the folder.
  5. Review in Preview. Every proposed name and folder is listed before anything is written.
  6. Fix exceptions. Unsure reads, missing separators, bad file names and duplicates wait in the inbox for you to type the fields, fix the name, or skip.
  7. Commit. Originals are never changed, moved or deleted, no file is overwritten, and a CSV manifest records the SHA-256 of every file written.

A name ScanRoute flags as a bad file name waits in the inbox rather than being written, so check the template against the rules above. Check how dates appear in your documents: write your pattern to match the date format your documents actually use, and test the result in Preview.

Our post on renaming scanned PDFs from an OCR zone covers drawing the zone and writing patterns in more detail.

When is a simpler approach enough?

If you scan a handful of documents a week, typing names by hand to a written convention works, and File Explorer’s rename is free. A convention is worth more than any tool: without one, automation just produces inconsistent names faster. ScanRoute earns its place when volume is high, several people scan, or names must come from numbers printed on the page.

Frequently asked questions

What is the best date format for file names?

YYYY-MM-DD, from ISO 8601. It sorts correctly and reads the same in every country.

Can I use a slash in a file name on Windows?

No. The slash and backslash are reserved, along with < > : " | ? *.

Should the client name go in the file name or the folder?

Usually the folder. It keeps names short and groups each client’s papers. Put it in the name too if files are often moved out of their folders.

Can ScanRoute Local save to a shared network drive?

Not in this version. Sources, the watched folder and the destination are folders on this PC.

Does ScanRoute need an internet connection?

No. Reading, OCR and writing all happen on your PC, using the Windows OCR language installed on it.

Try ScanRoute Local

ScanRoute Local is a one-time purchase in the Microsoft Store, with a free trial. Write your template once, scan a stack, and check the names in Preview. For more, see rename PDF based on content, split scanned legal documents, or the ScanRoute Local product page.

One convention, applied to every page you scan.

Get it from Microsoft

ISO is a trademark of the International Organization for Standardization. Microsoft, Windows and File Explorer are trademarks of the Microsoft group of companies. Other names are trademarks of their owners. ScanRoute Local is not affiliated with or endorsed by any of them.

Last updated 17 October 2026. Published by Automata Labs, a software company in Canada.

// release_radar

Get notified about new releases.

We build native, local-first tools for professionals who refuse SaaS fatigue. Drop your email to hear about new apps, major updates, and zero-telemetry releases as they land on the Microsoft Store. No spam — just release news.