Project Management

When you scope a project, LithicBlue breaks it into sections, and each section into the requirements it needs to satisfy. As the project knowledge base grows, it analyses your sources against those requirements and tracks how well each one is fulfilled, with every answer traced back to the passages that support it.

• Overview. See per-section fulfilment at a glance: which sections are answered, which are still thin.
• Section detail. Open a section to read its requirements, the answers LithicBlue found, and the source references behind each one.
• Re-run. As you add documents or refine the scope, re-run the analysis to refresh fulfilment against the latest evidence.

Data gaps are the flip side of scope: what the project still needs. LithicBlue surfaces the open questions a section can't yet answer from the documents you've provided, so you know exactly what to chase before the analysis is defensible.

• Overview. A count of open gaps per section, so you can prioritise.
• Section detail. The specific open questions for a section, with any partial sources already found.

Closing a gap is usually a matter of bringing in the missing source: upload it, or let it flow in from a connected Google Drive or SharePoint folder, then re-run the analysis.

Across a real project, documents disagree: an earlier board pack says one thing, a later model says another. LithicBlue identifies where claims drawn from your sources contradict each other and brings them to you for a decision, rather than silently picking a winner.

• Review. Work through detected contradictions, each shown with the conflicting claims and the source documents (and dates) they came from.
• Validate or override. Agree with LithicBlue's assessment, or override it; your decision is what stands.
• Document authority. Set authority levels on documents so that, when sources conflict, the more authoritative one is trusted to resolve the contradiction.