Trunk Tools

Trunk Tools ingests a construction project's documents, drawings, specifications, submittals, RFIs, contracts and schedule, and lets a superintendent ask a question in plain language and get an answer with a citation to the source page. TrunkText handles the question and answer path, including by text message so a foreman does not need to open a laptop. Other components review submittals for conflicts against the specification, draft RFI language, and tie schedule activities to the documents that support them. What makes it commercially interesting is that it does not try to replace the document system of record. It reads what is already in Procore, Autodesk Construction Cloud or a file store and adds retrieval on top, which means the buying decision is an add-on decision rather than a migration. That lowers the barrier to a trial and it also means the value is entirely dependent on whether the underlying document set is well maintained; a project with an out-of-date drawing register will get confident answers from superseded sheets. Buyers are large general contractors and specialty trades running projects big enough that the document set is unmanageable by memory, typically nine-figure work with a superintendent team that spends real hours per week searching. The trade-off is that pricing is quoted, the tooling is new enough that reference customers are limited, and citation accuracy on a badly organised project is the whole risk of the product.

• 

  Trunk Toolsvs

  

  Procore

  Procore: If you want the document system of record itself rather than a retrieval layer over it

• 

  Trunk Toolsvs

  

  Autodesk Construction Cloud

  Autodesk Construction Cloud: If your drawings and models already live in Autodesk and you would rather use the search built into that platform

• 

  Trunk Toolsvs

  

  Bluebeam Revu

  Bluebeam Revu: If the problem is marking up and comparing drawing revisions rather than answering questions about them