Scan, name, file, repeat
Lesson 2 of 6 · Digitize & De-identify
1 · Learn the move · Recipe pattern
Scanning isn't the hard part, the scanner does that. The hard part is the twenty minutes after, when 300 pages sit in a folder called Scans with names like DOC_20260305_0012. The recipe pattern locks the loop so that never happens: one box on the desk at a time, scan the batch, name every file before you touch the next batch, file it, mark the box, move on. Naming happens inside the loop, never after, because "I'll name them later" is how the backlog quietly becomes a digital backlog with worse search.
You are writing my scan-to-filed runbook. One loop, numbered steps, from box on the desk to box marked done. Naming happens inside the loop, never batched to the end. Include the quality check, what to do with a page that won't scan, and how the box gets marked. Use my naming recipe and my folder tree, pasted below, don't design new ones. Under one page, written for someone doing this cold. [naming recipe + folder tree]
2 · Your turn. You write the prompt
You scanned 300 pages last Thursday. Forty of them sit in a folder called Scans with names like DOC_20260305_0012.pdf, and you can no longer tell which box they came from. Write a prompt that builds the pipeline so the next 300 land filed.
Remember: the AI sees only your prompt, not this page. If the situation isn't in your prompt, it doesn't exist.
Optional. These shape the output when you run your prompt below, not your score.