Overview
Discovery Questions help you find and fill the gaps in a project's requirements. Based on the categories and capabilities you select for a project, Glossa seeds a set of targeted questions — the things a good discovery process would ask but that your uploaded files may not have covered yet. As you answer them, Glossa can turn answers into requirements, and you can ask Glossa to generate follow-up questions that dig deeper — so your requirement set gets more complete without you having to guess what's missing.
Discovery Questions live at the project level. Open them from Questions in the project navigation.
Key Concepts
Categories and Capabilities
Categories are attached to a project and determine which questions Glossa seeds. You choose categories when you create a project (see Creating Projects) and can adjust them later from the Questions page. Deselecting a category means Glossa won't ask questions about it.
Questions
Each question targets a specific gap. A question can be:
Unanswered — waiting for your input
Answered — you've provided an answer
Skipped — you've set it aside
Follow-up questions
After you answer a question, click Let's dive deeper to have Glossa generate follow-up questions that dig deeper into your answer. Follow-ups are organized under the question that prompted them ('topics').
Suggested closes
As your requirements grow, Glossa may detect that an existing requirement already satisfies an open question and suggest closing it. You can accept the suggestion or dismiss it.
Selecting Categories
Categories are chosen during project creation, in their own step, and can be changed afterward:
When creating a project, select the categories relevant to the engagement (see Creating Projects).
To change them later, open Questions in the project and adjust the selected categories.
Glossa seeds an initial set of questions for the categories you select.
Answering Questions
Open Questions in the project navigation.
Work through the open questions. For each, enter your answer (or ask it in your meeting, and know that the meeting recording will answer it)
Optionally, choose to generate a requirement from your answer. Glossa creates a draft requirement and links it back to the question and answer (visible on the requirement's detail view — see Requirements Management).
To go deeper on an answered question, click Let's dive deeper. Glossa generates follow-up questions based on your answer, grouped under that question.
Answers from Uploaded Files
You don't have to answer every question by hand. When you upload a document or a meeting recording, Glossa checks the content against your open discovery questions and automatically answers any it can confirm from the source. Auto-answered questions are marked as answered and show which file they came from. Review automatically answered questions the same way you would your own.
When a question was answered from an uploaded file, the answer shows a Source: label with the file name, so you can see at a glance where it came from.
Sharing Questions with Your Client
Some discovery questions are best answered by the client directly. You can mark a question as client-facing to share it in the client portal, where your client can answer it asynchronously — before your discovery sessions instead of during them.
Client answers appear alongside your own in the Questions view, labeled with the contact's name so you can see who answered.
You can generate a requirement from a client's answer, the same way you would from your own.
Clients only ever see the questions you've marked as client-facing — nothing else from the Questions page is visible to them.
See the Client Portal article for how the portal works, and Client Review Experience for what your client sees.
Skipping Questions and Topics
You can set questions aside without answering them:
Skip a single question to remove it from your open list.
Skip a topic to stop being asked further questions on that thread (for example, "I don't need any more questions on this topic"). Already-answered questions are left untouched.
Triaging Suggested Closes
When Glossa suggests that an existing requirement already answers an open question:
Accept the suggestion to close the question as satisfied.
Dismiss the suggestion to keep the question open.
When a question has been satisfied by a requirement, the Questions view shows a Resolved by Requirement link to open that requirement directly.
Suggested Question Matches on New Requirements
When you manually add a requirement to a project, Glossa checks your open Discovery Questions for ones that the new requirement may already answer.
If Glossa finds likely matches, you'll see a prompt to review suggested questions for that requirement
Confirm a match to link the question to the requirement and mark it answered
Dismiss to leave the question open
This is separate from Suggested closes, which Glossa surfaces automatically as your requirement set grows — this flow triggers specifically when you add a new requirement by hand.
Exporting
You can export discovery questions from the Questions page.
Best Practices
Pick categories deliberately. Only select the areas relevant to this engagement so you're not asked questions that don't apply.
Answer early, then iterate. Working through Discovery Questions soon after uploading your first files surfaces gaps while discovery is still active.
Generate requirements from answers when the answer is concrete. This keeps requirements traceable to the discovery conversation.
Use suggested closes to avoid duplication. If a requirement already covers a question, closing it keeps your open list focused on real gaps.