Documentation
Reviewing Data Gaps
Reading the view
Open the project's Data Gaps tab. In Report mode you get an Overall Status bar and an executive summary, then a breakdown you can drill into:
- Sections and categories each show how many questions are answered (e.g. 3/8).
- Each question shows a coloured result, the Answer LithicBlue found, and the Sources behind it (with file and page links).
- Results read as Yes, Unsure or No; the open gaps are everything that isn't a confident Yes.
Run or refresh the analysis
- With no results yet, click Run Research; once results exist, use Re-run Research to refresh against new documents.
- You'll see progress (Starting…, then Researching X/Y); a run can be cancelled, and a failed run offers Retry.
Research answers each question from your project's documents first, and will research the web and external knowledge bases where appropriate to fill the gaps; your own sources always take precedence.
In Edit mode you can adjust the questions, Regenerate them from the scope, or Quickstart with AI on an empty form. If you disagree with a result, click its coloured dot to override it (Yes / Unsure / No with a reason).
Requesting data from a client
When the missing evidence has to come from the client, click Request Data. It drafts an email covering the outstanding gaps, so you can chase exactly what the project needs in one go. Otherwise, close a gap by adding the source yourself: upload it, or let it flow in from a connected Google Drive or SharePoint folder, then re-run the research.
Two sides of the same coin
Data gaps and scope are the same analysis from opposite ends: scope shows what's answered, data gaps show what's still needed.