Skip to main content

Documentation

Checking Progress Against Scope

The Scope view shows how well your source documents satisfy what the project set out to answer: overall, by section, and down to each requirement and its sources.
The Scope view showing overall completion and per-section fulfilment
Overall completion, the breakdown by section, and a status for each requirement.

Open the Scope view

On the project, open the Scope tab. It has two modes: Report (read the analysis) and Edit (change the scope itself). Start in Report.

Read the results

  • Overall Completion. A weighted bar at the top, segmented by status: Completed (green), Partial (yellow), Not Found (red) and Pending (grey).
  • Executive Summary. A written summary of where the scope stands, once analysis has run.
  • Sections. Each section (phase) shows its own progress bar and an answered count such as 2/5. Expand one to see its requirements.
  • Requirements. Each shows its research question, a coloured result, an Assessment (the answer LithicBlue found) and a Sources list you can click through to the underlying documents.

Run or re-run the analysis

Saving a scope in Edit mode (Save scope) automatically kicks off the research. To refresh an existing analysis, use the menu in Report mode:

  1. Re-check for changes: a cheap incremental pass that picks up new or changed documents.
  2. Full re-run: re-researches every requirement from scratch (it asks you to confirm).

While it works, the status reads Analysing…; otherwise it shows Last checked with the time of the most recent pass.

Override a result

If you disagree with an automatic result, click its coloured result dot to open the override dialog. Choose Yes, Unsure or No, give a reason (required), optionally point to a reference file, and click Save override. Your decision then stands in place of the automatic one.

Closing the gaps

Where the scope isn't yet satisfied, the project's Data Gaps tab spells out exactly what's missing: run Run Research / Re-run Research there, or use Request Data to draft an email to the client for the missing inputs. See Project management for the bigger picture.

Check it from your assistant

The same analysis is readable over the MCP connector with get_scope_status and get_data_gaps.