Onboarding

Create a research brief checklist for a virtual assistant

A checklist that states the decision a brief must support, the depth and finish line, the sources that count as evidence, and the way uncertainty is recorded.

By OnboardingEmployees editorial team | | 6 min read

Create a research brief checklist for a virtual assistant
On this page
  1. State the decision the brief must support
  2. Define the finish line and the depth
  3. List the sources that count as evidence
  4. Set a format that makes comparison easy
  5. Record uncertainty instead of hiding it
  6. Review the brief against the request
  7. Key takeaways
  8. Related reading

A research brief checklist is not a list of search terms and it is not a page limit. For a virtual assistant, the checklist should make the decision, the evidence standard, and the finish line explicit before the work begins. A brief that answers an interesting question but not the asked question wastes the reader's time. The checklist protects both the assistant and the person who requested the work.

State the decision the brief must support

Ask the requester what decision or action the brief will inform. A brief about vendor options may support a renewal decision, while a brief about competitors may support a cost discussion. Write the decision in one sentence at the top of the request. Without that sentence, the assistant cannot judge which facts matter.

Record the person who will read the brief and the person who will act on it. These may be different people, and they may need different levels of detail. The assistant should know whether the reader wants a recommendation or a summary of evidence. The format should follow the reader's job, not the assistant's preference.

Note the deadline and the cost of being wrong. A quick brief for a low-stakes meeting can rely on fewer sources than a brief that supports a contract decision. The assistant should record the confidence the requester needs. A high-stakes request deserves a slower review.

Define the finish line and the depth

Write what the brief must contain before the research starts. A comparison brief may need three options, a common set of criteria, and a recommendation. A landscape brief may need categories and examples rather than a winner. The checklist should state which type is expected.

Set a source minimum and a source mix. A brief that relies on three vendor pages is not the same as one that includes a regulator, an industry body, and a customer reference. The assistant should record the types of sources required. The mix matters more than the raw count.

Agree on the length and the format in advance. A one-page memo with a short table is often more useful than a long report with no clear recommendation. The assistant should know whether the reader wants an appendix. The appendix can hold detail without burying the answer.

List the sources that count as evidence

Name the source types that are acceptable for the question. Primary documents, regulator guidance, and direct interviews usually outrank a summary blog post. The assistant should record why each source was chosen. A source list without a reason is hard to defend later.

Check the date and the scope of every source. A regulation may have changed, or a market report may cover a different segment. The assistant should note the publication date and the population studied. A recent date does not fix a mismatched scope.

Record the source location as a link or a file reference that another person can open. A citation that only the assistant can find is not evidence. The brief should use the same reference in the text and the source list. This makes a later fact check possible.

Set a format that makes comparison easy

Use a consistent structure for every option or source. If the brief compares vendors, each vendor should have the same fields in the same order. The assistant should not let one option receive a longer narrative because it is more familiar. A shared structure exposes gaps.

Put the recommendation near the top and the supporting detail below it. The reader should be able to stop after the first section and still understand the answer. The assistant should state the confidence level and the main caveat there. The rest of the brief explains how the conclusion was reached.

Use a table only when the reader needs to compare the same attributes across rows. A table with empty cells or mixed units creates more work than it saves. The assistant should define every column and unit. A short note under the table can explain a missing value.

Record uncertainty instead of hiding it

Mark each important claim with the source that supports it. If a claim comes from an estimate, say so and describe the method. The assistant should not present a guess as a measured fact. A reader who discovers an unsupported claim will distrust the rest of the brief.

List the questions the research could not answer. A brief that admits a gap is more useful than one that fills the gap with confident language. The assistant should name what would be needed to close the gap. The requester can then decide whether more work is worth it.

Separate a disagreement between sources from a gap in the evidence. Two credible sources may report different figures because they use different definitions. The assistant should explain the difference rather than average the numbers. An average of incompatible measures is a new error.

Review the brief against the request

Read the original request again before sending the brief. Check that every required question has an answer or a stated gap. The assistant should confirm that the recommendation follows from the evidence. A brief can be well written and still miss the decision it was meant to support.

Ask a colleague to find the recommendation and the main caveat without reading the whole document. If they cannot, the structure needs work. The assistant should record the feedback and adjust the format. A brief is judged by what the reader can use.

Save the final brief with the request, the source list, and the date. Record which parts were used in the decision if the requester shares that information. The next brief will start from a better template. The archive also shows where the research added value.

Key takeaways

Write the decision the brief must support in one sentence before any research begins. Name the reader, the deadline, and the cost of being wrong. A brief without a decision is only a collection of notes. Record the reader's role as well, because a legal reviewer and a sales lead need different evidence in the same brief.

Define the required source types and the minimum depth in advance. Check the date and scope of every source and keep a link that another person can open. The mix of sources matters more than the count. If the request needs a recommendation, say so before the research starts rather than adding one at the end.

Use the same fields for every option and put the recommendation near the top. State the confidence level and the main caveat there. A consistent structure makes gaps visible. A table should define every column and unit so an empty cell cannot be mistaken for a zero.

Record what the research could not answer and why sources disagree. Review the brief against the original request before sending. A brief that admits uncertainty is more trustworthy than one that hides it. A short appendix can hold the source detail without pushing the recommendation further down the page.

Continue building the workflow

Related support: onboarding operations support, contact us. The U.S. Bureau of Labor Statistics - Secretaries and administrative assistants describes administrative support duties that include preparing documents and gathering information.