Project · Finance · Quality · Safety
See the contractas your role needs it.
Upload once. Every answer cites the clause.
9 role views · Minutes to brief · Clause-level citations
Documents and prompts stay in your deployment. When the documents do not support an answer, it says so.
Evidence
The answer sits next to the clause it came from.
Every information need maps to a passage in the documents, or is marked as not found. Nothing is guessed.
Sopimus 2026 · §9.2 Payment schedule
“The contract price is invoiced in three milestones: 30 % on approval of the design package, 50 % on delivery, and 20 % on final acceptance.”
Milestone dates, amounts and invoicing triggers
“The contract price is invoiced in three milestones: 30 % on approval of the design package, 50 % on delivery, and 20 % on final acceptance.”No clause in the uploaded documents addresses this.
Penalty conditions and exposure
Not found in the documentsHow it works
Four moves. Same files.
- 01
Upload
Contract and annexes land in one project.
- 02
Index
The files become one shared layer, read once.
- 03
Read by role
Each role gets its own cut of the same pages.
- 04
Cite
Every answer points back to the clause, or says it found none.
Roles
Same pages. Different questions.
- 01Finance ManagerCostWhat payment milestones and guarantees apply to this project?
- 02Project ManagerTimelineWhat are the most important obligations before kick-off?
- 03Designer / EngineerSpecWhich standards and drawings constrain the design?
- 04Purchasing ManagerSupplyWhat must I include when ordering materials?
- 05Safety / HSESiteWhat safety obligations apply at installation?
- 06Quality & WeldingConformityWhich welding, inspection and documentation requirements apply?
- 07ManagementExposureWhat deserves management attention before we start?
- 08SalesScopeWhat do I need to pass to the project team?
- 09Life-cycle servicesSupportWhat needs to be retained for long-term support?
Trust
Built so a claim can be checked, not just trusted.
The evidence model is enforced in how the data is stored, not only in how it looks.
- 01Project-isolated
A role only ever reads documents uploaded to its own project.
- 02Verified, not guessed
A claim must quote text found in a retrieved passage. What cannot be verified is marked unsupported, not hidden.
- 03Logged decisions
Correcting or rejecting a fact needs a reason, and is recorded against the person who made the call.
- 04Deletion takes effect at once
Removing a document drops its text from every answer immediately — no re-indexing step to wait on.
- 05Stays in your deployment
Documents and models run inside your own infrastructure.
RoleCite