> ## Documentation Index
> Fetch the complete documentation index at: https://terrascout.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Research workflow

> Follow a Ploti research request from intake through decision-ready maps and evidence

# One workflow from question to map

Ploti's primary workflow is a research request. You provide the goal and context; Ploti checks the data, completes the research, and preserves the outputs in your workspace.

```text theme={null}
Research brief → Data readiness → Research run → Artifacts → Map and follow-up
```

<Steps>
  <Step title="Create the request">
    Describe what you need to learn, where, why it matters, and what a useful
    answer should contain. Attach files and source links when they add context.
  </Step>

  <Step title="Check data readiness">
    Ploti evaluates the workspace datasets against the request, explains what is
    ready, identifies missing data, and asks for clarification when needed.
  </Step>

  <Step title="Run the research">
    Start with the available data, request missing datasets, or run an interim
    analysis while data agents fill the gaps. Work continues on Ploti's servers.
  </Step>

  <Step title="Review artifacts">
    The request page collects the maps, checkpoints, tables, saved queries,
    documents, plans, and files produced by the run.
  </Step>

  <Step title="Continue on the map">
    Open a result to inspect features, combine layers, ask follow-up questions,
    export data, or save important findings as records.
  </Step>
</Steps>

## Geography is context

Put the market, jurisdiction, corridor, address, or study area in the request. When an exact shape matters, you can use a map boundary as input. A boundary is not an agent mode and is not required for every request.

## Requests can be broad or property-specific

The same workflow supports market research, site selection, owner research, ordinance questions, portfolio analysis, and a deep dive on one property. You do not need to select a different agent for each job.

## Next steps

<CardGroup cols={2}>
  <Card title="Create a request" icon="file-pen" href="/docs/research/creating-a-request">
    Learn how to write the brief and attach context.
  </Card>

  <Card title="Understand data readiness" icon="database" href="/docs/research/data-readiness">
    See what happens before the full research run.
  </Card>
</CardGroup>