Once verification is complete and the verifier has notified you they are finished, you should now have all usable sections of ResearchOS, and you are ready to scope out the project.

• On average, we provide 15-20 separate data points per three-hour request. We will use this to scope out the rest of the project.
  • We can use this to “round out” or complete a research path by ONLY having the analyst fill in the missing pieces.
    • IE: We wouldn’t spend three hours on a best practices request just because it was missing success metrics. We can just ask the analyst to find success metrics.
  • If a project is on the harder side, we will want to ask the analyst to provide no more than 15 data points. If it is an easier topic, we can push the scope to 20.
  • Keep in mind that certain data points are grouped together, and we can count them as one. Generally, if we ask for information about a company, like founding date, location, etc., and we know that will be found all on the same website, like Crunchbase, for example, we can count that as one data point.
    • Just make sure they are easily accessible and are simple copy/paste types of information.
    • We would not want to group together data points and count them as one if the analyst needs to provide analysis, synthesis, or explanations.
• We would not put a client update through this process. We would only use verification for those projects where ResearchOS provided information.
• Use the Edit Request feature to raise the scope to the desired amount. If the project would need to be adjusted more than 6 hours, notify a Lead to review. (NOT LIVE YET)
• Scope in research paths, not project types. This will make your job so much easier.
• Don’t create a whole new research path unless it is absolutely necessary.
• When writing RCs, make sure they align with the research paths.
• It is hard to figure out where to put something when things are different across our scoping. For example, if the research path is Fall Home Improvement Projects Consumers Undertake, we would not want to put something like Consumer DIY Projects in our RCs. It makes it too hard for the analyst to put everything where it needs to be.
• Think Teammate scoping. Try to move away from being so exact in our scoping.
  • For those concerned, we have had no issues with analysts using Project Types to complete jobs. Make your job easier and move away from being exact with your scoping.
  • There are times when the client has a very exact ask. In those cases, it is perfectly fine to use traditional scoping methods.
• Let’s walk through an example request to show how we will scope.
  • Over-Processed Food
    • Over-Processed Food After Verification
  • Factors that Make for a Great Company Culture
    • In this one, ResearchOS met all the objectives. Check it out to see the plan!

Obtain ResearchOS

1. This Tango shows you how to access the AI Admin Dash so you can access your ResearchOS.
   1. You will notice that the client's name is also shared. This is the easiest way to locate the run you need.
2. Create a document and paste the ResearchOS run.

Analyzing ResearchOS

**Here is an example of a Verified ResearchOS run.**

1. Paste in all the objectives from the ResearchOS run at the top.

1. Convert the objectives to the appropriate headers that you would need in the research editor. Below are example headers for the first objective.
   1. US Television Industry Overview
   2. US Television Industry Key Players
   3. US Television Trends
2. Delete all summaries from each research objective, but leave the executive summary.
3. Place all usable data under the correct headers.