Start with a document someone needs to find
Choose one recurring workflow: a supplier invoice packet, employee onboarding file or signed customer agreement. Ask the receiving person to show how they locate the current approved record. Missing attachments, unclear versions and private inbox copies are different problems and need different fixes.
Create a small document register
A register links people to the authoritative file. It should not become another uncontrolled copy of sensitive documents.
| Register field | What to record | Why it helps |
|---|---|---|
| Record reference | Stable internal identifier | Connects related files without relying on names alone |
| Document type | Agreement, invoice or supporting evidence | Applies the right review rule |
| Source location | Approved repository link | Keeps one retrievable source |
| Status | Draft, under review or approved | Prevents draft use as final evidence |
| Owner and reviewer | Named responsible people | Gives exceptions a destination |
| Next action | Missing item or review deadline | Makes incomplete work visible |
Agree names before reorganizing files
Use a consistent date format, record reference and document type. For example, an illustrative supplier packet might use 2026-10-30_SUP-042_Invoice_INV-107_Draft. Avoid unnecessary personal information in filenames. Where the repository has reliable version history, use that instead of accumulating files named final, final-new and final-approved.
Example: a supplier packet with a missing approval
The assistant finds an invoice and receiving record but cannot locate approval. They link the two documents in the register, mark the packet incomplete and assign the missing approval to the authorized reviewer. They do not label the invoice approved simply because it has been uploaded. Once the reviewer supplies the decision, the assistant records its location and updates the packet status.
Separate preparation from permission decisions
An assistant can organize approved folders, apply naming rules, identify missing items and prepare a review queue. Your internal owner decides who may access restricted records, which version is authoritative and whether a record can be deleted. Stop and escalate conflicting instructions, unexpected sensitive material or a legal hold.
Test retrieval before expanding the workflow
Ask someone who did not organize the files to locate a sample using the register. Check that links open with their intended permissions, approved and draft versions are distinguishable, and missing documents remain visibly unresolved. Correct the structure before moving a larger collection. Preserve a migration record so misplaced files can be traced.
Keep the handoff useful
At the agreed review interval, return completed packets, missing items, broken links and decisions awaiting an owner. Measure retrieval failures and unresolved exceptions, rather than the number of folders created. Document management support can cover this preparation and follow-up within your approved process.
Practical questions
Should every department use the same folder tree?
Use shared conventions where they improve retrieval, but separate access and retention rules when the records require it. A personnel file and a public supplier brochure should not inherit the same permissions.
Can the assistant delete duplicate files?
Only under an approved rule with an identifiable authoritative copy and a recoverable process. Similar filenames are not proof that contents, signatures or linked history are identical.
What should remain with the business?
Access approval, retention decisions, legal holds and final acceptance of the organized records stay with designated internal owners.