The use case: how Torcon deploys Trunk Tools
Torcon project engineers, project managers, and superintendents use Trunk Tools on two active projects to get source-backed answers from project documentation and to speed up compliance reviews of submittals.
More reported results
Figures published in Trunk Tools’s case study. They are not independently measured by usedby.
64 submittal reviews completed with ~43.5 minutes saved per review (~46 hours)
Most reviews flagged non-compliant (69%) or partially compliant (30%), surfacing issues earlier
453 hours (57 days) saved from TrunkText in the first four full months — ~24.7 minutes per prompt across nearly 1,100 prompts
In the customer’s words
Trunk Tools is definitely a time saver. For the first dive into any particular topic, I’ve been using it because it takes some of the human error out of the equation.Trunk Tools users in Construction
Companies in the same sector, with public evidence.
Cleveland ConstructionConfirmed
Gilbane Building CompanyConfirmed
HaskellConfirmed
SuffolkConfirmedBakerObserved
CharpsObservedGo straight to the source
Based on Trunk Tools’s published case study. We check the public evidence; the results are reported by the vendor.
trunktools.com- Source published
- Mar 12, 2026
- Last checked
- Nov 9, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 453 hoursChecked
Printed word for word on the page, near the name of Torcon.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Torcon.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Torcon uses Trunk ToolsChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Torcon’s two-project pilot saved 450+ hours in four months — source-backed answers from project docs plus faster submittal reviews that catch compliance issues earlier.
