Philippines staffing guide · Published
On this page
Set up a document naming standard for scanned client files
A naming standard that helps a remote assistant file scanned client documents consistently, avoid duplicates, and keep sensitive identifiers out of visible filenames.
A scanned client document is easy to create and hard to find three months later. The scanner produces a generic name, the assistant adds a note, and the file lands in a folder that made sense to one person at one moment. A naming standard fixes this with a short pattern that every file follows, so search works without opening twelve PDFs to check their contents. The pattern also gives a reviewer a quick way to spot a missing or misfiled item.
The standard should be simple enough to apply at the scanner and specific enough to survive a handoff. It also needs a privacy rule, because a filename is often visible in shared screens, email attachments, and backup tools. Agree on the pattern, document the exceptions, and test it on a small batch before changing years of existing files. A standard that only one assistant understands will fail on the first busy week.
Choose the fields the name should carry
Most client document sets need four pieces of information: the client or matter reference, the document type, the document date, and a version marker. That is enough to sort a folder and enough to find a specific item without opening it. Resist adding staff names or workflow states, because those change and will force a rename later. A stable name describes the document, not its current owner.
Write the order down as a pattern with examples. For instance, use the client reference first, then the document type, then the date in year-month-day form, then a version only when more than one copy exists. Show a correct name beside a rejected name so the rule is concrete. Keep the pattern in the shared operations manual rather than in a chat message that will be forgotten.
Fix the date format once
Use a single date format across the whole repository. Year first, then month, then day sorts correctly and cannot be confused with a day-first format used by a client in another country. Write the four-digit year every time, because a two-digit year becomes ambiguous as records age. The date should reflect the document itself, not the day it was scanned.
When the document has no date, use a documented convention rather than leaving the field empty. For example, mark the date as unknown and add the period covered by the document in the type field. Do not invent a date from the file creation time, because that records the scanner's clock rather than the document's history. A consistent placeholder is more useful than a confident error.
Handle versions and duplicates
Add a version marker only when a document is replaced or corrected. Use a simple sequence such as v1, v2, and v3, and keep the earlier version until the retention rule allows deletion. The newest file should never overwrite the old one silently, because a reviewer may need to see what changed. Mark superseded files clearly so the folder does not present two current-looking documents.
Duplicates arrive through re-scans, forwarded copies, and two assistants working the same intake. Before saving a new file, search by the client reference and the document type. If a likely match exists, compare the first page and the file size rather than trusting the name alone. Merge only when the content is identical, and record the merge in the intake log so the decision can be reviewed later.
Keep client identifiers out of visible names
A filename travels further than the folder it lives in. It appears in email subject lines, download lists, and support tickets. Avoid full account numbers, government identifiers, and health details in the name. Use an internal client reference that maps to the full record in the practice management system, and keep the mapping table access-controlled.
If a client requests a copy of a file, rename the exported copy for the client rather than exposing the internal pattern. The internal name can stay in the repository, and the client-facing copy can use a neutral label. Document both names in the intake row so the two versions can be matched without guesswork. This small step prevents an identifier from leaking through a routine file share.
Apply the rule at the scanner
The best naming rule fails if it depends on a rename after the fact. Set the scanner or intake tool to prompt for the client reference and document type before the file is saved. Where the tool cannot prompt, create a cover sheet with those fields and scan it as the first page. The assistant can then read the fields from the image instead of reconstructing them from memory.
Give new team members a one-page card with the pattern, two examples, and the privacy rule. Ask them to name five sample files during onboarding and review the results together. Correcting a new habit early is easier than repairing a shared folder later. The card should name the person who approves exceptions, so an unusual document does not stall at the scanner.
Audit a sample every month
Pull a random sample of twenty files each month and check them against the pattern. Record the client reference, type, date, and version field for each file, and note every mismatch. Group the errors by cause, such as a missing scanner prompt or an unclear document type. The goal is to fix the cause rather than to rename the same files every month.
Report the sample result in the weekly operations note with one corrective action. If most errors come from one document type, simplify that type or add it to the scanner menu. If errors cluster around one intake shift, check the handoff instructions for that shift. A monthly sample of twenty files is small enough to complete and large enough to reveal whether the standard is actually working.
Questions and operating boundary
Should existing client files be renamed to the new standard?
Only as part of a planned migration with a backup and a mapping log; do not rename live folders during routine intake.
Can the client name replace the internal reference?
No. Use the internal reference in filenames and keep the client name in the access-controlled record.
What belongs in the version field when there is only one copy?
Leave the version marker off until a second copy exists, so the pattern stays short and the exceptions are meaningful.
Source
irs.gov provides authoritative background and does not endorse this service.