Onboarding

Build a reference library a virtual assistant can search in one pass

A small reference library with stable names, a visible owner, and a search rule that lets a virtual assistant find the current answer without asking twice.

By OnboardingEmployees editorial team | | 5 min read

Build a reference library a virtual assistant can search in one pass
On this page
  1. Start with the questions, not the folders
  2. Give every entry a stable name
  3. Mark the owner and the review date
  4. Write the search rule
  5. Retire what no longer applies
  6. Test the library with a stranger
  7. Related reading

Start with the questions, not the folders

A reference library should be built from the questions the role actually receives. Collect the first two weeks of questions from the assistant, the manager, and the client. Group them by the decision they support rather than by department. A library organized around real questions is easier to search than one organized around an old folder structure.

Choose the ten questions that occur most often and write a short answer for each. Link the answer to the source document that supports it. If the answer depends on a client preference, say so and name the person who confirmed it. A library that mixes general rules and client-specific choices without labels will mislead the reader.

Keep the question list in the library's own workspace so it can be updated as the role changes. A question that appears only during a busy season still belongs in the review. Note the date the question first appeared. That context helps the next trainer decide whether the answer is seasonal or permanent.

Give every entry a stable name

Use the same title for the same topic everywhere: the library, the task instructions, and the client emails. A stable name lets a search find the entry even when the reader does not remember the folder. Avoid cute labels or internal shorthand that a new person cannot guess. A reader who finds the old title should be led to the current one rather than left to guess.

Add a short description under each title that states when to use the entry. A title like leave policy is too broad. A title like leave request for a salaried client employee is specific enough to route the reader. Keep the description to one sentence so it remains scannable.

Ask the assistant to add a question that the library does not answer but that comes up often. The request is a signal about the next entry, not a complaint. Review the request at the weekly check-in and decide whether to write, redirect, or retire the topic. That habit keeps the library connected to live work.

Mark the owner and the review date

Every entry needs an owner and a date. The owner is the person who can confirm that the answer is still correct. The date shows when it was last checked. An entry without an owner becomes folklore, and an entry without a date cannot be trusted after a policy change.

Put the owner and date at the top of the entry, not in a metadata panel nobody opens. When the answer changes, update the date and add a short note about what changed. Do not delete the old answer if it explains a decision that is still in flight. Mark it superseded and link to the new entry.

Use a naming rule that puts the topic before the client name, such as leave request — client name. That order helps a reader browse by topic while still finding the client-specific version. Apply the rule to file names as well as titles. A consistent order reduces the number of near-duplicate entries.

Write the search rule

Tell the assistant how to search before telling them what to memorize. Start with the exact task name, then try the client name, then the system name. If the first search fails, use the index rather than opening folders at random. A search rule saves time and makes the result easier to explain.

Keep a one-page index at the top of the library. The index should list the main question groups and the entry that answers each one. Update the index when a new entry is added. An index that is out of date teaches the reader to distrust the library. Review it at the same time as the entries.

Use the same date format everywhere so a reader can sort entries without guessing. A mix of month names and numeric dates slows a search and can hide an old entry. Choose one format and apply it to titles, descriptions, and review notes. The format is small, but it reduces avoidable confusion.

Retire what no longer applies

A reference library grows faster than it shrinks unless someone owns the retirement. Review the entries at a fixed interval and mark the ones that no longer match the work. Remove a retired entry from the main index but keep it in an archive. The archive explains why the team used to do something differently.

Tell the assistant when an entry is retired. A quiet deletion leaves the old answer in someone's memory. Add a short note to the replacement entry that names the old one. That link helps a reader who remembers the old rule find the new one without asking.

Ask the owner to confirm the retirement rather than deciding alone. The owner may know that a rule still applies to one client even though it was removed from the general guide. Record the exception and the client it covers. A retirement that ignores an exception creates a new gap.

Test the library with a stranger

Ask a person who has not worked on the role to answer five common questions using only the library. Time the search and note every question they cannot answer. The test shows whether the library works for a new reader, not whether the author can find their own work. Their search path is often more informative than the final answer.

Fix the two most costly gaps and test again with a different set of questions. Keep the test notes with the library version. A library that has never been searched by a stranger is still a draft. The goal is a first pass that finds the current answer, not a perfect archive.

Keep a short changelog at the top of the library. It should list the date, the entry, and the reason for the change. A reader who remembers an old answer can find the replacement without asking. The changelog also shows the owner that the library is being maintained rather than rewritten.

Continue building the workflow

Related support: onboarding operations support, contact us. The U.S. Bureau of Labor Statistics — Secretaries and administrative assistants context on the administrative tasks and information handling a support role performs.