{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiap2p7yddubxys4yxyf3spx3a3goqkdo25pfsbmc6363iennnfrle",
    "uri": "at://did:plc:2jhaz5p2w5y3oosc3zr26cjo/app.bsky.feed.post/3meh63nnvzht2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreigaqb7g3txxqoc7dkxocbgw2n3il3zaprqapyxkqh3hizzj5hxzey"
    },
    "mimeType": "image/jpeg",
    "size": 185041
  },
  "description": "Your contracts, IDs, medical, taxes.",
  "path": "/scanned-documents-naming-system/",
  "publishedAt": "2026-02-09T19:19:01.000Z",
  "site": "https://www.yonkeydonkey.blog",
  "tags": [
    "Memex Method for digital organization"
  ],
  "textContent": "**Y** ou don’t lose important documents all at once. You lose them one small panic at a time.\n\nA contract clause you can’t find. A clinic bill that “never arrived.” A tax form that’s somewhere, you swear. And suddenly your scanner for digitizing paper documents feels like it’s been feeding paper into a fog machine.\n\nA for , part of broader file naming conventions used to maintain order, fixes that, not by being clever, but by being consistent. One pattern. A small set of words. Filenames that carry their own flashlight.\n\n## The one rule that makes scanned documents searchable for years to come\n\nTreat every filename like evidence. Because later, that’s what it becomes.\n\n💡\n\n****The rule is simple:**** start with the date in ISO 8601 format.\n\nThis is the primary format: `YYYY-MM-DD`. Your computer sorts that cleanly. Your brain learns it fast. And when you search, this boosts searchability; you aren’t guessing whether you filed it under “April” or “Taxes” or “That Thing With the Accountant.\"\n\nHere’s the base pattern you’ll use for almost everything:\n\n**`YYYY-MM-DD__DOCTYPE__WHO__WHAT__STATUS-or-V#`**\n\nKeep it boring. Boring is reliable.\n\nA few ground rules keep you out of trouble:\n\n  1. **Use real dates** when you can (signed date, visit date, filing date).\n  2. **Use double underscore (`__`) separators**. They’re easy to spot in a long filename.\n  3. **Avoid special characters** like `/:*?\"<>|` (essential for cross-platform compatibility across different operating systems).\n  4. **Pick one style and stick to it** (all caps for DOCTYPE is clean).\n  5. **Don’t hide meaning in folder structure**. Put meaning in the filename; folders are just neighborhoods.\n\n\n\nDigital is easy to copy and search, and that’s the seduction. It’s also fragile in its own way. File formats change, services vanish, and “I’ll remember where I put it” turns into a lie you tell yourself. When possible, store scans as **PDFs** in your document management system. If you keep notes about a document, save them as plain **.txt** alongside the scan. Old-school, blunt, hard to corrupt.\n\nIf you like a wider system for remembering what you stored and why, borrow ideas from the Memex Method for digital organization. Your filenames become the hooks your memory can grab.\n\n## A small vocabulary keeps your document naming system from rotting\n\nMost file chaos isn’t caused by mess. It’s caused by synonyms in descriptive file names.\n\nYou name one file “Agreement,” the next “Contract,” the next “Signed Deal FINAL(2).pdf,” and now search turns into a hostage negotiation.\n\nSet a tight vocabulary as the foundation for effective file naming conventions. Ten or twelve document types. A few statuses. That’s it. The point is not to describe the universe, it’s to find your stuff.\n\nHere’s a starter set that covers most lives without getting cute:\n\nToken type| Use| Examples you type\n---|---|---\nDOCTYPE| What category this is (document type codes)| CONTRACT, ID, MED, TAX, INS, BANK, RECPT, LEGAL, HOME, EMP\nWHO| Person or org (short)| IRS, AETNA, KAISER, ACME-LLC, SMITH-J\nWHAT| Plain topic| RENT-LEASE, PASSPORT, MRI, W2, 1040, TITLE, CLAIM\nSTATUS| Where it stands| DRAFT, SIGNED, FILED, PAID, OPEN, CLOSED, FINAL\nV#| Version numbers for simple version control when it matters| V1, V2, V3\n\nA few choices matter more than people admit:\n\nFor **DOCTYPE** , while some prefer CamelCase or Snake Case, all-caps is the recommended style here for clarity.\n\nWrite **WHO** the same way every time. If you sometimes write “Blue Cross” and sometimes “BCBS,” you’ll pay for it later. Pick one.\n\nKeep **WHAT** short and blunt. Two to four chunks, with hyphens as the preferred separator, are sufficient.\n\nUse **STATUS** only when it helps. If everything is “FINAL,” nothing is.\n\nAnd if the date is unknown, don’t guess. Use an honest placeholder that still sorts:\n\nUnknown date, but consistent with underscore separation: **`0000-00-00__DOCTYPE__...`**\n\nUnknown day, known month, using underscore: **`2026-02-00__...`**\n\nYour goal is a filename that survives bad memory, stress, and a late-night search on a laptop in some strange room.\n\n## Copy-and-paste examples\n\n### For contracts, IDs, medical, and taxes\n\nA good naming pattern should feel like muscle memory. You shouldn’t have to think. You should just type it, like locking the door.\n\nBelow are copy-and-paste examples for naming scanned documents; copy them and edit the names. Keep the bones, swap the details. Metadata is the hidden companion to these visible filenames.\n\n### Contracts: leases, freelance, services, anything with signatures\n\nUse these as legal naming templates for personal or business use. Use the signed date if available. If not, use the date you received it.\n\nFor legal or client-based work, include a **Matter ID** as an optional token:\n\n  1. **2026-01-18__MATTER-ABC123__CONTRACT__ACME-LLC__WEBSITE-REDESIGN__SIGNED.pdf**\n  2. **2025-11-01__CONTRACT__SMITH-J__RENT-LEASE__SIGNED.pdf**\n  3. **2026-02-03__CONTRACT__VERIZON__SERVICE-AGREEMENT__SIGNED.pdf**\n  4. **2026-02-03__CONTRACT__VERIZON__SERVICE-AGREEMENT__V2.pdf**\n\n\n\nIf a contract has add-ons, make them explicit instead of burying them:\n\n  1. **2026-02-03__CONTRACT__VERIZON__SERVICE-AGREEMENT__ATTACH-A__SIGNED.pdf**\n  2. **2026-02-03__CONTRACT__VERIZON__SERVICE-AGREEMENT__SOW__SIGNED.pdf**\n\n\n\nSame date. Same core name. Different document. No mystery.\n\n### IDs: passport, driver’s license, birth certificate, immigration docs\n\nFor IDs, you usually care about **expiry** as much as issue date. You’ve got options. These naming patterns are often used in human resources contexts:\n\nOption A (use issue date in the filename, put expiry in the notes field of your scanner):\n\n  * **2024-06-12__ID__DOE-J__PASSPORT__ISSUED.pdf**\n\n\n\nOption B (use expiry date as the leading date, because it’s the date you’ll search under):\n\n  * **2034-06-11__ID__DOE-J__PASSPORT__EXPIRES.pdf**\n  * **2028-09-30__ID__DOE-J__DRIVERS-LICENSE__EXPIRES.pdf**\n\n\n\nThat second approach feels a little criminal the first time you do it. Then it saves you at renewal time.\n\n### Medical: visits, lab results, imaging, bills, EOBs\n\nMedical paperwork multiplies in the dark. Keep it tied to the **date of service**. Add the provider, then the document type. Clean filenames like these improve indexing and OCR performance when searching for text within documents.\n\n  1. **2026-01-09__MED__KAISER__OFFICE-VISIT__NOTES.pdf**\n  2. **2026-01-09__MED__KAISER__LABS__CBC-CMP__RESULTS.pdf**\n  3. **2026-01-13__MED__KAISER__BILL__STATEMENT__OPEN.pdf**\n  4. **2026-01-20__MED__AETNA__EOB__CLAIM-7842231__FINAL.pdf**\n\n\n\nIf you’re scanning a whole visit packet, say so:\n\n  * **2026-01-09__MED__KAISER__VISIT-PACKET__FINAL.pdf**\n\n\n\nYou’re not writing a novel. You’re labeling a file so Future You doesn’t have to re-live the appointment just to find the receipt.\n\n### Taxes: returns, W-2s, 1099s, receipts you might claim\n\nTaxes are their own kind of pressure, including for accounting files in financial record-keeping. You want two things: **tax year** and **form**. You can still lead with a date, but make the year obvious in WHAT.\n\n  1. **2026-01-31__TAX__ACME-LLC__2025-1099-NEC__RECEIVED.pdf**\n  2. **2026-02-02__TAX__EMPLOYER-XYZ__2025-W2__RECEIVED.pdf**\n  3. **2026-04-12__TAX__IRS__2025-1040__FILED.pdf**\n  4. **2026-04-12__TAX__STATE-CA__2025-540__FILED.pdf**\n\n\n\nFor tax-deductible receipts, the purchase date is the date that matters:\n\n  1. **2025-08-19__RECPT__BESTBUY__LAPTOP__TAX-2025.pdf**\n  2. **2025-12-28__RECPT__PHARMACY__RX__TAX-2025.pdf**\n\n\n\nThat little `TAX-2025` tag isn’t pretty. It’s effective.\n\n## Conclusion: name the file like you’ll need it in court\n\nA dead-simple file-naming conventions system doesn’t try to impress you. It helps you, especially with **document retention** and **legal readiness**. Date first, a small vocabulary, and filenames that say what they are without begging for context.\n\nTonight, pick one folder and rename 20 scans. Just 20. You’ll feel the drag of it at first, then the relief. The kind you don’t brag about, because it’s private.\n\nLater, when you can find the right PDF in ten seconds flat, you’ll know you did something rare: you built a robust electronic file cabinet that outperforms physical ones, forming a true document management system. While manual now, it lays the logic for future automated file-naming tools.\n\nCongrats, you made your own life a little less heavy. It's called order, and order is good. Order is lovely. Order is what they tried to teach you in school. You graduated today.",
  "title": "A Simple System for Naming Scanned Documents",
  "updatedAt": "2026-02-09T19:19:01.000Z"
}