AI suggestionAccepted
MOM-004 · Kickoff meeting minutes
Decision aboutSOW-001
AcceptReject
Linked
(00)Product / Project Intelligence
Different teams write a project's requirements, proposals, contracts, invoices and acceptance records over many months. Project Intelligence connects them to the project and to each other, so anyone reviewing a decision can see its context without assembling it by hand.
(01)Scattered context
The requirements sit in one folder, the meeting minutes in another, and the progress reports arrive by email. Before anyone can answer a simple question about the project, someone has to find those records and work out how they relate to each other.
This is an illustrative example.
(02)One project, one map
The project sits on the left, and its documents fill three rows to its right. Requirements and proposals sit at the top, the order, contract and amendment fill the middle, and invoices and acceptance records sit at the bottom. Every line carries a label that says how two documents relate, such as “Sets requirements for”, “Amends” or “Bills for”.
The project arrives first, with its client, its status and the documents linked to it.
The recorded documents join it row by row, and each one belongs to the project.
The contract and its amendment take the middle row, and the older proposal moves aside because a newer revision has superseded it.
AI suggests three new connections, and each one appears as a dashed line until someone reviews it.
The suggestion that the October invoice bills for the purchase order opens with its supporting quote.
Someone on your team accepts it, so the line becomes solid and two suggestions remain for review.
Nothing is linked until someone on your team accepts it, and access to a project does not open documents that are restricted.
(03)AI suggests, your team decides
Each suggestion shows the evidence behind it, including the supporting quote and the page it came from. Your team confirms the project, the scope of the connection and the final decision, so a person stays accountable for the map.
(04)One record, many projects
You can connect documents and contract workspaces to a project with a defined role and scope. When a record is relevant to another project, you connect it there as well, so the same file is reused rather than duplicated.
Project Intelligence also connects requirements, responses, progress reports and recorded decisions, which helps reviewers understand how each document relates to the work.
Document
SOW-001 · Statement of work
StatusFinal
Project
Head-office Backup Refresh
Project
Branch Backup Rollout
(05)Find and check
Search documents by their content or by meaning, and ask questions within the records you are allowed to see. Every answer cites its sources, so you can open them and check the answer yourself.
Summaries, extracted fields and suggested classifications help you review content faster, and your team checks each suggestion before it is applied.
Sample data
(06)Find related documents
Start with a few examples, either example documents or an example folder, and press Find connections. AI then suggests related documents and the connections between them, and each suggestion waits in the review queue with its evidence.
Existing linked project documents are also included as context, and nothing is linked until you review and accept a suggestion.
Project Intelligence and Contract Intelligence are the two halves of one module, Contract & Project Intelligence, and you license them together. AI discovery also needs the AI module, and it only uses documents that the person asking is allowed to open. An administrator can run a local model, use an approved provider or switch AI off for the whole deployment.
(07)Your project
Using safe samples from that project, we will review its requirements, meeting minutes and progress reports with you, and we will agree on the evidence that a pilot should test.
Capabilities depend on the modules you choose.
Also explore: Contract Intelligence Collaboration Document Control