Name Client Documents So You Can Find Them

Decide what the filename needs to answer

A useful filename should answer three questions at a glance:

1. When does this document belong in the client's history?
2. What kind of document is it?
3. Where did it come from, when the source matters?

That is usually enough. The filename does not need to summarize the client's situation or repeat information that already lives in the client profile.

A practical pattern is:

YYYY-MM-DD - document type - source

For example:

• 2026-09-18 - release-of-information - signed.pdf
• 2026-08-04 - prior-provider-records - westside-clinic.pdf
• 2026-07-22 - insurance-letter - client-upload.pdf
• 2026-06-11 - referral - family-doctor.pdf

Use the date the document was signed, issued, or received, whichever will be most useful when someone reviews the record later. Pick one interpretation for each document type and write it into your rule.

Put the date first

Dates are much easier to sort when they follow the year-month-day format.

2026-09-18 will sit in the right order beside 2025-12-03. A date written as 9-18-26 may be read differently by different people, and a word such as "September" sorts alphabetically rather than chronologically.

Putting the date first also helps when several versions of the same document exist. You can quickly distinguish an older consent form from the one the client signed this year.

Avoid using the upload date automatically. If a practitioner scans a March referral in September, naming it with the September date can make the clinical sequence harder to understand. Use the meaningful document date when it is clear. If it is not clear, use the received date and make that choice consistent.

Use a small list of document types

Consistency matters more than the perfect label.

One person may call the same file a "doctor letter," another a "referral," and another "medical paperwork." All three names may make sense, but they make searching less reliable.

Start with the document types your practice actually receives. Your list might include:

• referral;
• release of information;
• prior provider records;
• insurance letter;
• consent form;
• assessment report; and
• client correspondence.

Keep the list short enough that a team member can choose without consulting a manual. If two labels seem interchangeable, keep the plainer one.

Review the list after a month. Add a category only when several files genuinely do not fit. A list with eight useful types is better than a list with thirty precise types that nobody remembers.

Keep sensitive detail out of the name

The document itself may appropriately contain private health information. The filename usually does not need to.

Avoid putting a diagnosis, a detailed reason for referral, a medication name, or a summary of a difficult event in the filename. File names can appear in download folders, browser history, operating-system search, backup tools, or screenshots. Use the minimum detail needed to recognize the document.

For example, prefer:

2026-09-18 - assessment-report.pdf

over:

2026-09-18 - anxiety-and-trauma-assessment.pdf

Inside a client profile, you may not need the client's name in the filename either. The profile already tells you whose document you are viewing. If your workflow requires files to be downloaded or transferred outside that context, decide how your approved process will keep them connected to the right record without creating unnecessary exposure.

Rename the file before you upload it

Make renaming part of receiving the document, not a cleanup job for later.

When a file arrives:

1. Confirm that it belongs to the correct client.
2. Check that the pages are complete and readable.
3. Choose the meaningful date.
4. Apply the standard document type.
5. Add the source only when it helps distinguish the file.
6. Upload it to the client record.
7. Open the stored file once to confirm it is the right document.

This takes less than a minute when the rule is familiar. It also catches practical problems early, such as a scan saved sideways, a missing signature page, or two clients' pages combined into one PDF.

If several files arrive at once, rename and verify them one at a time. A batch of nearly identical scans is where mistakes become easy to make. Speed is useful only if every document still lands with the right person.

Do not make version words carry the history

Names such as final.pdf, final-new.pdf, and final-revised-2.pdf tell you how the file moved through someone's computer, not where it belongs in the client record.

Use the meaningful date to separate versions. If two documents of the same type share a date, add one plain qualifier such as signed, amended, or provider-copy.

For example:

• 2026-09-18 - release-of-information - signed.pdf
• 2026-09-18 - release-of-information - amended.pdf

Do not overwrite an older document simply because a newer one exists unless your retention rules clearly allow it. The older version may still matter to the history of consent, communication, or care. Follow the record-retention and professional rules that apply to your practice.

Give the rule a five-file test

Before you teach the system to everyone, try it on five different documents from your normal work.

Choose a clean PDF, a phone photo, a multi-page scan, a document from another provider, and an updated version of something already on file. Ask a colleague to identify each one using only the filename and its place in the client record.

Then check:

• Can they tell what each file is without opening it?
• Do the dates sort in a useful order?
• Are any labels unclear or too similar?
• Does a filename reveal more health detail than necessary?
• Can the rule handle a second version without adding "final-final"?

If the rule fails, simplify it. A naming system should reduce decisions at the moment of upload. If people need a chart to decode every abbreviation, the system is creating another form of clutter.

Make the rule visible where the work happens

Write the pattern in one line and place it beside the scanner or in the team's short procedure for incoming documents:

Date first, then document type, then source if useful. No diagnosis or detailed health information in the filename.

If you work alone, the rule is still worth writing down. A busy month is enough to turn a clear habit into a folder full of mystery scans.

If you work with a team, choose one person to answer edge cases for the first few weeks. Correct the shared rule when the same question appears twice. Do not build a private list of exceptions that only one person understands.

Make each upload easier to trust

Good filenames do not replace a complete client record. They remove a small but frequent source of friction inside it.

Put the date first, use a short list of document types, keep sensitive detail out of the name, and verify the stored file before you move on. The result is simple: fewer mystery files, fewer unnecessary opens, and a clearer history when you need it.

Stillpoint's client Documents section keeps outside records with the client they belong to. You can upload or drop PDFs and images up to 25 MB, watch the upload progress, and open the stored document from the client profile when you need it.