Outsourced Philippines guide
Make a Shared Drive Readable to a New Philippines Hire
A practical filing standard for distributed teams: fewer folders, descriptive names, version labels, an archive rule, and a finding guide a new hire can use.
A new Philippines-based hire can lose a week inside a shared drive that grew one folder at a time. Files sit under people’s names, the current contract shares a folder with three superseded drafts, and the only map is a message in someone’s inbox. A simple filing standard turns the drive from a personal archive into a place where a new colleague can find the current version without asking. The standard does not need to be elaborate, but it does need to be visible and enforced.
On this page
Map the folders people actually use
Before creating a new structure, list the folders that people open every week and the folders that nobody has touched in a year. Ask three team members to show you where they look for a client contract, a weekly report, and a current procedure. The gaps between their answers show where the drive is failing, not where the team is careless. The difference between those answers is the real specification for the redesign.
Build the top level around the work, not the org chart. A small set of durable areas such as clients, operations, finance, and reference material is easier to maintain than a folder for every manager or project. If a client needs its own space, put it under the client area and keep the internal work separate. The goal is a structure a new hire can predict.
Adopt names that describe the work
Use a consistent name pattern: the subject, the document type, and the version or period where relevant. A name like “Northwind contract 2026-03-14 signed” tells a reader more than “scan 0042.” Avoid names that depend on a person, a chat thread, or an internal code nobody outside the team understands. Reserve short codes for systems that require them, and document the code beside the folder. A name that only makes sense to the person who created it will fail the first handoff.
Write the pattern down with two or three real examples and one counter-example. Put the guide at the top of the drive so it is visible before a new hire opens a folder. Naming rules only work when people can see them at the moment they are saving a file, not in a policy document three levels away. Review the guide with one new hire and one long-tenured colleague before publishing it.
Set a version and status convention
Decide how the team will mark draft, review, approved, and superseded files. A simple status word in the file name or a controlled folder is enough if everyone uses it. The important part is that a reader can tell whether the document is safe to use without opening it and reading the first page. Apply the same status words in the file name and in the folder view so the two do not disagree.
Keep the current approved version in the main folder and move earlier versions into an archive subfolder with the date and reason for replacement. Do not rely on the drive’s automatic version history as the only record, because a new hire may not have permission to see it. The visible file should carry the status, and the archive should carry the history. The archive folder should be read-only for most of the team, with one owner who can restore a file.
Separate current files from archive
Archive by year or by client close date, and write the rule for what qualifies. A superseded procedure, a closed project, and a terminated client file all need a home, but they should not sit beside live work. The archive can be read-only for most of the team, with a named owner who approves retrieval or restoration. Write the archive rule into the onboarding checklist so a new hire does not create a parallel archive.
Review the archive on a schedule so it does not become a second unmanaged drive. Check that the retention period is still correct, that personal data is handled under the privacy policy, and that the index still points to the right folder. An archive nobody reviews is just a slower version of the original mess. Record the review date and the reviewer so the archive does not become a folder nobody can vouch for.
Write a one-page finding guide
Create a short guide that answers the questions a new hire asks in the first week: where client contracts live, where the current procedures are, where finished reports go, and who owns each area. Add a simple decision tree with three or four branches rather than a long narrative. The guide should fit on one page and be linked from the onboarding checklist. Link the guide from the top of the drive and from the onboarding checklist, not only from a chat message.
Test the guide with someone who did not write it. Give the person three finding tasks and watch where they hesitate. If they open the wrong folder, the guide or the folder name is wrong. Revise the guide and the structure together; a finding guide cannot compensate for a drive that is organized around old habits.
Audit the drive after the first month
After the new hire has worked for a month, ask which files they could not find and which folders they stopped using. Sample ten recently saved files and check the name, the status, and the location. Look for files saved to the desktop, duplicate folders, and documents with no owner. These small signals show whether the standard is being followed.
Fix the top three problems and write the changes into the guide. Then repeat the audit at the next onboarding rather than waiting for a annual cleanup. A filing standard is a habit, and habits drift when nobody checks the shelf. The measure is simple: a new colleague can find the current version of a document without asking a colleague.
Sources and next steps
Use the operations support work lane as a practical starting point, then review the onboarding checklist before expanding the role.