> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/content-designers/from-client-needs-to-a-varbase-plan/run-a-discovery-session.md).

# Run a Discovery Session

Discovery turns a client's requests into needs you can plan against. Ask by topic, listen for the need behind each request, and write down the constraints and the people who decide.

## Questions by Topic

Ask questions grouped by topic:

| Topic                   | Ask                                                                          |
| ----------------------- | ---------------------------------------------------------------------------- |
| Content                 | What do you publish, how much, how often, and who writes it?                 |
| People                  | Who reviews and approves, in which roles?                                    |
| Pages                   | Which pages do you want to build and change yourselves?                      |
| Languages               | Which at launch, which later, who translates, and is anything right to left? |
| Search, forms and email | What must visitors find, what do they send you, and where should it go?      |
| Security and privacy    | Which rules and standards must you follow?                                   |
| Integrations            | Which other systems must the site talk to?                                   |
| AI                      | Eager, careful or not yet? Which provider and budget?                        |

* **Listen for the real need.** Behind "a chatbot" may be "visitors must find answers faster"; behind "a new design" may be "pages editors can change". Ask why, twice, and write the need next to the request.
* **Collect constraints**: accessibility level, privacy laws, hosting rules such as data staying in one country, procurement and security questionnaires.
* **Map the people**: the sponsor, the day-to-day decision maker, weekly users, and which decisions need IT, legal or communications. Many delays come from decisions, not building.

Next: [Map Requirements to Varbase](https://docs.varbase.vardot.com/content-designers/from-client-needs-to-a-varbase-plan/map-requirements-to-varbase.md).
