Gleanings
A reasoning agent reads schedules, drawings, budgets, and meeting notes together, then ranks conflicts by anticipated cost and schedule impact.
The interface is built for triage rather than exhaustiveness: a project manager needs the three discrepancies worth acting on, with the evidence chain still attached.
Role
Product designReasoning architectureBuild
Outcome
A handed-off project-reasoning workflow that turns cross-document conflict into a prioritized, inspectable action list.
The triage model
Find the three conflicts worth acting on.
Project risk appears between documents: a schedule and drawing set, a budget and field note, an RFI and the decision it awaits. Gleanings reads those records together, surfaces scope drift and unresolved dependencies, then ranks findings by anticipated cost and schedule impact. Every issue keeps its source trail attached. The system replaces an exhaustive discrepancy list with a short, evidence-backed queue a project manager can confirm, reject, or investigate.
01 · Ranked register
Risk becomes an inspectable queue.
Portfolio reconstruction from the handed-off workflow
02 · Evidence chain
The claim stays attached to its record.
Finding
Fabrication starts before the coordinated drawing releaseHuman review gate
At a glance
4+ heterogeneous source classes · Cost-and-schedule conflict ranking · Human review gate
In the record
File-ingestion and reconciliation map · Ranked discrepancy interface · Finding-to-source evidence trail · Schedule / drawing / budget cross-checks · Cost-and-schedule ranking model · PM confirmation and dismissal states
Read across the project
Schedules, drawings, budgets, RFIs, and notes stay distinct while the system searches for consequential disagreement between them.
Rank what compounds
Findings are ordered by anticipated cost and schedule impact rather than by detection order or document type.
Keep the source attached
Every proposed issue points back to the evidence a project manager needs to confirm or dismiss it.