# Trunk Tools — full content > Trunk Tools is the AI intelligence layer for construction. This file contains the canonical copy for key product, company, guide, and blog pages. --- ## / ### Trunk Tools | The AI platform built for construction > Trunk Tools is the AI platform built for construction. One brain that reads every document on your job, and tools that transform your team’s workflows. ### Hero - **H1 Lead:** Trunk Tools creates AI-enabled #### Rotating Titles - Superintendents - Project Managers - Project Engineers - Project Executives - Sub Contractors - Owners - **Subhead:** Top construction teams use Trunk Tools to reduce the document grind, keep projects on schedule, and protect margins. ### Intro - **Heading:** Designed for builders. Trained on the jobsite. - **Body:** Custom AI models trained on 5+ years of real jobsite data. Live on 1,000 U.S. projects. Handling $50B in construction volume. ### Cortex - **Eyebrow:** The platform - **Heading Lead:** Cortex: - **Heading Rest:** The brain of construction - **Body:** Cortex plugs into your tech stack and reads every document and drawing on your project. Connections between documents are mapped, creating a living knowledge graph that constantly evolves as your project progresses. ### Tools - **Heading:** Tools that automate the busywork - **Subhead:** Ready-to-deploy tools sit on top of Cortex, using project data to automate the work that slows you down. #### Cards ##### TrunkText - **Body:** Ask your project a question by text and get cited answers instantly. ##### TrunkSubmittal - **Body:** Analyzes every submittal against your specs and drafts responses. ##### TrunkRegister - **Body:** Reads a whole spec book and builds your submittal register in minutes. ##### TrunkReview - **Body:** Highlights clouded and unclouded changes from every new bulletin. ##### TrunkRFI - **Body:** Catches the RFIs your documents already answer and drafts the rest. ##### TrunkBid - **Body:** Maps subcontractor bids against your scope and highlights the gaps. ##### TrunkBrowse - **Body:** Click any object on a sheet and see its full context. ##### TrunkChange - **Body:** Change event detection and analysis. ### Support - **Heading:** Human support, from deployment to adoption #### Columns ##### On jobsites - **Body:** We train site teams in person, on their projects, with their documents and stay on as a partner and resource long after value is unlocked. ##### In head office - **Body:** We deliver full change management programs, building AI-enabled GCs that run more efficiently and win more business because of it. ### Founder - **Eyebrow:** A letter from our founder - **Heading:** We believe construction deserves better tools. - **Body:** We didn't come to construction from AI. We came to AI from construction. From our founder and CEO down to our support and product teams, construction is in our DNA. - **Name:** Dr. Sarah Buchner - **Role:** Founder & CEO - **Bio:** PhD in construction data + 20 years on jobsites ### Impact - **Heading:** Real impact for real customers #### Metrics ##### Project team weeks returned - **Value:** 2,456 - **Caption:** Across deployed projects in U.S. ##### Active U.S. projects - **Value:** 1,000 - **Caption:** Using Trunk Tools agents ##### Submittal cycle time reduction - **Value:** 74% - **Caption:** Avg reduction after implementing Trunk Tools ##### Submittal reviews processed - **Value:** 35,000 - **Caption:** Compliance gaps in 90% of processed reviews ### Testimonials - **Heading:** Don't just take our word for it #### Items ##### Senior Superintendent - **Quote:** Trunk Tools showed that it can help our teams increase efficiency and save significant time by preventing rework. With TrunkText doing the 'document digging' for me, I can work more effectively and be more responsive in the field - **Name:** Andrew Roy - **Company:** Gilbane Building Company ###### Logo - **Alt:** Gilbane ##### Superintendent - **Quote:** When we get a fast response and a sub mobilizes quickly, it saves us serious time and money on the job. - **Name:** Andrew Bared - **Company:** Suffolk ###### Logo - **Alt:** Suffolk ##### Director of Construction Technology - **Quote:** The implementation was almost plug-and-play...one of those rare instances where the transition to using a new tool was seamless, and the benefits were evident right from the start. - **Name:** Mike Trenski - **Company:** AMLI Residential ###### Logo - **Alt:** AMLI Residential ##### Former SVP of Operations - **Quote:** TrunkSubmittal takes a PE or APM with little to no experience in the industry and gives them five-plus years of experience to work with. It drives efficiency, catches things some of our most senior PM staff doesn't look for, and ensures we aren't just passing paper to the architect to review. - **Name:** Elliot Christiansen - **Company:** Cleveland Construction ###### Logo - **Alt:** Cleveland Construction --- ## /platform/ ### Cortex | The brain of construction > More than 5 years of training on real jobsite documents, so your drawings, specs, submittals, and RFIs finally read as one project. ### Hero - **H1:** Cortex: The Brain of Construction - **Subhead:** More than 5 years of training on real jobsite documents, so your drawings, specs, submittals, and RFIs finally read as one project. ### Intro - **Heading:** Turn your system of record into a system of action - **Body:** Your PMS and DMS store project documents. They don't read, interpret and connect them. Cortex changes that by creating a living knowledge graph that our AI tools can then act on. ### Tour - **Eyebrow:** How it works - **Heading:** Read. See. Act. #### Steps ##### Cortex reads every project document - **Body:** Specs, submittals, RFIs, schedules, contracts, change orders, and drawings all flow into Cortex. The system reads from every PMS and DMS so regardless where your documents are stored, they are centralized and processed. ##### Then it sees how they connect - **Body:** Cortex builds a map of how every document and drawing connects. A door tag links to a door schedule, a spec section, a submittal, and an open RFI. A bulletin change ripples across trade partners and schedules. ##### Then our tools go to work - **Body:** Multiple tools, purpose-built for construction workflows then act on your project data, reducing the document grind, increasing accuracy, and protecting your margins. As the tools work, outputs feed back into Cortex and your knowledge graph gets deeper. ### Vision - **Eyebrow:** What sets Cortex apart - **Heading:** Drawings don't communicate in words - **Body:** Drawings speak in geometry, symbols, spatial relationships, cross-sheet references, and revision clouds. Cortex's vision layer is built to read all of it, including the 10–20% of meaningful bulletin changes nobody clouded. #### Comparison - **Baseline Label:** Best frontier model, fully optimized - **Cortex Label:** Cortex - **Metric:** Doors found - **Baseline Value:** 3 in 10 - **Cortex Value:** 9 in 10 ### Stack - **Eyebrow:** Out-of-the-box integrations - **Heading:** Cortex sits on top of what you run today. - **Body:** You don’t need another point solution to manage. You need a single platform that adds an intelligence layer on top of the software you already use. ### Trust - **Eyebrow:** Private by design - **Heading:** Your project data stays yours. #### Columns ##### Project data stays under your control - **Body:** Your drawings, specs, and contracts stay inside your workspace and under your control. ##### Role-based access and full audit logs - **Body:** Permissions mirror your project structure, and every action Cortex takes is logged and reviewable. ##### SOC 2 Type II, built and run in the U.S. - **Body:** Independently audited controls, with subprocessors and data handling documented in the Trust Center. ### Faq - **Eyebrow:** FAQs - **Heading:** Your questions answered #### Items ##### What is Cortex? - **Answer:** Cortex is Trunk Tools' construction intelligence layer. It ingests every document type on a project, structures the unstructured content, and maps how each document relates to the others, so the tools built on it reason with the full picture of the project instead of one file at a time. ##### How is Cortex different from ChatGPT or Claude? - **Answer:** General-purpose models read text well but don't read drawings, and a single construction workflow spans more documents than they can hold at once. Cortex was trained on construction documents specifically and includes a vision layer for drawings. ##### Does Cortex replace Procore or Autodesk? - **Answer:** No. Cortex is the intelligence layer on top of your system of record. It reads from and writes back to Procore and Autodesk, and connects to SharePoint, Box, Egnyte, and Dropbox. Nothing gets migrated. ##### Do we have to build or maintain the tool? - **Answer:** No. Every tool ships pre-built, pre-trained, and validated against real project data. There's no prompting, no configuration, and no model tuning on your side. They're live on day one. ##### How does Cortex read drawings? - **Answer:** Its vision layer recognizes geometry, symbols, spatial relationships, cross-sheet references, and revision clouds, and it detects both clouded and unclouded changes. TrunkBrowse, the tool that exposes this visually, is trained on 400+ object types and more than 2 million labels. --- ## /ai-enablement/ ### AI Enablement | AI-enabled GC program | Trunk Tools > Trunk Tools creates AI-enabled GCs: the full platform, whole-workforce AI education, and forward-deployed experts who build custom agents for your workflows — with adoption we own. ### Hero - **Eyebrow:** AI Enablement - **H1:** Move from AI-curious to AI‑enabled - **Subhead:** Software alone does not change how GCs work. We bring the full Trunk Tools platform, whole-workforce AI education, and forward-deployed experts embedded on your hardest workflows. ### Outcomes - **Eyebrow:** The outcome - **Heading:** What an AI-enabled GC looks like #### Items ##### A certified, AI-fluent workforce - **Body:** Most of your people trained and certified — site and corporate — not a handful of power users. ##### Measurable time back on every job - **Body:** Every person more efficient on the work that already slows projects down: docs, reviews, RFIs, bids. ##### Margin that shows up on the job - **Body:** Reworks caught earlier, leaner delivery, and fewer hours spent hunting for answers. ##### An edge in owner interactions - **Body:** An AI-first team that can speak to how work gets done when owners start asking for it in bids. ##### Trainers who carry it forward - **Body:** Your own champions and certified trainers, so the program compounds after the launch window. ### Pillars - **Eyebrow:** The program - **Heading:** One enterprise program. Six pillars #### Items ##### AI strategy & governance - **Pain:** A flood of AI tools, but with no cohesive strategy. - **Action:** Co-author your AI strategy, policy, and owner narrative. - **Result:** A clear AI strategy, with a partner. ##### Training & certification - **Pain:** Software spend that never gets maximized. - **Action:** AI Foundations for everyone, plus role and product certs. - **Result:** An AI-first team, productive from day one. ##### The full platform - **Pain:** Generic AI that does not know construction. - **Action:** Roll out every current and future agent, across every job. - **Result:** AI built for your work, everywhere. ##### Engagement & adoption - **Pain:** Adoption fades after rollout. - **Action:** Champions, train-the-trainer, awards, and reporting. - **Result:** Adoption that sustains itself. ##### Executive AI advisory - **Pain:** Leaders guessing where AI is headed. - **Action:** CEO, CPO, and CTO advisory hours plus Stanford GSB sessions. - **Result:** An AI-first leadership team. ##### Forward Deployed Experts - **Pain:** Your hardest workflows go unsolved. - **Action:** Embed experts on live, high-value work to configure agents. - **Result:** Results that build trust fast. ### Change - **Eyebrow:** Change management - **Heading:** AI education for the whole workforce - **Lead:** Change-management programming co-developed with Stanford GSB faculty. Training runs C-suite to mid-management to champions to the field so adoption is a performance expectation, not a hope. #### Features ##### AI Foundations for every persona - **Body:** From the C-suite to the trailer, every role gets a tailored path: what AI is, how Trunk Tools fits construction work, and how to use it safely and well. ##### Role and product certification - **Body:** Layer product certs on top of Foundations so supers, PMs, estimators, and corporate staff are fluent in the agents they actually use. ##### Champions who keep it alive - **Body:** Mid-management selects champions. They attend an in-person boot camp, then train-the-trainer carries the program into normal product use with awards and reporting that keep momentum visible. ### Fdx - **Eyebrow:** Forward Deployed Experts - **Heading:** Experts build custom agents for your hardest workflows #### Points ##### Embedded on live projects - **Body:** Forward Deployed Experts sit with your site and corporate teams to understand the workflows that cause the most operational friction. ##### Custom agents for your workflows - **Body:** They configure and develop agents against your processes, documents, and standards so the platform fits how you build, not a generic template. ##### Field AI, developed for you - **Body:** Keep your back-office AI investments. When you need a customized field agent, that is what our experts are for. ### Rollout - **Eyebrow:** How we roll it out - **Heading:** We make it real. We own the adoption #### Phases ##### Foundation - **Step:** 01 - **Body:** Executive alignment, platform live on first projects, leaders trained first. ##### Scale - **Step:** 02 - **Body:** Region by region product certifications and train-the-trainer. ##### Enterprise - **Step:** 03 - **Body:** Full portfolio: your certified trainers carry it forward. --- ## /tools/trunktext/ ### TrunkText | Ask your project a question | Trunk Tools > Ask by text message, web, or Teams and get a cited answer from your specs, drawings, RFIs, and submittals in seconds. - **Name:** TrunkText ### Hero - **Pill:** TrunkText - **H1:** Every project doc is one text message away. - **Subhead:** Get a question on the jobsite, pull out your phone, message us via text, web or Teams and get an answer back in seconds with the source cited. ### Benefits - **Lead In:** No more walking back to the trailer to find answers #### Rows ##### Ask anywhere, any time - **Body:** Ask by voice or text and get cited answers from every project document, or the web when your docs don't have what you need. - **Demo Label:** Demo: ask anywhere ##### Everything sourced, down to the page number - **Body:** See a full list of sources for every request you make, so you have complete confidence giving answers to your trade partners. - **Demo Label:** Demo: sourced answers ##### Dive deeper to get the full picture - **Body:** Need to go a layer deeper? Click any source document to open the file directly to the right place. No searching files and hoping to find what you need. - **Demo Label:** Demo: dive deeper ### Why - **Heading:** Get the answer without leaving the work #### Cards ##### saved on every question asked - **Metric:** 30+ min - **Body:** Get instant answers vs. hunting through disconnected systems ##### of answers cite two or more sources - **Metric:** 73.9% - **Body:** Multiple sources give you the confidence you need. ##### from question to cited answer - **Metric:** Seconds - **Body:** Fast enough to ask in the moment instead of adding it your list of follow-ups. ### Faq - **Eyebrow:** FAQ - **Heading:** Your questions answered #### Items ##### What can I ask TrunkText? - **Answer:** Anything in your project record from specs, drawings, RFIs, submittals, schedules, contracts, photos, or any other documents you've synced into Trunk Tools. Ask in plain language and get the exact data point back with its source. ##### How is TrunkText different from a generic AI chatbot? - **Answer:** TrunkText is powered by Cortex, Trunk Tools' construction-specific intelligence layer. It reads connected project documents together and returns answers with source citations you can check. ##### How do I ask TrunkText a question? - **Answer:** By text message, in Microsoft Teams, or in our application from any device — whether you are on the jobsite or in the trailer. ##### How fast are the answers, and can I trust them? - **Answer:** Depending on the complexity of the query, answers come back in seconds or just a few minutes. They always cite the source document so you can verify before you act. ##### Does TrunkText connect to my existing project management system? - **Answer:** Yes. TrunkText reads across your connected systems, including Procore and Autodesk, and surfaces the answer without you needing to dig through either platform. ##### What is a construction document AI assistant? - **Answer:** It is a tool that answers questions about a specific project by reading that project's documents — specs, drawings, RFIs, submittals, schedules, and contracts — and returning the answer with the source cited. ##### Can I search project documents from my phone? - **Answer:** Yes. You can ask by text message, in Microsoft Teams, or in the web app, so you can get an answer on the jobsite instead of walking back to the trailer. ##### How do I check where an answer came from? - **Answer:** Every response lists its sources down to the page number, and you can click any source document to open the file at the right place. --- ## /tools/trunksubmittal/ ### TrunkSubmittal | Get submittals approved faster | Trunk Tools > TrunkSubmittal automatically reviews new submittals, flags what's non-compliant for your review, and drafts a response to your trade partner to fix issues. - **Name:** TrunkSubmittal ### Hero - **Pill:** TrunkSubmittal - **H1:** Don't let submittal review cycles slow your project down. - **Subhead:** TrunkSubmittal automatically reviews new submittals, flags what's non-compliant for your review, and drafts a response to your trade partner to fix issues. ### Benefits - **Lead In:** Get submittals approved faster. #### Rows ##### Run detailed submittal reviews automatically - **Body:** TrunkSubmittal starts working the moment a submittal enters your PMS. - **Demo Label:** Demo: automatic submittal review ##### Don't stress about spec and RFI tags - **Body:** TrunkSubmittal finds the correct spec sections and related RFI responses even when they're untagged or incorrectly tagged in your PMS. - **Demo Label:** Demo: spec and RFI matching ##### Find compliance gaps and take action. - **Body:** Every submittal is given a compliance recommendation with cited discrepancies, and TrunkSubmittal drafts an email to the subcontractor or architect. - **Demo Label:** Demo: compliance recommendation ### Why - **Heading:** Builders using TrunkSubmittal have transformed their submittal process #### Cards ##### Submittals with compliance gaps in our platform - **Metric:** 90% - **Body:** TrunkSubmittal catches those gaps before they reach the architect. ##### Median time to first-pass review - **Metric:** 3.92 min - **Body:** Compared to the 45–60+ minutes a proper manual review takes. ##### Drop in median submittal cycle time for TrunkSubmittal users - **Metric:** 74% - **Body:** Faster first-pass reviews, faster corrections, faster approvals, and fewer "stuck" submittals. ### Faq - **Eyebrow:** FAQ - **Heading:** Your questions answered #### Items ##### Does TrunkSubmittal replace my PE's review, or support it? - **Answer:** TrunkSubmittal handles the first pass so your PE reviews a completed analysis instead of starting from scratch. ##### What systems does TrunkSubmittal integrate with? - **Answer:** Procore and Autodesk, plus support for teams on SharePoint, Egnyte, Box, or Dropbox. ##### How does TrunkSubmittal find the right spec sections if they're untagged? - **Answer:** Cortex, Trunk Tools' construction intelligence layer, reads the submittal and identifies the governing spec sections and related RFI responses when tags are missing or are incorrectly tagged in Procore or Autodesk. ##### What types of submittals can TrunkSubmittal review? - **Answer:** TrunkSubmittal supports Product Data, Test Reports, Certificates, Operation & Maintenance Manuals (O&M), Sustainability and LEED, Final Warranty (Closeout), Sample Warranty, and Qualifications submittal types. ##### What happens after a submittal is reviewed? - **Answer:** TrunkSubmittal drafts a response to the subcontractor if there's an issue or to the architect if the submittal is clean. It also publishes a PDF summary to the submittal record in Procore or Autodesk. ##### Can Trunk Tools help me build my submittal register too? - **Answer:** Yes. Pair it with TrunkRegister, which reads your full spec book and builds the submittal register. ##### What is submittal review software? - **Answer:** It is software that checks a submittal against the specifications and related RFI responses that govern it, then reports where the submitted product or documentation does not comply. ##### What is a submittal compliance gap? - **Answer:** It is a place where a submittal does not meet the requirements in the governing spec section or a related RFI response. TrunkSubmittal cites each discrepancy it finds so your team can see exactly what needs to change. ##### When does the submittal review start? - **Answer:** TrunkSubmittal starts working the moment a submittal enters your PMS, so the first-pass analysis is underway without anyone assigning it. --- ## /tools/trunkregister/ ### TrunkRegister | Build a complete submittal register | Trunk Tools > TrunkRegister saves you days of time building your register and ensures no requirements are missed. - **Name:** TrunkRegister ### Hero - **Pill:** TrunkRegister - **H1:** Build a complete submittal register in minutes. - **Subhead:** TrunkRegister saves you days of time building your register and ensures no requirements are missed. ### Benefits - **Lead In:** From spec book to register #### Rows ##### Upload and split - **Body:** Upload a spec book PDF, or select one already in your Trunk Tools project files. TrunkRegister automatically splits it into individual CSI sections. - **Demo Label:** Demo: upload and split ##### Extract every requirement - **Body:** TrunkRegister reads every section, pulls out directives from Part 1 plus product groups and individual products from Part 2, and categorizes each. - **Demo Label:** Demo: extract every requirement ##### Review, edit, and sync - **Body:** Review an editable register with every submittal linked to its source paragraph. Edit, bundle, or rename items, then send the finished register straight to your PMS. - **Demo Label:** Demo: review, edit, and sync ### Why - **Heading:** From a week of manual work to a complete register in minutes #### Cards ##### Typical time to build a register by hand - **Metric:** 30+ hours - **Body:** You can read a 1,000+ page spec book line by line to extract submittal requirements. Or you can let TrunkRegister do the work in a fraction of the time. ##### Spec coverage - **Metric:** 100% - **Body:** Every CSI section is read, so requirements buried outside the obvious sections, especially closeout submittals, don't get missed. ##### Pages read per spec book, automatically - **Metric:** 1,000+ - **Body:** TrunkRegister reads the entire spec book, no matter how large, and generates every submittal requirement. ### Faq - **Eyebrow:** FAQ - **Heading:** Your questions answered #### Items ##### What does TrunkRegister need from me to get started? - **Answer:** Just a spec book PDF in CSI format either uploaded directly or already sitting in your Trunk Tools project files. ##### How does TrunkRegister decide what's Action, Informational, or Closeout? - **Answer:** Cortex reads every CSI section and classifies each submittal directive and product based on the language and context in Part 1 and Part 2 of the spec. ##### Can I edit the register before I use it? - **Answer:** Yes. The register is fully editable. You can edit, bundle, rename items, and set product-level granularity before syncing. ##### Where does the finished register go? - **Answer:** You can push it straight to Autodesk via API or export a Procore-ready CSV. ##### How is TrunkRegister connected to TrunkSubmittal? - **Answer:** TrunkRegister builds the register TrunkSubmittal reviews against, so your submittal reviews start with a complete, accurate register from day one. ##### What is a submittal register? - **Answer:** It is the list of everything a project's specifications require a team to submit, drawn from the submittal directives in Part 1 and the product groups and products in Part 2 of each CSI section. ##### How do you build a submittal register from a spec book? - **Answer:** Upload the spec book, let it be split into individual CSI sections, extract and categorize every submittal requirement, then review the editable register and sync it to your PMS. ##### Can TrunkRegister handle a very large spec book? - **Answer:** Yes. It reads the entire spec book, including books over 1,000 pages, so requirements buried outside the obvious sections — especially closeout submittals — still make it into the register. ##### Does every register item link back to the spec? - **Answer:** Yes. Each submittal in the register is linked to the source paragraph it came from, so you can check the original spec language before you approve it. --- ## /tools/trunkreview/ ### TrunkReview | AI drawing and bulletin review | Trunk Tools > A 20-sheet bulletin takes about 6 hours to review by hand. TrunkReview does it in under 10 minutes and finds all changes, clouded and unclouded. - **Name:** TrunkReview ### Hero - **Pill:** TrunkReview - **H1:** A bulletin dropped. Find out what changed instantly - **Subhead:** The moment a revision lands in your PMS, TrunkReview compares every sheet to the prior version, highlights changes, clouded or not, and writes the narrative for you. ### Benefits - **Lead In:** Find every change, including ones that aren't clouded #### Rows ##### Visualize changes with interactive overlays - **Body:** No need to carve out time to run a diff. Old and new sheets are overlaid automatically, with every difference marked, so you know exactly what changed and where. - **Demo Label:** Demo: visual overlay ##### Catch what never got clouded - **Body:** Around 10–20% of meaningful bulletin changes never get clouded by design teams. Catch them before they turn into rework. - **Demo Label:** Demo: unclouded change ##### Review narratives and accelerate RFI workflows - **Body:** Every change is described in plain language. Use narratives to draft RFIs and then easily export current and previous versions as PDFs. - **Demo Label:** Demo: narrative output ### Why - **Heading:** Get time back. Remove headaches down the road #### Cards ##### A 20-sheet bulletin, reviewed - **Metric:** <10 min - **Body:** Eliminates nearly 6 hours of manual review time for your PMs and PEs per bulletin. ##### of meaningful changes aren't clouded - **Metric:** ~10–20% - **Body:** TrunkReview flags clouded and non-clouded changes so you don't miss anything important. ##### Minimum cost of rework for one missed change - **Metric:** $10K+ - **Body:** Even if you can bill for the change, a drawn out process presents risk to your schedule. - **Supporting Line:** TrunkReview hands its findings to TrunkRFI with full context, so the question you need to ask the design team is already drafted. #### Handoff - **Label:** See TrunkRFI ### Faq - **Eyebrow:** FAQ - **Heading:** Your questions answered #### Items ##### How does TrunkReview know what changed between drawing revisions? - **Answer:** TrunkReview is powered by Cortex, Trunk Tools' construction-specific AI intelligence layer trained on thousands of real project drawings. Cortex can read the entire drawing, not just text in the title block or markups. Built on Cortex, TrunkReview can compare every sheet to its prior version to detect visual and textual changes. ##### Does TrunkReview only catch clouded changes? - **Answer:** No. TrunkReview is built specifically to catch non-clouded changes too. These are the changes most manual reviews miss, even when done by experienced staff. ##### Which systems does TrunkReview integrate with? - **Answer:** TrunkReview connects directly to Procore and Autodesk and starts analyzing the moment a new bulletin is uploaded. ##### What do I get from TrunkReview after a bulletin lands? - **Answer:** A visual overlay of every change, a written narrative describing what changed, and a drafted RFI or subcontractor email ready for your review when needed. ##### How long does a review take? - **Answer:** A 20-sheet bulletin is reviewed in under 10 minutes, compared with the roughly six hours the same review takes by hand. ##### What is AI drawing comparison? - **Answer:** It is an automated comparison of a new drawing set against the prior version that marks every visual and textual difference, rather than relying on someone to spot changes sheet by sheet. ##### What is an unclouded change? - **Answer:** It is a real change to a drawing that the design team never marked with a revision cloud. Around 10–20% of meaningful bulletin changes arrive this way, which is why manual reviews miss them. ##### Can I export the compared drawings? - **Answer:** Yes. You can export the current and previous versions of a sheet as PDFs alongside the written narrative of what changed. --- ## /tools/trunkrfi/ ### TrunkRFI | Bring control to your RFI process | Trunk Tools > TrunkRFI checks drafts against past responses, specs, and drawings, writes the ones you genuinely need, and analyzes new responses for impact. - **Name:** TrunkRFI ### Hero - **Pill:** TrunkRFI - **H1:** Bring control to your RFI process - **Subhead:** TrunkRFI checks drafts against past responses, specs, and drawings, writes the ones you genuinely need, and analyzes new responses for impact. ### Benefits - **Lead In:** Submit better RFIs. Understand project impact faster #### Rows ##### Set draft analysis on auto-pilot - **Body:** TrunkRFI watches Procore and Autodesk for draft RFIs and starts analysis automatically. You can also start a check manually by describing the question in the TrunkRFI dashboard or in TrunkText. - **Demo Label:** Demo: auto-pilot draft analysis ##### Avoid unnecessary RFIs - **Body:** Drafts get compared against your specs, drawings, and prior responses, so the ones already answered never go out. - **Demo Label:** Demo: avoid unnecessary RFIs ##### Understand impact instantly - **Body:** Once RFI responses come back from designers, the tool instantly summarizes the impact and builds a prioritized to-do list. - **Demo Label:** Demo: understand impact instantly ### Why - **Heading:** Builders using TrunkRFI are transforming their RFI processes #### Cards ##### Submitted RFIs already addressed in project docs or past responses - **Metric:** 15–20% - **Body:** Many RFIs never needed to be submitted in the first place. TrunkRFI helps you avoid questions like "Did you read the docs?" from the design team. ##### Median time to get an RFI response - **Metric:** 6 days - **Body:** Every day an RFI sits open is a day of schedule risk. TrunkRFI keeps unnecessary submissions off the clock entirely. ##### Hours saved per RFI response analysis by TrunkRFI users - **Metric:** 5–15 - **Body:** TrunkRFI aggregates and summarizes the impact of the RFI response across all relevant project docs with a clear action plan. ### Faq - **Eyebrow:** FAQ - **Heading:** Your questions answered #### Items ##### Will TrunkRFI submit RFIs without my review? - **Answer:** No. TrunkRFI drafts and flags recommendations, but you always review, edit, and approve before anything is submitted to Procore or Autodesk. ##### How does TrunkRFI know if an RFI is unnecessary? - **Answer:** It searches all of your project documents previously synced to Trunk Tools for an existing answer before a new RFI is drafted. ##### What do I get once an RFI response comes back? - **Answer:** TrunkRFI summarizes the response, flags its impact on your project, catches potential conflicts, and gives you a prioritized to-do list. ##### Which systems does TrunkRFI work with? - **Answer:** The agent pulls draft RFIs from Procore and Autodesk. It also has seamless handoffs with TrunkText (Q&A) for questions that might warrant an RFI and TrunkReview (drawing review) for seeking clarity on a change in a bulletin / revision / ASI. ##### How much time does TrunkRFI save? - **Answer:** Users report saving 5–15 hours per RFI response analysis, because the impact summary and prioritized to-do list are already assembled when the response comes back. ##### What is RFI management software? - **Answer:** It is software that manages the request-for-information process end to end: checking drafts against the documents you already have, drafting the questions that still need to go out, and analyzing the design team's response when it returns. ##### How can I reduce unnecessary RFIs? - **Answer:** Compare every draft against your specs, drawings, and prior responses before it goes out. Roughly 15–20% of submitted RFIs are already addressed in the project documents or a past response. ##### Can I start an RFI check from a field question? - **Answer:** Yes. You can describe the question in the TrunkRFI dashboard or in TrunkText and start the check manually, instead of waiting for a draft to appear in your PMS. --- ## /tools/trunkbid/ ### TrunkBid | Find scope gaps in bids | Trunk Tools > TrunkBid maps each line item in subcontractor bids to your scope requirements, surfacing gaps so you can move quickly and avoid surprises and disputes later on. - **Name:** TrunkBid ### Hero - **Pill:** TrunkBid - **H1:** Find scope gaps in bids. Award subcontracts confidently - **Subhead:** TrunkBid maps each line item in subcontractor bids to your scope requirements, surfacing gaps so you can move quickly and avoid surprises and disputes later on. ### Benefits - **Lead In:** Compare bids under tight deadlines #### Rows ##### Select bids and scopes - **Body:** Select bids, scope of work docs, and specs. No reformatting required. - **Demo Label:** Demo: select bids and scopes ##### Compare bids apples-to-apples - **Body:** Exclusions, inclusions, conflicts, and alternates surfaced instantly. - **Demo Label:** Demo: apples-to-apples comparison ##### Excel exports in seconds - **Body:** Download structured Excel files to complete leveling and buyout decisions. - **Demo Label:** Demo: Excel export ### Why - **Heading:** Builders using TrunkBid save time and reduce risk #### Cards ##### Time to thoroughly analyze bids for one trade package - **Metric:** 4–8 hours - **Body:** First-pass analysis done in minutes with TrunkBid. ##### Percentage of disputes connected back to scope gaps - **Metric:** 25.7% - **Body:** TrunkBid surfaces gaps so you can negotiate before award. ##### Reduction in estimator and/or PM bid analysis time - **Metric:** 80% - **Body:** Less manual comparison and data entry. More award decisions made quickly and confidently. ### Faq - **Eyebrow:** FAQ - **Heading:** Your questions answered #### Items ##### How many bids can TrunkBid compare at once? - **Answer:** TrunkBid can analyze all bids received for a trade package against the scope of work, regardless of how inconsistent their formats are. ##### What does TrunkBid actually flag? - **Answer:** For every bidder, TrunkBid flags what's covered, what's excluded, what's priced as an alternate, and what's silent relative to your scope requirements plus recommended follow-up questions for each bidder. ##### What do I get at the end of the process? - **Answer:** A structured, downloadable Excel sheet you can use to complete leveling and make buyout decisions. ##### Does TrunkBid replace my estimator's judgment? - **Answer:** No. TrunkBid handles the first-pass analysis and data entry so your estimators and PMs can focus on judgment calls and award decisions. ##### How does TrunkBid help with scope-gap-related disputes? - **Answer:** Nearly 26% of disputes trace back to scope gaps. By surfacing gaps, exclusions, and silences before award, TrunkBid helps you close them before they become disputes. ##### What is bid leveling in construction? - **Answer:** It is the process of putting every subcontractor bid for a trade package on the same basis — inclusions, exclusions, alternates, and conflicts — so you can compare price against identical scope before buyout. ##### What is a scope gap in a subcontractor bid? - **Answer:** It is a scope requirement a bid does not cover, whether it is excluded outright, priced only as an alternate, or simply silent. TrunkBid flags all three against your scope requirements. ##### What do I need to provide to compare bids? - **Answer:** The bids you received plus the scope of work documents and specs for that package. No reformatting is required, however inconsistent the bid formats are. --- ## /tools/trunkbrowse/ ### TrunkBrowse | Connect drawings to every project document | Trunk Tools > Click any object on a sheet and its full context opens beside it: the schedule row, spec section, RFIs, submittals, and every other sheet it appears on. - **Name:** TrunkBrowse ### Hero - **Pill:** TrunkBrowse - **H1:** Connect your drawings to every other project document - **Subhead:** Click any object on a sheet and its full context opens beside it: the schedule row, spec section, RFIs, submittals, and every other sheet it appears on. - **Note:** Launching Q4 2026. ### Benefits - **Lead In:** Your entire project connected visually #### Rows ##### Navigate drawings by object type - **Body:** TrunkBrowse identifies the objects on every sheet you upload and classifies them automatically. - **Demo Label:** Demo: navigate by object type ##### Access all data about an object. - **Body:** TrunkBrowse links each object to its schedule row, spec section, related RFIs and submittals, and every other sheet it appears on. No need to try and find all those relevant docs. - **Demo Label:** Demo: object data panel ##### One click access to related documents - **Body:** Linked documents paint the full picture of whether a change is in or out of scope and help inform whether an RFI is necessary. - **Demo Label:** Demo: related documents ### Why - **Heading:** Generic AI can't read your drawings #### Cards ##### Object types recognized - **Metric:** 400+ - **Body:** Cortex classifies hundreds of construction-specific object types general AI models have never been trained on. ##### Expert-verified labels used to train our computer vision models - **Metric:** 2M+ - **Body:** Cortex learns from millions of hand-labeled project drawings, not the open internet. ##### Cortex's precision vs. the best generic AI model at door detection - **Metric:** 97% vs. 26% - **Body:** On a simple task like door detection, Cortex outperforms the best generic AI model by more than 3x. ### Faq - **Eyebrow:** FAQ - **Heading:** Your questions answered #### Items ##### Is TrunkBrowse available now? - **Answer:** TrunkBrowse is currently in beta, with general availability coming in Q4 of 2026. Join the waitlist for early access. ##### How is TrunkBrowse different from clicking around in Procore or Autodesk? - **Answer:** TrunkBrowse is powered by the Cortex knowledge graph, which pre-connects every object on a sheet to every place it shows up across your project documents. No one needs to remember and pull up 10+ documents in your PMS that reference a particular object when your teams use TrunkBrowse. ##### What kinds of objects can TrunkBrowse recognize? - **Answer:** TrunkBrowse recognizes around 400 construction-specific object types, trained on more than 2 million expert-verified labels. Some examples include double-swing doors, concrete columns, toilets, sinks, and fire extinguisher cabinets. ##### Does TrunkBrowse work across the whole project or just one drawing? - **Answer:** TrunkBrowse connects your entire project into one visual, navigable surface: every sheet, schedule, spec section, RFI, submittal, and drawing. ##### What is construction drawing navigation software? - **Answer:** It is software that turns a drawing set into a navigable index of the project. Objects on each sheet are identified and classified, then linked to the documents that describe them. ##### How do I find every document related to one object? - **Answer:** Click the object on the sheet. Its schedule row, spec section, related RFIs and submittals, and every other sheet it appears on open beside it, so you don't have to pull up each document yourself. ##### Can TrunkBrowse help me tell if a change is in scope? - **Answer:** Yes. Seeing the linked documents together shows whether a change falls inside or outside your scope, and helps you judge whether an RFI is necessary. --- ## /tools/trunkchange/ ### TrunkChange | AI change event detection and analysis | Trunk Tools > A bulletin or accepted RFI can quietly become a change order weeks later. TrunkChange detects the change event as it lands, traces every affected trade, and drafts the change order for you. - **Name:** TrunkChange ### Hero - **Pill:** TrunkChange - **H1:** A change landed. Know the cost, schedule, and scope impact instantly - **Subhead:** The moment a bulletin or RFI response lands, TrunkChange detects the change event, traces every affected trades, and drafts the change order, including estimated costs. - **Note:** Launch Q4 2026. ### Benefits - **Lead In:** Faster, more efficient change management workflows #### Rows ##### Launches the second changes hit your PMS - **Body:** TrunkChange picks up revision narratives from TrunkReview and response analyses from TrunkRFI automatically, so it starts with the full history of what changed and why. - **Demo Label:** Demo: launches when changes hit your PMS ##### See every affected trade and what the changes cost - **Body:** TrunkChange traces changes throughout the project and reports the impact on cost, schedule, and scope, broken out by every trade it touches. - **Demo Label:** Demo: affected trades and cost impact ##### Get drafted change orders and ROM estimates - **Body:** TrunkChange drafts the change event and potential change order and writes them back to your system of record. Each one carries a rough order of magnitude estimate by affected discipline. - **Demo Label:** Demo: drafted change orders and ROM estimates ### Faq - **Eyebrow:** FAQ - **Heading:** Your questions answered #### Items ##### What is construction change management software? - **Answer:** Construction change management software helps teams identify, document, assess, and route project changes before they become disconnected cost, schedule, or scope issues. ##### What does TrunkChange analyze? - **Answer:** TrunkChange analyzes revision narratives from TrunkReview and RFI response analyses from TrunkRFI to trace affected trades and report potential cost, schedule, and scope impacts. ##### Can TrunkChange draft change orders? - **Answer:** Yes. TrunkChange drafts the change event and potential change order, including a rough order of magnitude estimate by affected discipline, for your team to review. ##### How does TrunkChange detect project changes? - **Answer:** It starts when a bulletin or accepted RFI reaches the connected project workflow, using the available history of what changed and why. ##### Is TrunkChange available now? - **Answer:** TrunkChange is planned to launch in Q4 2026. Teams can request a demo to learn more. --- ## /tools/contract-review/ ### AI Contract Review Built for Construction > Free AI contract review for construction. Get pre-signature risk analysis or a post-signature compliance guide — then delete your data on your own timeline. ### Hero - **Eyebrow:** Free tool - **H1 Lead:** AI Contract Review - **H1 Rest:** Built for Construction - **Body:** AI can handle many tasks for construction teams. Some should be free. Get instant analysis of your construction contracts, then delete the data on your own timeline and terms. ### Modes - **Eyebrow:** Two ways to use it - **Heading:** Compliance guide or pre-signature review #### Items ##### Already signed? Stay compliant. - **Description:** Transform contract legalese into an actionable field operations guide your PMs, supers, and project engineers can actually use. ###### Items - Notice Deadlines & Methods - Submittal Requirements - Payment Application Process - Schedule Compliance - Change Order Procedures - Testing & Inspections - Safety Requirements - Documentation Standards - Meeting Cadence - Closeout Checklists - Insurance Renewals - Certified Payroll - **Footer:** You'll receive a compliance calendar, critical deadline matrix, delegation chart by role, and warning flags for high-risk provisions. ##### Should you sign? Find out in minutes. - **Description:** Our construction-specific AI models review your contract across 14 critical categories to give you a head start on redlining. ###### Items - Payment & Retainage Terms - Change Order Procedures - Delay & Liquidated Damages - Indemnification & Liability - Insurance Requirements - Warranty Obligations - Termination Rights - Dispute Resolution - Bond & Lien Provisions - Site Conditions - Subcontract Flow-Down - Labor Compliance - Scope & Precedence - Consequential Damages - **Footer:** You'll receive an executive summary with risk ratings, top issues requiring negotiation, and specific contract language to push back on. ### Upload - **Eyebrow:** Try it free - **Heading:** Ready to review your contract? - **Body:** Understand your construction contract in basic terms — completely free. No account required. ### Data Control - **Eyebrow:** Privacy - **Heading:** Your data, your control - **Body:** We know construction contracts contain sensitive project and business information. That's why we will never train AI models with your documents, and you maintain complete control over your data. #### Cards ##### 256-bit encryption - **Body:** Bank-level security for uploads ##### 7-day expiration - **Body:** Links auto-expire for protection ##### Instant deletion - **Body:** One-click removal anytime ##### PDF export - **Body:** Download for offline access ### Report - **Eyebrow:** After analysis - **Heading:** How your report works #### Steps - After analysis, you'll receive an email with a secure link to your report. - The link expires automatically in 7 days. If you still need access after that, follow the link to request a new one. - Download as PDF to keep a permanent copy, or delete the report entirely with one click. - Your contract is never stored long-term and is never used to train our AI models. ### How It Works - **Eyebrow:** Process - **Heading:** How it works - **Subhead:** Three steps to contract clarity. No account required. No credit card. #### Steps ##### Upload your contract - **Body:** Drop your PDF into the form. We accept AIA, ConsensusDocs, and custom construction contracts up to 100MB. ##### AI analyzes every clause - **Body:** Our construction-trained AI reviews your entire contract against industry standards and best practices. ##### Get your report via email - **Body:** Receive a comprehensive analysis with risk ratings, action items, and specific recommendations. ### Faq - **Eyebrow:** FAQ - **Heading:** AI contract review questions #### Items ##### What is AI contract review? - **Answer:** AI contract review is a first-pass analysis that turns contract language into a structured summary of obligations, deadlines, risks, and clauses that may need closer review. ##### What does the construction contract review cover? - **Answer:** The pre-signature review covers 14 construction-specific categories, including payment, retainage, changes, delays, indemnification, insurance, termination, disputes, liens, and flow-down provisions. ##### Can I review an already signed contract? - **Answer:** Yes. The compliance-guide option turns a signed contract into practical deadlines, role assignments, warning flags, and field-facing requirements. ##### Is the contract review free? - **Answer:** Yes. The tool is free to use, requires no account or credit card, and sends the completed report through a secure email link. ##### How is my contract data handled? - **Answer:** Documents are encrypted, are not used to train AI models, and are not stored long term. Report links expire after seven days, and you can delete the report sooner. --- ## /about/ ### About | Construction AI, built by builders > Trunk Tools is the AI intelligence layer for construction, so the people running projects can lead from the field instead of chasing information. ### Hero - **H1 Lead:** Creating technology that - **H1 Accent:** lets builders build - **Subhead:** Trunk Tools is the AI intelligence layer for construction. Our mission is to let the people running projects lead from the field, not chase information across it. ### Story - **Body:** We started Trunk Tools in 2021 because the tools construction teams were being sold weren't built for how construction actually works. General-purpose AI can't read a drawing. Legacy software can't reason across documents. Point solutions add to the sprawl instead of solving it. - **Accent:** how construction actually works ### How - **Eyebrow:** How we do it - **Heading:** AI purpose-built for construction #### Columns ##### Cortex - **Body:** Cortex is the brain of construction projects. It plugs into project and document management systems, reads every document on the job, and sees how it all connects. ##### Tools - **Body:** Tools sit on top of Cortex. These purpose built tools automate the most time consuming construction workflows, freeing up builders to focus on what they do best: building. ### Numbers - **Eyebrow:** By the numbers - **Heading:** Trunk Tools agents are at work on jobsites totalling over $20BN in construction volume. #### Metrics ##### Company founded - **Value:** 2021 ##### U.S. team members - **Value:** 100+ ##### Active projects - **Value:** 1,000 ##### Active daily users - **Value:** 4,000+ ### Investors - **Eyebrow:** Backed by the best - **Heading:** Over $70M raised from leading VCs and industry investors to transform outdated construction workflows ### Careers - **Eyebrow:** Careers - **Heading:** Come build with us - **Body:** Low ego. High output. No BS. If that's how you work, we should meet. We're hiring across departments. --- ## /careers/ ### Careers | Construction AI jobs > Join Trunk Tools and help build the AI intelligence layer for construction. ### Hero - **Eyebrow:** Careers - **Heading:** Come build with us - **Body:** Trunk Tools is building the AI intelligence layer for construction. We're a team of builders, doers, and thinkers tackling problems that have plagued the industry for decades. If that mission excites you, we'd love to hear from you. ### Values - **Eyebrow:** Values - **Heading:** The values we live by #### Items ##### Low Ego - **Body:** You can't move fast if you're surrounded by people with big egos. It gets in the way of hiring and execution. And it's the fastest way to damage customer relationships, particularly on jobsites. ##### High Output - **Body:** Results matter. We're leading the market in construction AI and we're not going to lose that position by moving slowly. We celebrate speed, we learn from failure, and we do more with less. ##### No BS - **Body:** We don't say things in meetings just to say something. We don't ship products that don't add value. We push back when we need to, and we do it with a smile on our face. ### Openings - **Heading:** Current openings - **Department Label:** Department - **Location Label:** Location - **All Departments Label:** All departments - **All Locations Label:** All locations - **Empty Label:** No openings match these filters. #### Columns - **Role:** Role - **Team:** Team - **Location:** Location ### Benefits - **Heading:** Benefits #### Items ##### Health insurance - **Body:** Your health matters to us, so we've got you covered. Trunk Tools offers comprehensive health insurance plans that keep you and your family protected. ##### 401(k) - **Body:** Trunk Tools is committed to helping employees build financial security for the future. We offer a 401(k) plan through Human Interest, helping you easily get your saving goals on track. ##### Equity - **Body:** We're building something big at Trunk Tools and we want you to have a real stake in where we're headed. That's why we offer stock options to all employees. ##### Unlimited time off - **Body:** We believe time away is essential for rest and recovery. Employees get unlimited paid time off from day one, plus very special perks when you hit your three and four year anniversaries. ##### Disability, short & long term - **Body:** Life is unpredictable, and we want you to feel secure no matter what comes your way. That's why Trunk Tools covers 100% of both short-term and long-term disability insurance. ##### Parental leave - **Body:** Your family matters to us, so we make sure you have time for it. Trunk Tools offers generous parental leave for all new parents. #### Spotlight - **Title:** Unlimited AI tokens - **Body:** No credit caps. No approval forms. No rationing. Every person gets unlimited access to Claude, ChatGPT, Cursor, and whatever helps you move faster. We build AI for construction, so this is us practicing what we preach. --- ## /pricing/ ### Pricing | Unlimited users, every app | Trunk Tools > Trunk Tools pricing is one annual price sized to construction volume — unlimited users, every app, unlimited usage. No seats. No consumption. No upsells on new tools. ### Hero - **Eyebrow:** Pricing - **H1:** Simple, transparent pricing. ### Plans #### Core - **Price Detail:** One clear price based off your construction volume. - **Includes Label:** Includes ##### Features ###### Full Cortex ingestion for every project - **Summary:** Cortex reads every document and drawing on the job and maps how they connect. ###### Proprietary construction AI models - **Summary:** Proprietary AI models trained on 5+ years of construction data ###### Unlimited seats - **Summary:** Every user is included. No per-seat fees as your team grows. ###### No token limits - **Summary:** Unlimited usage. We absorb the model cost. ###### Site team training - **Summary:** In-person training on your projects, with your documents. ###### Dedicated CS support - **Summary:** A dedicated partner after go-live, not a ticket queue. ###### Data privacy - **Summary:** Your project data stays yours. We do not train on it. #### Enterprise - **Price Detail:** One clear price based off your construction volume. - **Includes Label:** Includes ##### Features ###### Full Cortex ingestion for every project - **Summary:** Cortex reads every document and drawing on the job and maps how they connect. ###### Proprietary construction AI models - **Summary:** Proprietary AI models trained on 5+ years of construction data ###### Unlimited seats - **Summary:** Every user is included. No per-seat fees as your team grows. ###### No token limits - **Summary:** Unlimited usage. We absorb the model cost. ###### Site team training - **Summary:** In-person training on your projects, with your documents. ###### Dedicated CS support - **Summary:** A dedicated partner after go-live, not a ticket queue. ###### Data privacy - **Summary:** Your project data stays yours. We do not train on it. ###### Full change management training - **Summary:** AI education from the C-suite to the field so adoption sticks. ###### Custom LMS for your specific business - **Summary:** AI Foundations plus role and product certifications in an LMS tailored to your workflows. ###### FDE support to create custom skills and tools - **Summary:** Forward Deployed Experts build custom skills and tools for your hardest workflows. ###### First look at new products - **Summary:** Early access to new tools before they ship broadly. ### Why - **Eyebrow:** Why we price this way - **Heading:** Built so your team can unlock value. Not so we can meter them. - **Lead:** Consumption pricing punishes adoption, which is the opposite of what we want to achieve. We don't want any barriers between your site teams and the value we deliver. #### Reasons ##### We absorb the model cost - **Body:** Documents are preprocessed and models are pretrained up front, so usage stays unlimited for you. ##### Curiosity should be free - **Body:** If every experiment shows up on an invoice, teams stop experimenting. That kills the value. ##### Access should be wide - **Body:** The super who needs the answer at 6am should not wait on a license. Unlimited users means unlimited reach. --- ## /blog/2024-construction-tech-trends-to-watch/ ### 2024 Construction Tech Trends to Watch > As we step into 2024, it's crucial to anticipate how the acceleration of these contech trends will enhance productivity, safety, and sustainability. _In 2023, technology continued to affect how we conceptualize, design, and build structures. As we step into 2024, it's crucial to anticipate how the acceleration of these trends will shape our industry. This report outlines the key areas where technology is not just supplementing, but revolutionizing, the construction sector, promising enhancements to productivity, safety, and sustainability._ ## Columbia University's Global Leaders in Construction Management and Trunk Tools co-publish report on most important Construction Trends of 2024 [Download PDF](/content/blog/media/Trunk-Tool-x-GLCM-2024-ConTech-Trends-to-Watch-FINAL.pdf)  This report is a joint publication of The Global Leaders in Construction Management (GLCM) and Trunk Tools, Inc. [**GLCM**](http://www.GLCM.info) is a Strategic Management Research Initiative founded at Columbia University in 2011 by [**Professor Ibrahim Odeh**](https://www.linkedin.com/in/ibrahim-odeh-phd-mba-3310025/).  **[Trunk Tools](https://trunktools.com)** is your firm's partner for Field-First A.I. Construction Technology. Know Everything, with [**TrunkText**](/tools/trunktext/), and Build Anything, with **TrunkPerform**. --- ## /blog/2025-construction-tech-trends-to-watch/ ### 2025 Construction Tech Trends to Watch > As 2024 comes to a close and we kick off 2025, it's crucial to anticipate which contech trends will enhance productivity for construction. _2024 brought growth and innovation to construction tech. This report highlights key trends and previews 2025's advancements, from AI-driven tools to sustainable practices._ ## Trunk Tools publishes its annual report on construction tech trends to watch in 2025. [Download PDF](/content/blog/media/2025-ConTech-Trends.pdf) **[Trunk Tools](https://trunktools.com)** built the "brain" behind construction and is transforming the $13 trillion construction industry. As the preeminent AI platform for the built environment, Trunk Tools is making information available to the right people at the right time, avoiding construction delays and rework that can cost millions of dollars. Trunk Tools deploys solutions that streamline construction data management, automate tedious work, and reduce waste to #letbuildersbuild. --- ## /blog/a-i-in-construction-trunk-text-vs-gpt4/ ### A.I. in Construction: Trunk Text vs GPT4 > Discover how TrunkText outperforms GPT-4. TrunkText offers superior integration, faster queries, and construction-specific features. Construction professionals constantly face challenges on the job site, ranging from managing vast amounts of project documents to ensuring efficient communication among teams. These challenges often lead to mistakes, confusion, delays, increased costs, and reduced productivity. Many construction professionals are turning to new AI solutions, as the need for streamlined processes and accurate information retrieval has become more critical than ever. Trunk Tools' Trunk Text, an AI-enabled search engine designed to crawl through an organization's project documents and provide precise responses to workers in the field. By leveraging this innovative technology, construction companies can save valuable time and money, enhancing their overall efficiency, accuracy, and project outcomes. ## How does TrunkText Compare to ChatGPT? https://www.youtube.com/watch?v=0pRsHU7c8E8 ## Getting Started To start with either ChatGPT or TrunkText, you must connect your relevant project files.  ChatGPT isolates these files into a single chat, which is not scalable across your organization. File uploads are limited to 20MB and can take a long time to upload, limiting your ability to ingest complex project documents. Lastly, updating your documents as you continue the chat is extremely challenging. On the other hand, TrunkText makes getting the data very simple, shares them organization-wide, and does not have a size limit. Trunk Tools integrates directly with your document systems, like Procore, Sharepoint, Autodesk at the project level. Everyone can see exactly which project folders TrunkText has access to and configure permissions accordingly.  ## Running a Query In both TrunkText and ChatGPT, its simple to ask questions and run queries. Both tools reference your specific question and begin searching for answers.  ChatGPT has a website and smartphone application, while TrunkText is accessible via webpage and SMS text message. For simple queries, such as locating an HVAC schedule in project documents, both TrunkText and ChatGPT will search all documents available to locate the result.  ChatGPT will average 20 seconds for a query of this nature, highlight the result, and report the source document.  TrunkText averages 12 seconds for this same query and will highlight the specific reference inside of the source document.  Although this time difference appears small, the ability to go directly to the source to foster confidence makes a huge difference to professionals on-site.  When asking ChatGPT for the most recent project document, it can only reference the documents you have specifically uploaded into your chat. TrunkText can review every project document at your organization to locate the updated documentation.  TrunkText can also read details from blueprints, drawings, and other documents.  This provides another example of TrunkText’s construction-specific focus when comparing it to ChatGPT. ## TrunkText vs. ChatGPT Comparison While ChatGPT is popular, it is not optimized for the construction industry. With the inability to share documents across an organization, delays in uploading, and slow query times, TrunkText has ChatGPT beat. Setting up separate GPT conversations, user accounts, and uploading documents each time creates the exact headaches your teams are trying to avoid.  Documents should be uploaded once, and results should be transparent. TrunkText automatically searches all your documents, makes sure that your results are the most up-to-date, and links you to the results directly inside the source documents. It is designed to be accessible and consistent for everyone on your team.  Most importantly, you can access TrunkText via webapp or text message, making it a field-friendly tool always at your disposal.  With better search controls and results, TrunkText effectively delivers the answers to any question. ## Conclusion It’s time to use AI specifically designed for construction workers in the field. TrunkText was built to search construction documents and get you the right answer in seconds. Your millions of pages of documentation: specifications, RFIs, schedules, submittals, change orders, and more, are all searchable in the palm of your hand. Improve your teams' productivity and avoid mistakes by trying TrunkText today. [Request a Demo](/#demo) --- ## /blog/ai-construction-documents/ ### AI construction documents: how it works > A primer on how AI reads, connects, reviews, and generates the documents on a construction project — where the tech is real, where it's not. AI for construction documents is software that reads the core project documents like drawings, specs, submittals, RFIs, schedules, and change orders, connects them to each other, and runs the document-heavy workflows on a team's behalf. The technology has moved fast in the last two years. It has also picked up a lot of vague marketing, and the buyer question underneath most sales conversations is now the same one: what part of this actually works for construction teams, and what is not yet reliable enough for a jobsite? This piece is the honest primer. It covers the four things AI actually does with construction documents today (ingestion, connection, review, and generation), the outcomes teams have reported, and the specific places where general-purpose AI still falls short on a project compared to construction-specific AI solutions. ## What are AI construction documents? "AI construction documents" is shorthand for using artificial intelligence to read, connect, and act on the documents that describe a construction project. A single commercial job routinely produces hundreds of thousands of files, and construction generates two to five times more documentation today than it did a decade ago. Roughly 85 to 90 percent of that content is unstructured data in drawings, specs, submittal packages, RFI threads, and meeting minutes, and invisible to a project management system that only indexes filenames and metadata. The category exists because that gap between what is in the documents and what a project management system can see is where projects lose money. A missed drawing revision is a rework event that typically starts at ten thousand dollars. A stuck submittal delays long-lead procurement. An RFI that could have been answered from the spec book still takes 30 minutes to draft and might halt work while you wait for a response. ## How does AI read construction documents? AI reads construction documents in two layers: text and vision. The text layer handles specs, RFI threads, product data submittals, meeting minutes, contracts, and change order logs. This is the layer general-purpose AI does well, and it is why chat interfaces like ChatGPT, Claude, and Gemini can summarize a spec section or explain a clause when a user pastes it in. The vision layer is where general-purpose AI struggles. Drawings communicate through geometry, symbols, spatial relationships, cross-sheet references, and revision clouds, not through paragraphs. Reading a drawing means recognizing that a specific symbol on sheet A-201 is a door, that its tag references the door schedule on A-601, that the door's specification lives in Section 08 11 00, and that a submittal for that door is in cycle. Purpose-built construction AI models train on that pattern for years across millions of labeled objects; general-purpose models have not. > The gap is measurable. On the [AECV-Bench benchmark](https://aecv-bench.com/#results) — 118 drawings and more than 4,300 labeled instances — the best fully optimized frontier model detected roughly three in ten doors. [TrunkReview](/tools/trunkreview/), the Trunk Tools object-recognition surface, detected roughly nine in ten at 97 percent precision. Trained on hundreds of object types and millions of labels, this is the current best public proof of how much construction-specific training changes the picture on drawings. ## How does AI connect construction documents to each other? Connection is the difference between AI that summarizes a single document and AI that acts on a project. Construction workflows only happen when dozens of pieces of data and documents are linked to each other: a submittal is compared to its spec, a bulletin change is traced across every sheet it appears on, an RFI response is checked against every prior RFI that touched the same detail. That web of implicit relationships is what the industry calls a knowledge graph when it is represented explicitly. A [construction AI platform](/pricing/) that does this well can take a single click on a door tag and open the schedule row, the spec section, every submittal against that spec, every open RFI on the detail, and every sheet the object appears on beside it because the platform ingested all of those documents together and knows how they refer to each other. Cortex, the Trunk Tools intelligence layer, is built this way. General-purpose models are not, because their context windows and their training corpus do not model a project as a connected system. The [pre-processing step](/blog/pre-processing-is-preconstruction/) is where the knowledge graph gets built. AI is only as good as the input data, and cleaning, structuring, and cross-referencing project documents before an agent runs on them is the unglamorous work that separates a working product from a demo. Teams that skip the pre-processing step end up with confident answers that cite the wrong data. ## How does AI review construction documents? Once documents are read and connected, AI can do the reviews that eat the workweek. Four review workflows are in production today at real general contractors. **Submittal review.** [TrunkSubmittal](/tools/trunksubmittal/) compares each submittal to its spec and returns a compliance status. Before the tool, submittal review typically consumed 50 to 60 percent of an assistant project manager's day. With the tool, the median submittal cycle time drops from 54.8 days to 14.0 days on platform data, and Cleveland Construction reported more than 790 hours and $60,000 saved across four projects. **Drawing and bulletin review.** [TrunkReview](/tools/trunkreview/) reads each sheet in a bulletin, writes a change narrative, and flags every change against the prior revision, including the 10 to 20 percent of meaningful changes the architect does not cloud. A 20-sheet bulletin that takes a project engineer about six hours to review manually runs in under 10 minutes; unclouded changes are the ones that would otherwise show up as rework in the field. **RFI review.** [TrunkRFI](/tools/trunkrfi/) checks whether a proposed RFI is already answered by the project's own documents or a prior RFI, drafts the RFI when it isn't, and analyzes responses for implications. On platform data, roughly 15 percent of RFIs sent today are preventable because the answer exists in project documentation or previous RFI responses no one looked through. **Field question review.** [TrunkText](/tools/trunktext/) answers field questions from SMS, web, or Microsoft Teams by pulling cited answers from the full document set. On platform data, 73.9 percent of Q&A responses cite at least two sources, which is what makes the answer defensible when a superintendent forwards it to the design team. ## How does AI generate construction documents? Generation is the newest of the four, and it is real for a narrow but useful set of documents. The category worth naming: - **RFIs** — cited, structured drafts written from the project's own drawings and specs. Teams recover 15 to 30 minutes per RFI. - **Revision narratives** — the plain-English summary of what changed in a bulletin, sheet by sheet, ready to send to the field. - **Submittal registers** — [TrunkRegister](/tools/trunkregister/) reads the entire spec book, captures every requirement, categorizes each as Action, Informational, or Closeout, and pushes the finished register into the project management system. Saves up to 30 hours on register creation. - **Bid analyses** — [TrunkBid](/tools/trunkbid/) normalizes subcontractor bids and returns an apples-to-apples comparison with scope gaps, inclusions, exclusions, and value engineering proposals surfaced. What AI does not do well yet is generate contractual documents from scratch: the spec book, the drawing set, the prime contract. The judgment those documents encode is not in the training data, and a hallucinated clause is a legal problem. Generation is a first-draft-and-a-cited-record job today, not a replacement for the design team or the attorney. ## Where is AI for construction documents real, and where is it still lacking? Real: platforms that ingest the full document set (including drawings), connect the documents to each other, and run named workflows with named customer outcomes. Real: purpose-trained vision layers that read drawings with double-digit precision improvements over general-purpose models. Real: unlimited-usage annual pricing that matches how construction companies already budget. Lacking: general-purpose LLM wrappers with a "for construction" landing page and no training on drawings, no knowledge graph, and no published benchmark. Lacking: consumption-priced experiments where every failed prompt is metered and every learning curve is a P&L event. Lacking: AI features bolted onto legacy tools that were built before data hygiene mattered, where the underlying storage was never designed to feed a model. The [Trunk Tools vs. generic LLMs comparison](/guides/why-trunk-tools-vs-generic-llms/) covers the specific differences in more depth, and the [build vs. buy AI for construction guide](/guides/build-vs-buy-ai-construction/) walks through the decision framework a technology leader can use inside their own organization. ## How to evaluate AI for construction documents Six questions separate a working platform from a demo: 1. What kind of construction documents can it read, and specifically, can it read drawings — not just extract text from PDFs, but recognize objects, symbols, and revision clouds? 2. Can it connect documents to each other, or does each answer live inside one document at a time? 3. Is there a published drawing-reading benchmark, or only a demo? 4. How is it priced: annual and predictable, or metered by token where every experiment costs the buyer money? 5. Who is running the agents: the vendor, or your team? A platform that ships pre-trained agents is a very different investment than a toolkit that expects the customer to prompt and maintain them. 6. Which named general contractors are using it in production, and what did they measure? The [AI vendor questionnaire](/guides/ai-vendor-questionnaire/) has a longer version of this list, formatted so a procurement team can use it in an RFP. ## Frequently asked questions **What are AI construction documents?** AI construction documents refers to using AI to read, connect, review, and generate the documents on a construction project — including drawings, specs, submittals, RFIs, schedules, and change orders. A construction AI platform reads the full document set as a connected system so agents can act on it: comparing a submittal to its spec, flagging changes in a new bulletin, drafting a cited RFI, or building a submittal register from the spec book. **Can AI read construction drawings?** Purpose-built construction AI can read construction drawings. General-purpose AI models struggle with drawings because drawings communicate through geometry, symbols, spatial relationships, and revision clouds rather than through paragraphs. On the AECV-Bench benchmark of 118 drawings and 4,300+ labeled instances, the best fully optimized frontier model detected roughly three in ten doors, while TrunkReview from Trunk Tools detected roughly nine in ten at 97 percent precision. **How does AI connect construction documents to each other?** A construction AI platform builds a knowledge graph — a map of the implicit relationships between every document on the project. When a user clicks a door tag on a sheet, the platform can open the schedule row, the spec section, every submittal against that spec, and every open RFI on the detail beside it, because it has already ingested and cross-referenced the full set. **Can AI write an RFI or a submittal review?** Yes, with cited sources. A construction AI platform can draft an RFI in under a minute using the project's own drawings and specs, and can return a submittal-to-spec compliance status with a written narrative. The team still makes the final call, but the first pass is done for them, and the response is anchored to the specific documents it came from. **What is a construction AI platform?** A construction AI platform is software built specifically to read, connect, and act on the documents on a construction project. It differs from a general-purpose AI like ChatGPT or Claude in three ways: it is trained on construction data, it reads drawings as well as text, and it runs pre-built agents on a shared knowledge graph rather than expecting the customer to prompt and maintain each workflow. **Which AI is best for construction documents?** The right answer depends on the workflow. For high-volume document reviews — submittals, bulletins, RFIs, spec compliance — a purpose-built construction AI platform will outperform a general-purpose model that has not been trained on drawings. General-purpose models remain useful for one-off text summarization and light Q&A on individual documents that a user pastes in. **How is AI for construction documents priced?** Two models are common. Consumption-based pricing charges by the token or credit consumed, which makes spend hard to forecast as usage scales across projects. Annual, unlimited-usage pricing is a flat subscription regardless of volume, which matches how general contractors already budget for enterprise technology. Trunk Tools uses the [annual, unlimited-usage model](/pricing/). ## Related reading - [Build vs. buy AI for construction](/guides/build-vs-buy-ai-construction/) - [Why Trunk Tools vs. generic LLMs](/guides/why-trunk-tools-vs-generic-llms/) - [Pre-processing is preconstruction](/blog/pre-processing-is-preconstruction/) --- *By the Trunk Tools team. Published September 8, 2026.* *Sources: [AECV-Bench](https://aecv-bench.com/#results) + Trunk Tools internal benchmark (2025–2026, 118 drawings, 4,300+ labeled instances); TrunkReview product webinar (May 2026); Trunk Tools platform data; [Cleveland Construction case study](/customers/case-study-cleveland-construction-sped-up-submittal-reviews-with-trunk-tools/). Last updated September 2026.* ### Frequently asked questions #### What are AI construction documents? AI construction documents refers to using AI to read, connect, review, and generate the documents on a construction project — including drawings, specs, submittals, RFIs, schedules, and change orders. A construction AI platform reads the full document set as a connected system so agents can act on it: comparing a submittal to its spec, flagging changes in a new bulletin, drafting a cited RFI, or building a submittal register from the spec book. #### Can AI read construction drawings? Purpose-built construction AI can read construction drawings. General-purpose AI models struggle with drawings because drawings communicate through geometry, symbols, spatial relationships, and revision clouds rather than through paragraphs. On the AECV-Bench benchmark of 118 drawings and 4,300+ labeled instances, the best fully optimized frontier model detected roughly three in ten doors, while TrunkReview from Trunk Tools detected roughly nine in ten at 97 percent precision. #### How does AI connect construction documents to each other? A construction AI platform builds a knowledge graph — a map of the implicit relationships between every document on the project. When a user clicks a door tag on a sheet, the platform can open the schedule row, the spec section, every submittal against that spec, and every open RFI on the detail beside it, because it has already ingested and cross-referenced the full set. #### Can AI write an RFI or a submittal review? Yes, with cited sources. A construction AI platform can draft an RFI in under a minute using the project's own drawings and specs, and can return a submittal-to-spec compliance status with a written narrative. The team still makes the final call, but the first pass is done for them, and the response is anchored to the specific documents it came from. #### What is a construction AI platform? A construction AI platform is software built specifically to read, connect, and act on the documents on a construction project. It differs from a general-purpose AI like ChatGPT or Claude in three ways: it is trained on construction data, it reads drawings as well as text, and it runs pre-built agents on a shared knowledge graph rather than expecting the customer to prompt and maintain each workflow. #### Which AI is best for construction documents? The right answer depends on the workflow. For high-volume document reviews — submittals, bulletins, RFIs, spec compliance — a purpose-built construction AI platform will outperform a general-purpose model that has not been trained on drawings. General-purpose models remain useful for one-off text summarization and light Q&A on individual documents that a user pastes in. #### How is AI for construction documents priced? Two models are common. Consumption-based pricing charges by the token or credit consumed, which makes spend hard to forecast as usage scales across projects. Annual, unlimited-usage pricing is a flat subscription regardless of volume, which matches how general contractors already budget for enterprise technology. Trunk Tools uses the annual, unlimited-usage model. --- ## /blog/ai-contract-review-for-construction-explained/ ### AI contract review for construction, explained > AI contract review for construction flags payment, indemnification, insurance, and termination risk before signing. How it works, what Document Crunch and Procore add, and why Trunk Tools offers a free first pass. AI contract review for construction is software that reads a construction contract and flags the clauses that carry the most risk: payment and retainage terms, indemnification, liquidated damages, insurance requirements, and termination rights, among others, so a project team gets a head start before a lawyer's full read. It doesn't replace legal counsel on a contract that actually matters to the business; it gives a project executive, PM, or ops lead a faster first pass on what to push back on and what's standard. Trunk Tools offers a version of this free, with no account or credit card required, at [contracts.trunktools.com](/tools/contract-review/). ## Why does contract review risk matter on a construction project? A construction contract is where risk gets allocated long before the first trade shows up on site: who eats the cost of a delay, who's on the hook for a subcontractor's mistake, how retainage gets released, and what happens if the schedule slips. Bid and award timelines are tight, and a contract often gets signed under the same time pressure that produces rushed submittals and bid leveling. An unfavorable indemnification clause, an uncapped liquidated damages provision, or a payment term that doesn't match the actual cash flow of the job doesn't show up as a problem at signing; it shows up months later, when the project is already committed to it. A fast, honest first read at signing is cheap insurance against that. ## What does AI contract review actually do? The core job is reading a contract the way an experienced construction attorney or risk manager would: not line by line in isolation, but against a known set of categories that tend to create exposure on a construction project. That includes payment and retainage terms, change order procedures, delay and liquidated damages, indemnification and liability, insurance requirements, warranty obligations, termination rights, dispute resolution, bond and lien provisions, site conditions, subcontract flow-down terms, and scope and precedence language, the kind of clauses that decide who eats the cost when something goes wrong. The output is typically a risk rating per category, a plain-language summary of what the clause actually says, and specific language to push back on in a redline. ## How does AI contract review work? Most tools in this category follow the same three steps. A user uploads the contract as a PDF, usually a standard form like an AIA or ConsensusDocs agreement or a custom document. The AI reads the full document against the categories above, drawing on training in construction-specific language and industry norms rather than general legal boilerplate. The output comes back as a report: an executive summary, risk ratings by category, and the specific issues worth negotiating before signing. Some tools go further and convert an already-signed contract into an operational guide, mapping deadlines, notice requirements, and responsible parties by role so the compliance obligations buried in the legal language actually get followed in the field. ## Is a specialized construction AI tool necessary for this, or can general models do it? This is worth asking honestly, because the answer differs by task. A task like reading a construction drawing and connecting it to other related project documents requires purpose-built training and a knowledge graph that understands how construction documents relate to each other. General-purpose AI models are demonstrably weaker at that kind of work. Contract review is a different kind of task. A contract is text, organized in fairly standard sections, and identifying risky language in it is closer to the kind of document reasoning general foundational models already do well. That's a meaningful part of why Trunk Tools offers its own contract review tool for free: a good first pass on contract risk doesn't require the same level of document processing and reasoning across multiple documents that a workflow like drawing or submittal review does, so charging a premium for it isn't necessary to deliver a useful result. ## What do dedicated contract review tools add beyond a general model? Document Crunch is the best-known dedicated player in this category, and it does real things a one-off prompt to a general model doesn't. It maintains a Project Playbook that condenses a signed contract's obligations into a repeatable reference the whole team can use throughout the project, not just at signing. It integrates directly into Procore and Microsoft Word, so the review happens inside a workflow a team already runs rather than a separate upload. Document Crunch was acquired by Trimble in 2026, reinforcing that this kind of tooling is becoming a standard line item in construction tech stacks rather than a niche add-on. That said, a firm managing dozens of contracts across a large portfolio has different needs than a project team reviewing one subcontract before award. The first case benefits from the consistency, the workflow integration, and the institutional playbook a dedicated tool like Document Crunch builds over time. The second case is often well served by a fast, free first pass, which is the gap Trunk Tools built its own tool to fill rather than compete on the portfolio-management use case. ## Does Procore have an AI contract review tool? Yes. Procore added a Contract Review agent in 2026 as part of its Digital Coworker agent library, built partly on its acquisition of Datagrid. The agent reviews contracts alongside drawings and specs to identify possible conflicts and adds resolution-oriented comments directly for follow-up, positioning it as a co-reviewer embedded in the same platform a team already uses for project management, rather than a standalone review step. This is part of a paid package of AI tools with a credit-based consumption pricing model that is difficult to predict and budget for. ## What should you look for when evaluating AI contract review software? A few questions matter more than which brand is doing the reviewing. Does it cite the specific clause and language behind each flagged risk, or does it return an unexplained score? Does it protect your data, meaning your contract isn't used to train someone else's model and you control how long it's retained? Is the pricing proportional to the task: a one-off contract review shouldn't cost the same as an ongoing, portfolio-wide compliance system. And does it stop at the signature, or does it also help the field team follow what the contract actually requires once the project is underway, since a well-negotiated contract still creates risk if nobody tracks its notice deadlines and documentation requirements during construction. ## How much should AI contract review cost? Pricing in this category ranges from free to an ongoing subscription billed per user or per portfolio. Dedicated platforms like Document Crunch are built as a recurring line item, priced for firms running contract review as a continuous, portfolio-wide practice across many active projects and reviewers. For a single project team reviewing a contract before signing, or a smaller GC or subcontractor without an in-house construction attorney, paying a recurring subscription for the same first-pass read that a free tool or a careful prompt to a general model can already produce is often paying more than the task requires. The honest answer is to match the spend to how often the review actually needs to happen and how much institutional consistency across contracts genuinely matters to the business. ## Trunk Tools' free AI contract review tool Trunk Tools built a free tool at [contracts.trunktools.com](/tools/contract-review/) that covers both sides of the contract lifecycle. Before signing, it reviews a contract across 14 risk categories, payment and retainage terms, change order procedures, delay and liquidated damages, indemnification and liability, insurance requirements, warranty obligations, termination rights, dispute resolution, bond and lien provisions, site conditions, subcontract flow-down, labor compliance, scope and precedence, and consequential damages, and returns an executive summary with risk ratings and specific language to negotiate. After signing, the same tool converts a contract into a field operations guide: a compliance calendar, a critical deadline matrix, a delegation chart by role, and warning flags on high-risk provisions, covering notice deadlines, submittal requirements, payment application timing, schedule compliance, change order procedures, testing and inspections, safety requirements, documentation standards, meeting cadence, closeout checklists, insurance renewals, and certified payroll. The process takes three steps: upload a contract PDF up to 100MB, the AI reviews it against those categories, and the report arrives by email as a secure link. Nothing is used to train Trunk Tools' models, uploads are protected with 256-bit encryption, the report link expires automatically after 7 days, and a user can delete it instantly at any point before that. It's a genuinely free tool because reviewing a contract's language against known risk categories is a task well-suited to AI without the deeper construction-specific processing that a workflow like drawing or submittal review requires; those workflows are where Trunk Tools' paid agents, built on Cortex, earn their place. --- ## Frequently asked questions **What is AI contract review for construction?** AI contract review is software that reads a construction contract and flags risk across categories like payment terms, indemnification, insurance, and termination rights, giving a project team a faster first pass before a lawyer's full review. **Is AI contract review accurate enough to replace a lawyer?** No. It's a first pass that surfaces the clauses worth a closer look and the language worth negotiating; a contract that matters to the business should still get a lawyer's review before signing. **Is Trunk Tools' AI contract review tool actually free?** Yes. It's available at [contracts.trunktools.com](/tools/contract-review/) with no account or credit card required, and covers both pre-signature risk review and post-signature compliance guidance. **What's the difference between Document Crunch and a general AI model for contract review?** Document Crunch adds a repeatable Project Playbook, direct integration into Procore and Microsoft Word, and consistency across many contracts and reviewers. A general AI model can produce a useful first read on a single contract without that infrastructure. **Does Procore have an AI contract review tool?** Yes. Procore's Contract Review agent, part of its Digital Coworker library launched in 2026, reviews contracts alongside drawings and specs and flags possible conflicts for follow-up. --- *By the Trunk Tools team. Last updated September 6, 2026.* *Sources: Trunk Tools ([contracts.trunktools.com](/tools/contract-review/)); Document Crunch product pages; Procore press materials on its Digital Coworker agent library.* ### Frequently asked questions #### What is AI contract review for construction? AI contract review is software that reads a construction contract and flags risk across categories like payment terms, indemnification, insurance, and termination rights, giving a project team a faster first pass before a lawyer's full review. #### Is AI contract review accurate enough to replace a lawyer? No. It's a first pass that surfaces the clauses worth a closer look and the language worth negotiating; a contract that matters to the business should still get a lawyer's review before signing. #### Is Trunk Tools' AI contract review tool actually free? Yes. It's available at contracts.trunktools.com with no account or credit card required, and covers both pre-signature risk review and post-signature compliance guidance. #### What's the difference between Document Crunch and a general AI model for contract review? Document Crunch adds a repeatable Project Playbook, direct integration into Procore and Microsoft Word, and consistency across many contracts and reviewers. A general AI model can produce a useful first read on a single contract without that infrastructure. #### Does Procore have an AI contract review tool? Yes. Procore's Contract Review agent, part of its Digital Coworker library launched in 2026, reviews contracts alongside drawings and specs and flags possible conflicts for follow-up. --- ## /blog/best-construction-drawing-management-software/ ### Best construction drawing management software (2026) > Compare six construction drawing management tools on set management, revision tracking, AI review, markup, and mobile access — including Bluebeam, Procore, Autodesk Forma, and TrunkReview. The best construction drawing management software depends on what problem you're actually trying to solve: organizing and version-controlling a drawing set, marking it up in the field, or catching what changed in the latest issued set or bulletin before it becomes rework. No single product does all three equally well. This guide compares six tools general contractors, architects, and construction technology leaders evaluate for drawing management in 2026, split across two categories: established platforms that manage the drawing set itself, and a newer wave of AI-native tools built specifically to read what's on the sheet. A drawing set on a mid-size commercial project can run into the hundreds of sheets, revised in bulletins throughout construction, and every revision carries the same question: what actually changed, and did anyone catch it before it hit the field? Set management and version control solve the "which file is current" problem. Reading the drawing itself, catching a dimension that shifted, a note that was added, a detail that was quietly redrawn, is a different problem, and it's the one most of these tools still don't solve. ## Comparison at a glance | Software | Drawing set management | Revision tracking | AI review | Markup | Mobile access | Pricing model | | :---- | :---- | :---- | :---- | :---- | :---- | :---- | | Bluebeam | Yes, via Studio and Sets | Version comparison, Studio Sessions | Add-on (Bluebeam Max), only reads text on drawings | Industry-standard PDF markup | Yes | Per-seat subscription | | Autodesk Forma | Yes, via Autodesk Docs | Version history and audit trail | Very limited, Assistant only | Yes, within Forma Build | Yes | Platform subscription | | Procore Drawings | Yes, OCR-organized sets | Automatic revision detection | Drawing analysis agent only reviews text on drawings | Personal and published markup layers | Yes, with offline sync | Platform subscription | | BuildCheck | Focus on precon drawing sets | Analyzes across design milestones for pre-set list of checks | Limited, hundreds of automated checks across disciplines followed by human review, total process takes 5-10 days | Minimal, focused on flagging rather than redlining | Not a mobile-first tool | Not publicly listed | | LightTable | Focus on precon design review | Compares versions across milestones | Yes, reads drawings and specs across 35-plus scopes | Not a markup tool | Not publicly listed | Not publicly listed | | TrunkReview | Yes, pulls in most recent revisions from PMS and stores version history in drawing log | Detects both clouded and unclouded changes and produces written narratives to accompany visual overlay | Yes, AI can compare up to 2,500 sheets from one revision to the next in preconstruction or construction phase | No, complements existing markup tools | Yes | Flat annual, unlimited usage and users | ## What actually matters when comparing these tools? Drawing set management is the baseline: can the software organize sheets by discipline, keep the current set easy to find, and prevent someone from working off an outdated drawing? Revision tracking goes further, flagging that a sheet changed at all. AI review is the newest and least commoditized category: does the software actually read what changed on the sheet, or does it just log that a new version was uploaded. Markup and mobile access matter for the day-to-day of a project engineer or superintendent working from the field. Pricing model matters more than it gets credit for, since a consumption-based tool can get expensive exactly when a team is using it frequently on large drawings sets. Two more questions are worth asking of any tool in this space before signing a contract. First, does it work with the drawing set you already manage in Procore or Autodesk Forma, or does it require re-uploading and re-organizing a set that already lives somewhere else. Second, is the AI review, if there is one, built for pre-construction design coordination or for construction-phase revision and bulletin review; those are different jobs on different timelines, and a tool built for one doesn't necessarily do the other well. ## Why AI drawing review is a distinct category For most of the history of construction software, "drawing management" has meant organizing files, not reading them. A drawing communicates through geometry, symbols, and spatial relationships rather than sentences, which is a different problem than the text-extraction most document software, and even most AI tools, are built to solve. That gap is exactly why a bulletin or revision review still falls to a person: someone has to open the new sheet, compare it to the last one, and figure out what actually moved. On a typical bulletin, that manual review can take hours per sheet set, and it still depends on the architect having marked every change with a revision cloud in the first place. AI-native tools, whether built for pre-construction coordination or construction-phase revision tracking, exist specifically to close that gap. ## Bluebeam Bluebeam Revu is the tool most project teams already have open when they're marking up a drawing, and Studio Sessions let multiple reviewers mark up the same sheet in real time from different locations. Its core strength is markup: clouds, callouts, dimensions, and stamps built specifically for construction documents, plus version comparison to see what changed between two uploads. Bluebeam Max, an add-on tier, layers AI on top by connecting Anthropic’s Claude general purpose AI models via MCP. Smart Review scans drawings and specs for clashes and gaps, and Smart Overlay compares documents and highlights what changed. Bluebeam Max has only publicly demonstrated the ability to detect textual changes in drawings and is hampered by Claude’s ability to read construction drawings. ## Autodesk Forma Autodesk Forma, the platform formerly known as Autodesk Construction Cloud, manages the drawing set through Autodesk Docs, with version history and an audit trail that keeps the current set clear, and ties that document control to Forma Build for field coordination. Autodesk’s AI tooling is limited mostly to an “Assistant” to ask questions and perform basic user-prompted tasks in the platform. For teams already standardized on Autodesk's design tools, the appeal is a single system connecting design and construction; the tradeoff is that catching changes between drawing sets or revisions is still largely a manual review, done by someone opening the current and prior version side by side. ## Procore Drawings Procore organizes a drawing set with OCR-based sorting and automatically detects when an uploaded file is a revision of an existing sheet rather than a new document, preserving markups across revisions. Procore's broader AI push, a set of agents branded Digital Coworker, arrived in 2026 following its acquisition of Datagrid, and includes a drawing review agent among its initial set. Public demonstrations of this tool indicate that it only has the ability to track textual changes across drawings rather than read and understand the visual language of drawings. With Procore AI’s consumption-based pricing model and the higher credit consumption of drawing-related AI tasks, this can result in an unpredictably high bill that is hard to budget for. ## BuildCheck BuildCheck is a newer, AI design review platform focused specifically on pre-construction. BuildCheck runs hundreds of automated checks across architectural, structural, civil, and MEP drawings to catch errors, omissions, and coordination conflicts before a project breaks ground. BuildCheck has a human-in-the-loop review process which extends delivery to 5-10 days. It isn't primarily built for managing a live drawing set during construction or for markup during field review. BuildCheck’s pricing can be prohibitive, offering an introductory rate of $30 per sheet to perform a review. ## LightTable LightTable is another AI-native entrant aimed at the same pre-construction moment: it reads drawings and specs across more than 35 scopes to catch coordination, constructability, and compliance issues before they turn into RFIs or field delays. Like BuildCheck, it's a design-review tool rather than a drawing set manager or field markup tool, so it's typically run alongside, not instead of, a platform like Procore or Autodesk Forma. ## TrunkReview [TrunkReview](/tools/trunkreview/) is Trunk Tools' agent for drawing and bulletin review, and it sits on top of whatever system a team already runs rather than replacing it. While TrunkReview works successfully for pre-construction drawing review on sets up to 2,500 pages, the tool is built primarily for the recurring job of reviewing a bulletin or drawing revision during construction. It produces a visual overlay and a written narrative of every change, including changes the architect didn't mark with a revision cloud. Among AI-native tools built specifically for that bulletin-review workflow, TrunkReview is a category leader. ## Which one should you actually use? Most projects end up running more than one of these together, since drawing set management, markup, and AI review are three different jobs. A typical stack looks like a platform such as Procore or Autodesk Forma to manage the set and keep everyone on the current version, a markup tool like Bluebeam for day-to-day redlining, and an AI review layer, whether that's a precon tool like BuildCheck or LightTable for pre-construction design coordination, or a construction-phase tool like TrunkReview for bulletin and revision review, to catch what a manual read would miss. The question worth asking of any tool in this category is the same one that applies across construction software generally: does it actually read the drawing, or does it just store it? Timing matters too. BuildCheck and LightTable are primarily built to run before a project breaks ground. TrunkReview is built primarily for the recurring cadence of bulletins and revisions once construction is underway, when a missed change turns into rework rather than a redesign. A team evaluating this category should match the tool to the phase of the project it's actually trying to protect, rather than assuming one AI review tool covers the whole timeline. In Trunk Tools platform data, teams using TrunkReview have accelerated drawing and bulletin reviews by up to 85%, and an estimated 10% to 20% of meaningful bulletin changes go unmarked by the architect's revision cloud, which is the gap AI-native review exists to close. --- ## Frequently asked questions **What's the difference between drawing management software and AI drawing review?** Drawing management software organizes, versions, and stores the drawing set so teams know they're working from the current sheet. AI drawing review goes further, reading the content of the drawing itself to catch changes, conflicts, or errors that a person would otherwise have to find manually. **Does Procore or Autodesk Forma include AI drawing review?** Not yet in a dedicated form. Procore's 2026 AI agent library, built partly on its Datagrid acquisition, includes a drawing revision agent whose only publicly demonstrated capability is to analyze textual changes across drawing sets. Autodesk Forma's AI investment has been more muted, with no clear innovation around construction drawings yet. **What is TrunkReview?** TrunkReview is Trunk Tools' agent for drawing and bulletin review. It produces a visual overlay and written narrative of every change in a revision, including changes the architect didn't mark with a cloud, and sits on top of platforms like Procore or Autodesk Forma rather than replacing them. --- *By the Trunk Tools team. Last updated September 6, 2026.* *Sources: Trunk Tools platform data; Bluebeam, Autodesk Forma, Procore, Datagrid, BuildCheck, and LightTable product and press pages.* ### Frequently asked questions #### What's the difference between drawing management software and AI drawing review? Drawing management software organizes, versions, and stores the drawing set so teams know they're working from the current sheet. AI drawing review goes further, reading the content of the drawing itself to catch changes, conflicts, or errors that a person would otherwise have to find manually. #### Does Procore or Autodesk Forma include AI drawing review? Not yet in a dedicated form. Procore's 2026 AI agent library, built partly on its Datagrid acquisition, includes a drawing revision agent whose only publicly demonstrated capability is to analyze textual changes across drawing sets. Autodesk Forma's AI investment has been more muted, with no clear innovation around construction drawings yet. #### What is TrunkReview? TrunkReview is Trunk Tools' agent for drawing and bulletin review. It produces a visual overlay and written narrative of every change in a revision, including changes the architect didn't mark with a cloud, and sits on top of platforms like Procore or Autodesk Forma rather than replacing them. --- ## /blog/best-construction-submittal-software/ ### Best construction submittal software (2026) > Compare seven construction submittal tools on register building, AI compliance review, submittal types covered, and whether review runs automatically — including Procore, Forma, and TrunkSubmittal. The best construction submittal software depends on two questions: how much of the review does the software actually do, and how many submittal types can it do that for? This guide compares seven tools evaluated for submittal management in 2026. Most submittal software organizes the process: logging what's due, routing it, stamping a decision. A smaller set actually reads the submittal, and a smaller set still reads more than one type of it. That distinction decides whether a tool helps for the two or three months a project is in equipment buyout, or for the full lifecycle, since closeout submittals like O&M manuals, warranties, and LEED documentation keep arriving through substantial completion. The category also splits by which side of the table someone sits on: architect-side tools review what comes in, GC-side tools review what goes out. ## Comparison at a glance | Software | Log or register creation | Spec compliance review | Submittal types reviewed | Review trigger | Integrations | Pricing model | | :---- | :---- | :---- | :---- | :---- | :---- | :---- | | Bluebeam | Manual, by trade or spec section | Manual with approval stamping | N/A | Manual, run by a reviewer | Wide, including Procore | Per-seat subscription | | Autodesk Forma | Automated via AutoSpecs | Manual | N/A | N/A | Autodesk Docs, Forma Build | Platform subscription | | Procore | Automated submittal builder | Yes, via Submittal Review agent | Not yet itemized by type | Agent triggered by user prompt, not automated based on document activity | Procore Marketplace has a wide range of integrations | Platform subscription + credit-based consumption model for AI tools like submittal review agent | | Part3 | Not a register-building tool | Yes, designed for architects and engineers | Not publicly itemized by type | User-triggered | Procore | Not publicly listed | | Remy | Not a register-building tool | Yes | Product data; Not publicly itemized by type | Not publicly specified | Procore, Autodesk, CMIC | Not publicly listed | | BuildSync | Creates submittal packages for subcontractors, but does not build submittal register. | Yes | Public materials only mention product checks | User-triggered via upload | Procore, Autodesk | Not publicly listed | | TrunkSubmittal | Works from an existing register or builds one through TrunkRegister | Yes, against spec sections and prior RFI responses | All primary types except physical samples and shop drawings: product data, test reports, certificates, O&M manuals, LEED/sustainability, warranties, qualifications | Automatic, on upload to Procore or Autodesk Forma | Procore, Autodesk Forma | Flat annual, unlimited usage | ## What actually matters when comparing these tools? Two questions matter more than any single feature. First, does the tool review only product data, or does it also handle additional submittal types over the lifecycle of the project? A tool scoped to product data alone only helps during equipment buyout; one that covers the full submittal set stays useful from mobilization through closeout. Second, does a review start automatically the moment a submittal hits the project management system, or does a project engineer have to remember to kick it off? Manual triggering means the review depends on busy project engineers and assistant project managers to change their workflow to benefit from the first pass done by AI. A couple more questions apply regardless of category: is the tool built for the architect side or the GC side, and when it flags a gap, does it show the spec requirement and the evidence, or just a pass-or-fail verdict a reviewer has to take on faith? ## Bluebeam Bluebeam organizes submittal packages by trade or spec section, routes each through a defined reviewer sequence, and applies standardized stamps so decisions look consistent across reviewers. Studio Sessions let multiple reviewers mark up the same submittal in real time. Compliance review stays entirely manual: a person opens the spec and the submittal side by side and applies the approval stamp themselves. ## Autodesk Forma Autodesk Forma automates the register side of submittals through AutoSpecs, which reads a project's spec set and produces a log in minutes. That automation stops at the register; comparing a submitted document against the spec it corresponds to is still a manual step. ## Procore Procore's submittal builder generates a log organized by division in seconds, and reviewers can mark up and stamp submittals directly in the platform. Its 2026 Submittal Review agent, part of the Digital Coworker library built on the Datagrid acquisition, runs when a user prompts it rather than automatically off document activity, and it bills on a credit-based consumption model layered on top of the platform subscription. Procore hasn't publicly itemized which submittal types the agent covers. ## Part3 Part3 is built for the architect and engineer side of construction administration, and it isn't a register-building tool. Its Submittal Assistant reads a submittal against the spec when a user runs it, though Part3 hasn't publicly itemized which submittal types it covers. It's a strong fit for a design firm, less so for a GC's own buyout process. ## Remy Remy positions itself as a dedicated submittal intelligence platform, comparing submittals against specs and drawings to flag gaps before they reach the field. Its public materials confirm product data as a reviewed type but don't itemize the rest of its coverage, and don't confirm whether a review triggers automatically once a submittal lands in Procore, Autodesk, or CMIC. Its cross-project knowledge base feature is also enterprise-tier only. ## BuildSync BuildSync creates ready-to-submit packages for subcontractors, though it isn't a submittal-register-building tool itself. A submittal review runs when a user uploads a submittal and triggers it, rather than automatically off document activity, and BuildSync's public materials mention product-level compliance checks without itemizing the full range of submittal types covered. It integrates with Procore and Autodesk, and doesn't publish pricing. ## TrunkSubmittal [TrunkSubmittal](/tools/trunksubmittal/) is Trunk Tools' AI agent for submittal compliance review, and it's scoped to the widest range of submittal types in this category: product data, test reports, certificates, O&M manuals, LEED and sustainability documentation, final and sample warranties, and qualifications, everything except physical samples and shop drawings. A review runs automatically the moment a submittal is uploaded to Procore or Autodesk Forma, rather than waiting on a project engineer to start one, and it reads against the applicable spec sections and prior RFI responses. It's built for the general contractor's side of the process, and a person still makes the final call before anything goes out. ## Which one should you actually use? Most teams combine a broad platform for logging and routing, Procore or Autodesk Forma, with a compliance-review layer that actually reads the submittal, whether that's Part3 on the architect side or a GC-focused agent like Remy, BuildSync, or TrunkSubmittal. Two things separate the AI-native tools more than any feature list: how many submittal types the review covers, and whether it starts on its own. A tool scoped to product data only helps during buyout, then goes quiet. A tool that needs a person to remember to trigger it works only as well as that person's week is going, and across this category, TrunkSubmittal is the only one confirmed to run automatically off document activity rather than a user prompt or upload action; Procore's agent is user-prompted, and Part3's and BuildSync's reviews are user-triggered. TrunkSubmittal is also the only one with publicly documented breadth across product data, test reports, certificates, O&M manuals, LEED documentation, warranties, and qualifications. Pricing model matters too: a flat annual rate for unlimited usage removes the incentive to ration how often a team actually uses the tool, unlike a credit-based consumption model. In Trunk Tools platform data, roughly 55% of reviewed submittals carry a significant compliance gap and another 35% to 40% carry a minor or moderate one, and projects using TrunkSubmittal have seen median submittal cycle time drop from about 55 days to 14 days, a 74% reduction. --- ## Frequently asked questions **What is the best construction submittal software?** It depends on the problem. Autodesk Forma and Procore lead on automatically building the register. Bluebeam leads on markup and routing. Among the tools that read submittal content, TrunkSubmittal covers the widest range of submittal types and triggers automatically on upload. **What's the difference between a submittal log tool and a submittal compliance review tool?** A log tool tracks what needs to be submitted, who's reviewing it, and its current status. A compliance review tool reads the submitted document and compares it against the spec requirement, flagging gaps a person would otherwise have to find by reading both side by side. **Which submittal types does AI submittal review software actually cover?** Coverage varies widely and isn't always itemized publicly. Remy confirms product data as a reviewed type without detailing the rest of its coverage; BuildSync's public materials mention product-level checks without a full breakdown; Part3 hasn't publicly itemized its range either. TrunkSubmittal covers product data, test reports, certificates, O&M manuals, LEED and sustainability documentation, warranties, and qualifications, everything except physical samples and shop drawings. **Does submittal review software run automatically, or does someone have to start it?** Mostly, someone has to start it. TrunkSubmittal is the only tool in this comparison confirmed to run a review automatically off document activity, the moment a submittal is uploaded to Procore or Autodesk Forma. Procore's Submittal Review agent runs when a user prompts it, and Part3's and BuildSync's reviews run when a user triggers them via upload. Remy doesn't publicly specify, and Bluebeam's compliance stamping stays entirely manual. **What is TrunkSubmittal?** TrunkSubmittal is Trunk Tools' AI agent for submittal compliance review. It runs automatically on upload to Procore or Autodesk Forma, reads nearly every submittal type against the applicable spec sections and prior RFI responses, and flags non-compliance before a submittal reaches the architect. --- *By the Trunk Tools team. Last updated September 7, 2026.* *Sources: Trunk Tools platform data; Trunk Tools case study with Cleveland Construction; Bluebeam, Autodesk Forma, Procore, Part3, Remy, and BuildSync product pages.* ### Frequently asked questions #### What is the best construction submittal software? It depends on the problem. Autodesk Forma and Procore lead on automatically building the register. Bluebeam leads on markup and routing. Among the tools that read submittal content, TrunkSubmittal covers the widest range of submittal types and triggers automatically on upload. #### What's the difference between a submittal log tool and a submittal compliance review tool? A log tool tracks what needs to be submitted, who's reviewing it, and its current status. A compliance review tool reads the submitted document and compares it against the spec requirement, flagging gaps a person would otherwise have to find by reading both side by side. #### Which submittal types does AI submittal review software actually cover? Coverage varies widely and isn't always itemized publicly. Remy confirms product data as a reviewed type without detailing the rest of its coverage; BuildSync's public materials mention product-level checks without a full breakdown; Part3 hasn't publicly itemized its range either. TrunkSubmittal covers product data, test reports, certificates, O&M manuals, LEED and sustainability documentation, warranties, and qualifications, everything except physical samples and shop drawings. #### Does submittal review software run automatically, or does someone have to start it? Mostly, someone has to start it. TrunkSubmittal is the only tool in this comparison confirmed to run a review automatically off document activity, the moment a submittal is uploaded to Procore or Autodesk Forma. Procore's Submittal Review agent runs when a user prompts it, and Part3's and BuildSync's reviews run when a user triggers them via upload. Remy doesn't publicly specify, and Bluebeam's compliance stamping stays entirely manual. #### What is TrunkSubmittal? TrunkSubmittal is Trunk Tools' AI agent for submittal compliance review. It runs automatically on upload to Procore or Autodesk Forma, reads nearly every submittal type against the applicable spec sections and prior RFI responses, and flags non-compliance before a submittal reaches the architect. --- ## /blog/celebrating-women-in-construction-march-2024/ ### Celebrating Women in Construction - March 2024 > Featuring Q&As with 3 women in construction, asking about their careers in driving innovation, change, and disruption in the built environment ## International Women's Day in Construction As we celebrate International Women's Day this Friday, we're shining a spotlight on several remarkable women driving innovation in the construction industry. In an era of unprecedented advancement, we’re excited to see female leaders spearheading many of these critical initiatives. In our conversations with these women, we’ve noticed several compelling themes. We’ve discovered diversity ignites accelerated innovation. We’ve seen that embracing technology can empower us to pursue our most meaningful work, and lastly, sometimes unexpected challenges pave the way for pivotal opportunities—particularly for women ascending in historically male-dominated fields. As we adopt an all-hands-on-deck approach to the challenges we face in the built environment, we want to thank these leaders and all women for their contributions, not only this month but every month. May their stories inspire you, as they have inspired us! ## Q&A with Women in Construction Management ![](/content/blog/media/Kelly-Benedict-Head-of-Innovation-and-Transformation-at-Gilbane-1-1024x512.png) ### Can you share a pivotal moment in your career within the construction industry that significantly influenced your professional trajectory? In a prior role, I was asked to establish an innovation program and work with a global team of people for a large property development company. At the time I didn’t see it as a great opportunity – rather another initiative in an already initiative-fatigued business.   I remember asking (maybe to my detriment) why me?  I believe I lacked the qualifications for the role and I considered politely declining the opportunity. But what my CEO said to me changed my perspective.   He knew he needed someone who knew the business – how we make and lose money, how to motivate and collaborate with various disciplines throughout the business, and someone with an external network to understand industry trends. But what struck me most was his comment: “You don’t walk into a room and act like you know everything.” Instead, he encouraged me to “ask good questions and consider options. By doing so, people will feel heard and valued.”  That decision changed my career path trajectory forever. It’s a hard job and can be lonely, frustrating, and thankless at times, as there is a high level of failure in innovation. After all, if we know the outcome – it’s not an experiment, right? Our industry is fragmented and low margin and so we tend to look at risk differently which could impact how and if we take calculated risks to innovate. Despite the challenges, what keeps me going are the people I get to engage with – academia, venture capital, emerging technology start-ups, clients, and even our competitors. And working with our teams and seeing how they respond to innovations that will make their lives easier.  ### **How do you foster a culture of innovation and promote diversity in your role?** Diversity is the foundation for better innovative outcomes. It’s a scientific fact. We get better ideas that are more inclusive when we have a diverse team of people. To foster a culture of innovation – there is of course the strategy part to include process, change management, stakeholder engagement, investment/funding appetite, identifying all the interdependencies, and a flexible agile road map for execution aligned with objectives and key results – all things that most companies do. But I think you need to set realistic goals and start with quick wins. This business is a “show me” business and so I’ve tried to show how we got the quick wins, put people’s names up in lights (recognition), and celebrate the wins. That for me started the momentum from which to build on.  When we are looking to launch a new pilot or conduct an innovation hack, team composition becomes a critical consideration alongside the problem we aim to address. It’s integral to our approach. Recently, we had approved a pilot with a new Gen AI start-up company and when looking to find the project sites for us to run the pilots, I selected two women business leaders in two different markets as our core sponsor of these efforts. The outcome? A dynamic collaboration between two women leaders working with a female founder of the start-up and me as the innovation leader.  One of the big industry challenges is what we call shadow IT solutions. Solutions that were purchased with the best of intentions but failed in adoption or just automated more complexity. Root causes when you look at what happened is generally not having a diverse team involved in making the decision, and most importantly, including the people that do the work. ### **What are the most exciting developments on the horizon for construction technology?** I look at innovation as more than technology – we define it as delivering shared value. It could be a process improvement/non-technology solution. To stay on topic with technology – I think the most exciting development is Generative AI because of the trajectory and the benefits to society. The irony is that many may look at this technology as replacing humans, but the reality is that we are looking at technology that will allow people to work on more **_purposeful_** work – eliminating redundant or low value work so that they can focus on high value, more meaningful work. We will still need humans involved with the technology – and they might just be happier people. I think we are all struggling to imagine the benefits of this technology as there has been a lot of information published about its risks. We are running some pilots now and our initial assessments and ROI analysis is showing promising efficiencies and ROI. It also feels like there is more collaboration and sharing within the industry on emerging technology and innovation which will make our industry better in the long run.  ![](/content/blog/media/WIC-Article-LinkedIn-Images-1024x512.png) ### **Can you share the reason you entered the construction industry?** I am in construction "involuntarily" to an extent. I grew up in a small town in Austria in a fairly poor environment. My dad was a carpenter, so he took me to construction sites to help him. I began working at age 12 as an apprentice carpenter, ultimately working in skilled trades for several years. The skilled trades taught me the value of hard work and allowed me to fund my dreams of education and entrepreneurship. In just a few years, I worked my way up to foreman, superintendent, and site manager of increasingly large and complex construction projects. ### **Can you share a pivotal moment in your career within the construction industry that significantly influenced your professional trajectory?** A defining moment in my career occurred during my tenure as a site manager overseeing a team of several hundred people. There was a tragic accident where a worker lost their life on the job. Around the same time, I was getting my PhD in data science and civil engineering, essentially construction technology. I understood that software can be used to decrease job site accidents and make construction sites safer - which is why I developed a health-and-safety app. This gave me my first taste of entrepreneurship and made me realize that the positive impact I can have with software in construction is way greater than as a construction executive. ### **Could you highlight one achievement that you are particularly proud of?** I am incredibly proud of what we are building at Trunk Tools. Trunk Tools’ mission is to enable the deskless workforce. While many construction tech solutions focus on office staff, our approach enables field workers at the heart of the industry. We are dedicated to enhancing their productivity, safety, and predictability through intuitive, mobile-friendly tools designed to be used in their existing daily routines. Currently, we are leading worldwide when it comes to applied generative AI in the field, and I am incredibly proud of our team that has pulled this off.  ![](/content/blog/media/WIC-Article-LinkedIn-Images-1-1024x512.png) ### **Can you share the key milestones and experiences that led you to become a project manager in the construction industry?** I wish it was a bit more intentional - my mother, a huge proponent of education, encouraged me to pursue either business or engineering. Business sounded boring and I was good at math, so I chose engineering (spoiler: I chose both in the end). Since I liked architecture, cities, and the tangible world, civil engineering seemed like the right fit. After completing my B.S. at Maryland in Civil Engineering and a few internships at GCs, I went straight to study Sustainable Design & Construction at Stanford - a unique program that focused on construction management. My goal was to become some sort of structural engineer-architect who could optimize function and aesthetics. In theory, amazing, but after my first structural engineering job, I realized this is really quite challenging in practice. I stumbled upon SpaceX and immediately did everything I could to get in the door - after nearly harassing HR to find a use for my skill set, I learned they had a construction department and they were hiring interns. Some people travel to Europe when they graduate, I chose my version of space camp. SpaceX was the perfect combination of everything I was looking for - construction, aerospace, and a high-speed culture, so the rest was history. I spent roughly 7 years working up from intern to, in the end, managing the construction department. I have temporarily hung up my hard hat to work on the next milestone to become a better leader in construction to pursue an MBA at Harvard Business School, but I can’t wait to get back to the field. ### **Could you highlight one or two projects that you are particularly proud of and share the impact they had on your career?** The most challenging construction project was definitely building a single-span pedestrian bridge across several lanes of traffic. The schedule was fast-tracked and the budget was slim. In hindsight, I think I was given the project because no one wanted to touch it. It was high profile and didn’t have a high chance of success given the prescribed metrics for success: time, money, and quality (these are hard to achieve all at once). Not only did completing this project with \[minimal\] fire drills propel my career at SpaceX, it taught me the necessity to dive into the details, the need to leverage and learn from my elders, and the immense complexity of construction plans especially when multiple designers are involved. Similarly challenging, I bought a distressed triplex a few years ago and spent six months renovating and turning over units to new tenants. There was a reason the property was discounted - perhaps similar to the project above, no one wanted this one. Through a rupture of the main water line, sewer leak, tenant dispute, contractor dispute, structural issues, and flea-pocolypse, I learned a lot by doing. I took a leap and when there is no other option than to figure it out, you really rise to the occasion. In summary, sometimes the projects no one will touch are the best opportunities to prove yourself. For better or worse, oftentimes women need to strive harder to establish a reputation in a field like this, so when opportunity knocks, answer the door. ### **Looking towards the future, what excites you most about construction and real estate?** Thinking toward the future, I am most excited about the use of robotics in construction to maximize productivity and quality, while minimizing errors and safety incidents. In the same vein, I am excited to see how many technologies emerging from the aerospace industry can inform and advance construction technologies. With mundane, repetitive, and unsafe tasks handled, I hope it empowers our labor force to focus on the most value-add activities. Finally, I am excited for a future where we are building on not only Earth, but the Moon, Mars, and beyond. I’ve loved space since I was a little girl, so I dream of the day extraterrestrial construction becomes within our capabilities as humans. Soon! --- ## /blog/construction-drawing-coordination-trunkcoordinate/ ### Coordination doesn't fail in the model. It fails in the set. > TrunkCoordinate automates construction drawing coordination across architectural, structural, and MEP sheets to catch conflicts before they become field rework. The mechanical sheet still carries a background from three revisions ago. A fixture count on the plans disagrees with the schedule. A section callout points at a detail that was renumbered two issuances back. None of these are exotic. All of them reach the field as rework. Ask a VDC coordinator how it happened and the answer is never that nobody looked. It's that looking doesn't scale. Architectural against mechanical, mechanical against structural, structural against plumbing, sheet by sheet, by eye. Then a revision lands and the whole pass is stale. The set is too big to check the same way twice, so the second pass is shorter than the first, and the third is shorter than that. ## Why the gap survives Model-based clash detection is good at what it does, and what it does is check the model. Plenty of projects never produce a fully coordinated one. On the projects that do, the contract documents are still the issued 2D sheets, and the trades build from those. Drawing schedules, callout chains, title blocks, and embedded backgrounds don't exist in the model at all. They only exist on the sheets. So the most consequential construction drawing coordination work on a job is still done by hand, against a document set nobody automated, by the person with the fewest spare hours. ## What we built TrunkCoordinate registers sheets from every discipline onto one coordinate frame. Once architectural, structural, and MEP share a frame, an object at one point on one sheet can be compared against whatever sits at the same physical location on another. From there it reconciles three things. **Objects across disciplines.** The same object resolved to a single entity wherever it appears, then compared trade to trade for count, location, type, and tag. Where two disciplines claim the same spot on the same plane, that's one finding carrying every trade involved, not a stack of pairwise ones. **Schedules and references.** Objects on the plans with no schedule row, and schedule rows with nothing on the plans. Blank or TBD cells flagged instead of passed through. Callouts followed to the sheet they point at, so a renumbered or deleted detail gets caught. **Set integrity.** Every embedded background compared against the current architectural source of record, so walls that moved on one set don't quietly stay put on another. Title blocks and the sheet index reconciled both ways. Every finding carries its source sheets, the objects involved, and an impact rating. Findings push out as RFIs, coordination issues, or change events, and they keep their identity across revisions, so a re-run on a new issuance builds on prior triage instead of starting over. ## Where it sits [TrunkReview](/tools/trunkreview/) finds what changed. TrunkCoordinate finds what that change broke. [TrunkChange](/tools/trunkchange/) finds who pays. TrunkCoordinate is in development, and we're previewing it at Autodesk University this week. We'll publish performance numbers when we've measured them, not before. If you want your set among the first we run it against, [tell us](/#request-demo). ## Frequently asked questions **What is construction drawing coordination?** Construction drawing coordination is the process of comparing architectural, structural, and MEP sheets to find conflicts in object locations, counts, types, tags, schedules, references, backgrounds, and set information before those conflicts reach the field. **Why is model-based clash detection not enough?** Clash detection checks the model, but the issued 2D sheets remain the contract documents on many projects. Schedules, callout chains, title blocks, and embedded backgrounds may only exist on those sheets, so they require their own coordination review. **What does TrunkCoordinate check?** TrunkCoordinate compares objects across disciplines, reconciles plans with schedules and callout references, checks embedded backgrounds against the current architectural source, and compares title blocks with the sheet index. **How does TrunkCoordinate handle drawing revisions?** Each finding keeps its identity across revisions, so a new run builds on the team's prior triage instead of forcing coordinators to restart the review. **How is TrunkCoordinate different from TrunkReview and TrunkChange?** TrunkReview finds what changed between drawing versions. TrunkCoordinate finds what that change broke across the document set. TrunkChange helps determine who pays for the resulting scope. --- *By the Trunk Tools team. Published September 15, 2026.* ### Frequently asked questions #### What is construction drawing coordination? Construction drawing coordination is the process of comparing architectural, structural, and MEP sheets to find conflicts in object locations, counts, types, tags, schedules, references, backgrounds, and set information before those conflicts reach the field. #### Why is model-based clash detection not enough? Clash detection checks the model, but the issued 2D sheets remain the contract documents on many projects. Schedules, callout chains, title blocks, and embedded backgrounds may only exist on those sheets, so they require their own coordination review. #### What does TrunkCoordinate check? TrunkCoordinate compares objects across disciplines, reconciles plans with schedules and callout references, checks embedded backgrounds against the current architectural source, and compares title blocks with the sheet index. #### How does TrunkCoordinate handle drawing revisions? Each finding keeps its identity across revisions, so a new run builds on the team's prior triage instead of forcing coordinators to restart the review. #### How is TrunkCoordinate different from TrunkReview and TrunkChange? TrunkReview finds what changed between drawing versions. TrunkCoordinate finds what that change broke across the document set. TrunkChange helps determine who pays for the resulting scope. --- ## /blog/construction-glossary/ ### Construction glossary: 20 terms builders and buyers use every day > A plain-English construction glossary of the 20 terms that show up on every RFI, submittal, and change order, with links to detailed guides. A construction glossary is a shared vocabulary for the documents, workflows, acronyms, and contract instruments that move a project from bid to closeout. The 20 construction terms below appear on nearly every commercial project: in RFI and submittal logs, drawing sets, specifications, change documentation, and punchlists. This plain-English glossary is written for field teams and the corporate offices that support them. Each entry starts with a direct definition, then explains what triggers the document, who uses it, and where it fits in the construction workflow. ## How to use this construction glossary Use the alphabetical index to jump to a definition. Follow the links within each entry for a detailed guide or related construction terminology. **[Addendum](#addendum)** · **[ASI](#asi)** · **[As-built](#as-built)** · **[Bid leveling](#bid-leveling)** · **[CCD](#ccd)** · **[Change order](#change-order)** · **[Closeout](#closeout)** · **[MasterFormat](#masterformat)** · **[Notice of intent](#notice-of-intent)** · **[Punchlist](#punchlist)** · **[Redline](#redline)** · **[Retainage](#retainage)** · **[RFI](#rfi)** · **[Scope gap](#scope-gap)** · **[Shop drawing](#shop-drawing)** · **[Specification](#specification)** · **[Submittal](#submittal)** · **[Substantial completion](#substantial-completion)** · **[Takeoff](#takeoff)** · **[Transmittal](#transmittal)** ## Addendum An addendum is a formal document issued during bidding that changes the drawings, specifications, or bid instructions before bids are due. Unlike a [change order](#change-order), it is issued before the construction contract is signed. Bidders must price the work as amended by every addendum, so missing one can leave required work out of a bid. Addenda are typically numbered in sequence and become part of the contract documents after award. ## ASI ASI stands for Architect's Supplemental Instructions, a document used to clarify or make minor adjustments to the contract documents without changing contract cost or time. An ASI may resolve a detail or direct a small change that remains within the original scope. If the instruction affects cost, schedule, or contracted scope, the contractor should provide notice and follow the contract's change process rather than treating it as a no-cost clarification. ## As-built As-built drawings record what was actually constructed in the field, including deviations from the original design. Subcontractors and the general contractor usually maintain [redlines](#redline) throughout construction, then turn that information over during [closeout](#closeout). The design team may use those markups to prepare final record drawings. Owners, facility teams, inspectors, and future renovation designers rely on accurate as-built information long after construction ends. ## Bid leveling Bid leveling is the process of normalizing subcontractor bids so a general contractor can compare scope, inclusions, exclusions, assumptions, and price on equal terms. Because bids arrive in different formats and rarely cover scope in exactly the same way, an estimator must identify gaps and align each proposal before selecting a trade partner. Learn [how software helps with bid leveling](/blog/how-does-software-help-with-bid-leveling/) or explore [TrunkBid](/tools/trunkbid/). ## CCD CCD stands for Construction Change Directive, a written instruction directing a contractor to proceed with a change before the parties agree on its cost or schedule impact. It allows work to continue while the adjustment is determined under the contract's change provisions. Once the parties agree on the impact, the directive may be incorporated into a [change order](#change-order). A CCD is distinct from an [ASI](#asi), which is intended for a clarification or minor adjustment that does not change contract cost or time. ## Change order A change order is a formal, signed amendment to a construction contract that changes scope, price, schedule, or a combination of the three. Change orders can result from owner-directed revisions, differing site conditions, design changes, or unresolved scope. They matter because they update the parties' contractual obligations, not merely the project drawings. A disciplined team connects each change to its source documents, notices, pricing, schedule analysis, approvals, and field execution. Learn why that requires a [system of action, not only a system of record](/blog/system-of-action-vs-system-of-record/). ## Closeout Construction closeout is the final project phase in which the contractor completes remaining work and turns over the building and required documentation to the owner. Typical closeout deliverables include [as-built drawings](#as-built), warranties, operation and maintenance manuals, training records, final lien waivers, testing reports, [retainage](#retainage) documentation, and final [punchlist](#punchlist) sign-off. Strong teams start collecting closeout documents during construction instead of waiting until the end. ## MasterFormat MasterFormat is the Construction Specifications Institute numbering system used to organize specifications and other written construction information into divisions. Commercial project teams use the same classification to organize spec sections, submittal registers, estimates, and scopes of work. The familiar sequence runs from Division 00, Procurement and Contracting Requirements, through Division 49, with reserved numbers along the way. See our guide to [construction specifications and CSI MasterFormat](/blog/construction-specifications-explained/). ## Notice of intent A notice of intent is written notification that a party plans to take a contractually significant action, such as awarding work, making a claim, or terminating an agreement. Its exact meaning depends on the contract and context. Common examples include a notice of intent to award and a notice of intent to claim added cost or time. Because contracts often impose strict notice methods and deadlines, project teams treat these notices as clock-starters and preserve proof of delivery. ## Punchlist A punchlist is a list of incomplete or corrective work that must be addressed before final acceptance and project closeout. Items often include missing components, finish defects, adjustment work, incomplete testing, or documentation still owed. The owner, architect, contractor, and relevant trade partners may walk the project together to identify items. The contractor then assigns, tracks, verifies, and closes each item according to the contract. ## Redline A redline is a marked change or annotation on a drawing, specification, or other project document. The name comes from the traditional use of red ink to make changes stand out from the underlying information. Field redlines record installed conditions and feed the [as-built](#as-built) set. Design and submittal reviewers also use redlines to identify corrections. A useful redline shows exactly what changed, where it changed, and enough context for the next person to act. ## Retainage Retainage is a portion of each progress payment withheld until defined project milestones or contract requirements are met. The amount, release conditions, and applicable limits depend on the contract and governing law. Owners may withhold retainage from general contractors, who may apply corresponding terms to subcontractors. Because the withheld balance can represent a meaningful share of a contractor's profit and cash, timely documentation and [closeout](#closeout) are essential to its release. ## RFI An RFI, or Request for Information, is a formal written question used when the drawings, specifications, or other contract documents do not provide enough information to proceed. A contractor routes the question to the responsible architect, engineer, or other decision-maker and tracks the response as part of the project record. A good RFI is specific, cites the relevant documents, explains the schedule or cost impact, and asks for a decision. Read [what an RFI is in construction](/blog/what-is-an-rfi-in-construction/), use our [construction RFI template and example](/blog/construction-rfi-template-and-example/), or explore [TrunkRFI](/tools/trunkrfi/). ## Scope gap A scope gap is required work that is missing from, or falls between, the scopes assigned to project participants. Gaps commonly appear at trade interfaces, where each subcontractor assumes the other owns a connecting or supporting task. Careful scope review and [bid leveling](#bid-leveling) help teams find these seams before contracts are executed. If a gap survives buyout, the team must determine contractual responsibility before it becomes delay, rework, or a disputed [change order](#change-order). ## Shop drawing A shop drawing is a detailed document prepared by a subcontractor, fabricator, or manufacturer that shows how a specific part of the work will be fabricated or installed. Examples include steel connection details, rebar placing drawings, millwork layouts, and duct fabrication drawings. Shop drawings pass through the [submittal](#submittal) process for review before fabrication or installation. Construction drawings communicate design intent for the whole project; shop drawings communicate execution for a specific scope. [TrunkReview](/tools/trunkreview/) compares drawing revisions so teams can see what changed. ## Specification A construction specification is a written contract document that defines materials, quality, performance, workmanship, and installation requirements. Specifications complement drawings, which primarily communicate geometry, location, and quantity. Most commercial specifications follow CSI MasterFormat and divide each technical section into General, Products, and Execution. When drawings and specifications appear to conflict, teams should follow the contract's order-of-precedence and RFI provisions rather than assume one always governs. Read [construction specifications, explained](/blog/construction-specifications-explained/). ## Submittal A submittal is documentation submitted for review to demonstrate that a proposed product, material, or method complies with the contract documents. Submittals can include [shop drawings](#shop-drawing), product data, samples, mock-ups, test reports, and delegated-design calculations. The typical review chain runs from subcontractor to general contractor to architect or engineer and back. Learn [what a submittal is in construction](/blog/what-is-a-submittal-in-construction/), compare the [best construction submittal software](/blog/best-construction-submittal-software/), or explore [TrunkSubmittal](/tools/trunksubmittal/). ## Substantial completion Substantial completion is the contractual milestone at which the owner can occupy or use the project for its intended purpose even though minor work may remain. The architect or other designated contract administrator typically certifies the date. That date can trigger warranty periods, responsibility for utilities and security, insurance changes, liquidated-damages provisions, and partial [retainage](#retainage) release. Substantial completion is not the same as final completion: [punchlist](#punchlist) and administrative work can remain. ## Takeoff A construction takeoff is a quantified list of the materials, assemblies, and units of work required to build a project. Estimators extract quantities from drawings, specifications, and models, then apply labor, material, equipment, overhead, and other pricing inputs. Typical takeoff quantities include square feet of drywall, linear feet of pipe, door counts, tons of steel, and cubic yards of concrete. Accurate takeoffs are a foundation for reliable estimates and bids. ## Transmittal A transmittal is a cover document that records the project information sent from one party to another. It identifies what was sent, who sent it, who received it, the date, the delivery method, and often the purpose or required response. Teams use transmittals for drawings, [submittals](#submittal), samples, specifications, and other formal exchanges. The record can establish that a party delivered specific information by a contractual deadline. ## Frequently asked questions **What is a construction glossary?** A construction glossary is a reference list of the documents, workflows, contract instruments, and acronyms used on a construction project, defined in the way builders and project owners use them on the job. **What are the most common construction acronyms?** Common construction document acronyms include RFI (Request for Information), ASI (Architect's Supplemental Instructions), CCD (Construction Change Directive), CO (Change Order), NOI (Notice of Intent), and CSI (Construction Specifications Institute). **Who uses construction glossaries?** Owners, general contractors, subcontractors, architects, engineers, project engineers, superintendents, and estimators all use shared construction terminology to interpret project documents and workflows. **What is the difference between a submittal and a shop drawing?** A submittal is any documentation sent for review to show that a proposed product or method complies with the contract documents. A shop drawing is one type of submittal that shows how a specific item will be fabricated or installed. **What is the difference between an ASI and a change order?** An ASI clarifies or makes a minor adjustment to the drawings or specifications without changing contract cost or time. A change order formally amends the contract to change scope, price, schedule, or a combination of the three. **Where do construction terms appear on a project?** Construction terms appear throughout the project record, including RFI, submittal, and change order logs; drawings; specifications; meeting minutes; schedules; daily reports; and closeout documents. ## How Trunk Tools connects construction documents Every term in this glossary describes work a project team does with documents. Trunk Tools builds AI agents on Cortex, our construction AI platform, to connect those documents and help teams act on them. [TrunkRFI](/tools/trunkrfi/) drafts questions from project information, [TrunkSubmittal](/tools/trunksubmittal/) reviews submittals against specifications, [TrunkReview](/tools/trunkreview/) compares drawing revisions, and [TrunkBid](/tools/trunkbid/) levels subcontractor bids against scope. --- *By the Trunk Tools team. Published September 1, 2026.* ### Frequently asked questions #### What is a construction glossary? A construction glossary is a reference list of the documents, workflows, contract instruments, and acronyms used on a construction project, defined in the way builders and project owners use them on the job. #### What are the most common construction acronyms? Common construction document acronyms include RFI (Request for Information), ASI (Architect's Supplemental Instructions), CCD (Construction Change Directive), CO (Change Order), NOI (Notice of Intent), and CSI (Construction Specifications Institute). #### Who uses construction glossaries? Owners, general contractors, subcontractors, architects, engineers, project engineers, superintendents, and estimators all use shared construction terminology to interpret project documents and workflows. #### What is the difference between a submittal and a shop drawing? A submittal is any documentation sent for review to show that a proposed product or method complies with the contract documents. A shop drawing is one type of submittal that shows how a specific item will be fabricated or installed. #### What is the difference between an ASI and a change order? An ASI clarifies or makes a minor adjustment to the drawings or specifications without changing contract cost or time. A change order formally amends the contract to change scope, price, schedule, or a combination of the three. #### Where do construction terms appear on a project? Construction terms appear throughout the project record, including RFI, submittal, and change order logs; drawings; specifications; meeting minutes; schedules; daily reports; and closeout documents. --- ## /blog/construction-rfi-template-and-example/ ### Construction RFI template and example > Download a free construction RFI template and see what a well-written RFI includes — fields, common mistakes, and a step-by-step writing guide. An RFI in construction, short for Request for Information, is a formal written question a contractor sends to the design team when a drawing or a spec section doesn't give the field enough information to build correctly. The architect or engineer's written answer becomes part of the official project record, carrying the same weight as the drawings and specs it clarifies. RFIs should be concise, well-sourced, clearly written, and contain all relevant information to increase the likelihood of a timely, satisfactory response from the design team. [Download RFI template →](/content/blog/pdfs/construction-rfi-template.pdf) ## What does a proper construction RFI example look like? An RFI should contain the following basic information for the design team. You can download a fillable copy using the button above. - RFI \# - Project name and number - Date submitted - Expected response date - Responsible contractor - Subject - Drawing/spec reference - Question - Proposed solution - Cost/schedule impact - Additional sources/attachments Why these components? The subject line lets anyone scanning the RFI log find it without opening it. The drawing or spec reference points the design team straight to the conflict instead of making them search for it. The question is a single, specific ask, not several bundled together. The proposed solution gives the architect something to approve instead of starting from a blank page. The responsible contractor field routes any follow-up to the right party without someone tracing it back through the log, and attaching the source documents up front lets the architect verify the conflict without requesting them separately. The expected response date and cost or schedule impact turn a routine question into one the design team can prioritize correctly and reply to promptly. ## What are the most common mistakes in a construction RFI? Whether you're working from a sample RFI construction teams shared with you or drafting from scratch, these are the three mistakes that most often send an RFI back for clarification: - **Vague framing.** "Please confirm door frame type" tells the design team nothing about which door, which drawing, or which spec section is in conflict, so they have to ask a follow-up question before they can answer the original one. - **Missing drawing or spec reference.** Without it, the architect has to go find the context themselves, which adds days to an already slow loop. - **Asking a question that's already answered.** In Trunk Tools platform data, an estimated 17.2% of draft RFIs are already answered by previous RFI responses or other project documents, meaning the question never needed to go out at all. This can lead to tension with the design team, owner’s rep, and owner when it happens frequently. ## How do you write a construction RFI? 1. Check whether the answer already exists in the drawings, the specs, or a prior RFI before drafting a new one. 2. Identify the exact drawing sheet or spec section causing the conflict. 3. Frame one clear question. Split multiple issues into separate RFIs. 4. Propose a solution if you have one; it gives the design team something to approve rather than originate. 5. Set a response-needed-by date tied to your schedule and aligned to contractual terms. 6. Flag the potential cost or schedule impact so it isn't a surprise later. 7. Submit it through your project management system so it's logged, dated, and trackable. ## How do RFIs get processed once they're submitted? An RFI moves through a consistent chain: a subcontractor or field team raises the question, a project engineer drafts it using the steps above and submits it via a project management system, and the architect or engineer of record answers it before it routes back to the field. Every RFI gets logged in the project's RFI register with its status tracked to closure. If the answer reveals a scope, cost, or schedule impact that wasn't part of the original contract, the RFI becomes the documentation trail behind a change order. ## How Trunk Tools helps you draft a better RFI TrunkRFI, the RFI agent built on Cortex, Trunk Tools' construction intelligence layer, fills in these fields automatically, including the responsible contractor, spec reference, question, proposed solution, and supporting attachments, by scanning the full project document set before a draft ever reaches the design team. If the question is already answered, it flags that so you can avoid sending an unnecessary RFI. If it genuinely needs to be sent, the agent drafts a complete RFI, leaving a project engineer a few minutes of review instead of the roughly 30 minutes a draft normally takes. It also analyzes the response from the design team and makes recommendations on next steps, a process that often takes 4+ hours. ## Frequently asked questions **How is an RFI supposed to look like on a construction project?** It should be short and structured rather than a loose email. It should be written clearly and cite relevant sources to ensure prompt response from the design team. Finally, you should check to ensure the answer to the question is not already present in project documents or previous RFI responses. **What information should a construction RFI include?** An RFI number, project name and number, date submitted, expected response date, the responsible contractor, a subject line, the drawing or spec section in question, a specific question, a proposed solution if one exists, a cost or schedule impact flag, and any supporting sources or attachments. **What is an example of a well-written construction RFI?** A well-written RFI names the exact drawing sheet or spec section in conflict, asks one specific question instead of several bundled together, and proposes a solution rather than leaving the design team to originate one. **Why do RFIs get sent back for clarification?** The most common reasons are a vague question, a missing drawing or spec reference, or a question the project documents already answer. **Is there a standard construction RFI template?** There's no single universal format, but most templates include the same core fields: project and RFI number, drawing or spec reference, the question, a proposed solution, an expected response date, and a cost or schedule impact flag. *By the Trunk Tools team. Last updated August 26, 2026\.* *Sources: Trunk Tools platform data.* ### Frequently asked questions #### How is an RFI supposed to look like on a construction project? It should be short and structured rather than a loose email. It should be written clearly and cite relevant sources to ensure prompt response from the design team. Finally, you should check to ensure the answer to the question is not already present in project documents or previous RFI responses. #### What information should a construction RFI include? An RFI number, project name and number, date submitted, expected response date, the responsible contractor, a subject line, the drawing or spec section in question, a specific question, a proposed solution if one exists, a cost or schedule impact flag, and any supporting sources or attachments. #### What is an example of a well-written construction RFI? A well-written RFI names the exact drawing sheet or spec section in conflict, asks one specific question instead of several bundled together, and proposes a solution rather than leaving the design team to originate one. #### Why do RFIs get sent back for clarification? The most common reasons are a vague question, a missing drawing or spec reference, or a question the project documents already answer. #### Is there a standard construction RFI template? There's no single universal format, but most templates include the same core fields: project and RFI number, drawing or spec reference, the question, a proposed solution, an expected response date, and a cost or schedule impact flag. --- ## /blog/construction-specifications-explained/ ### Construction specifications, explained > Construction specifications (specs) define quality, performance, and installation standards. Here's how CSI MasterFormat organizes them, what the three parts of a section mean, and which divisions fail compliance most often. Construction specifications are the written requirements that describe the quality, performance, and installation standards a project must meet. Most people just call them specs. Drawings show what gets built and where; specs describe how well it has to perform and how it has to go in. ## How are construction specs organized? Most commercial specs follow MasterFormat, the numbering system published by the Construction Specifications Institute. MasterFormat organizes specs into 50 divisions, numbered 00 through 49, grouped into six broad categories: Procurement and Contracting Requirements (00), General Requirements (01), Facility Construction (02 through 19), Facility Services (20 through 29), Site and Infrastructure (30 through 39), and Process Equipment (40 through 49). Not every number is in active use; several are reserved for future categories, so the divisions you actually see on a project skip around. A plain-English cheat sheet for the divisions that show up on most commercial projects: | Division | What it covers | | :---- | :---- | | 01 | General requirements: submittals, RFIs, quality control, project administration | | 02 | Existing conditions: demolition, hazardous material remediation | | 03 | Concrete | | 04 | Masonry | | 05 | Metals: structural steel, miscellaneous metals | | 06 | Wood, plastics, and composites | | 07 | Thermal and moisture protection: roofing, waterproofing, insulation | | 08 | Openings: doors, windows, hardware | | 09 | Finishes: drywall, paint, flooring, ceilings | | 22 | Plumbing | | 23 | HVAC | | 26 | Electrical | | 27 | Communications | | 28 | Electronic safety and security | | 31 | Earthwork | | 32 | Exterior improvements: paving, landscaping | | 33 | Utilities | ## What are the three parts of a spec section? Every spec section follows the same three-part format. Part 1, General, covers administrative and procedural requirements: what has to be submitted, which reference standards apply, and what quality assurance is required. Part 2, Products, lists the acceptable materials, manufacturers, and models, along with the performance criteria they have to meet. Part 3, Execution, describes how the product actually gets installed, inspected, and tested in the field. ## How do specs and drawings relate, and what wins when they conflict? Drawings and specs are meant to work together, not compete: drawings communicate geometry, location, and quantity, while specs define quality, performance, and installation method. On most private commercial projects, contracts based on AIA A201 deliberately don't rank one document above the other. Both are equally binding, so a contractor can't point to the drawings to skip a spec requirement, or point to the spec to ignore what's drawn. When the two genuinely conflict, the contract calls for the issue to be raised with the architect, typically through an RFI, rather than assumed away. Federal construction contracts work differently: standard federal contract language states that specifications govern over drawings in a conflict, but that's the exception, not the default, on private work. ## Which CSI divisions have the most compliance issues? In Trunk Tools platform data across tens of thousands of submittal compliance reviews, mechanical, electrical, and plumbing divisions fail at roughly twice the rate of structural and site divisions: | Division | Name | Non-compliant | Fully compliant | | :---- | :---- | :---- | :---- | | 03 | Concrete | 31.8% | 12.1% | | 31 | Earthwork | 38.9% | 13.7% | | 04 | Masonry | 41.4% | 22.9% | | 05 | Metals | 47.3% | 7.4% | | 09 | Finishes | 50.6% | 6.1% | | 07 | Thermal and moisture protection | 53.1% | 8.1% | | 23 | HVAC | 60.5% | 8.6% | | 26 | Electrical | 65.0% | 4.9% | | 22 | Plumbing | 66.8% | 5.0% | | 28 | Electronic safety and security | 72.1% | 7.0% | Concrete and earthwork specs, governed by well-established numeric standards, tend to produce the cleanest submittals. MEP divisions and electronic safety and security specs, where performance thresholds, code requirements, and approved-manufacturer lists stack up inside a single section, produce the most compliance gaps. The pattern holds regardless of who's reviewing the submittal: spec quality drives more of the variation in compliance than the individual reviewer does. ## What are the most common problems with construction specs? 1. Performance criteria get buried: A fire rating, a load requirement, or a warranty term sits in a paragraph of boilerplate language, easy to miss until a submittal gets rejected for missing it. 2. Specs conflict with drawings: A product, dimension, or detail described in the spec doesn't match what's shown on the drawing, and it often surfaces mid-construction instead of during review. 3. References go stale: This is especially common when specs are copied from one project to the next given the size and scale of many large construction projects and the time it takes to assemble a new spec book. A spec section may cite a code edition that's been superseded or a product that's been discontinued, especially on projects that sat in design for a long time before bidding. ## How Trunk Tools helps teams work with specs TrunkSubmittal reviews every incoming submittal against the applicable spec sections automatically, catching a missed performance requirement or an unapproved substitution before it reaches the architect. Underneath that review sits Cortex, Trunk Tools' construction intelligence layer, which connects every spec section to the drawings, submittals, and RFIs tied to it, so a conflict between a spec and a drawing surfaces on its own instead of waiting to be discovered in the field. ## Frequently asked questions **What is Division 1 in construction specs?** Division 1, General Requirements, covers the administrative and procedural requirements for the whole project: submittal procedures, RFI procedures, quality control, and project administration, rather than a specific trade or material. **What's the difference between specs and drawings?** Drawings show what gets built and where, using geometry and dimensions. Specs describe how well it has to perform and how it has to be installed, using written requirements. **Who writes construction specs?** The architect or engineer of record typically writes or compiles the specs, often with input from specialty consultants for trades like structural, mechanical, or electrical work. **What are the three parts of a spec section?** Part 1, General, covers administrative requirements. Part 2, Products, lists acceptable materials and their performance criteria. Part 3, Execution, describes installation, inspection, and testing. *By the Trunk Tools team. Last updated August 25, 2026\.* *Sources: Construction Specifications Institute MasterFormat; AIA A201, General Conditions of the Contract for Construction; Trunk Tools platform data.* ### Frequently asked questions #### What is Division 1 in construction specs? Division 1, General Requirements, covers the administrative and procedural requirements for the whole project: submittal procedures, RFI procedures, quality control, and project administration, rather than a specific trade or material. #### What's the difference between specs and drawings? Drawings show what gets built and where, using geometry and dimensions. Specs describe how well it has to perform and how it has to be installed, using written requirements. #### Who writes construction specs? The architect or engineer of record typically writes or compiles the specs, often with input from specialty consultants for trades like structural, mechanical, or electrical work. #### What are the three parts of a spec section? Part 1, General, covers administrative requirements. Part 2, Products, lists acceptable materials and their performance criteria. Part 3, Execution, describes installation, inspection, and testing. --- ## /blog/enr-futuretech-conference-insights-transforming-construction-with-trunk-tools-ai-innovations/ ### ENR FutureTech Conference Insights: Transforming Construction with Trunk Tools' AI Innovations > At ENR FutureTech, Dr. Buchner detailed innovations behind TrunkText while Roy illustrated its practical advantages on construction sites. At the recent ENR FutureTech conference, Dr. Sarah Buchner, CEO and Founder of TrunkTools, and Andy Roy, Superintendent at Gilbane Building Company, shared their insights into the changing landscape of construction technology. Dr. Buchner detailed the innovations behind TrunkText, TrunkTools' pioneering generative AI product, while Roy illustrated its practical advantages on the construction sites. ## Andy Roy's Construction Journey Andy Roy's lifelong passion for construction led him to a career in the field. After earning a degree in Construction Engineering from Marquette University, Andy joined Gilbane Building Company, where he now works as a Superintendent. Throughout his career, Roy has encountered inefficiencies stemming from the increasing complexity and volume of project data, a challenge he believes requires innovative solutions. ## Introducing TrunkText: The AI Brain Behind Construction To address these challenges, Dr. Sarah Buchner showcased TrunkText, an AI tool specifically designed for the construction industry. TrunkText enables users to easily query project data by texting a dedicated phone number or via web app, providing answers along with links to the original source documents for accuracy and transparency.  ## Real-World Application: Andy Roy's Experience Andy Roy shared his eight-month experience with TrunkText, highlighting its practical benefits. He asked various project-specific questions, such as the cure time for structural glazing sealant and scheduling requirements for water tests. Each query was answered promptly, complete with relevant source documents. This quick access to accurate information improves efficiency and reduces the risk of errors and rework. Let’s dive deeper into some of these examples below. ### Example 1: Information Retrieval and Planning **Question 1:** What is the manufacturer-approved cure time for the structural glazing sealant for the east glass facade? **Response 1:** TrunkText retrieves the relevant documents, then replies: “The manufacturer-approved cure time for the structural glazing sealant is 7 to 14 days. However, full adhesion time is 14 to 21 days. **Question 2:** When should all sealants and gaskets be installed to ensure everything has cured before a water test on June 8. **Response 2:** TrunkText retrieves the relevant documents, then replies: “To ensure that all sealants and gaskets have fully cured before a water test on June 8, 2024, they should be installed no later than May 18, 2024. This allows for the maximum full adhesion time of 21 days. That’s great! Now your key questions are answered and you can continue building. Let’s try another use case. ### Example 2: Translation and Creating RFIs **Question 1:** I’m installing the Stellar manufactured fireplace. Are there any requirements in the product specifications, submittals or shop drawings to tape/seal all pipe and elbow joints in the fireplace vent ductwork? **Response 1:** TrunkText retrieves the relevant documents, then replies: “Yes, according to the provided document, all pipe and elbow joints in the fireplace vent ductwork must be sealed. This includes the longitudinal seam on the pipe. High Temp RTV Silicone and/or fail tape must be used on each joint/seam. Failure to do so may cause issues. **Question 2:** Please answer my last question in Spanish. **Response 2:** Returns response in Spanish language: "Sí, hay requisitos específicos en las especificaciones del producto. Cada junta y costura en el tubo y los codos deben estar sellados. Esto incluye la costura longitudinal en el tubo. Debe usarse silicona RTV de alta temperatura y/o cinta de aluminio en cada junta/costura. Si no se hace esto, puede causar falta de eficiencia en el funcionamiento de la chimenea." **Question 3:** Does door 20103-2 require power-actuated hardware and at what voltage? **Response 3:** Yes, according to the door schedule, door 20103-2 has power-actuated hardware. However, the electrical drawings do not appear to show a callout for power and a panel designation at this opening. Would you like to create an RFI? TrunkText then suggests the built-in option to create an RFI, and after a few clicks, creates and emails this document to the requested individual. As you saw with this example, TrunkText has the ability to answer follow-on questions, translate into another language, and create and send an RFI! ## Expanding Capabilities: Querying Drawings Dr. Buchner also announced that TrunkText now includes the ability to query drawings, allowing users to extract detailed information from project drawings, such as assembly sequences and floor clearances. This feature underscores TrunkTools' dedication to ongoing innovation in construction technology. Let’s dive into the detailed examples below. ### Example 1: Counting Rigging Points **Question 1:** It doesn’t seem like there are enough rigging points installed to hang the FLOE sculpture in the Atrium. Can you confirm how many upper cables the sculpture contains so I can validate that the quantity of rigging points match? **Response 1:** TrunkText retrieves the relevant documents, then replies: “The FLOE sculpture contains 23 upper cables for hanging, as per the provided documents. You can cross-check this number with the quantity of rigging points installed in the Atrium.” This answer was visible in a table so let’s try another example that would definitely require the computer to read the drawing. ### Example 2: "Reading" Drawings **Question 1:** What is the assembly sequence of the middle and lower cables for the FLOE sculpture? And what is the floor clearance below the FLOE sculpture? **Response 1:** The assembly sequence for the middle and lower cables of the “FLOE sculpture” is as follows: 1. Pre-assemble middle and lower cables, acrylic, murmuration and school pieces in the shop to the greatest extent possible. 2. Attach upper cables to ceiling hoist rings. 3. Attach the frame to upper cables and level using turnbuckles at the bottom of upper cables. 4. Attach the top of middle cables to the frame after the frame has been leveled. 5. Adjust grippers below level acrylic pieces after middle cables are installed so that all level pieces hang at the same elevation. The floor clearance below the “FLOE” sculpture is 14.5 feet. ## The Future: AI Agents and Intelligence Augmentation Looking forward, TrunkTools is developing a suite of AI agents—workflow automation tools that utilize the AI brain built for each construction site. These agents aim to streamline project management tasks, from creating RFIs to ensuring data accuracy across all project documents. Dr. Buchner emphasized that this technology is meant to augment human intelligence, not replace it, allowing construction professionals to focus on critical decision-making and creative problem-solving. ## Embracing the Future of Construction Dr. Buchner concluded by emphasizing the broader impact of TrunkTools' technology: reducing overall construction costs and addressing the labor shortage in the industry. By keeping humans integral to the process and enhancing their capabilities with AI, TrunkTools is helping the construction industry focus on building enduring, impactful structures that fulfill fundamental human needs. As TrunkTools continues to innovate and lead in construction technology, its commitment to improving efficiency, transparency, and quality remains strong. For construction professionals like Andy Roy and companies across the industry, TrunkText represents a significant step forward, aligning incentives and transforming the way we build.   [**Watch the Keynote Recording Here.**](/blog/futuretech-24-trunktext-keynote-dr-sarah-buchner-amp-andy-roy/) --- ## /blog/fostering-innovation-the-idea-bounty-program-revolutionizing-workplace-dynamics/ ### Fostering Innovation from the front lines through an Idea Bounty Program > How one company uses TrunkPerform to incentivize construction employees to submit process improvement ideas for continual innovation. ## Bold New Ideas from Boots on the Ground The most valuable ideas for process improvements often come from those on the front lines - the employees deeply entrenched in the day-to-day operations. However, many organizations don’t encourage or empower these folks with the agency to share great ideas they have in their heads. One of Trunk Tools’s forward-thinking partners initiated an Idea Bounty Program to harness the collective creativity of their workforce and drive continuous improvement. Under this program, employees of this formwork contractor are encouraged and incentivized to submit any process improvement idea to their local management team. These ideas could range from streamlining workflows and optimizing resource allocation to improving customer experiences and enhancing product quality.  What sets this program apart is its incentive structure. To kickstart participation and incentivize idea generation, each viable idea submitted by an employee receives an immediate $5 cash payout onto their Trunk Tools debit card. This not only recognizes the value of their contribution but also serves as a tangible reward for their proactive engagement in driving organizational improvement.  For ideas that are not only deemed feasible but also implemented within the organization, an additional reward of $100 in cash is disbursed to the employee. This not only motivates employees to think critically about their work environment but also encourages them to take ownership of the implementation process, fostering a culture of accountability and innovation. The benefits of the Idea Bounty Program extend far beyond monetary rewards. By tapping into the collective intelligence of its workforce, organizations can uncover hidden inefficiencies, identify untapped opportunities, and adapt more quickly to changing market dynamics. This not only drives bottom-line results through cost savings and increased productivity but also cultivates a sense of ownership and empowerment among employees. Most forward-thinking management teams of organizations with human capital-intensive operations want their teams to continue to improve operations. However, many lack the framework to incentivize and empower employees to do so.  TrunkTools’s **TrunkPerform** product gives organizations exactly what they need to implement an Idea Bounty Program: * An executive dashboard to view and manage incentive programs * A platform for team leads and supervisors to communicate goals and messages to frontline employees via SMS text message * A compliant system to instantly distribute cash rewards to employees via a debit card (even if employees don’t have a SSN) If you’d like to learn more about how to implement an idea bounty program to foster innovation on your jobsite, [**submit the “Contact Us” form**](/#demo) or email sales@trunktools.com. --- ## /blog/from-chaos-to-clarity-tackling-unstructured-data/ ### From Chaos to Clarity - Tackling Unstructured Data​ > Transform unstructured construction data with AI. Streamline workflows, manage documentation, and boost project efficiency effortlessly. ### **The Complexity of Construction Data** Construction project managers are the central hub in a wheel of ever-changing information. While project managers are highly trained, it is nearly impossible to expect all of this information to be memorized, mentally filed, and executed day in and day out. Furthermore, people take vacations. They get sick. They switch companies. Life happens. Despite this, we often rely on one project manager to make sense of it all and stay on top of every detail. They must know the latest information for all spokes while connecting the dots—time, money, quality, and safety are at stake.  ![](/content/blog/media/image-1-1024x576.png) For a 24-month commercial construction project, a team may start with fewer than 50 documents; by the end of the project, this number explodes into millions of pages. ### **The Burden of Unstructured Data** The sheer volume of documentation is staggering, but the unstructured nature of this data compounds the problem. Unstructured data is not organized in a predefined manner at the beginning of a project and grows increasingly complex as the project progresses. "A project manager must understand all the reference standards, budgets broken into bids and change orders, schedules with monthly and two-week updates, and tons of meetings. The project manager is often the only person who can mentally connect the dots between these items," one industry professional notes. Adding to the challenge, documents are often stored as separate PDFs that cross-reference one another and are continuously updated. This creates difficulties in: * **Finding critical information:** Important details may be buried in unrelated files. * **Maintaining accuracy:** Outdated documents can lead to errors and delays. * **Ensuring efficiency:** Searching for files or information manually wastes time and mental energy. For example, locating the specifics for a single procurement item, such as a roof hatch, may require sifting through submittals, RFIs, and drawings—each stored in separate locations. ![](/content/blog/media/image-2-1024x576.png) ### **Current Industry Solutions** The construction industry has made strides in addressing unstructured data through cloud-based tools. These tools create shared repositories of project documents, allowing stakeholders to access the latest information. However, they come with limitations: * Documents remain separate linked files. * Structuring data relies on manual input, such as naming conventions or metadata fields. * Performing holistic searches across all documents is cumbersome, requiring excessive downloads, manual cross-referencing, and countless control+F searches. Despite these advances, project teams still spend considerable time managing unstructured data, impacting efficiency and decision-making. ### **Structuring Construction Data with Advanced Technology** Looking ahead, AI offers transformative potential for managing unstructured data. By automatically tagging, classifying, and organizing documents, AI can: * Enable quick searches for contracts, drawings, and reports using keywords and context. * Ingest thousands of pages and create connections between disparate sets of information, alleviating the cognitive load on project managers. * Automate document categorization and indexing, turning data chaos into actionable insights. * Lay the groundwork for predictive analytics, identifying risks or delays based on trends from past projects. Unstructured data poses a significant hindrance to construction efficiency, quality, and informed decision-making. However, by embracing AI and advanced tools, the industry has an incredible opportunity to improve project outcomes, streamline workflows, and boost team morale by transforming data chaos into clarity. ## Unlock the Power of Construction-Centric AI From document management to workflow automation, Trunk Tools is built for builders. Talk to our team to learn how we can support your projects. [TALK TO SALES](https://trunktools.com/#request-demo) --- ## /blog/futuretech-24-trunktext-keynote-dr-sarah-buchner-amp-andy-roy/ ### FutureTech '24: TrunkText Product Demo, Dr. Sarah Buchner & Andy Roy > The Trunk Tools Product team describes our newest AI-powered feature: image summarization. Image summaries can be queried to answer questions. ![](/content/blog/media/1717192496934.jpeg) ## Trunk Tools' Dr. Sarah Buchner and Gilbane's Andy Roy Give Stellar Keynote at ENR FutureTech 2024 Learn about how TrunkText leverages cutting-edge AI technology to help field workers like Andy spend less time on bureaucratic chores and more time building. [Watch Now!](#) --- ## /blog/gilbane-building-co-launches-national-rollout-of-trunk-tools/ ### Gilbane Building Co. Launches National Rollout of Trunk Tools > Gilbane Building Company and Trunk Tools are excited to announce the first national rollout of Trunk Tools’ field-first AI solution TrunkText. Gilbane, a leading global construction manager, has signed on to expand across the U.S. and will scale the platform beginning with ten projects. Excerpt:  “TrunkText’s ability to provide instant access to critical project information offers a real opportunity to enhance productivity and project execution,” states Karen Higgins-Carter, Gilbane’s Chief Information and Digital Officer. “We partnered with Trunk Tools for its innovative approach to document management and productivity enhancement. We believe AI can transform our operations by refocusing our teams’ work on higher value, more strategic tasks.”  “We’re beyond excited to continue our collaboration with Gilbane,” says Dr. Sarah Buchner, Founder & CEO of Trunk Tools. “This partnership highlights our mutual commitment to augmenting construction workers with tools that make them more productive, reduce rework by 65% and deliver exceptional value to our clients.” [Read Full Article](https://www.gilbaneco.com/about/whats-new/news/gilbane-building-company-partners-with-trunk-tools-for-national-rollout-of-trunktext/) | [Talk To Sales](http://www.trunk-tools.test/#request-demo) --- ## /blog/gilbane-uses-trunk-tools-to-track-21000-documents-construction-dive/ ### Gilbane uses Trunk Tools to track 21,000 documents (Construction Dive) > How Gilbane used an AI tool to track 21,000 documents: the Providence, Rhode Island-based contractor leveraged Trunk Tools’ artificial intelligence program to prevent costly rework and save time and money. [Trunk Tools](https://trunktools.com/) was recently featured in a Construction Dive Article about how Gilbane Building Company used AI to prevent costly rework and save time and money. Excerpt:  "Keeping track of every detail in every contract a builder signs before stepping onto a jobsite can be a Sisyphean task. You can roll that metaphorical boulder up that mountain, but something, some detail, has the chance to bring progress tumbling down. Gilbane Building Co.’s Andrew Roy knows this well. Roy, a lead superintendent, oversaw the Baird Center expansion project, a $456 million renovation of the Milwaukee convention venue, as part of a joint venture with Fond du Lac, Wisconsin-based C.D. Smith.  Together, Roy and his team added approximately 300,000 square feet to the existing structure — which originally opened in 1998 — including 24 new meeting rooms, more than 400 indoor parking spaces, six loading docks and an executive kitchen, according to the project’s information page. The group broke ground in 2021 and fast-tracked completion, leading to a May 2024 finish. But getting there wasn’t easy. The job’s specifications and contracts added up to around 21,000 discrete documents, an issue that has become increasingly common on today’s more complex builds.  “It isn’t humanly impossible to be completely familiar with every single document on the project and every single change or conversation that’s going on,” Roy said. This is where New York City-based Trunk Tools came into play. The company makes an artificial intelligence-based tool that contractors can use to track a project’s documents and contracts to get immediate answers without leaving the jobsite." [Read Full Article](https://www.constructiondive.com/news/gilbane-trunk-tools-ai-baird-center/725378/) | [Talk To Sales](http://www.trunk-tools.test/#request-demo) --- ## /blog/how-does-software-help-with-bid-leveling/ ### How does software help with bid leveling in construction? > Bid leveling software helps GCs compare subcontractor bids on equal terms by normalizing formats, surfacing exclusions, and cutting the 4–8 hours estimators spend per package by hand. Software helps with bid leveling in construction by reading every bid against the project's requirements and organizing that comparison automatically instead of leaving an estimator to reconstruct it by hand from bids that all arrive in different formats, with exclusions buried in a cover letter and assumptions written in ambiguous language. The manual version of that work is where most of the time on a bid package actually goes. ## What does bid leveling actually involve? Bid leveling means taking every subcontractor's bid for a given scope of work and lining them up on the same terms, so a general contractor can tell whether Bidder A's number is actually lower than Bidder B's, or just missing scope that Bidder B included. That sounds simple until the bids themselves arrive: one sub emails a PDF with the number in the body of the email, another sends a spreadsheet with its own line-item breakdown, and a third submits through a bid portal with exclusions listed in a cover letter attachment instead of the form itself. Assumptions are rarely stated the same way twice. Before anyone can compare price, someone has to read every bid closely enough to figure out what each one actually includes. ## Why does manual bid leveling take so long? A bid package usually has 3 to 5 bidders to compare, and an estimator or project manager typically spends 4 to 8 hours leveling a single bid package. A project with 40 bid packages, which is common on a mid-size to large commercial job, works out to 20 to 40 working days, or roughly 4 to 8 weeks of estimator time across a single buyout season spent reading and comparing bids before anyone gets to negotiating or awarding. That timeline runs in parallel with a buyout schedule that doesn't wait, so the practical result is that leveling gets rushed, or scope gaps get missed, or both. ## Manual bid leveling vs. software-assisted bid leveling | | Manual (spreadsheet or email) | Software-assisted | | :---- | :---- | :---- | | Time per bid package | 4 to 8 hours | Minutes to review a generated comparison | | Format handling | Estimator re-keys each bid into a shared format | Bids are read and normalized automatically | | Exclusion detection | Depends on catching it in a cover letter or footnote | Flagged automatically against the scope of work | | Consistency across estimators | Varies by who's doing the leveling | Same comparison logic applied to every package | | Output | Spreadsheet built from scratch each time | Structured comparison, typically exportable to Excel | ## What does bid leveling software actually change? The core job doesn't change: someone still has to decide which subcontractor to hire, and that decision still depends on price, scope, schedule, and trust in the sub. What software changes is how long it takes to get from a stack of inconsistent bids to a clean, apples-to-apples comparison, and how much of that comparison an estimator can trust without re-checking it line by line. A bid that looks 8% cheaper on the cover page can turn out to exclude fireproofing, or assume a longer float in the schedule than the general contractor planned. Catching that difference is the entire point of leveling, and it's also the part that's easiest to rush when 40 bid packages are due on the same tight schedule. ## What software helps with bid leveling? **Spreadsheets and email.** Still the default on plenty of projects. An estimator builds a comparison spreadsheet by hand, copying each bidder's numbers and exclusions into the same rows so they line up. It’s a reliable method for experienced estimators, but every hour spent re-keying bids is an hour not spent negotiating scope or vetting a sub's schedule. **Invitation and bid-collection platforms like PlanHub and ConstructConnect.** These focus on the front half of the process: sending invitations to bid out to a network of subcontractors, sharing project documents through a plan room, and tracking who has viewed or responded. PlanHub connects general contractors to a large subcontractor and supplier network for exactly that purpose. Neither one reads what comes back and compares it against the scope of work; that step still happens after the bids land in someone's inbox. **Bid management software like Archdesk.** Archdesk covers the bidding process end to end, from building the request for bids off a bill of quantities through side-by-side comparison and award, with a subcontractor database and standardized comparison templates layered on top. That comparison still runs on data an estimator enters or imports, rather than on the software reading a submitted bid PDF and populating the comparison itself. **Platforms with a built-in "leveling" feature, like BuildingConnected, SmartBid (part of ConstructConnect), and Procore.** These let an estimator build a side-by-side comparison view once bids are in, and BuildingConnected specifically lets an estimator edit scope sheets and compare bids once they're in the system. But the comparison itself still depends on manual entry. Someone still has to open each bid, discover what's included or excluded, and type it into the comparison. None of them read a submitted bid PDF and extract the scope gaps automatically. **AI-first bid analysis tools.** A newer category of software, including Trunk Tools' TrunkBid, is built specifically to read the scope of work, or a scope sheet, alongside every bid that comes in, line by line, and surface gaps, exclusions, and alternates automatically. Instead of giving an estimator a faster way to build the comparison by hand, the software builds a first version of the comparison itself, so the estimator's time goes into judgment and negotiation instead of data entry. ## Where the risk actually sits when leveling gets rushed The cost of a weak leveling job rarely shows up during buyout. It shows up later, when a sub who was awarded work based on a bid that quietly excluded a scope item files a change order for it, or when two trades both assumed the other would cover a piece of work that landed in neither bid. On a project with 40-plus packages and a compressed buyout window, that risk multiplies simply because there isn't time to read every bid submission as closely as the last one. Software doesn't remove the judgment call about which trade partner to hire, but it does shrink the window where a buried exclusion has time to slip through unnoticed. ## What should actually drive the decision on bid leveling software? A few questions matter more than which category a tool falls into. Does it read the actual content of a bid, including exclusions buried in a cover letter, or does it just organize where bids get stored and tracked? Does it compare bids against your specific scope of work or scope sheet? Does an estimator still have to retype anything to get from a bid PDF to a usable comparison? And does the output leave your team with something they can act on immediately and confidently, ideally a clean export they can drop into their existing buyout workflow, rather than a dashboard that has to be interpreted before it's useful? ## Frequently asked questions **What is bid leveling in construction?** Bid leveling is the process of comparing subcontractor bids for the same scope of work on equal terms, so pricing differences reflect actual differences in scope rather than differences in how each bid was formatted or what it happened to include. **How long does bid leveling take manually?** An estimator or project manager typically spends 4 to 8 hours leveling one bid package with 3 to 5 bidders. On a project with 40 bid packages, that adds up to 160 to 320 hours, or roughly 20 to 40 working days, across a single buyout season. **Does bid leveling software replace the estimator's judgment?** No. Software speeds up the comparison and catches scope gaps that are easy to miss by hand, but the decision on which subcontractor to hire still depends on a person weighing price, schedule, and trust in the sub. **Which construction bidding platforms have a bid leveling feature?** Platforms including BuildingConnected, SmartBid (part of ConstructConnect), Archdesk, and Procore include some form of side-by-side bid comparison or leveling feature. In each case, an estimator still enters or imports the bid details manually; none of them read a submitted bid PDF and extract the scope gaps automatically the way an AI-first tool does. **What is TrunkBid?** TrunkBid is Trunk Tools' bid analysis agent. It reads subcontractor bids against the scope of work, scope sheet, or spec sections and surfaces gaps, exclusions, qualifications, and alternates in a structured comparison exported to Excel before buyout. *By the Trunk Tools team. Last updated August 27, 2026\.* *Sources: Trunk Tools platform data; BuildingConnected (Autodesk Construction Cloud); PlanHub; ConstructConnect and SmartBid; Archdesk.* ### Frequently asked questions #### What is bid leveling in construction? Bid leveling is the process of comparing subcontractor bids for the same scope of work on equal terms, so pricing differences reflect actual differences in scope rather than differences in how each bid was formatted or what it happened to include. #### How long does bid leveling take manually? An estimator or project manager typically spends 4 to 8 hours leveling one bid package with 3 to 5 bidders. On a project with 40 bid packages, that adds up to 160 to 320 hours, or roughly 20 to 40 working days, across a single buyout season. #### Does bid leveling software replace the estimator's judgment? No. Software speeds up the comparison and catches scope gaps that are easy to miss by hand, but the decision on which subcontractor to hire still depends on a person weighing price, schedule, and trust in the sub. #### Which construction bidding platforms have a bid leveling feature? Platforms including BuildingConnected, SmartBid (part of ConstructConnect), Archdesk, and Procore include some form of side-by-side bid comparison or leveling feature. In each case, an estimator still enters or imports the bid details manually; none of them read a submitted bid PDF and extract the scope gaps automatically the way an AI-first tool does. #### What is TrunkBid? TrunkBid is Trunk Tools' bid analysis agent. It reads subcontractor bids against the scope of work, scope sheet, or spec sections and surfaces gaps, exclusions, qualifications, and alternates in a structured comparison exported to Excel before buyout. --- ## /blog/how-field-users-are-using-trunk-tools-on-jobsites/ ### How Field Users are using Trunk Tools on Jobsites > What are the most common types of questions asked on construction projects? To find out, we used AI to analyze one month of queries from TrunkText users. The results offer a fascinating look at the fragmented nature of construction information and the challenges project managers face keeping track of it all. ### A Game of 20(000) Questions If you've ever managed a construction project, you know the pain of _dumpster diving_. And no, we're not talking about literal dumpsters (though that's sometimes involved too). We’re talking about document diving - the equally messy and significantly more time-consuming process of sifting through a mountain of construction plans, admin paperwork, and communication logs. Thousands of pages spread across multiple PDFs, colorful markups layered upon older markups, and let’s not forget the scribbles on crumpled paper plans (always with a faint coating of drywall dust). Whether you need to confirm one small detail or give the go-ahead for a critical task, it can take minutes, even hours, to find the answer. And if you're really unlucky, you’ll realize after all that searching that the answer doesn’t exist at all. This got us thinking: what are the most common types of questions asked on construction projects? To find out, we used AI to analyze one month of queries from TrunkText users. The results offer a fascinating look at the fragmented nature of construction information and the challenges project managers face keeping track of it all. ![](/content/blog/media/question-types.jpg) We were not surprised that **Technical Specifications and Standards** dominated the chart at 30%. It makes sense, considering how much time gets spent squinting at spec sheets, cross-checking plans against submittals, and digging through submittal logs to confirm (for the fifth time) that the screws are, in fact, supposed to be stainless steel, not galvanized. **Installation and Construction Details** came in a close second. If you’ve ever fielded the “Wait, is this a 2-inch reveal or a 3-inch reveal?” question from a contractor, you’ll understand why this category holds its weight. Details can make or break a build (and your sanity). From there, **Procurement and Work Orders** at 15% reflect the realities of supply chain volatility (because no project is complete without at least one missing part or delayed delivery). The rest of the categories, including schedules, task clarifications, document retrieval, and miscellaneous follow in descending order. ### Information Gathering Doesn't Have to Suck When you think about the lowest valleys of information gathering, what questions were you struggling with? How long did you spend hunting for details that could have been easy to find? These inefficiencies aren’t just frustrating - they can cost time, money, and trust. If you mapped out your own project’s questions, would they look like ours? Most importantly, how much time could you save if the answers were at your fingertips? At Trunk Tools, we’re on a mission to make the 20,000 questions of construction management feel like a game you’re _winning_. ### Ready to start winning the game of 20(000) questions? [LEARN MORE](https://trunktools.com/#request-demo) --- ## /blog/how-to-evaluate-ai-software-for-construction-5-key-points-for-success/ ### How to Evaluate AI Software for Construction: 5 Key Points for Success > As the construction industry increasingly turns to artificial intelligence (AI) to streamline operations, improve decision-making, and drive innovation, choosing the right AI software becomes crucial. Here are five key points to consider when evaluating AI software for your construction projects: As the construction industry increasingly turns to artificial intelligence (AI) to streamline operations, improve decision-making, and drive innovation, choosing the right AI software becomes crucial. Here are five key points to consider when evaluating AI software for your construction projects: ## **1\. Evaluate the Capabilities of the Platform** Understanding the capabilities of the platform you choose is key to assessing whether it will meet the needs of your team. Some areas to consider include: * Reading Drawings and Text: Make sure the platform you choose can read and understand both drawings and text. This will help ensure all your project files are part of the data set to which the AI is applied. * Data Integration: Check if the platform can integrate with your existing systems, such as project management tools, BIM software, and ERP systems. Seamless data integration ensures that the AI can access and process all relevant information without manual intervention. * Predictive Analytics: Evaluate the platform’s ability to perform predictive analytics. This includes forecasting project timelines, budget overruns, and potential risks. The more accurate the predictive capabilities, the better you can plan and mitigate issues before they arise. ## **2\. Conduct a Thorough Security Review** Security is paramount when integrating AI software into your construction operations. Begin with a comprehensive security review to ensure that the software meets your organization's cybersecurity standards. Here are some critical steps to follow: * Assess Data Protection: Ensure the AI software has robust data encryption protocols to protect sensitive project information. For instance, end-to-end encryption and secure socket layer (SSL) protocols are essential. * Vendor Security Practices: Evaluate the vendor's security practices and history. Look for compliance with industry standards, such as SOC 2. Investigate their incident response plans and past performance in handling data breaches. * Regular Audits and Updates: Confirm that the software undergoes regular security audits and updates to address vulnerabilities and evolving threats. This includes automated patch management and scheduled penetration testing. ## **3\. Identify a Specific Project for Implementation** Pinpointing a specific project for AI implementation helps in evaluating the software's fit for your needs. Follow these steps to identify a suitable project: * Business Objectives: Align the project with your organization's strategic goals, such as improving project management, optimizing resource allocation, or enhancing safety protocols. * Feasibility and Impact: Choose a project that is feasible in terms of data availability, complexity, and resource requirements. Evaluate the potential impact and return on investment (ROI). Projects with clear metrics, like reduced downtime or increased on-time project completion, are ideal. * Pilot Testing: Consider starting with a pilot project to test the software's capabilities in a controlled environment before scaling up. This can help identify any potential issues and allows for adjustments before a full-scale rollout. ## **4\. Plan Your Financial Strategy** Understanding the financial aspects of adopting AI software is crucial for budgeting and planning. For the initial pilot(s), understand how you will pay for this while you build out an ROI to justify expanding across the enterprise. Here are some considerations: * Pricing Model: Evaluate the vendor's pricing model, whether it's subscription-based, usage-based, or a one-time license fee. Ensure it aligns with your budget and usage patterns. For instance, a subscription model might be more manageable for ongoing costs. * ROI Analysis: Conduct a thorough ROI analysis to justify the investment. Factor in both direct benefits (e.g., cost savings, increased efficiency) and indirect benefits (e.g., better project insights, improved safety). Tools like Net Present Value (NPV) and Internal Rate of Return (IRR) can be useful in this analysis. ## **5\. Engage the Project Team Early** Involving the project team early in the evaluation process ensures a smoother implementation and better alignment with business needs. Establishing champions early on can ensure broad adoption and usage, reducing the risk of reverting to old ways of doing things. Here’s how to engage your team effectively: * **Cross-Functional Collaboration**: Include representatives from different departments (e.g., project managers, superintendents, project executives, IT, operations) to provide diverse perspectives and identify potential challenges. Regular meetings and workshops can facilitate this. * **Training and Readiness**: Assess the team’s readiness to adopt the new technology and plan for necessary training and support. Develop a comprehensive training program that covers both the technical aspects and the practical application of the AI software. * **Feedback Loop**: Establish a feedback loop to gather input from the team throughout the evaluation and implementation phases, ensuring the software meets their needs and expectations. This can include regular check-ins, surveys, and a dedicated support channel for addressing concerns. ## **Conclusion** Evaluating AI software for construction involves careful consideration of platform capabilities, security, project alignment, financial planning, and team involvement. By following these five key points, you can make informed decisions that not only meet your business needs but also pave the way for successful AI integration. Thorough evaluation today can save you from potential pitfalls and maximize the benefits of AI for your construction projects.  To learn more about our approach to AI at Trunk Tools, contact [sales@trunk.tools](mailto:sales@trunk.tools) or complete the outreach form on our [website](http://www.trunk-tools.test). --- ## /blog/how-to-evaluate-construction-ai/ ### How to evaluate construction AI before your 2027 budget locks > Judge construction AI on outcomes before 2027 budgets lock: where to start, success criteria, vendor accuracy questions and a checklist. Most construction companies will set their 2027 technology budgets in the next few weeks, and artificial intelligence (AI) should be on every list. Too many of those line items will be approved on the strength of a good demo alone. This guide shows executives, operations leaders and finance teams how to evaluate construction AI on outcomes: start from the workflow, write success criteria before you sign, ask what happens before the model reads your documents, ask for the receipts, bring legal and IT in early, and check that the price rewards adoption. We included a helpful checklist below. **The short answer:** judge construction AI by a measured result on one costly workflow, tested on your own documents, with precision and recall stated for your drawing types and a price that stays predictable as adoption grows. ## Which workflow should construction AI fix first? A bulletin lands on a Tuesday afternoon. Twenty sheets, a handful of clouds, and a project engineer who already has a full day of submittals waiting. That is where AI earns its budget, or doesn't. Before you compare vendors, answer two questions as a leadership team. Which workflow eats the most hours on your projects? What does a missed detail in that workflow cost you? For most builders the answer sits in submittal review, drawing and bulletin review, requests for information (RFIs), or bid leveling. Pick one or two. If you can't name the workflow and the cost of a miss, you're about to buy a tool in search of a problem. ## What success criteria should you set before you sign? For each workflow, write down the metric, today's baseline, the target with a date, and the person who owns the result. "Median cycle time on critical-path submittals" is a metric you can track. "Faster submittals" is a hope. Then measure on four levels, in order: - Usage: are teams actually using it? - Workflow results: is the work faster or better? - Project outcomes: were schedule days protected, rework avoided and change orders captured? - Business outcomes: did margin or capacity improve? Each level is only believable when the one below it is measured. The levels also run on different clocks. Usage shows up in weeks, project outcomes in months, and margin at closeout. Settle the dollar assumptions with finance now, such as a daily general conditions rate, so nobody argues about them at renewal. ## What happens before the model reads your documents? Most construction information isn't plain text. Drawings speak in geometry, symbols and cross-sheet references: a window can be three thin lines in a wall. Schedules keep their meaning in rows and columns. The answer to a real field question usually spans several documents. So the most useful vendor question is about the work that happens before any AI model sees your files. Our own testing shows why: - Drawings: in our September 2026 test on real construction drawings, the best general-purpose AI model available found 66 of every 100 windows and flagged about 99 things that weren't windows (66% recall, 40% precision). The models we trained at Trunk Tools found 97, with about 3 false alarms (97% recall, 97% precision). That's why we pre-process every sheet with models built for construction drawings before anything answers a question. - Connections: across our platform, 73.9% of project Q&A answers cite two or more sources, because builders' questions rarely live in one document. Precision is how often a tool is right when it flags something. Recall is how much of what's on the sheet it finds. Ask every vendor: 1. What are your precision and recall on a held-out set of our drawing types, and when did you last test? 2. How do you handle schedules and tables? 3. How do you know which documents relate to each other? If most answers come back as "the model handles it," keep digging. ## How do you check a vendor's accuracy claims? Ask for the receipts - What known-correct answers do you test against, and how often? - When the underlying model changes, how do you know accuracy didn't drop? - Can you show me the record of one run, step by step, with page-level sources? - What does it do when it isn't sure? - Who builds and maintains the agents after go-live? A vendor with a tested product answers with specifics. Notice when a vendor steers you back to the demo. ## When should legal and IT get involved? Security and legal reviews often set the real timeline. Some owner contracts carry clauses about AI and data use, and your legal team may want to check each candidate project. IT will ask for a SOC 2 Type 2 report, an independent audit of a vendor's security controls, and whether the vendor trains its models on your data. Start those reviews now so they don't push your pilot past budget lock. ## What pricing rewards adoption? AI pays off only when people use it. If cost climbs with every question, user or document, your best month becomes your most expensive one, and teams start rationing. Check the fit with how you budget, too: company-wide, in a project's general conditions, or in overhead. Ask each vendor what happens to your bill when adoption takes off. ## Your pre-budget checklist for success before you see any demos - Determine your top two workflows by hours spent, and how much each of those costs you in dollars. - Define a metric, a baseline, a dated target and an owner for each of those workflows. - Submit the business case to Finance for approval. ### When reviewing each demo - Make sure demos run on your own bulletins or submittals. - Collect each vendor's precision and recall on your drawing types, with the test date. - Compare how each vendor tests accuracy and what happens when the model changes. - Ask for a step-by-step record of one run, with sources, and what the tool does when it isn't sure. ### When you have narrowed down your selection - Ask Legal and IT to review contract clauses, security reports and data-use terms. - Confirm what happens to cost when usage grows, and where the cost will sit in your budget. - Assign a field owner, such as a superintendent or project engineer, alongside an executive sponsor. ## Common questions about evaluating construction AI **Can general-purpose AI read construction drawings?** Partly. In our September 2026 test, the best general-purpose model found 66 of 100 windows and raised about 99 false alarms. Models trained on construction drawings found 97, with about 3. Ask every vendor for its own numbers on your drawing types, with the test date. **What is the difference between precision and recall?** Precision is how often the tool is right when it flags something. Recall is how much of what's actually there it finds. You need both: high recall with low precision buries your team in false alarms. **What should we measure first?** Usage, in the first few weeks. Workflow results, project outcomes and margin follow, and each is only believable once the level below it is measured. **Next step:** Download our [AI vendor questionnaire](/guides/ai-vendor-questionnaire/) for the full question list with scoring guidance. Or bring a real bulletin or submittal to a 30-minute working session with our team and watch Trunk Tools read it. *Part 3 of 6 in the How to Buy AI series.* ### Frequently asked questions #### Can general-purpose AI read construction drawings? Partly. In our September 2026 test, the best general-purpose model found 66 of 100 windows and raised about 99 false alarms. Models trained on construction drawings found 97, with about 3. Ask every vendor for its own numbers on your drawing types, with the test date. #### What is the difference between precision and recall? Precision is how often the tool is right when it flags something. Recall is how much of what's actually there it finds. You need both: high recall with low precision buries your team in false alarms. #### What should we measure first? Usage, in the first few weeks. Workflow results, project outcomes and margin follow, and each is only believable once the level below it is measured. --- ## /blog/inside-trunk-tools-ai-team/ ### Building the Brain Behind Construction: Inside Trunk Tools’ AI Team > At Trunk Tools, AI isn’t an add-on—it’s the foundation. With one of the largest AI teams in construction tech, Trunk Tools is fusing research-level expertise with real jobsite challenges. Their engineers—spanning computer vision, NLP, and MLOps—are transforming how the world builds, already driving results across $100B+ in construction volume. At [Trunk Tools](https://trunktools.com/), AI isn’t a buzzword; it’s the foundation. Construction is one of the most complex, data-heavy, and risk-sensitive industries on Earth. Every project generates thousands of drawings, specs, and submittals, and every small mistake can ripple into real-world cost and delay. Trunk Tools was [built around one radical idea](/about/): making AI a core capability, not a feature. We didn’t bolt AI onto construction software. We built construction intelligence from the ground up. ![](/content/blog/media/Sarah-Buchner_Headshot_Portrait-1.jpg) Dr. Sarah Buchner Founder & CEO, Trunk Tools ## **The Largest AI Team in Construction Tech** While many companies are only beginning to experiment with AI, Trunk Tools has quietly assembled one of the largest and most experienced machine learning teams in construction technology over the last four years. The team is 25+ engineers strong, spanning major AI disciplines: computer vision, natural language processing, evaluation, optimization, and MLOps. Collectively, the group brings more than 200 years of experience, over fifteen advanced degrees (including six PhDs), and more than fifteen patents and publications. Team members have built, deployed, and refined machine learning systems at Apple, Amazon, Microsoft, NASA, IBM, DocuSign, Dataminr, and 3M, and now they are applying that expertise to an industry that literally builds the world. ![](/content/blog/media/ML-Team-Infographic-791x1024.png) You can’t just plug a foundation model like GPT into a construction site. It has to understand the noise, the context, and the consequences. ![](/content/blog/media/1711686499649.jpeg) Alex Shyr VP of AI, Trunk Tools ## **From Research Labs to Real Jobsites** Beyond impressive résumés, this team delivers real-world impact. AI in the field is unforgiving: constantly changing drawings, inconsistent specs, messy PDFs, and jobsite chaos. Trunk Tools’ engineers take that complexity head-on, combining academic rigor with construction pragmatism. * NLP specialists decode the nuanced language of submittals and contracts. * Computer vision engineers interpret drawings and finish schedules with precision. * MLOps experts ensure every model update is tested, traceable, and deployable in hours, not weeks. * AI evaluation engineers stress-test model reliability against real-world data, not just benchmarks. ## **A Multidisciplinary Team for a Multidimensional Industry** Trunk Tools’ ML engineers collaborate across specialties. Each project blends natural language processing for text-heavy submittals and specifications, vision models for plans and sheets, optimization for scheduling, and reinforcement learning for process improvement. The result is not a single model but a network of cooperating agents designed to help humans make faster, better decisions. We don’t just work with data; we make it meaningful. This is the difference between having AI features and being an AI-first company. ![](/content/blog/media/Sarah-Buchner_Headshot_Portrait-1.jpg) Dr. Sarah Buchner Founder & CEO, Trunk Tools ## **Proof, Not Promises** This work isn’t theoretical. [Trunk Tools’ AI](/platform/) now powers workflows across hundreds of active construction projects **totaling $50B+ in construction volume**, including a [nationwide rollout with Gilbane Building Company](/blog/gilbane-building-co-launches-national-rollout-of-trunk-tools/). On the ground, that translates to tangible outcomes: * **50%+ reduction** in **submittal review** time * **$100K monthly rework expenses eliminated** before they ever reach the field. * **20+ hours a week back** to building, not paperwork. ### **The Bottom Line** Trunk Tools’ AI team is not only imagining the future of construction but actively engineering it. ### **Bring AI Intelligence to Your Jobsites** Ready to see how Trunk Tools’ AI team is transforming construction from the ground up? [Schedule a demo](https://trunktools.com/#request-demo) to experience how our AI-driven workflows reduce rework, accelerate reviews, and give your teams more time to build. Let’s engineer the future of construction—together. [REQUEST A DEMO](https://trunktools.com/#request-demo) --- ## /blog/pre-processing-is-preconstruction/ ### Pre-processing is preconstruction for your project data > Before construction AI can answer questions or run agents reliably, it has to pre-process the project — classify documents, read drawings, and build a knowledge graph. Skip it and you get guesses or expensive re-reads. Preconstruction is invisible once a building is standing. The average person touring a finished project doesn’t think about the takeoff, the clash detection, or the sequencing worked out months earlier. Skip that work, though, and it shows up fast: rework, wrong orders, a schedule that doesn't hold. Construction AI has its own version of preconstruction. Before an assistant can answer anything about your project or an agent completes a task on your behalf, it has to make sense of thousands (maybe millions) of documents across drawings, specs, submittals, RFIs, contracts, and schedules, usually scattered across three or four systems that don't talk to each other. We call that work “pre-processing,” and it's the reason why the answer you get back or the AI agent’s output is trustworthy. ## What “pre-processing” actually is Pre-processing is the work of turning a pile of disconnected documents into something an AI system can reason across: pulling every document in from wherever it already lives, classifying each one by type (a submittal is not an RFI is not a spec section, an architectural drawing is not a civil drawing, etc.), and then actually reading it: text, the visual language of drawings, structured data from schedules, tables, or data fields in other connected platforms. This work happens before an agent ever completes a task, or a superintendent asks a question. ## Building the “knowledge graph” The output of pre-processing isn't a bigger pile of searchable text. It's a knowledge graph: a structured map of how every document and data point on a project relates to every other, rather than a flat list or index. This submittal references this spec section and is amended by this RFI. This drawing detail is connected to this schedule line and appears on these two other sheets. This change order impacts all of these documents. Nothing on a construction project exists in isolation, and a knowledge graph lets a system reason the way an experienced superintendent already does, by holding the whole project in a connected project “brain.” ## What it costs you to skip this step Without pre-processing, an AI system has two options, and both don’t work for construction teams: guess from a narrow slice of context and miss the connections that matter, or re-read the relevant documents from scratch on every question or agent run. Both depend on a human remembering every relevant document for a given task or question, but when a project document set numbers in the tens or hundreds of thousands, this is an unrealistic expectation. Ultimately, neither option is reliable, and neither is cheap. The cost problem compounds. Comparing an approach that reprocesses full documents on every call against one that reasons over a pre-built knowledge graph, the gap on common tasks is stark: drafting an RFI takes roughly 90,000 tokens versus 11,000, about 8 times more. Reviewing a submittal against a spec runs about 250,000 tokens versus 29,000, roughly 9 times more. That gap doesn't shrink as a project goes on; it grows, because document volume only increases as the project progresses. The reliability problem is worse. Without a knowledge graph connecting documents together, a system can't catch cases where a spec section was tagged wrong, a newly issued RFI response updates the owner’s design intent, or a detail buried in a drawing set contradicts the written spec. It can only tell you what one document says, not whether that's still true once every other document on the job is accounted for. ## What it makes possible This is why pre-processing matters more than any single feature. In Trunk Tools platform data, TrunkSubmittal, a submittal review agent, corrects the spec section already assigned in the project management system in roughly 30% of submittals, because the knowledge graph has already connected these data points and can identify human error. The alternative is that 30% of reviewed submittals are missing critical context and will surface as a rejected submittal or a field conflict weeks later. It's also why TrunkRFI, an RFI drafting and response analysis agent, can trace the downstream impact of an RFI response across every drawing, spec section, and schedule item it touches, and why TrunkBrowse lets you click any object in your drawings and see its full context: the schedule row, the spec section, and every RFI and submittal connected to it, instantly. None of this works backward. A knowledge graph can't be bolted onto an AI system after the fact any more than preconstruction can be retrofitted into a building already framed. It has to happen first, on every project, before a single agent handles a task or a user asks a question. That's the trade Trunk Tools made: harder work up front, so the work that happens in our platform allows builders to offload the document processing and get back to building. --- ## /blog/product-deep-dive-schedule-lookahead-agent-connecting-the-dots-in-construction-scheduling/ ### Product Deep-Dive: Schedule Agent – Connecting the Dots in Construction Scheduling > The Schedule Agent is an innovative tool designed by Trunk Tools to tackle the complexities of managing construction scheduling with software like P6 Primavera. #### **What is the Schedule Agent?** The Schedule Agent is an innovative tool designed by Trunk Tools to tackle the complexities of managing construction scheduling with software like P6 Primavera. It serves as a bridge between the schedule and essential project documents, offering a streamlined approach to managing construction timelines and information flow. This agent is in Beta, with external parties just beginning to use and test its functionalities. ## 3 Pain Points Solved by TrunkSchedule **P6 Primavera Compatibility** **Pain Point #1:** P6 Primavera, the “go-to” scheduling tool for major construction sites, is notorious for its difficulty in integrating with other file formats. Its rigid structure often results in isolated schedules that don’t communicate with other project documents. **Solution #1:** The Schedule Agent connects P6 schedules with crucial documents like submittals, RFIs, and invoices, creating a unified platform where all related information is accessible. This integration eliminates the need for manual cross-referencing, significantly reducing errors and inefficiencies. **Complexity and Cost of Updating P6 Schedules** **Pain Point #2:** Updating a P6 schedule requires specialized training and a user license, which often requires project teams to rely on less efficient workarounds, such as Excel. These methods are time-consuming, short sighted and prone to mistakes. **Solution #2:** With the Schedule Agent, any team member with access to Trunk Text can create look-ahead schedules directly from the Project Schedule without needing a P6 license. The tool’s intuitive interface requires minimal training, similar to performing a simple Google search, democratizing access to critical schedule data. **Challenges for Non-Licensed P6 Users** **Pain Point #3:** For those without a P6 license, schedules are often printed out on dozens of pages, making it difficult to visually link activities spread over several sheets. This lack of clarity can lead to missed deadlines and uncoordinated efforts. **Solution #3:** The Schedule Agent generates look-ahead schedules that can be easily downloaded in .CSV format. This feature allows non-licensed users to interact with the schedule data in a more manageable and actionable way, improving overall project coordination and communication. ### **Functionality and Maturity Stage** The Schedule Agent is currently in the early stages of external testing. It is a proactive tool that runs on a user established cadence or when enabled by the user. This agent monitors the schedule to notify users of upcoming activities and potential risks due to missed tasks in relation to other project documents, i.e. overdue Submittals. By providing these timely alerts, the agent functions as a critical risk management tool, helping teams stay on track. ### **Why Did We Build the Schedule Agent?** The decision to develop this agent stemmed from the recognition that there was no structured data connection between activities in the schedule and relevant documents. Traditionally, the “when” and “what” in construction schedules have been disconnected, leading to inefficiencies and miscommunications. The Schedule Agent is the first tool to create this connection, allowing project teams to compile all relevant documents and link them directly to the schedule. This innovation not only saves time but also ensures that everyone involved in the project has access to the most up-to-date information. ### **How It Works: Bridging the Gap Between Schedules and Documents** The Schedule Agent operates by running a prompt that finds and establishes relationships between activities in the schedule and corresponding documents. When a user clicks on "Compile All Docs," the agent identifies all documents related to the schedule and makes them available in the context of the conversation. This is a groundbreaking development in construction scheduling, as it brings together two previously disconnected aspects of project management. ### **The Impact on Construction Projects** The Schedule Agent is set to revolutionize how construction projects are managed. By automating the process of linking schedules with relevant documents, it not only saves time but also reduces the risk of errors and missed deadlines. This tool empowers project teams to make more informed decisions, ultimately leading to smoother project execution and successful outcomes. In an industry where time is money, the Schedule Agent offers a significant advantage by keeping projects on track and ensuring that all team members have access to the critical information they need. ### **Ready to start saving hundreds of hours every year?** [TALK TO SALES](http://www.trunk-tools.test/#request-demo) --- ## /blog/product-deep-dive-trunkdetect-submittal-review/ ### Product Deep-Dive: TrunkSubmittal, Automated Submittal Review Built for Efficiency > Explore TrunkSubmittal, an automated submittal review solution built for construction teams. Quickly identify discrepancies, reduce errors, streamline workflows, and ensure projects stay on time and within budget. [TrunkSubmittal](https://detect.trunktools.com/) intelligently automates the submittal review process by identifying discrepancies between submittals and project specifications, clearly highlighting potential issues, and keeping construction teams on schedule and within budget. We’re excited to equip project teams with powerful tools that streamline workflows, reduce errors, and enhance overall project outcomes. **What does it mean to be "Built for Efficiency"?**  Trunk Tools [was founded to directly address common yet significant challenges](/about/) faced by construction project teams—particularly around documentation accuracy and administrative efficiency. Our previous [products](/platform/), such as [TrunkSchedule](/blog/product-deep-dive-schedule-lookahead-agent-connecting-the-dots-in-construction-scheduling/) and [TrunkText](/blog/product-deep-dive-trunktext-ai-built-for-the-field/), were built to solve critical field-specific problems, increasing productivity and enabling more effective management. With TrunkSubmittal, we continue this tradition, targeting the complex and often problematic submittal review process. ![](/content/blog/media/TrunkDetect-Compliance-Table-Mobile-1.png) ## 3 Key Challenges Solved by TrunkSubmittal ![](/content/blog/media/TrunkDetect-All-Submittal-Reviews-Table-Desktop-1024x728.png) **Challenge #1:** Project Engineers and Coordinators spend significant time manually reviewing detailed submittals, making the process tedious, error-prone, and slow. **Solution #1:** TrunkSubmittal automatically checks each submittal against your specifications and scans the project for RFI's, identifying discrepancies quickly and accurately. It categorizes issues clearly, enabling reviewers to address compliance concerns immediately rather than sifting through lengthy documentation. **Challenge #2:** Project Managers often forward submittals without thorough review, increasing risk and potentially causing costly delays and rework. **Solution #2:** TrunkSubmittal elevates the quality and accuracy of every submittal. By identifying noncompliant materials, missing information, and deviations upfront, reviews become more meaningful, approvals happen faster, and fewer RFIs arise during later project stages. ![](/content/blog/media/TrunkDetect-Compliance-Table-Desktop-768x546.png) **Challenge #3:** Operations Managers face inconsistent and varying review processes across different projects, complicating training and standardization. **Solution #3:** TrunkSubmittal standardizes and streamlines the review process across projects, adapting seamlessly to each project's unique requirements. This consistent approach makes it easier to onboard new engineers, maintain quality control, and ensure efficient operations across the organization. ## How TrunkSubmittal Works **TrunkSubmittal simplifies the review process into five clear stages: ** 1. **Intake** – Automatically identifies and matches new submittals with relevant specification documents. 2. **Alignment** – Reviews each submittal against exact requirements extracted directly from your project specifications. 3. **Analysis** – Clearly flags and categorizes discrepancies, highlighting missing data, deviations, or unapproved selections. 4. **Recommendation** – Provides concise summaries of discrepancies and suggested next steps, streamlining decision-making. 5. **Action** – Facilitates immediate resolution, including generating revision requests, routing unresolved items for further analysis, and instant re-analysis upon resubmission. ## Real-world Use Cases of TrunkSubmittal **TrunkSubmittal significantly enhances several critical project activities, including: ** * **Catching** noncompliant product details before costly design reviews * **Flagging** incomplete submittals lacking warranties or performance criteria * **Comparing** alternate materials and ensuring compliance with specified standards * **Generating** guided checklists for subcontractors to improve initial submission quality * **Streamlining** the handoff process between reviewers and design teams TrunkSubmittal is AI built for efficiency: it leverages intelligent automation to revolutionize submittal reviews, allowing construction teams to refocus their efforts on strategic decision-making, reducing errors, accelerating project timelines, and confidently building for the future. ### **Ready to experience TrunkSubmittal? Schedule your demo today and start reviewing smarter, not harder.** [REQUEST A DEMO](https://detect.trunktools.com/) --- ## /blog/product-deep-dive-trunktext-ai-built-for-the-field/ ### Product Deep-Dive: TrunkText, AI Built for the Field > TrunkText leverages artificial intelligence to help construction professionals instantly get answers and find relevant documents. [**TrunkText**](/tools/trunktext/) is AI built for the field: it’s accessible on the construction site via SMS, understands the nuances of construction-specific documentation, and gives you answers along with relevant source documents. We’re excited to put the power of artificial intelligence in the pockets of tradespeople everywhere, enabling them to keep building for the future. **What does it mean to be "Built for the Field"?**  Trunk Tools was founded by Dr. Sarah Buchner, who worked as a construction site and project manager – seeing firsthand the challenges that tradespeople face. From its inception, Trunk Tools has built products specifically for the boots on the ground, solving their biggest pain points. TrunkPerform, Trunk Tools’ first product, aims to put more money in the pockets of each construction worker, aligning incentives across the organization. With our newest product, [TrunkText](/tools/trunktext/), we aim to solve a few crucial pain points that, if solved, will unlock new levels of productivity and quality in the built environment. ![](/content/blog/media/Mobile-Ask-Questions-2.png) ## 3 Pain Points Solved by TrunkText ![](/content/blog/media/image.png) **Pain Point #1:**  When in the field, workers need answers to their questions quickly, and walking back to their trailers to dig up information slows down productivity. Most construction software is designed for the desktop solution and can be inconvenient or unnecessarily time-consuming. **Solution #1:** TrunkText was built to maximize access, without compromising efficacy. You can text your project site's specific phone number from any SMS device, receiving answers (with sources) directly to the palm of your hand, in seconds. Although mobile and web app experiences are also available, SMS access alone is enough to experience the power of AI through TrunkText. **Pain Point #2:** Construction documents (submittals, change orders, RFIs, drawings) have specific nuances and uses that are difficult to understand without years of industry experience. Generic AI tools like ChatGPT lack construction expertise and, more importantly, the context from your specific project. **Solution #2:** TrunkText is an AI solution that is built atop your project's specific repository of data. Because our engineers are constantly collaborating with our construction industry advisors, TrunkText "reads" your RFIs, submittals, change orders, schedules, etc. from the perspective of an experienced project manager. ![](/content/blog/media/Ultimate-Parsing-Engine-768x712.png) _This diagram shows how a resume parser "reads" a resume to "learn" important information. TrunkText "reads" construction documents in this way._ ![](/content/blog/media/image-282x300.png) _click on the source hyperlink ->_ #### LHS\_Schematic\_Design\_Drawings.pdf ![](/content/blog/media/Screenshot-2023-11-21-at-2.47.20-PM-1024x414.png) **TrunkText highlights the answer to your question, on the source document** **Pain Point #3:** On a construction site, finding the right information in the right document at the right time is difficult. So much rework happens because someone acted upon information that was out-of-date or from the wrong document. **Solution #3:** TrunkText accompanies every answer with the relevant source documents, highlighting where the answer was found. You can verify and know exactly where the answer comes from, with important context. TrunkText is AI built for the field: it’s accessible on the construction site via SMS, it understands the nuances of construction-specific documentation, and it gives you answers along with relevant source documents. We’re excited to put the power of artificial intelligence in the pockets of tradespeople everywhere, enabling them to keep building for the future.  ### **Ready to start saving hundreds of hours every year?** [GET STARTED](/tools/trunktext/#get-started-above) --- ## /blog/setting-up-an-effective-construction-safety-incentive-program/ ### Setting Up An Effective Construction Safety Incentive Program > Safety incentive programs in construction are often well-intentioned, aiming to reduce accidents and improve overall safety. Safety incentive programs in construction are often well-intentioned, aiming to reduce accidents and improve overall safety. Experts are divided – can you properly implement them and achieve the desired increases in safety compliance, or are you more likely to do harm than good? The devil is in the details. Today, we’ll cover the best ways to structure a safety program to protect your people. ## OSHA Guidelines for Safety Incentive Programs OSHA guidelines aim to ensure that such programs promote a safe and healthy work environment without leading to underreporting or misreporting of injuries and illnesses. OSHA published final clarification around safety incentive programs in 2018 with a memorandum regarding guidance in [29 C.F.R. § 1904.35(b)(1)(iv)](https://www.whistleblowers.gov/memo/2018-10-11) documentation. ### **What Safety Incentive Programs Can Include:** 1\. **Positive Reinforcement:** OSHA supports programs that encourage safe work practices and compliance with safety rules. This can include rewards for employees who follow safety protocols, participate in safety training sessions, or identify and report hazards. 2\. **Reporting Leading Indicators:** Incentives can be based on leading indicators like safety audits, safety meetings attendance, employee safety suggestions, and near-miss reporting, rather than just lagging indicators like injury rates. 3\. **Team-Based Rewards:** Programs can include team-based incentives to promote a collaborative approach to safety, where all team members work together to maintain a safe working environment. ### **What Safety Incentive Programs Should Not Do:** **1\. Discourage Reporting:** Programs must not discourage workers from reporting injuries, illnesses, or unsafe conditions. Any incentive plan that penalizes employees for reporting is not compliant with OSHA’s regulations. **2\. Solely Focus on Injury Rates:** Programs should not solely reward employees based on low injury rates. This can create a disincentive for employees to report incidents, leading to underreporting and a false sense of workplace safety. ## ❌ Key Pitfalls in Setting Up a Safety Incentive Program **1\.** **Superficial Motivation:** Rewards can create a superficial motivation for safety. They may encourage compliance in the short term, but they don't necessarily promote a deep, lasting commitment to safety practices. They must be clearly linked as a reinforcement mechanism for fostering a culture of safety **2\.** **Delayed Recognition:** Annual or quarterly events, while celebratory, delay recognition. Immediate feedback is crucial in reinforcing safe behavior, and long intervals between behavior and reward can diminish the impact of the incentive. Programs should publicly recognize safety as immediately as possible. **3\.** **Generic Rewards:** Generic rewards may not resonate with all employees. Personalization of rewards can be more effective in motivating a diverse workforce. Gift Cards, branded items, and others are typically less desirable, and less effective, than cash for immediate rewards. Personalized rewards are more valuable when the timing allows for such touches. **4\.** **Lack of Focus on Behavior Change:** Many programs focus on rewarding the absence of accidents rather than actively promoting safe behaviors. This can lead to a passive approach to safety, where avoiding incidents is prioritized over actively engaging in safe practices. Incentive activities such as compliance, reporting, and injury prevention. **5\.** **Creating the Wrong Incentives:** Programs that reward low incident rates can inadvertently incentivize under-reporting. Workers might not report minor incidents or near-misses to ensure the team qualifies for rewards, leading to a culture where safety issues are hidden rather than addressed. ## ✅ Incentive Program Best Practices Safety programs are most effective when they are easy to implement, easy to communicate, structured and transparent.  Using a simple, digital system is often easier and less laborious for management personnel than analog systems.  Platforms like **TrunkPerform** by Trunk Tools are a great way to plug and play safety programs on your job-sites. Best practices include: **1\. Rewarding Positive Behaviors:** Shift the focus from penalizing or rewarding based on incident rates to acknowledging positive safety behaviors. This can include reporting hazards, participating in safety training, or proactive safety measures. Prevention, unsafe conditions reports, reporting near misses, and reporting accidents are all examples of behaviors to reward. **2\. Encourage Reporting:** Create an environment where reporting safety issues is encouraged and rewarded. This ensures a more accurate understanding of the safety landscape and opportunities for improvement. Communication should be frequent and across multiple means. It should be a consistent message verbally, digitally, and behaviorally. TrunkPerform helps to align communication behaviors to your employees using its digital platform. **3\. Transparent Communication:** Maintain transparent communication about the purpose and mechanics of the safety incentive program. Ensure that employees understand that the goal is to improve safety, not just to reduce reported incidents. **4\. Regular Review and Adaptation:** Continuously review the effectiveness of the program and be willing to make changes. This may include seeking feedback from employees on what types of incentives and recognitions are most meaningful to them. Monitoring safety dashboards, reviewing reports, and evaluating trends are easy in digital programs, such as TrunkPerform. Implementing a digital safety incentive program with TrunkPerform could help your company foster a culture of safety through modern, engaging methods. It can be challenging to set up a program, identify behaviors to reward, and communicate to employees. By using a digital platform that encourages consistent and active participation in safety practices, one can make compliance both rewarding and easy to track. A safety incentive program that aligns with OSHA guidelines and focuses on positive reinforcement not only enhances workplace safety but also boosts employee morale and productivity, making it an ideal choice for forward-thinking companies. [Request a Demo](/#demo) --- ## /blog/streamlining-pipeline-construction-with-trunk-tools-a-conversation-with-jamie-pm-charps/ ### Streamlining Pipeline Construction with Trunk Tools: A Conversation with Jamie (Charps Project Manager) > In the fast-paced world of pipeline construction, efficiency and accuracy are key. We sat down with Jamie, a Project Manager at Charps, to discuss how Trunk Tools has become an indispensable part of his daily workflow, helping him manage the complexities of his projects with greater ease and precision. In the fast-paced world of pipeline construction, efficiency and accuracy are key. We sat down with **[Jamie](https://www.linkedin.com/in/jamie-grover-abb7542b/)**, a Project Manager at Charps, to discuss how [Trunk Tools](/customers/) has become an indispensable part of his daily workflow, helping him manage the complexities of his projects with greater ease and precision. **Q: Jamie, can you tell us about your role at Charps and what your day-to-day responsibilities look like?** **Jamie:** As a Project Manager at Charps, my main responsibility is to estimate and manage pipeline construction jobs. This involves a variety of tasks including managing schedules and costs, organizing subcontractors, and ensuring client expectations are met. On a typical day, I’m bidding for jobs while also running multiple projects. This means I’m constantly approving crew and equipment costs, managing RFI (Request for Information) and Change Order requests, coordinating subcontractors, and updating key performance indicators (KPIs) and schedules. It’s a lot to juggle, but it’s all part of ensuring our projects run smoothly. **Q: What are some of the biggest challenges you face in your role?** **Jamie:** The biggest challenge is ensuring compliance with our customer specifications. We work with several different pipeline operators, each with their own set of specifications, which can vary widely. Keeping track of these and ensuring our work aligns with them is crucial, but it can also be incredibly time-consuming.   ![](/content/blog/media/Jamie-Headshot.jpg) **Q: How has Trunk Tools helped you tackle these challenges?** Jamie: Trunk Tools has been a game-changer for us. I use it almost daily to look up specifications, which is crucial when you’re dealing with different client requirements. It’s also incredibly useful for challenging inspectors on site or clarifying points raised by Project Managers or Construction Coordinators during meetings. With Trunk Tools, I can get accurate answers quickly, which keeps our crews moving forward and ensures we’re always in compliance. **Q: Can you share a specific example of how Trunk Tools has saved you time or money?** Jamie: Absolutely. Recently, we had an issue where the drawings for a new Block Valve we were installing didn’t include rest blocks or thrust blocks. The engineer simply told us to follow the specification, but finding the relevant information in the customer’s database would have been a nightmare—it has a poor search function and doesn’t return results unless you have the exact language. Before Trunk Tools, this would have taken me at least two hours of searching. But with Trunk Tools, I found the specification in seconds, got the materials ordered, and kept the crew moving forward. Over three months, I’ve saved nearly three full workdays thanks to Trunk Tools. That’s also saved our crew time on site, preventing delays and potential rework. **Q: How was the process of implementing Trunk Tools into your workflow?** Jamie: The implementation was very smooth. Kevin and the team made it easy for us to get started. They set everything up, demonstrated how to use the tool, and ensured we were comfortable with it before we went live. The transition from demonstration to actual use was seamless. **Q: Looking ahead, what are your hopes for the construction industry, particularly regarding technology?** Jamie: With all the new technology emerging, I hope the construction industry will be more open to implementing these innovations. There’s often resistance to change, with people saying, “this is how we’ve always done it,” which is one of my biggest pet peeves. I’d also like to see customers start using tools like Trunk Tools, not just contractors. It would help them manage their specifications better, answer RFI’s more efficiently, and ensure compliance during plan reviews. My biggest hope is that technology like this will continue to free up time for Project Managers, Foremen, and Superintendents, allowing them to focus on doing their jobs correctly, efficiently, and safely. \--- Jamie’s experience with Trunk Tools highlights the platform’s impact on streamlining workflows, reducing time spent on compliance and improving overall project efficiency. As technology continues to evolve, AI tools like Trunk Tools are paving the way for a more efficient and effective construction industry. [LEARN More About Trunk tools](http://www.trunk-tools.test/#request-demo) [LEARN More About Charps](https://www.charps.com/) --- ## /blog/suffolk-inks-enterprise-agreement-trunk-tools-ai-partnership/ ### Suffolk Inks Enterprise Agreement with Trunk Tools, Cementing AI Partnership > Suffolk signs an enterprise agreement with Trunk Tools, deploying AI agents to 1,500+ field users nationwide to streamline construction workflows and jobsite decision-making. [Suffolk](https://suffolk.com/), one of the most innovative construction enterprises in the country, has selected [Trunk Tools](https://trunktools.com/) as an enterprise AI partner — deploying the platform and agents across more than [1,500+ field users nationwide](https://trunktools.com/resources/). For both companies, this agreement is less a starting line than a milestone: the result of a relationship years in the making, and a shared conviction that AI belongs at the center of how leading contractors operate. ## **From Accelerator to Enterprise Partner** The story starts in 2023, when [Trunk Tools was selected for BOOST](/newsroom/trunk-tools-featured-in-businesswire/) — Suffolk Technologies' flagship accelerator program and the #1-ranked AEC accelerator in the industry. Designed to connect high-growth construction tech startups with the real-world access and validation needed to scale, BOOST put Trunk Tools in front of the people who build for a living — and proved the technology could solve problems that field teams face every day. Suffolk's operating teams took notice. The company brought Trunk Tools on as a customer that same year, followed by a structured pilot and then scaled adoption across active jobsites. Now: an enterprise agreement that extends Trunk Tools across multiple regions and sectors. What began in an accelerator cohort has become a significant   commitment in the continued investment in the future of AI in construction. ## **Choosing the Right AI Partner** Suffolk has been intentional about how it adopts technology — focused not on chasing innovation for its own sake, but on identifying where AI can tangibly change how teams operate in the field. The problem it needed to solve was clear: as projects grow in scale and complexity, the volume of documentation teams must manage — drawings, RFIs, submittals, bulletins, contracts — has outpaced the teams responsible for navigating it. Trunk Tools addresses this directly. Rather than spending hours manually searching for answers buried across thousands of pages of project documents, Suffolk teams can now instantly surface RFI histories, review submittals, analyze bulletin and drawing revisions, clarify scope, and get critical information in the field — in seconds. The result is less time chasing paperwork and more time focused on building. This commitment to innovation is rooted in a long-term strategic vision. "Ten years ago, we made a bold decision to invest heavily in technology and data because we believed it would transform how we build. Today, that foundation allows Suffolk to harness AI to solve real challenges on our jobsites, improving safety, reducing risk and delivering greater value to our clients," said John Fish, Suffolk Chairman and CEO. "Our long-term vision is now driving real-world results." ## **Proven in the Field** The confidence behind this agreement is grounded in what Suffolk teams have already experienced. Field leaders across active projects have seen firsthand how quickly Trunk Tools changes the pace and quality of daily work — getting answers that once required hours of digging, and redirecting that time to the real challenges on the jobsite. "Generative and agentic AI can radically simplify the way our teams interact with the increasingly complex document management aspect of construction management, allowing them to refocus their time on building," said Jit Kee Chin, Chief Technology Officer at Suffolk. "Partnering with Trunk Tools allows us to accelerate this journey." The impact compounds across a team. As [Senior Project Manager Chris Force](/customers/video-interview-in-the-field-with-suffolk-chris-force-sr-project-manager/) put it: "The collection of those small time savings... probably saves days or weeks — and that's just one person. Apply that to a 20-person team and you're saving man-months of time. That's time now spent in the field dealing with real problems." Project Manager Vanessa Kennedy framed it simply: "It's not making us dumber — it's just helping us with the busy work so that we can focus more on resolving the other issues." On the ground, the reaction has been equally clear. After putting the platform to use on-site, [Superintendent Andrew Bared](/customers/video-interview-in-the-field-with-suffolk-andrew-bared-superintendent/) said it best: "Why isn't every job using this?" ## **A Partnership Built to Scale** For Trunk Tools, this enterprise agreement with Suffolk represents a defining moment in its mission to let builders build. "This partnership proves that AI is delivering real, measurable value on construction jobsites — not as an experiment, but as an essential part of how leading contractors operate," said [Dr. Sarah Buchner, Founder and CEO of Trunk Tools](/about/). "Suffolk's commitment to operational excellence and innovation aligns perfectly with our mission to empower field teams with cutting-edge technology that streamlines workflows and drives efficiency. We're just getting started." Trunk Tools continues to expand its [suite of AI agents](/platform/) purpose-built for construction — helping teams turn complexity into clarity. For Suffolk, committing to this rollout isn't the conclusion of an evaluation. It's the foundation for embedding AI into how they build. [Request a Demo of Trunk Tools](http://www.trunktools.com/#request-demo) --- ## /blog/system-of-action-vs-system-of-record/ ### The dots your system of record was never going to connect > A construction system of record stores documents. A system of action connects them so teams can review, price, and act on change. Here's what that gap costs. ## What the system of record was designed to do The system of record did exactly what it was designed to do. It gave the industry one place to put things, then distributed that data outward to tools that each solved a specific, siloed problem. A tool for takeoff. A tool for scheduling. A tool for submittal logs. Each competent inside its own boundary. What none of them do is connect to each other. That job goes to the people managing the job. And it's the full view, not the individual document, that lets you draw the lines that lead to the right decision. A spec section governs a submittal. An RFI response amends that spec. A revision quietly contradicts an answer the design team gave two months ago. Those relationships are where the risk lives, and no single tool in the stack can see them, because each one only holds its own slice. Dodge Construction Network's 2026 study with CMiC found that [only 6% of contractors have a fully connected project controls environment, and just 41% can identify a potential overrun while it's still manageable on at least half their projects](https://www.globenewswire.com/news-release/2026/08/05/3339530/0/en/most-u-s-contractors-still-struggle-to-catch-cost-overruns-in-time-new-study-finds.html). A separate Dodge study of capital project owners put it more memorably: organizations are, in the words of research director Dr. Donna Laquidara-Carr, ["operating in silos of excellence, rather than fully integrating their data, and that puts a ceiling on the benefits they can expect."](https://www.businesswire.com/news/home/20260602410646/en/New-Research-Reveals-Major-Gap-in-Digital-Maturity-Among-Capital-Construction-Owners) Silos of excellence. That's the point-solution era described precisely. Every tool good at its job, the project still blind between them, while [95.5% of the data captured in the industry goes unused](https://www.autodesk.com/blogs/construction/construction-insights-data/). The record isn't the problem. The record is good at being a record. The problem is that we kept adding tools on top of it and kept leaving the hardest work, the connecting, to the person with the least time to do it. ## What a system of action does with a single bulletin Here's the difference a fully integrated system can make compared to a set of disjointed tools. The project below is illustrative, but every step is a real capability running today. Bulletin 4 lands. It revises **135 sheets across six disciplines**: 86 Interior Design, 18 Technology, 13 Plumbing, nine Electrical, eight Architectural, one General. Under the old paradigm this is the beginning of a week. **Read the change and write it down.** Three days after issue, the bulletin has a narrative. Not a diff, an explanation: guestroom finishes, casework, and device layouts reworked across unit types, and the enlarged unit plumbing plans picking up new cleanouts, floor drains, and fixture tags. One line matters more than the rest, and it's the one a reviewer under deadline is most likely to miss: *the added plumbing scope in the enlarged unit gravity plans is not reflected in the current contract documents and may carry cost impact.* **Localize it.** Sheet P-402 holds the enlarged unit gravity plans. Comparing Bulletin 4 against the 100% CD set surfaces 11 change areas. In Unit KDA alone: a revision cloud with a note and tag, a floor drain (FD-1) added inside a cloud, a cleanout added to a 4" SS pipe with a "WC-1" tag added to the toilet, and a double swing door removed with its wall opening. Four changes, one unit, one sheet, out of 135. **Check it against the rest of the project.** Click WC-1 and spec section 224000, Plumbing Fixtures, opens beside it. This is where a change stops being a drawing edit and becomes a scope question. The linked documents tell you whether it's inside your contract or outside it. **Decide whether the question is worth asking.** Before drafting an [RFI](/blog/what-is-an-rfi-in-construction/), the system reads P-402 against spec 224000, the P-601 fixture schedule, and the interior design finish schedule, then checks the existing RFI log. Its finding: the revision adds the cleanout without a type callout, neither the spec nor the fixture schedule designates floor versus wall there, and ID-003 still shows LVT in the area with no access panel called out. No existing RFI covers the scope. The question is genuinely unanswered, so draft it. The same reasoning that produces a good RFI is what prevents a bad one; an agent that can only draft will draft everything. **Price it.** The change event carries a rough order of magnitude: **~$205,000**, working range $140K to $270K, broken out by who bears it. Finishes and casework ~$105K across the 86 Interior Design sheets. Plumbing rough-in ~$40K. Electrical and technology ~$25K for device coordination. GC and architectural coordination ~$35K. From there it drafts as a potential change order, line by line, per subcontractor, labeled *AI-generated, verify before submitting*. The team still makes the call. What's gone is the three days of tracing required to make it. Count the systems that would have had to talk to each other for that to happen in a point-solution world: [drawing comparison](/tools/trunkreview/), [spec retrieval](/tools/trunkbrowse/), [RFI log](/tools/trunkrfi/), [cost estimation](/tools/trunkchange/), [change management](/tools/trunkchange/). Five tools, five exports, five chances to drop the thread. And none of them could have produced the $205,000 on its own, because that number is a function of relationships living outside every individual document. ## Every system of action runs on a knowledge graph This is the difference between a platform and a bundle. A system of action cannot act on documents. It acts on a model of how documents relate. That model is a [knowledge graph](/blog/pre-processing-is-preconstruction/), and building it is the actual work. Every Trunk Tools project begins there: we read the construction documents and build the graph before any agent runs. Underneath it sits a construction ontology, a structured definition of what a submittal, a spec section, an RFI, a drawing detail, and a schedule activity each are, and how they depend on one another. That's what [Cortex](/platform/) is. Point solutions build knowledge graphs too. They just build shallow, private ones scoped to a single task, and throw them away at the boundary. Five AI point solutions means five partial models of the same project, none of which can see the others. That doesn't add up to a system of action. It adds up to five more places where context gets dropped. It's why the handoffs above are the product rather than a convenience: the RFI reasoning knew which change it was responding to because the review had already characterized it, and the change event carried per-trade pricing because the graph knew which trades touched which sheets. ## How construction tech sprawl fails, in order Tech sprawl doesn't fail all at once. It starts with slower detection, because nothing is watching the relationships between systems. That pushes teams back onto manual review and hallway communication. Then the value stops being visible to the people on site, who are doing the same work they always did plus logging into another tool. Trust erodes. Software nobody trusts becomes shelfware. That last stage is where most AI pilots in construction quietly end. Not with a failed evaluation. With an unused license. ## The question to take into your next vendor conversation Most AI evaluations in construction ask what a tool can do. That's the wrong question, because the answer is always impressive and always narrow. Ask instead: **what does this system know about how my project documents relate to each other, and where did that knowledge come from?** If the answer is a general-purpose model with a good prompt, you're buying a point solution with better marketing. If the answer is a knowledge graph built from your documents, on an ontology that knows what a submittal is, you're buying something that can act. That's the same test as the [questions worth asking any construction AI vendor](/guides/ai-vendor-questionnaire/) before you buy. Point solutions solved one problem each, and solved them well enough for the projects we were building a decade ago. They are antiquated for the realities of the modern jobsite. The volume is bigger, the documents are more connected, and the people who used to hold the lines together are leaving faster than they can be replaced. Somebody still has to connect the dots. The only question is whether it's your project team, at 9pm, from memory. ## Frequently asked questions **What is a system of action in construction?** A system of action is software that acts on how project documents relate — drawings, specs, RFIs, schedules, and change — rather than only storing them. It runs on a knowledge graph of those relationships, so a bulletin review, an RFI draft, and a cost estimate can share context instead of being handed off between disconnected tools. **What's the difference between a system of record and a system of action?** A system of record is the project management or document platform that stores files and distributes them to other tools. A system of action sits on top of that record, connects the documents to each other, and completes work across those connections. The record is necessary. It is not sufficient for reviewing, pricing, or deciding on change. **Why don't construction point solutions add up to a system of action?** Each point solution builds a shallow, private model of one workflow and drops context at the boundary. Five AI tools on the same project produce five partial pictures, none of which can see the others. Connecting those pictures remains the job of the project team. **What is a construction knowledge graph?** A construction knowledge graph is a structured map of how project documents depend on one another: this spec section governs that submittal, this RFI amends that spec, this detail appears on these sheets. Trunk Tools builds that graph from the documents on every project, on a construction ontology, before any agent runs. That graph is [Cortex](/platform/). **How should contractors evaluate construction AI vendors?** Ask what the system knows about how your project documents relate to each other, and where that knowledge came from. If the answer is a general-purpose model with a good prompt, you are buying a point solution. If the answer is a knowledge graph built from your documents on an ontology that knows what a submittal is, you are buying something that can act. --- *By the Trunk Tools team. Last updated September 11, 2026.* *Sources: Dodge Construction Network / CMiC, [Most U.S. Contractors Still Struggle to Catch Cost Overruns in Time](https://www.globenewswire.com/news-release/2026/08/05/3339530/0/en/most-u-s-contractors-still-struggle-to-catch-cost-overruns-in-time-new-study-finds.html) (2026); Dodge Construction Network, [New Research Reveals Major Gap in Digital Maturity Among Capital Construction Owners](https://www.businesswire.com/news/home/20260602410646/en/New-Research-Reveals-Major-Gap-in-Digital-Maturity-Among-Capital-Construction-Owners) (2026); Autodesk, [Construction Insights: Data](https://www.autodesk.com/blogs/construction/construction-insights-data/).* ### Frequently asked questions #### What is a system of action in construction? A system of action is software that acts on how project documents relate — drawings, specs, RFIs, schedules, and change — rather than only storing them. It runs on a knowledge graph of those relationships, so a bulletin review, an RFI draft, and a cost estimate can share context instead of being handed off between disconnected tools. #### What's the difference between a system of record and a system of action? A system of record is the project management or document platform that stores files and distributes them to other tools. A system of action sits on top of that record, connects the documents to each other, and completes work across those connections. The record is necessary. It is not sufficient for reviewing, pricing, or deciding on change. #### Why don't construction point solutions add up to a system of action? Each point solution builds a shallow, private model of one workflow and drops context at the boundary. Five AI tools on the same project produce five partial pictures, none of which can see the others. Connecting those pictures remains the job of the project team. #### What is a construction knowledge graph? A construction knowledge graph is a structured map of how project documents depend on one another: this spec section governs that submittal, this RFI amends that spec, this detail appears on these sheets. Trunk Tools builds that graph from the documents on every project, on a construction ontology, before any agent runs. That graph is Cortex. #### How should contractors evaluate construction AI vendors? Ask what the system knows about how your project documents relate to each other, and where that knowledge came from. If the answer is a general-purpose model with a good prompt, you are buying a point solution. If the answer is a knowledge graph built from your documents on an ontology that knows what a submittal is, you are buying something that can act. --- ## /blog/the-verticalization-of-ai-how-ai-is-revolutionizing-industries-with-tailored-solutions/ ### The Verticalization of AI: How AI is Revolutionizing Industries with Tailored Solutions > In Summer 2024, AI is advancing rapidly, with 65% of organizations adopting generative AI, expanding into new industries like marketing and sales. ## The State of AI in Summer 2024 In the summer of 2024, AI is experiencing significant advancements and widespread adoption across various industries. According to [McKinsey](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai), the key trends and developments include: 1. **Generative AI Adoption**: The adoption of generative AI has surged, with **65%** of organizations using these tools regularly, up from **33%** the previous year. This spike in usage is leading to noticeable improvements in cost savings and revenue growth. 2. **Expanded Use Cases**: AI applications are expanding beyond traditional domains into areas like marketing, sales, and product development. Companies are leveraging AI to enhance product features, optimize development cycles, and create new AI-driven products. 3. **Focus on Value Creation**: High-performing AI adopters prioritize creating new business opportunities and revenue streams over mere cost reduction. These organizations are integrating AI into multiple business functions and investing significantly in AI technologies to maintain a competitive edge. 4. **Risk Awareness**: As AI becomes more pervasive, organizations are increasingly aware of associated risks such as inaccuracy, cybersecurity threats, and intellectual property issues. Leading companies are adopting robust risk mitigation practices and MLOps (machine learning operations) to manage these challenges. 5. **AI-Driven Transformations**: AI is driving digital and operational transformations across industries. Companies are using AI to reimagine business models, improve customer experiences, and enhance operational efficiencies. These transformations are often supported by partnerships with leading technology firms and the development of proprietary AI assets. Artificial Intelligence (AI) is at a pivotal inflection point, akin to the dawn of the internet age. This new era of technology is set to be characterized by the application of AI across various layers, each serving a unique purpose in the ecosystem. Understanding these layers—foundational models, infrastructure, and applications—is key to grasping how AI is revolutionizing industries such as healthcare, finance, and construction. This article explores these layers, provides real-world examples, and delves into the specific benefits and challenges of vertical AI, with a spotlight on how [Trunk Tools](http://www.trunk-tools.test) is leading the charge in the construction industry. ## The Layers of AI To grasp how AI is revolutionizing industries, it's essential to understand its foundational layers: 1. **Foundational Models**: **Foundational models** are the commoditized, expensive AI models that form the backbone of AI capabilities. These include large-scale machine learning models trained on vast amounts of data, such as GPT-4o by OpenAI and Claude by Anthropic. These models offer generalized capabilities that can be adapted for various tasks. 2. **Infrastructure**: The **infrastructure layer** involves the systems and tools required to deploy and scale AI models. It includes cloud services, data management systems, and computing resources provided by platforms like AWS, Microsoft Azure, and Google Cloud. Efficient infrastructure is crucial for the scalability and performance of AI applications, ensuring they can handle large volumes of data and computation. 3. **Applications**: At the **application layer**, AI solutions are tailored to meet specific needs, either horizontally (across various industries) or vertically (tailored to specific industries). This layer is where AI's capabilities are realized, providing tangible benefits and driving innovation within specific contexts. ## Horizontal vs. Vertical AI * **Horizontal AI**: Solutions like [Glean](https://www.glean.com/), which offer document search capabilities across multiple domains, aim to provide broad utility. However, they often struggle to perform optimally in every use case due to their generalized nature. * **Vertical AI**: In contrast, vertical AI solutions are designed for specific industries, offering deeper integration and more specialized functionality. This approach creates a data moat, making these solutions harder to replicate and providing significant competitive advantages. ## The Benefits of Vertical AI Vertical AI brings tailored solutions to complex, data-rich industries. The benefits include: * **Industry-Specific Insights:** By focusing on a single industry, vertical AI can deliver more relevant and actionable insights for customers, helping them make better-informed decisions. * **Improved Efficiency:** Tailored AI applications streamline processes, leading to efficiency gains and reduced operational costs. * **Competitive Edge:** The specialization inherent in vertical AI creates a barrier to entry for competitors, ensuring sustained advantage for customers who adopt these solutions. ### Industry Applications of Vertical AI **Healthcare**: AI in healthcare is revolutionizing diagnostics, treatment planning, and patient care. For instance, AI algorithms analyze medical images to detect diseases with high accuracy, and personalized medicine uses patient data to tailor treatments. Companies like [PathAI](https://www.pathai.com/) and [Tempus](https://www.tempus.com/) are leading this change by developing AI systems that enhance diagnostic precision and patient outcomes. **Finance**: In the finance sector, AI enhances fraud detection, risk management, and customer service. Predictive analytics models forecast market trends, while chatbots provide personalized financial advice. Firms like [Rogo](http://www.rogodata.com) and [Zest AI](https://www.zest.ai/) are transforming financial services with AI-driven insights and automation tools. **Construction**: The construction industry is being transformed by AI. At [Trunk Tools](http://www.trunk-tools.test), our platform and AI agents augment your workflows using construction-specific models trained for your specific job site. ### Challenges of Vertical AI and Trunk Tools' Solution **Data Silos**: A major challenge in deploying AI is the existence of data silos. Trunk Tools tackles this by integrating with existing data sources, ensuring seamless data flow and utilization. **Scalability**: Scalability can be difficult due to the specialized nature of vertical AI. Trunk Tools' modular design allows for scalable solutions that can be tailored to varying project sizes and complexities. **Regulatory Compliance**: Ensuring compliance with industry-specific regulations is crucial. Trunk Tools incorporates compliance measures into its AI solutions, reducing the risk of legal issues and ensuring adherence to standards. You can read more about our approach to Trust & Safety at [trust.trunktools.com](http://trust.trunktools.com). ## The Future of AI is at the Application Level The future of AI lies in its application, especially in managing messy multimodal data sets that are information rich. Effective AI applications will need to tackle the communication and dissemination of information problem, empowering decision-makers with real-time insights. **Messy Multimodal Data Sets**: AI's ability to handle diverse data types (text, images, audio) will become increasingly important. This capability is crucial in industries like construction, where project data comes from multiple sources and formats. **Empowering Decision-Makers**: Real-time insights provided by AI applications can empower decision-makers to make informed choices quickly. This leads to enhanced efficiency, reduced errors, and improved project outcomes. **Quantifying this Trend**: The impact of AI in construction is measurable. For example, in a recent case study with an ENR top 25 company, the use of Trunk Tools resulted in: * 87%+, of 246 questions asked by 4 people in 37 working days, answered correctly * a 6.5x ROI from labor savings alone * a 40x combined ROI between labor savings and rework prevention * and a potential $100k+/month savings from potential rework if utilized from project inception. Trunk Tools' AI solutions showcase the tangible benefits of AI integration in the construction sector.  ### Looking Ahead The verticalization of AI represents the next leap in technological advancement, much like the transition to Web 1.0. By focusing on specific industries, vertical AI delivers unparalleled value through specialized applications. **Trunk Tools exemplifies this trend, leading the construction industry with innovative AI solutions that streamline processes and enhance productivity. As we continue to embrace AI, its tailored applications will drive efficiency and innovation across all sectors, paving the way for a smarter, more connected future.** For those eager to explore the future of AI in construction, we invite you to learn more about Trunk Tools' cutting-edge solutions through our website, at [www.trunktools.com](http://www.trunk-tools.test). The Verticalization of AI by Trunk Tools How Artificial Intelligence (AI) is Revolutionizing Industries with Tailored Solutions [Read on Substack](https://trunktools.substack.com/p/the-verticalization-of-ai) --- ## /blog/top-insights-trunk-tools-discovered-shadowing-a-large-boston-tenant-improvement-project/ ### Top Insights Trunk Tools Discovered Shadowing a Large Boston Tenant Improvement Project > Trunk Tools shadowed a large TI office project in downtown Boston, uncovering key pain points for construction superintendents, project managers, and engineers. Through 20+ hours of observation, we identified workflow challenges and areas for improvement. ### Trunk Tools spent 20+ hours shadowing a large construction site and here's what we learned: Trunk Tools spent 5 weeks shadowing a large tenant improvement (TI) office project in downtown Boston to find the biggest pain points for construction superintendents, project managers, and project engineers. Through 20+ hours of project shadowing, we gathered valuable insights including the breakdown of pain points and frustrations, challenges in different workflows, and areas for improvement. [Download the full report](/content/blog/media/Top-Insights-Trunk-Tools-Discovered-Shadowing-a-Large-Boston-TI-Project.pdf) for the top takeaways from our experience. ![](/content/blog/media/Top-Insights-Trunk-Tools-Discovered-Shadowing-a-Large-Boston-TI-Project-1024x736.png) --- ## /blog/trunk-tools-announces-chief-product-officer/ ### Chris Boyd Named Chief Product Officer at Trunk Tools to Drive Product Innovation in Construction AI > We’re thrilled to share that Chris Boyd has been named Chief Product Officer (CPO) at Trunk Tools. This milestone reflects our continued investment in product leadership as we scale our generative AI platform across the $13 trillion construction industry. ![](/content/blog/media/IMG_9222-1024x768.jpg) Trunk Tools CEO Dr. Sarah Buchner and Chief Product Officer Chris Boyd mark a milestone moment as they celebrate Chris’s promotion and the company’s continued commitment to field-driven AI innovation in construction, and to #LetBuildersBuild. We’re thrilled to share that [Chris Boyd](https://www.linkedin.com/in/chrisgboyd/) has been named Chief Product Officer (CPO) at [Trunk Tools](https://trunktools.com/). This milestone reflects our continued investment in product leadership as we scale our generative AI platform across the $13 trillion construction industry. Chris has been with Trunk Tools for over two years, and during that time, he’s been instrumental in shaping our product strategy. As VP of Product, he launched [foundational AI applications](/platform/) designed to solve real pain points in the field. He built and scaled our product function from the ground up, implemented structured development processes, and partnered closely with customers to ensure we delivered value from day one. Now, as CPO, Chris will lead our Product and Engineering organizations. His focus? Delivering high-impact solutions, improving execution, and aligning teams to [fulfill our mission](/about/): to empower construction to #LetBuildersBuild. “Chris has been a foundational part of our leadership team,” said [Dr. Sarah Buchner](https://www.linkedin.com/in/sarah-buchner/), Founder and CEO of Trunk Tools. “His deep empathy for the customer, rigorous product thinking, and ability to bring clarity to complexity have helped shape Trunk Tools into the company it is today. I’m thrilled to have him step into the Chief Product Officer role as we enter our next phase of growth.” Chris brings over a decade of product leadership experience across SaaS, AI, and construction tech—from early-stage startups to high-growth scale-ups. He’s known for translating complex technical challenges into intuitive, user-centric tools that construction professionals actually want to use. This practical, field-driven approach has been key to our rapid adoption across the industry. “We’re solving some of the most urgent problems in construction with incredibly powerful technology,” said Chris Boyd. “It’s a privilege to lead this team, and we’re just scratching the surface of what we’re capable of delivering. We’re going to stay close to [our customers](/customers/) and keep building solutions that empower them to do what they do best: build.” Chris’s promotion marks an exciting chapter in our journey to elevate the built world with practical, field-tested AI. We’re proud to have him at the helm as we continue to transform construction with tools that drive measurable impact on every jobsite. [Request a Demo of Trunk Tools](http://www.trunk-tools.test/#request-demo) --- ## /blog/trunk-tools-announces-launch-of-egnyte-integration/ ### Trunk Tools Announces New Integration with Egnyte: Streamlining Construction Workflows with AI-Powered Automation > Trunk Tools is excited to announce the launch of our integration with Egnyte, designed to empower construction teams by automating workflows, enhancing decision-making, and reducing costly rework. By combining the strength of Egnyte’s cloud content management platform with Trunk Tools’ AI capabilities, this partnership offers an innovative solution that connects project data and documentation with construction-specific artificial intelligence (AI). [Trunk Tools](https://trunktools.com/) is excited to announce the launch of our [integration with Egnyte](https://us-partner-integrations.egnyte.com/appstore/#/apps/TrunkTools), designed to empower construction teams by automating workflows, enhancing decision-making, and reducing costly rework. By combining the strength of Egnyte’s cloud content management platform with [Trunk Tools’ AI capabilities](/platform/), this partnership offers an innovative solution that connects project data and documentation with construction-specific artificial intelligence (AI). We are thrilled to add TrunkTools to Egnyte’s growing ecosystem of partners, enabling our customers to extend Egnyte’s data governance capabilities to other solutions. This integration will empower teams to automate workflows and make quicker, more informed decisions, whether in the office or the field, by leveraging AI, reflecting our mission of making AI practical, purposeful, and private. ![](/content/blog/media/1548451776139.jpeg) Kevin Soohoo Senior Director of Architecture, Engineering, and Construction Egnyte ## Simplifying Construction Workflows: A Smarter Way to Work The integration of Egnyte with Trunk Tools is a game-changer for the construction industry. Trunk Tools’ AI-powered construction assistant, [TrunkText](/blog/product-deep-dive-trunktext-ai-built-for-the-field/), now connects seamlessly with your Egnyte content, allowing field teams to instantly access and analyze project files, documents, and folders. Gone are the days of manually sifting through stacks of paperwork—this integration pulls all relevant documents, even as they change, into a centralized hub for immediate, actionable insights. **Key Benefits of the Trunk Tools + Egnyte Integration:** * **Automated Workflows:** TrunkText’s AI agents process files directly from [Egnyte](https://www.egnyte.com/), automating tedious tasks and significantly reducing manual effort. Whether it's cross-referencing documents, tracking project updates, or retrieving key information, everything becomes faster and more efficient. * **Enhanced Decision-Making:** Access to real-time, relevant data allows construction teams to make informed decisions quickly. Trunk Tools’ AI processes the documents from Egnyte, ensuring teams always have the right information at their fingertips—leading to faster decisions and more effective project management. * **Reduced Rework:** By continuously syncing with Egnyte, TrunkText automatically identifies discrepancies in project documents, helping teams spot issues early. This proactive approach minimizes the risk of costly rework, delays, and errors in construction. * **Real-Time Sync:** Even as documents are renamed, added, or moved within Egnyte, TrunkTools stays in sync with these changes in real-time. This means teams always have access to the latest project files, ensuring their workflows are continuously optimized. ![](/content/blog/media/TT_-QA-1024x728.png) ![](/content/blog/media/TT_-Contract-Review-Artifact-1024x728.png) Our goal was a zero-friction setup. Connect Egnyte, and Trunk Tools takes care of the rest—no manual syncing, no hassle. Field teams stay focused while everything stays in sync, quietly and reliably. ![](/content/blog/media/1698428808019.jpeg) Nick Akey Senior Integrations Engineer Trunk Tools ## **A Seamless Integration: How It Works** The integration leverages the Egnyte Workato SDK to ensure smooth, automated interaction between Egnyte and Trunk Tools. After a simple one-time setup, the system will automatically sync and retrieve files from Egnyte. Users can toggle different folders and documents for a highly customizable experience, making it easier than ever for construction professionals to retrieve and analyze the data they need. This integration is designed with field teams in mind—reducing the time spent on documentation management, improving efficiency, and enabling teams to focus on what matters most: building. ![](/content/blog/media/TT_-Submittal-Review-1024x728.png) ## **Powering Construction Professionals with AI** The Trunk Tools + Egnyte integration is built for the construction professionals who are continuously pushing the boundaries of what’s possible. Whether you’re a [Project Manager](/customers/#section2), [Superintendent](/customers/#section1), or Engineer, this integration ensures your team has the tools to reduce inefficiencies and avoid the headaches associated with disorganized or outdated documentation. ## **Customer Success: How the Integration Improves the Bottom Line** Leading construction firms are already seeing transformative results. The integration is helping project engineers, coordinators, and managers optimize their workflows, identify discrepancies earlier, and enhance collaboration—leading to faster project delivery and lower costs. With our new Egnyte integration, TrunkText becomes even more powerful for construction teams. By connecting with Egnyte, we can now bring in more user data to TrunkText and continue to automate their workflows. This integration enables us to deliver smarter, faster, and more connected project execution. ![](/content/blog/media/1643081736482.jpeg) Livia Lucas Product Manager Trunk Tools ### **Ready to Optimize Your Workflows?** With the Trunk Tools and Egnyte integration, you can say goodbye to manual processes and hello to a more efficient, smarter way of managing construction projects. Whether you’re looking to enhance decision-making or reduce rework, this integration is built to streamline your workflows from day one. ### **Get Started Today!** To learn more about how Trunk Tools and Egnyte can transform your construction workflows, reach out to our team or [schedule a demo](https://trunktools.com/#request-demo). Let’s build a smarter future for the construction industry—together. [REQUEST A DEMO](https://trunktools.com/#request-demo) https://youtu.be/2f5HSEPKR4k --- ## /blog/trunk-tools-announces-launch-of-trunkdetect/ ### Trunk Tools Announces Launch of TrunkSubmittal > Trunk Tools is proud to introduce TrunkDetect: Automate discrepancy detection across construction documentation, streamline spec and submittal reviews, and eliminate costly delays and rework. We are proud to introduce [TrunkSubmittal](https://detect.trunktools.com/), an innovative solution designed to automatically detect discrepancies across construction documentation—starting with spec and submittal reviews. TrunkSubmittal gives teams power to reduce schedule delays and cuts down administrative burdens, enhancing project efficiency from day one. TrunkSubmittal is the latest addition to our growing suite of tools, following the successful launches of [TrunkText and TrunkSchedule](/platform/), each crafted to optimize productivity and accuracy in construction workflows. Construction teams routinely face the challenge of manually reviewing and cross-checking scattered documents, often resulting in overlooked discrepancies, costly rework, and schedule delays. For example, discrepancies between submittals and project specifications frequently trigger tedious back-and-forth revisions, impacting schedules and losing valuable time. On a $100 million project, teams can manage over 3,000 submittals, 1,000 RFIs, and 250 specifications — and time spent on submittal reviews alone can cost a GC nearly half a million dollars. TrunkSubmittal catches discrepancies early, saving time, protecting schedules, and reducing costs at a scale that simply wasn't possible before. This is just the beginning — the future belongs to builders who use AI to move faster and build smarter. Dr. Sarah Buchner CEO & Founder Trunk Tools ## Built for Teams That Can’t Afford to Miss TrunkSubmittal tackles these challenges head-on. It intelligently flags discrepancies between submittals and project specifications, ensuring accuracy and completeness before issues escalate. By seamlessly integrating into existing workflows, TrunkSubmittal empowers teams with clear, actionable insights, guiding them efficiently through each submittal review process. **Key benefits of TrunkSubmittal include:** * **Fast compliance checks** of submittals against specifications * Thorough **identification** of missing information, deviations, and noncompliant materials * **Accelerate RFIs** and review cycles * Generation of clear, structured **product requirement lists** for subcontractors * Seamless **integration** with existing construction management systems TrunkSubmittal tackles one of the biggest pain points in preconstruction—chasing down discrepancies buried across construction documents. The idea that we can catch those issues upfront, before they turn into RFIs or delays, is a game-changer. Where preconstruction services are often undervalued, tools like this help us work more efficiently, reduce risk, and deliver measurable impact early in the project. ![](/content/blog/media/sawh-1.jpg) Rawle Sawh Director of Operations Technology Gilbane Building Company So many of our delays in the field start with missing or conflicting info in the documentation. I see TrunkSubmittal as a way to catch those problems before they ever reach the jobsite. If it can help us avoid that scramble and keep the project moving, it’ll be a huge win for our field teams. ![](/content/blog/media/1543594091776.jpeg) Andy Roy Senior Superintendent Gilbane Building Company ## Addressing Real-World Challenges Faced by Project Teams Construction leaders from top firms can experience transformative improvements using TrunkSubmittal. * **Project Engineers** and **Submittal Coordinators** find relief from tedious manual reviews. * **Project Managers** benefit from improved submittal quality and accelerated approvals. * **Operations Managers** appreciate the consistent and standardized review process provided by TrunkSubmittal across diverse projects. * **Project Directors** and **Hiring Managers** value how TrunkSubmittal simplifies training new hires, enabling them to rapidly become productive despite staffing challenges. ## Submittal Review, Reinvented TrunkSubmittal leverages the latest in intelligent automation to deliver unparalleled clarity, consistency, and speed, heralding a new era of building efficiency. At Trunk Tools, our mission remains clear: #LetBuildersBuild by providing them with the tools they need to automate construction, the most consumed product in the world. With this TrunkSubmittal release, we’re turning cumbersome submittal reviews into a seamless, intuitive experience. Project teams get clear, actionable compliance insights, and the system conducts the analysis without any clicks. No digging, no disruption—just faster decisions and fewer surprises. ![](/content/blog/media/1737497716483.jpeg) Chris Boyd Chief Product Officer Trunk Tools ### **To experience the transformative power of TrunkSubmittal for yourself, schedule a demo today.** [REQUEST A DEMO](https://detect.trunktools.com/) [TALK TO AN EXPERT](https://detect.trunktools.com/) https://youtu.be/ytwYLVaOPxw --- ## /blog/trunk-tools-announces-launch-trunkreview/ ### Trunk Tools Announces Launch of TrunkReview > Trunk Tools launches TrunkReview, an AI-powered agent that automatically detects and summarizes drawing revisions, helping construction teams reduce rework, accelerate bulletin reviews by up to 85%, and minimize project risk. We are excited to introduce [**TrunkReview**](/tools/trunkreview/), the newest agent from [Trunk Tools](https://trunktools.com/) designed to automate one of the most time-consuming and error-prone workflows in construction: reviewing drawing revisions. TrunkReview accelerates how teams assess changes between drawing sets, helping project teams avoid missed details that can quickly snowball into $10,000+ rework events. Drawing revisions—also commonly referred to as bulletins—are critical QA/QC moments in the project lifecycle. Yet they’re routinely reviewed under time pressure, across dozens of sheets, and with changes that may or may not be clouded by the design team. The result? Missed changes that can result in rework, delayed change orders, subcontractor fatigue (when GCs simply pass the responsibility to review down to their trades), and unnecessary risk to schedule and budget. TrunkReview changes that equation. Leveraging cutting-edge vision language models trained by architects and construction industry experts on millions of data points, TrunkReview automatically scans new drawing revisions uploaded in the project management system, detects both clouded _and_ unclouded changes, and presents them through a clear visual overlay _and written narrative summary_. Teams get instant clarity on what changed, where it changed, and which associated sheets are impacted—without manual comparison or guesswork. Reviewing drawing revisions is one of those workflows everyone knows is painful, but until now there hasn’t been a way to do it apart from slowly working through every sheet in the new bulletin and comparing against the previously issued set. TrunkReview gives project teams back hours of their time while reducing the risk of costly rework. It’s another big step toward our vision of autonomous agents handling the repetitive work so builders can focus on building. ![](/content/blog/media/Sarah-Buchner_Headshot_Portrait-1.jpg) Dr. Sarah Buchner Founder & CEO, Trunk Tools ## **Built for teams that can’t afford to miss a change** TrunkReview is purpose-built for Project Managers and Superintendents at General Contractors and Owners who self-perform work who are on the front lines of interpreting design changes and understanding their downstream impact. As soon as a new bulletin is uploaded to a project management system like Procore or Autodesk, TrunkReview gets to work automatically. Key benefits of TrunkReview include: * Automatic detection of drawing revisions upon upload * Visual overlays highlighting additions in blue and deletions in red * Identification of clouded and _non-clouded_ changes often missed by human reviewers * A written, bullet-point narrative summarizing all changes * Direct links to associated sheets impacted by each change * 70–85% faster review cycles compared to manual processes (e.g. a 20-sheet bulletin is analyzed in less than 5 minutes) By anchoring the review process with both visuals and a written summary, TrunkReview helps teams move faster, communicate more clearly with subcontractors, and get a head start on the change order process. ![](/content/blog/media/Screenshot-2026-02-25-at-9.58.02-AM-1-1024x517.png) ![](/content/blog/media/Screenshot-2026-02-25-at-9.58.44-AM-1024x517.png) ## **Addressing real-world challenges faced by project teams** Manual bulletin reviews are not just slow—they’re risky. Even with legacy tools that offer visual overlays, reviews still start only when a human gets around to it, and the written narratives that offer guidance to the field are manually generated. TrunkReview removes that friction by running autonomously and delivering actionable insights in minutes. * **Project Engineers** reclaim hours previously spent flipping between sheets and versions. * **Project Managers** gain faster visibility into schedule and budget impacts. * **Superintendents** receive clearer guidance for their trades in the field. * **Subcontractors** avoid fatigue from being asked to analyze revisions and report back on impacts to their scopes of work. * **Owners** benefit from clearer justification for change order requests and reduced rework caused by missed changes. ## **Bulletin review, reinvented** At launch, TrunkReview focuses on revision-to-revision comparisons within a specific discipline (architectural, structural, and all MEP drawings supported), but this is just the beginning. Future iterations will compare drawings across disciplines to catch potential conflicts and bridge into cost, schedule, and procurement implications—further accelerating decision-making and reducing risk across the project lifecycle. TrunkReview represents Trunk Tools’ first major step into AI-powered analysis of construction drawings, expanding beyond text-heavy documents and unlocking intelligence across _all_ project documentation. Our mission remains the same: **#LetBuildersBuild** by automating the work that slows teams down. TrunkReview has been in alpha and closed beta testing with a limited group of customers in early 2026, with broader availability planned for late Q1 2026. With TrunkReview, we’re bringing cutting edge AI capabilities to construction drawings. The agent doesn’t wait for someone to click ‘compare.’ It detects revisions instantly, analyzes every sheet, and delivers a clear narrative teams can act on right away. That’s a fundamentally different experience from anything that exists today. ![](/content/blog/media/1737497716483.jpeg) Chris Boyd Chief Product Officer, Trunk Tools ### **To learn more about TrunkReview or to express interest in upcoming availability, visit our website or schedule a conversation with our team.** [JOIN THE WAITLIST](/tools/trunkreview/#) [REQUEST A DEMO](https://trunktools.com/#request-demo) https://youtu.be/n4ogHfpGUzM?si=I4b80o09BAVCTbr- --- ## /blog/trunk-tools-announces-new-integration-with-dropbox-automate-optimize-document-management/ ### Trunk Tools Announces New Integration with Dropbox: Automate and Optimize Your Documentation Management > Trunk Tools is excited to announce our latest integration with Dropbox, designed to streamline document management and automate critical file handling workflows for our customers. By seamlessly connecting Dropbox’s powerful cloud storage capabilities with Trunk Tools’ AI-driven analytics platform, users can now effortlessly manage, access, and analyze their project documentation with unparalleled efficiency. [Trunk Tools](https://trunktools.com/) is excited to announce the launch of our latest integration with [Dropbox](https://www.dropbox.com/), designed to streamline document management and automate critical file handling workflows for our customers. By seamlessly connecting Dropbox’s powerful cloud storage capabilities with [Trunk Tools’ AI-driven analytics platform](/platform/), users can now effortlessly manage, access, and analyze their project documentation with unparalleled efficiency. ## **Simplifying Documentation Management: Automation Meets Intelligence** The Trunk Tools and Dropbox integration automates essential construction management tasks by delivering immediate access to relevant project documentation. Now, teams can focus on decision-making and strategic tasks instead of spending valuable time organizing and transferring files manually. **Key Benefits of the Trunk Tools + Dropbox Integration:** * **Automated Folder Structure Replication:** Effortlessly replicates your Dropbox project folder structures in Trunk Tools, including all nested folders, ensuring your documentation stays organized automatically. * **Real-Time File Metadata Delivery**: Receive immediate metadata for new or updated files from Dropbox directly within Trunk Tools, keeping your data current and accessible. * **Streamlined File Management**: Automatically manage deleted or moved files, ensuring Trunk Tools mirrors the Dropbox environment accurately, reducing potential errors or confusion. * **Hourly Syncs**: Your data stays up-to-date with hourly syncing, allowing your teams continuous access to the latest files without manual updates. ![](/content/blog/media/TT-Dropbox-QA-1024x728.png) ![](/content/blog/media/TT-Dropbox-Contract-Review-1024x728.png) Dropbox is a leader in secure cloud file management, and our integration with them is a critical step toward simplifying how construction teams handle documentation. With this integration, users can seamlessly and securely sync their Dropbox folders and files with TrunkText to get all the benefits TrunkText has to offer. ![](/content/blog/media/1680028199861.jpeg) Matt Pardee Director of Engineering Trunk Tools ## **Seamless Setup, Immediate Impact** This integration is straightforward to deploy and maintain. After an initial setup, the integration syncs regularly to ensure Trunk Tools and Dropbox remain aligned. ![](/content/blog/media/TT-Dropbox-Corpus-Filtering-1024x728.png) ## **Empowering Your Teams with Automated Documentation** Whether you're a [Project Manager](/customers/#section2), Field Engineer, or [Construction Executive](/customers/#section3), the Dropbox integration gives your team the power of connected, automated documentation. By synchronizing Dropbox files and metadata in real time, Trunk Tools enables more accurate decision-making, faster issue detection, and a major reduction in manual data handling, so your team can stay focused on execution. ## Driving Success Through Intelligent Automation The integration has already shown substantial benefits for our early-adopter [customers](/customers/). By automating the synchronization of Dropbox files to the Trunk Tools platform, teams can significantly reduce manual workload, prevent documentation errors, and maintain project accuracy, all of which directly contribute to improved project outcomes and reduced operational costs. This integration with Dropbox is a critical part of our mission to ‘let builders build.’ Teams can now bring more of their project data into Trunk Tools, giving our system a more complete and connected view of the jobsite documentation. This empowers our platform to detect discrepancies earlier, deliver more relevant insights to users, and continue automating workflows that matter most. It’s another step toward making intelligent automation the default across construction project management. ![](/content/blog/media/1643081736482.jpeg) Livia Lucas Product Manager Trunk Tools ### **Ready to Streamline Your Document Management?** With Trunk Tools’ Dropbox integration, streamline your workflows and elevate your documentation management processes today. Say goodbye to manual data transfers and tedious document tracking, and hello to automation-driven efficiency. ### **Get Started Today!** To discover how the Dropbox integration can transform your operations, reach out to our team or [schedule a demo](https://trunktools.com/#request-demo). Let's build a smarter documentation process together. [REQUEST A DEMO](https://trunktools.com/#request-demo) --- ## /blog/trunk-tools-builds-cortex-purpose-built-ai/ ### The Brain We Built for Builders: Why Construction Deserves Purpose-Built AI > How Cortex, our construction-specific intelligence layer, reads drawings, reviews submittals, and gives every Trunk Tools agent the full context of your project. _(Written by Dr. Sarah Buchner, Founder & CEO, Trunk Tools)_ I was twelve the first time I worked on a job site. My dad was a carpenter in a poor, rural part of Austria, so I grew up around the work and the challenges we all know: the coordination, the paperwork, the way missed details can cost a crew a day, a week, or a relationship with an owner that took years to build. By the time I [founded Trunk Tools in 2021](/about/), I'd spent my whole life in and around construction. We've since hired many people with the same story: people who've scrambled to prep for an OAC meeting, kept RFI logs, reviewed submittals, missed a change in a bulletin, and know in their bodies what the pressure of this work feels like. **Two things were clear to me from the start.** First, there is too much information on a project for any team to fully comprehend. One early customer was building a high-rise in Manhattan. When their documentation synced into our platform, there were 120,000 files averaging 30 pages each. Three and a half million pages for one building, a stack three times the height of the structure itself. Buried in that volume are the discrepancies that upend schedules: coordination problems, spec conflicts, drawing details that quietly contradict each other. Second, the workforce meant to catch those risks is aging faster than it can be replaced. Nearly 40% of skilled trades workers are already over 45, and an estimated 17 million construction workers will leave the trade over the next decade. This isn't a headcount problem you fix with a hiring cycle. It's an experience cliff: the judgment of a generation leaving faster than it can be passed down. Customers kept asking us whether AI could actually help with the volume, the discrepancies, the buried risk, and the labor force transformation. And most importantly, could Trunk Tools make AI able to read drawings? Today, our answer to those questions is an emphatic "yes" thanks to [Cortex](/platform/), our new construction-specific intelligence layer that powers [every Trunk Tools agent](/platform/). ## **What We Built First: TrunkText** We started with [TrunkText](/tools/trunktext/): a way for anyone on a project — in the field, on their phone, without walking back to the trailer — to ask a question and get a cited, context-aware answer in under a minute. That sounds simple. It wasn't. Construction documents aren't isolated text files; a single wall section has to be read against three other sheets, a spec section, and a detail drawn six months earlier. We couldn't point a general-purpose model at that and call it done. Some early customers had already tried. So we built our first version of a construction-specific AI "brain" trained on construction data: the institutional memory of a 30-year superintendent who has read every sheet, spec, and RFI on your project and never forgets a thing. ## **Why We Had to Build Cortex: Submittal Review at Scale** Because TrunkText worked, [customers](/customers/) pulled us deeper: "Why can't it do this?" "It would be great if it could…" So we turned next to one of the most time-intensive tasks in construction: submittal reviews. Reviewing a submittal properly requires awareness of all relevant spec sections and RFI responses that amend them, often with the tags missing in the system of record. Asking an early-career PE to review hundreds of submittals and catch every compliance gap invites rework and schedule delays that erode margin. We tested every generic model on this. None produced what was needed. So we built [TrunkSubmittal](/tools/trunksubmittal/), training our own models to infer the relationships between spec, submittal, and RFI automatically. One year later, [the results are clear](/platform/): * 35,000 submittal reviews run on our platform — 60% non-compliant, 35% partially compliant, only 5% fully compliant, proving how much PEs and APMs are up against. * Median run time of 3.92 minutes, against the 45–60 a proper manual review takes. * Median cycle time down from 54.8 days at launch to 14.0 today — a 74% reduction. * "Stuck" submittals (over 60 days for approval) down from 42.8% to about 2%. The proof shows up in the field. A PE at Gilbane told us the architect on her Milwaukee project praised her attention to detail at an OAC meeting. An APM at [Cleveland Construction](/customers/case-study-cleveland-construction-sped-up-submittal-reviews-with-trunk-tools/) said his architect recommended them to other owners in the area on the strength of their submittal process. ## **The Hardest Problem: AI That Reads Construction Drawings** But drawing review is where the problem gets especially hard. It's where the gap between [general-purpose and purpose-built AI](/platform/) matters most. Our platform data tells us that 10 to 20% of changes in a drawing set aren't clouded, and design teams include a quality narrative less than 5% of the time. How do you get in front of a problem you don't know is there? Any PE who has fed a drawing set into a general-purpose AI model knows how short it falls. The research confirms it: frontier models, the same ones underlying most "AI for construction," top out around 26% accuracy on something as basic as detecting a door. Not because the prompts are wrong, but because drawings communicate through visual symbols no general model was trained to read. Better prompting doesn't close that gap. Different training does. So we built it. There's no ImageNet for construction drawings, so we created the dataset ourselves, labeling symbols by hand, then scaling into a corpus of over two million labeled drawing artifacts. On that same door-detection task, we hit 97% precision and 90% recall. Cortex doesn't just read a sheet, it sees what changed when a bulletin arrives, including the changes the architect didn't cloud. For our [beta customers](/customers/), a 20-sheet bulletin that took up to six hours now takes under ten minutes, with written narratives, flagged risks, and RFI drafts ready to send. ## **Where We're Going: The Agent Network** The momentum compounds as the distance between workflows disappears. [TrunkRFI](/tools/trunkrfi/) prevents unnecessary RFIs, drafts the necessary ones, and reads the implications of a design team's response. [TrunkBid](/tools/trunkbid/) turns subcontractor proposals into an apples-to-apples leveling analysis for buyout. [TrunkBrowse](/tools/trunkbrowse/) lets teams pull every related detail, spec, and document by clicking a single element on a drawing. And the agents now hand off to each other: when [TrunkReview](/tools/trunkreview/) flags a change worth a question, TrunkRFI drafts the RFI with the context already filled in. No re-entry, no dropped detail. Cortex is what makes this possible. Underneath every agent is a construction ontology: a structured model of what a submittal, a spec section, an RFI, a drawing detail, and a schedule activity actually are, and how they depend on one another. On top of it, Cortex builds a knowledge graph that links every document and datapoint on your project: this spec section governs that submittal, this RFI amends that spec, this detail appears on these sheets and drives that schedule activity. The result isn't a system that retrieves text. It's one that understands relationships so every agent reasons with the full picture of your project, not one document in isolation. Let me be clear about what this is not. It's not a general-purpose model pointed at construction. Not AI acquired last quarter and bolted onto a legacy tool. Not a toolkit we hand you to build and maintain yourself (your PEs shouldn't have to become prompt engineers to leverage AI to review a submittal). Our agents arrive pre-built and pre-trained, working the day your documents land, not a roadmap promise you'll see in two years. We price them as a predictable, up-front commitment, not a meter that runs out of credits the moment your team leans in. And we don't ship software and disappear. Our people are in the field with yours, because adopting AI is as much a change-management challenge as a technical one. We build, maintain, and run [the agents](/platform/) so your team can stay on the build. My conviction is firm. Unless you have a construction-specific intelligence layer, and unless every agent is measured against a ground-truth evaluation dataset, you are no better than what a general model produces on a good day. In construction, where every minute carries weight, that isn't good enough. In the end, the technology only matters if it delivers. Builders on [Trunk Tools](https://trunktools.com/) catch risk before it compounds and save weeks of time. Their project teams start the day with a manageable to-do list because the tedious work is already done, and sleep better the night before an OAC meeting because we've taken many of the unknowns off the table. That's why we build what we build. Cortex is the next evolution of our mission: to let builders build. [Explore Cortex →](/platform/) ## **Frequently Asked Questions** **What is Cortex?** Cortex is Trunk Tools' construction-specific intelligence layer — the "brain" that powers every Trunk Tools agent. It combines a construction ontology with a knowledge graph that links every document and datapoint on a project, so each agent reasons with the full context of the job rather than one document in isolation. **How is Cortex different from general-purpose AI?** General-purpose models weren't trained to read the visual symbols and cross-referenced documents that construction runs on. Cortex is purpose-built and trained on real construction data, so it understands how specs, submittals, RFIs, drawings, and schedule activities depend on one another. Better prompting doesn't close that gap — different training does. **What can Trunk Tools agents do?** TrunkText answers project questions with cited sources in under a minute. TrunkSubmittal automates submittal reviews. TrunkReview reviews drawing bulletins and flags what changed. TrunkRFI prevents unnecessary RFIs and drafts the necessary ones. TrunkBid levels subcontractor proposals for buyout. TrunkBrowse pulls every related detail, spec, and document from a single element on a drawing. **Does Trunk Tools AI replace construction workers?** No. Trunk Tools augments project teams — handling the tedious, high-volume document work so people can spend their time building and making the decisions only humans can make. [EXPLORE CORTEX](/platform/) --- ## /blog/trunk-tools-closes-40m-series-b-construction-ai-transformation/ ### Trunk Tools Closes $40M Series B to Lead Construction’s AI Transformation > Trunk Tools raises $40M Series B, led by Insight Partners, to scale AI-powered construction solutions, tackling $1T in annual industry inefficiencies. ![](/content/blog/media/Z6C_0637-1024x683.jpg) **NEW YORK, NY** – **July 24, 2025** – [Trunk Tools](https://trunktools.com/), the AI-powered platform revolutionizing how construction teams interact with project data, today announced a $40 million Series B funding round led by global software investor [Insight Partners](https://www.insightpartners.com/) with participation from Redpoint Ventures, Innovation Endeavors, Stepstone, Liberty Mutual Strategic Ventures, and Prudence. The new investment will bring the total funding to $70 million, accelerating the company’s growth and helping to address the construction industry’s deeply rooted productivity losses, which exceed $1 trillion annually. Built by construction professionals for the realities of the field, Trunk Tools uses advanced AI to organize and provide insight into the millions of documents–drawings, specs, RFIs, schedules, and submittals–generated throughout the lifecycle of a project. The [platform](/platform/) enables teams to ask natural-language questions and receive instant, accurate, and actionable answers sourced from the relevant information. Fully autonomous agents are now handling entire workflows that once required human input, while simultaneously connecting data to the project schedule to flag potential issues before they lead to delays or costly rework.  [Founded by CEO Dr. Sarah Buchner](/about/), Trunk Tools was born out of her firsthand experience in the construction industry. She began her career as a carpenter at the age of 12 in a small village in Austria and worked her way up to become a superintendent, project manager, and group leader. Frustrated by the daily inefficiencies she witnessed on job sites, she pursued a PhD in civil engineering and data science to address these challenges at scale, ultimately setting out to develop a smarter, more innovative approach to how construction teams work. “Construction is the backbone of our global economy and daily life, yet the industry is still bogged down by outdated tools, fragmented systems, and overwhelming bureaucracy,” said Buchner. “We built Trunk Tools to eliminate the guesswork. General-purpose AI simply isn’t advanced enough for an industry built on proprietary data and complex workflows. This new round of funding gives us the resources to bring vertically tailored AI reasoning agents to every job site.”  Unlike traditional tools that serve as passive digital repositories, Trunk Tools functions like an intelligent teammate, structuring muddled documentation, proactively flagging risks, and surfacing insights in real time. The company is already deployed on hundreds of construction projects and has scaled revenue 5x over the past six months. “Trunk Tools is helping define a new category of AI with its construction platform,” said Jeff Horing, Co-founder and Managing Director at Insight Partners. “The recent advancements in AI have allowed significant value to be unlocked from construction documentation, and Sarah and her team have the deep industry expertise and technical know-how to build solutions that will transform the jobsite.” The $40 million Series B funding will support Trunk Tools in expanding its engineering, product, and go-to-market teams, growing its field enablement program, and continuing to scale the AI platform’s capabilities across increasingly complex projects but also the long tail of the market.  **About Trunk Tools** Trunk Tools built the brain behind construction and is transforming the $13 trillion construction industry. As the premier AI agent platform for the built environment, Trunk Tools deploys solutions that streamline construction data management, automate tedious and repetitive tasks, and minimize waste. Trunk Tools was founded by Dr. Sarah Buchner in 2021 and is headquartered in New York, NY. **About Insight Partners**Insight Partners is a global software investor partnering with high-growth technology, software, and Internet startup and ScaleUp companies that are driving transformative change in their industries. As of December 31, 2024, the firm has over $90B in regulatory assets under management. Insight Partners has invested in more than 800 companies worldwide and has seen over 55 portfolio companies achieve an IPO. Headquartered in New York City, Insight has offices in London, Tel Aviv, and the Bay Area. Insight’s mission is to find, fund, and work successfully with visionary executives, providing them with tailored, hands-on software expertise along their growth journey, from their first investment to IPO. For more information on Insight and all its investments, visit [insightpartners.com](https://www.insightpartners.com) or follow us on X @insightpartners. [Request a Demo of Trunk Tools](http://www.trunk-tools.test/#request-demo) --- ## /blog/trunk-tools-enhances-jobsite-ai-autodesk-forma-integration/ ### Trunk Tools Enhances Jobsite AI Capabilities with new Autodesk Forma Integration > Trunk Tools' AI agents are now available to project teams running Forma Build, automating document-intensive workflows and delivering construction intelligence across the project lifecycle. [Trunk Tools](https://trunktools.com/), the AI-powered platform transforming how construction teams interact with project data, today announced a [new integration with Autodesk Forma®](https://www.autodesk.com/integrations/partner/trunk-tools), the first end-to-end, cloud-based, AI-native platform built for architects, engineers, contractors, and owners. Construction teams can now deploy Trunk Tools agents alongside Autodesk® Forma Build™ to streamline and surface critical data in document-intensive workflows, from submittal review and drawing analysis to RFI management, with project data from Autodesk® Forma Data Management™ as the underlying source of record. Commercial construction projects generate an enormous volume of documentation, and the ability to act on that information quickly separates high-performing project teams from those that fall behind. The challenge often isn't access to information; it's giving engineers, superintendents, and project managers the tools to cut through the volume, apply the right expertise, and translate project requirements into decisions and progress in the field. Construction has always rewarded teams that can move fast and make the right call. The problem is that the knowledge required to do that is buried in thousands of documents, locked in the heads of senior staff, and rarely scales across projects the way it needs to. Trunk Tools is construction-specific AI, built to extend the expertise of every person on a jobsite, institutionalize the knowledge that usually walks out the door, and surface how the business is performing across their entire portfolio. Integrating with Autodesk Forma puts that capability at the center of how our shared customers run their projects. ![](/content/blog/media/Sarah-Buchner_Headshot_Portrait-1.jpg) Dr. Sarah Buchner Founder & CEO, Trunk Tools Construction teams generate, aggregate and manage large volumes of critical data in Autodesk Forma throughout their projects’ lifecycles. Trunk Tools’ integration with Autodesk Forma adds a new way to apply fast-evolving AI capabilities to help those teams extract even more value out of that data. ![](/content/blog/media/1551979096473.jpeg) James Cook Industry and Technology Partnerships, Autodesk ## **Integration Details** Trunk Tools makes every project document actionable through a suite of [purpose-built AI agents](/platform/). With the new integration, those agents connect directly to project data stored in Forma Data Management, so every action is grounded in a single, current source of record. Trunk Tools functions as an intelligent layer on top of project data, structuring the unstructured data buried in documentation, surfacing relevant information in real time, and autonomously handling workflows that would otherwise require significant manual effort. With **TrunkText**, Trunk Tools’ Q&A agent, project teams use natural language to search across project documents, including drawings, specifications, submittals, contracts, and RFIs, with responses citing the source document and highlighting the specific document section it pulled the data from. [**TrunkSubmittal**](https://detect.trunktools.com/) automates the comparison of subcontractor submittals against project specifications and related documents such as RFIs, surfacing compliance issues that would otherwise require time consuming manual review and / or result in revise-and-resubmit statuses from the project architect. [**TrunkReview**](/tools/trunkreview/) analyzes newly issued drawing sets in the preconstruction and construction phase for clouded and non-clouded changes and generates a narrative of these changes, giving project teams a chance to quickly digest and identify issues that might otherwise lead to rework. These capabilities, along with a growing suite of agents for [RFI management](/tools/trunkrfi/), bid analysis, SOP adherence, scope writing, and custom workflows, are all available to Autodesk Forma users. ## **Trusted in the Field** With deployments across hundreds of jobsites across the US, Trunk Tools is trusted by general contractors who have standardized on platforms like Autodesk Forma for project management and are looking to add AI on top of that foundation. Take [Cleveland Construction](/customers/case-study-cleveland-construction-sped-up-submittal-reviews-with-trunk-tools/), for example. After making the switch from another platform to Autodesk Forma, Cleveland Construction deployed Trunk Tools to give its engineers and superintendents the ability to cut through the volume of project documentation, act on the right information at the right moment, and handle workflows autonomously that would otherwise demand hours of manual review. [**Read more about how Cleveland keeps projects on track with Trunk Tools and Autodesk**](/customers/case-study-cleveland-construction-sped-up-submittal-reviews-with-trunk-tools/) TrunkSubmittal takes a PE or APM with little to no experience in the industry and gives them five-plus years of experience to work with. It drives efficiency, catches things some of our most senior PM staff don’t look for, and ensures we aren’t just passing paper to the architect to review. ![](/content/blog/media/Christiansen-Elliot-817-scaled.jpg) Elliot Christiansen SVP Operations, Cleveland Construction ## **Availability** The Trunk Tools integration with Forma Build is available now. Project teams can connect Trunk Tools to their Autodesk Forma environment through the Autodesk App Store. For more information, visit the [marketplace listing](https://www.autodesk.com/integrations/partner/trunk-tools). ### **Ready to Unlock the Full Power of Your Forma Data?** Trunk Tools' integration with Autodesk Forma puts purpose-built AI agents at the center of how your project teams work — automating document-heavy workflows, surfacing critical information in real time, and giving every engineer and superintendent the expertise to make the right call, faster. ### **Connect Trunk Tools to Autodesk Forma Today** Get started directly through the Autodesk App Store. Visit the [Trunk Tools integration page](https://www.autodesk.com/integrations/partner/trunk-tools) to connect your Forma environment and start turning project data into action. [CONNECT TRUNK TOOLS TO AUTODESK FORMA](https://www.autodesk.com/integrations/partner/trunk-tools) [REQUEST A DEMO OF TRUNK TOOLS](https://trunktools.com/#request-demo) --- ## /blog/trunk-tools-enters-preconstruction-launch-trunkbid/ ### Trunk Tools Enters Preconstruction with the Launch of TrunkBid > Trunk Tools launches TrunkBid, an AI agent that automates subcontractor bid leveling — saving estimators hundreds of hours and eliminating costly scope gaps. We are excited to introduce TrunkBid, [Trunk Tools](https://trunktools.com/)' first purpose-built agent for preconstruction. TrunkBid automates one of the most painful, time-consuming manual workflows in the construction procurement cycle: analyzing and leveling subcontractor bids. Starting today, TrunkBid will be available for beta testing with a select group of customers. Bid leveling is the type of workflow perfect for AI assistance: repetitive, time-intensive, and document heavy. When bids come in under tight deadlines, estimators are left manually cross-referencing each subcontractor's proposal against a scope of work document, populating hand-built spreadsheets, and hunting for gaps across dozens of line items for dozens of trade packages. A single missed exclusion or scope silence can mean defaulting to the lowest bidder for the wrong reasons, with real consequences downstream on project cost. It's not a failure of skill. It's the fault of an unwieldy process exacerbated by looming deadlines and estimators stretched thin across multiple projects. Trunk Tools has built the industry's most advanced construction-specific AI solutions, including robust document preprocessing and proprietary models trained for the most repetitive and time-intensive workflows experienced by project teams. With the release of TrunkBid, we're now leveraging our construction-specific AI 'brain' for critical preconstruction workflows to unlock the power of real AI across the project lifecycle for our customers. ![](/content/blog/media/Sarah-Buchner_Headshot_Portrait-1.jpg) Dr. Sarah Buchner Founder & CEO, Trunk Tools ## **Why existing tools haven't solved this** Legacy bid leveling software gave contractors digital templates to manually enter bid details and compare proposals side by side. An improvement over raw Excel, sure — but not by much. The hours required to do the work correctly stayed almost exactly the same. Until now, preconstruction teams haven’t had access to AI-native solutions to harness the power of modern technological advancements and meaningfully reduce the time estimators spend on this critical workflow. TrunkBid changes that. ![](/content/blog/media/Bid-Leveling-Agent-Overview-1024x883.png) I spent my first four years in construction as an estimator on large commercial projects. Doing bid analysis and leveling work at the quality level that protects a CM from scope gaps later on in the project took many weeks of my time. TrunkBid was built to eliminate the vast majority of that manual comparison work and give our customers the confidence that they know everything they need to get clarity from trades about before awarding a subcontract. ![](/content/blog/media/Z6C0030.jpg) John Altieri, P.E. Subject Matter Expert, Trunk Tools ![](/content/blog/media/Bid-Leveling-Agent-Requirements-List-1024x575.png) ## **How TrunkBid works** Once subcontractor proposals have been received, the leveling process begins. Traditionally, this means 4 to 8 hours per trade package of manual cross-referencing, screen-switching, and spreadsheet-building — multiplied by dozens of trade packages and 3–5 bids per scope of work on the project. TrunkBid brings the speed of AI trained specifically for this workflow into the equation. The estimator uploads their bid documents and any relevant scope of work documents. The agent then: * Extracts all relevant data from each subcontractor's bid and the scope of work document * Maps line items in the bid to project requirements * Identifies what each subcontractor covers, excludes, prices as an alternate, or is silent on entirely * Surfaces gaps, risks, and inconsistencies across bids with follow-up questions for each subcontractor bid to get needed clarity before awarding a subcontract * Exports a structured, ready-to-use leveling sheet to Excel to meet preconstruction experts where they usually work The result: the estimator's job shifts from data entry to strategic decision-making — exactly where their expertise belongs. ## **Built for estimators who can't afford to miss a scope gap** TrunkBid is designed for anyone and everyone responsible for subcontractor selection and buyout. On a large project involving dozens of trade packages, the risk of scope gaps isn't just a time problem; it's a financial one. TrunkBid gives teams a massive head start so the comparison process that once took multiple weeks can happen in a fraction of that time, with greater confidence and consistency. ## **What's next** TrunkBid marks Trunk Tools' entry into preconstruction — a major expansion of where our AI agents operate across the project lifecycle. Combined with our existing agents for submittals, RFIs, and drawing review, Trunk Tools is building toward a future where autonomous AI handles the repetitive, time-intensive work at every phase of a construction project. This is another step toward our mission to **#LetBuildersBuild**. TrunkBid is now available for beta testing with a select group of customers. To learn more or express interest in access, [schedule a conversation with our team](https://trunktools.com/#request-demo). ### **To learn more about TrunkBid or to express interest in upcoming availability, visit our website or schedule a conversation with our team.** [REQUEST A DEMO](https://trunktools.com/#request-demo) https://youtu.be/T0DMAYcoIAk --- ## /blog/trunk-tools-launches-trunktext/ ### Trunk Tools Announces Launch of TrunkText > Even with today's best construction project management tools, workers on the jobsite don't instantly have all the information they need. ## A.I. Construction Technology We are proud to introduce [TrunkText](/tools/trunktext/), a game-changing, patent-pending, text message-based AI tool designed to transform the way construction professionals access critical project information. TrunkText saves workers one-two hours daily, directly contributing to our larger vision of solving the skilled labor shortage. TrunkText is our second product, after TrunkPerform, a tool that improves project time and budget outcomes by incentivizing workers to complete project goals. At Trunk Tools, we believe in a future where the construction industry is propelled forward by the power of AI, where skilled workers can return to what they do best – building with their hands. The construction industry is inundated by thousands of pages of project documents, project specifications, change orders and RFIs. Finding the right information to answer crucial project questions has long been a daunting challenge, slowing progress and incurring high rework costs. For instance, a seemingly simple query like "What paint should I use for the lobby?" often triggers a laborious search through project specifications, RFIs, building codes, and change orders, causing unnecessary delays. TrunkText does what is humanly impossible: In a $500 million dollar high rise project, there’s 120,000 project files with an average of 30 pages - a total of 3.6 million pages. A construction superintendent would take 50 years to read all of that information; TrunkText only needs seconds. Dr. Sarah Buchner CEO & Founder Trunk Tools ![](/content/blog/media/Mobile-Ask-Questions-3.png) ## Built for All Construction Professionals We aim to solve this challenge with TrunkText. TrunkText is a text message-based AI tool and web app that is meticulously trained on a comprehensive range of construction data, such as specs, code, RFIs, contracts, policies, submittals, change orders, safety procedures, and inspection reports. By centralizing general and project-specific information, TrunkText will serve as a one-stop-shop for reliable information for construction projects and schedules. With TrunkText, construction professionals can text any construction project-related question and receive accurate answers within just a few seconds. The system not only provides answers but also supplies links to the relevant documentation, ensuring transparency, trust, and peace of mind. TrunkText is built on top of fast moving generative AI. Our engineers have worked hard to build an experience that leverages the best parts of LLMs, to empower your company with the tools to thrive in an ever-changing world. ![](/content/blog/media/chris.png) Christopher Belsole Senior Software Engineer Trunk Tools ![](/content/blog/media/Get-Answers-Desktop-Web.png) ![](/content/blog/media/Doc-Viewer-Desktop-Web.png) In a field as data-dense as construction, generative AI enables us to create experiences of near-magical simplicity. The natural language interface enables workers to ask questions in the exact same way they'd ask their foreman or super, and allows TrunkText to deliver the precise information they need the instant they need it ![](/content/blog/media/greg-photo.jpeg) Greg Korn Senior Product Designer Trunk Tools ## Save Time, Reduce Rework While in stealth mode, we’ve partnered with project teams from top construction companies like DPR and Suffolk to use TrunkText. These pilots have proven invaluable sources of customer feedback from the project engineers, superintendents, PMs, and other tradespeople we aim to serve. Whether they’re building a high rise condominium or a cutting-edge biomedical facility, our pilot users have experienced time savings by using TrunkText to ask questions and find relevant documents. By building for and with our users, we've built a field-first tool that saves workers' time. TrunkText captures the power of generative AI and places it in the palms of the deskless workforce, a population often underserved by emerging technologies. By saving valuable time and reducing rework costs, our Trunk Tools products hope to empower construction teams to work smarter, more efficiently, and with greater confidence. ### **Ready to start saving hundreds of hours every year?** [GET STARTED](/tools/trunktext/#get-started-above) https://youtu.be/oeOGmudZ50U&cc\_load\_policy=1 --- ## /blog/trunk-tools-series-a/ ### Trunk Tools Raises $20M Series A Led By Redpoint Ventures to Expand Suite of AI Agents for Construction > Trunk Tools, a groundbreaking AI platform disrupting the $13 trillion construction industry, announces a $20 million Series A. The new capital was led by Redpoint Ventures with participation from Innovation Endeavors, who led the Seed round, bringing the total capital raised to-date to $30M. **New York, NY – August 20, 2024 –** [Trunk Tools](https://trunktools.com/), a groundbreaking AI platform disrupting the $13 trillion construction industry, announces a $20 million Series A. The new capital was led by [Redpoint Ventures](https://www.redpoint.com/) with participation from Innovation Endeavors, who led the Seed round, bringing the total capital raised to-date to $30M. Trunk Tools leverages the latest in AI technology to build the “brain” behind construction. By structuring millions of pieces of unstructured project data and deploying AI agents that augment construction professionals in their administrative workflows, Trunk Tools ensures critical information is available to the right people at the right time, automating the tedious and repetitive tasks that have historically weighed on industry productivity and profitability. With Trunk Tools, construction professionals not only save time but avoid construction delays and rework that can cost tens of millions - or more - per project. "We are thrilled to have the support of Redpoint Ventures and our other valued investment partners, as we push the boundaries of innovation in the construction industry,” said Dr. Sarah Buchner, Founder and CEO of Trunk Tools. “Redpoint’s expertise in investing and scaling AI companies is a perfect match and this funding will enable us to accelerate our growth, develop new products, and cement our place as industry leaders in generative AI for construction. What is another vote of confidence is how many of our current and prospective customers have invested: WND Ventures (DPR’s CVC), Suffolk Technology, AEC Angels, STO Building Group, Liberty Mutual Strategic Ventures, Thornton Tomasetti/ TTWiiN, Charps, and many more." Redpoint’s Erica Brescia, also the newest member of Trunk Tools board, added, “Growing up in the construction industry, I have a deep appreciation for the complexities of commercial projects. We have zero doubt of AI's potential to revolutionize construction management. This is a truly massive market opportunity, and we've been searching for a team that combines the empathy that only comes with deep industry experience with the AI expertise to execute this audacious vision. We're thrilled to partner with Sarah and the team at Trunk Tools, who possess the ideal mix of passion, experience, and AI expertise to bring the power of AI to construction.” With today’s announcement, Trunk Tools is also introducing the first fully autonomous AI-powered agent tailored to the construction industry: the Trunk Tools Schedule Agent. Harnessing Trunk Tools’ underlying data infrastructure, the Schedule Agent offers an unprecedented solution in the construction industry: a dynamic link between scheduled activities and all essential supporting documentation to build on time, on budget and according to plan. This advanced agent builds upon Trunk Tools’ existing proprietary AI platform, which is already used by many of the largest general contractors and several Fortune 500 companies, to help construction teams stay on schedule by becoming more proactive on the jobsite without any additional effort by sensing project issues, surfacing insights and taking action. The Schedule Agent integrates seamlessly with schedule files, independently monitoring upcoming tasks to provide timely notifications to notify project managers, superintendents, and project engineers about open tasks, discrepancies or logistical problems.  By helping construction professionals proactively monitor project schedules, manage critical documentation, and automatically alert impacted parties, Trunk Tools fulfills its mission of “empowering construction; let builders build”.  Early users of the Trunk Tools platform are raving about the productivity gains realized in the field. Andy Roy, a Gilbane Building Company senior superintendent who has leveraged Trunk Tools since 2023 on a large, complex construction project states: “Trunk Tools showed that it can help our teams increase efficiency and save significant time by preventing rework. With TrunkText doing the ‘document digging’ for me, I can work more effectively and be more responsive in the field.” "We like to say we are not in AI but in IA - intelligence augmentation: augmenting the tedious, manual, painful parts of worker's jobs, so builders can focus on building,” continued Dr. Buchner. “This is just the beginning of what our AI platform and its army of AI agents can achieve. This industry has long been ripe for disruption, but the market has needed the underlying technology to actually get to a point where it can leverage unstructured data effectively. Generative AI is the answer to construction’s long standing incapability to adopt and leverage technology and we are proud to be the leading provider in our industry." **About Trunk Tools** Trunk Tools built the brain behind construction and is transforming the $13 trillion construction industry. As the preeminent AI agent platform for the built environment, Trunk Tools deploys solutions that streamline construction data management, automate tedious and repetitive work, and reduce waste. Trunk Tools was founded by Dr. Sarah Buchner in 2021 and is headquartered in New York, NY. **About Redpoint Ventures** Redpoint has partnered with visionary founders to create new markets and redefine existing ones since 1999. We invest in startups across the seed, early and growth phases, and we’re proud to have backed over 578 companies—including Snowflake, Looker, Kustomer, Twilio, 2U, DraftKings, Duo Security, HashiCorp, Stripe, Guild, HomeAway, Heroku, Netflix, and Sonos—with 181 IPOs and M+A exits. Redpoint manages $7.2 billion across multiple funds. For more information visit: [http://www.redpoint.com/](http://www.redpoint.com/) For more information, please visit [www.trunktools.com](http://www.trunk-tools.test/). [Talk To Sales](http://www.trunk-tools.test/#request-demo) | [Join The Team](https://trunktools.com/careers/) --- ## /blog/trunk-tools-webinar-conversation-with-andy-roy-gilbane-superintendent/ ### Trunk Tools Webinar: Conversation with Andy Roy, Gilbane Superintendent > In this webinar, Trunk Tools' VP of Product, Chris Boyd, discusses saving time and preventing rework with Andy Roy, Gilbane Superintendent. After a year of use, Andy and his team has found great ways to save time and improve project outcomes for their Gilbane jobsite. From implementation process to change management on site, Andy has great insights about how field workers are approaching new technologies and learning how to improve productivity with the right tools. In this webinar, Trunk Tools' VP of Product, [Chris Boyd](https://www.linkedin.com/in/chrisgboyd/), discusses saving time and preventing rework with [Andy Roy](https://www.linkedin.com/in/andrew-roy-a45709107/), Gilbane Superintendent. After a year of use, Andy and his team has found great ways to save time and improve project outcomes for their Gilbane jobsite. From implementation process to change management on site, Andy has great insights about how field workers are approaching new technologies and learning how to improve productivity with the right tools. https://youtu.be/O-xCFIrFh4o --- ## /blog/trunk-tools-white-paper/ ### Trunk Tools White Paper > See the data to understand how Trunk Tools is solving efficiency challenges in construction with incentives. [TT-White-Paper](/content/blog/media/TrunkTools-WhitePaper.pdf)[Download](/content/blog/media/TrunkTools-WhitePaper.pdf) --- ## /blog/trunktext-webinar-may-2024-image-summarization-functionality/ ### TrunkText Webinar May 2024: Image Summarization Functionality > The Trunk Tools Product team describes our newest AI-powered feature: image summarization. Image summaries can be queried to answer questions. ## Trunk Tools' Product Team Discusses TrunkText's Newest Feature: Image Summarization Learn about our newest AI-powered feature, and how it improves TrunkText, our Q&A agent.  [Watch Now!](#) --- ## /blog/turning-the-tide-on-increasing-labor-productivity-losses/ ### Turning the Tide on Increasing Labor Productivity Losses > Losses due to labor inefficiencies is the largest source of recurring waste in construction, and we can use technology to address it. Skilled construction professionals have mastered the art of balancing Construction’s 4 M's - money, manpower, machines, and materials. Despite advances in capital management, machines, and materials, managing construction labor is still a people problem. This industry depends on manpower to turn blueprints into tangible structures, operate machines, and interpret documents. Losses due to labor inefficiencies is the largest source of recurring waste on construction projects, and its significance is increasing. ## Decline in Labor Productivity Trends Labor productivity, crucial for the financial health of labor-intensive contractors, appears to be worsening. [**A University of Chicago examination**](https://www.awci.org/media/insync/productivity-falls-again/) of Bureau of Economic Analysis data found the value that each additional worker added to construction was 40% lower in 2020 than in 1970. Polls support this concerning trend: nearly 50% of construction professionals believe labor productivity has declined in the last decade.  This decline signifies a deeper malaise within the industry, pointing towards systemic issues in planning, communication, and collaboration – factors that are critical for efficient project execution. Furthermore, an overwhelming 79% of contractors believe that they could enhance labor productivity by at least 6% with better management practices. This improvement in productivity, surprisingly, could lead to an average increase of 50% in profitability, highlighting the direct correlation between effective labor management and financial success. ## The Alarming Cost of Labor Productivity Losses The construction industry is confronting a staggering annual loss of $30 to $40 billion due to labor inefficiencies according to [**FMI’s labor productivity study**](https://fmicorp.com/uploads/media/FMI_Labor_Productivity_Study_FINAL.pdf). This loss is not just a minor dent in the industry's profitability but a significant hemorrhage affecting the entire construction ecosystem. Considering the $900 billion in labor-intensive construction put in place during 2022, the annual labor cost was $270 billion according to FMI. Of this, approximately $40 billion was wasted due to inefficiencies. At an individual contractor level, these losses translate to significant eroded project margins.  This also provides a massive opportunity for improvement. FMI estimates that a 10% increase in labor productivity adds more than 3% to a company's bottom line, increasing profitability by 100%. Let that sink in - **_improving labor productivity by just 10% can double profit margins._** ## What’s Causing These Losses? The drivers of productivity losses vary by firm, as well as by internal or external factors. Internally, the four most critical factors affecting productivity are planning, communication, collaboration, and utilization. A significant number of contractors attribute inefficiencies to poor planning and communication by field and project management, subpar project team collaboration, and inadequate site logistics. These issues, stemming from organizational practices, significantly hinder the efficient execution of construction projects. Externally, contractors face challenges with low-quality design and construction documents, outdated and unrealistic schedules, lack of coordination with general contractors, and inefficiencies in handling change orders. Additionally, the industry is grappling with a [**skilled labor shortage**](https://www.abc.org/News-Media/News-Releases/construction-workforce-shortage-tops-half-a-million-in-2023-says-abc), with many contractors citing the lack of qualified craft labor as a major internal factor impacting productivity. These external factors, often beyond the direct control of individual contractors, exacerbate labor inefficiencies and contribute to the overall decline in productivity within the construction sector. Addressing these challenges requires a multifaceted approach, involving improved management practices, enhanced communication, and better collaboration both within organizations and with external partners. ## Unlocking Your Productivity Gains FMI estimates that $25 billion could be saved through enhanced management practices. This opportunity for improvement is immense, considering that construction remains a labor-intensive business despite advances in technology. We grouped recommendations into four categories: improving planning and management, using technology, developing the workforce, and implementing productivity systems. ### Improving Planning and Management **Enhanced Planning and Pre-Construction Efforts:** Contractors should optimize planning and pre-construction activities. This involves detailed project planning, risk assessment, and resource allocation before the project begins. Effective planning can identify potential bottlenecks early and ensure smoother execution. **Improved Communication and Collaboration:**  Establishing clear and consistent communication channels within the project team and with external stakeholders is crucial. This includes transparent sharing of information and collaborative decision-making processes between the field and office to ensure everyone is aligned and working towards common goals. **Addressing Supply Chain and Vendor Management:** Efficient management of the supply chain and vendor relationships can reduce delays and cost overruns. This involves strategic sourcing, maintaining good relationships with suppliers, and effective inventory management. **Strategic Use of Prefabrication and Off-Site Construction:** Where applicable, shifting to prefabrication and modular construction can reduce waste, improve quality control, and speed up construction timelines. ### Using Technology Adoption of Technology and Digital Tools: Leveraging modern technology can significantly improve productivity. This includes project management software, collaboration tools such as Building Information Modeling (BIM), project tools such as [**TrunkText**](/tools/trunktext/) and **TrunkPerform**, and other digital tools for better design coordination, scheduling, incentives management, and real-time monitoring of project progress. ### Developing the Workforce Focus on Workforce Development and Training: Developing a skilled workforce through continuous training and development programs is essential. Training should cover not only technical skills, but how to use digital technology and implement internal management and communication processes which are critical for effective teamwork and project execution. Strengthening Field Management Practices: Field managers should be empowered and equipped with the necessary tools and information to make informed decisions on-site. This includes better resource planning, site logistics management, incentive management, field management tools, and proactive problem-solving. AI tools such as [**TrunkText**](/tools/trunktext/) can help the field with this.  ### Implementing Productivity Systems Regular Productivity Tracking and Feedback: Tracking labor productivity and providing feedback to the workforce can help in identifying areas for improvement and making timely adjustments. Platforms such as **TrunkPerform** by Trunk Tools are designed to help contractors to easily implement these programs. Implementation of Lean Construction Principles: Adopting lean construction methods can streamline processes, reduce waste, and improve efficiency. This involves practices like just-in-time delivery of materials, efficient workflow design, effective labor employment, and continuous improvement processes. It also includes experimenting with new business processes such as incentive management platforms and other labor utilization strategies. --- ## /blog/what-is-a-change-order-in-construction/ ### What is a change order in construction? > A construction change order formally changes a contract's scope, price, or schedule. Learn what triggers one, who approves it, and the risks of delay. A change order in construction is a formal, signed document that modifies the original contract. It adds, removes, or changes the scope of work and adjusts the contract price, the schedule, or both to match. Until a change is authorized as the contract requires, the added or removed work may fall outside what the parties formally agreed to. That is why disputes over unpaid or unapproved work often trace back to a change that was never documented and approved. ## What triggers a change order? A change order starts with a change event: a drawing revision, an accepted [RFI response](/blog/what-is-an-rfi-in-construction/), a differing site condition, an owner-requested scope change, or a code requirement discovered mid-project. The change event is the moment something changes. The change order is the contract document that follows, usually after the team has evaluated the impact, priced it, and routed it for approval. The gap between when a change happens and when it is formally captured is where much of the risk sits. An unrecognized change event does not disappear. It can surface later as unbilled work, a dispute over who owns the cost, or a line item absorbed into contingency. ## How does a change order differ from a change event, an RFI, and a bulletin? These terms describe different parts of the change-management process: - **Bulletin:** The architect's formal update to the drawings or specifications, often issued to resolve a design gap or incorporate an owner decision. - **RFI:** A contractor's formal question to the design team when a drawing or specification is unclear. Most RFIs do not change the contract, but a response that reveals or adds scope can lead to a change event. - **Change event:** An occurrence with potential cost, schedule, or scope impact that needs to be evaluated and documented. - **Change order:** The final signed instrument that modifies the contract after the impact has been priced and approved. In practice, one bulletin can touch dozens of sheets across several trades. Determining which revisions are already covered by the contract and which represent added or deleted scope is the real work behind a change order. ## Who has to approve a change order? A change order needs approval from the parties with contractual authority over scope, price, and time. That typically means the owner or owner's representative and the contractor. The architect or engineer may also certify or approve the change when the agreement assigns them that role. On the general contractor's side, a project manager usually assembles the change documentation, gathers subcontractor pricing, evaluates schedule effects, and routes the package through internal review before sending it to the owner. Standard-form agreements, including AIA and ConsensusDocs contracts, define the required notices, signatures, and approval sequence. The governing contract—not a general industry custom—controls the process for a specific project. ## What should a construction change order include? A complete change order should clearly identify: 1. The contract and project it modifies. 2. The source of the change, such as a bulletin, RFI response, owner request, or field condition. 3. The added, deleted, or revised scope of work. 4. The contract-price adjustment, including subcontractor, labor, material, equipment, markup, credit, and allowance details as applicable. 5. The number of calendar days added to or removed from the contract time, or an explicit statement that time is unchanged. 6. Supporting drawings, specifications, estimates, and schedule analysis. 7. The required approvals, signatures, and effective date. Clear scope and traceable backup matter as much as the final price. If the document does not connect the cost and schedule adjustment to the source documents, teams may have to reconstruct that reasoning months later. ## What happens if a change order is not caught in time? A missed change order does not only affect the cost of one item. It can consume the contingency intended to absorb other project risks. A missed trade on a multi-discipline change can grow from a small unpriced item into a significant cost once labor, material, supervision, schedule, and downstream rework are included. The timing risk is also contractual. Many construction contracts require written notice within a defined period after the event giving rise to a claim. AIA A201-2017, for example, generally requires claims to be initiated within 21 days under Section 15.1.3, subject to the agreement's terms and applicable law. Missing a contractual notice deadline may limit or waive recovery. Teams should follow the notice and authorization provisions in the executed contract rather than relying on a standard rule of thumb. ## How long does it take to process a change order? There is no universal processing time because contract terms, project size, and change complexity vary. The sequence is consistent: identify the event, trace the affected drawings, specifications, RFIs, trades, and schedule activities, price the impact, negotiate it, and route it for approval. On a complex multi-trade change, tracing the impact by hand can take days before pricing or approval begins. [One illustrative example](/blog/system-of-action-vs-system-of-record/) follows a bulletin that revised 135 sheets across six disciplines. Identifying the affected scope, checking it against the specifications and RFI log, and pricing it at roughly $205,000 took three days of manual tracing before the team could draft the potential change order. ## How is Trunk Tools connecting change orders to the rest of the project? Trunk Tools is building [TrunkChange](/tools/trunkchange/), an agent planned to launch in Q4 2026. When a bulletin or RFI response lands, it uses the revision history already built by [TrunkReview](/tools/trunkreview/) and [TrunkRFI](/tools/trunkrfi/) to trace the affected sheets and trades. TrunkChange reports potential cost, schedule, and scope impact by discipline, then drafts the change event and a potential change order with a rough-order-of-magnitude estimate for a person to review. The goal is not to remove the judgment or contractual review behind a change order. It is to reduce the manual tracing required before the project team can make that judgment. ## Frequently asked questions **What is a change order in construction?** A change order is a formal, signed document that modifies a construction contract's scope, price, schedule, or a combination of the three after a change event occurs. **What is the difference between a change order and a change event?** A change event is an occurrence with potential scope, cost, or schedule impact, such as a bulletin, RFI response, or differing site condition. A change order is the signed contract amendment created after that impact is priced and approved. **Who signs a construction change order?** The parties with contractual authority sign the change order, typically the owner or owner's representative and the contractor. The architect or engineer may also certify or approve it when the contract requires. **What happens if work starts before a change order is signed?** Starting changed work without the written authorization required by the contract can put payment and schedule relief at risk because the parties have not formally agreed to the added scope, price, or time. **Does every RFI lead to a change order?** No. Most RFIs clarify the contract documents without changing the contract. An RFI may lead to a change order when its response adds, removes, or changes scope with a cost or schedule impact. --- *By the Trunk Tools team. Published September 23, 2026.* *Sources: Trunk Tools, [System of action vs. system of record in construction](/blog/system-of-action-vs-system-of-record/); AIA A201-2017, General Conditions of the Contract for Construction, Section 15.1.3; AIA and ConsensusDocs standard contract forms.* ### Frequently asked questions #### What is a change order in construction? A change order is a formal, signed document that modifies a construction contract's scope, price, schedule, or a combination of the three after a change event occurs. #### What is the difference between a change order and a change event? A change event is an occurrence with potential scope, cost, or schedule impact, such as a bulletin, RFI response, or differing site condition. A change order is the signed contract amendment created after that impact is priced and approved. #### Who signs a construction change order? The parties with contractual authority sign the change order, typically the owner or owner's representative and the contractor. The architect or engineer may also certify or approve it when the contract requires. #### What happens if work starts before a change order is signed? Starting changed work without the written authorization required by the contract can put payment and schedule relief at risk because the parties have not formally agreed to the added scope, price, or time. #### Does every RFI lead to a change order? No. Most RFIs clarify the contract documents without changing the contract. An RFI may lead to a change order when its response adds, removes, or changes scope with a cost or schedule impact. --- ## /blog/what-is-a-submittal-in-construction/ ### What is a submittal in construction? > A submittal in construction proves that the product or method a subcontractor plans to install matches the specs before it's ordered or built. Learn the types, review chain, and why so many get rejected. A submittal in construction is a document or sample a subcontractor is required to send to the design team. In many cases, submittals function to prove that what the subcontractor intends to install matches the project specifications before it's ordered, fabricated, or built. The general contractor reviews it against the drawings and specs as a first pass before sending it to the architect or design team. The design team either approves it, approves it with notes, or rejects it and sends it back. Once a submittal is approved, the material or method it describes is locked in. Catching a mismatch before approval is a paperwork problem. Catching it after installation is a rework problem. ## What are the different types of construction submittals? The primary submittal types in construction include product data, shop drawings, operations and maintenance (O\&M) manuals, physical samples, third-party test reports, qualifications, warranties, certificates, and sustainability / LEED documentation. Product data sheets are the type Trunk Tools reviews most often, making up roughly 85.5% of the submittals on our platform, followed by third-party test reports (5.6%) and operation and maintenance manuals (2.9%). That mix reflects what shows up for review most on active projects, not a definitive breakdown of every submittal type across the industry. Beyond those, teams also submit shop drawings (fabrication-level drawings for items like curtain wall or ductwork), samples and mock-ups (physical pieces reviewed for finish, color, or texture), and transmittals (the cover document logging what was sent and when). Qualifications, which establish that a contractor or manufacturer meets the requirements for the job, are typically submitted early, before work begins, rather than at closeout. Sample and final warranties, certificates, and sustainability or LEED documentation round out the rest, and those cluster toward closeout, once the work they cover is actually complete. ## How does the submittal review workflow work, and who's responsible for each stage? The submittal moves through a chain: the manufacturer or supplier prepares it, the subcontractor reviews and stamps it, the general contractor's project engineer or assistant project manager runs the first-pass review against the drawings and specs, and the architect or engineer of record makes the final compliance call. The general contractor's first pass carries the most weight in practice, since it determines whether the design team sees a clean package or a flawed one. ## How long does a submittal review actually take? A thorough review by an early-career project engineer or assistant project manager can take anywhere from 20 to 30 minutes for a low-complexity submittal checked against a single spec section, up to 3 to 4 hours for a complex, multi-hundred-page package like door hardware. ## What are the most common reasons a submittal gets rejected? Compliance problems are the norm, not the exception. In Trunk Tools platform data, around 55% of reviewed submittals carry significant compliance gaps, and another 35% to 40% carry minor to moderate gaps that still need a human judgment call. The gaps aren't distributed evenly across trades. MEP divisions (mechanical, electrical, and plumbing) fail at nearly twice the rate of structural divisions, with non-compliance between 60% and 70%. Concrete sits at the other end, with the lowest non-compliance rate of any division at just 32%. The single largest driver of non-compliance is manufacturer source: an unapproved substitution instead of the specified product. The quality of the design firm's spec itself also plays an important role in the submittal process. A clear, well-written spec produces cleaner submittals long before a reviewer opens the package. ## What's the difference between a submittal, a shop drawing, product data, and a sample? Submittal is the umbrella term for many types of trade partner submissions for approval. A shop drawing is a fabrication-level drawing showing exactly how a component will be built or installed. Product data is the manufacturer's printed or digital spec sheet for a product. A sample is a physical piece of material, like a paint chip or a flooring swatch, submitted for approval of color, finish, or texture. All of these are logged and tracked through the same review process, and a submittal register typically lists which type each spec section requires. ## How long does the full submittal cycle take? The median submittal cycle, from upload to design team approval, commonly runs around 55 days on projects relying on manual first-pass review, and roughly 43% of submittals get "stuck," taking more than 60 days to close out. The bottleneck is a combination of the General Contractor’s team having the bandwidth and experience to complete the manual comparison against the spec, the design team's contractual window to review and provide a response to the submittal, and any additional time needed for revisions before resubmission. Fewer stuck submittals also means fewer delays for material procurement, deliveries, and installation. ## How does submittal review affect early-career project engineers? The people running first-pass review are often the least experienced on the team, which is exactly where the risk concentrates. Spec quality drives most of the variation in compliance rates project to project, but reviewer experience determines how much gets caught before the package reaches the architect. That gap between a junior and a senior reviewer is the real cost of putting first-pass review on the newest person on the team without the right tools to assist. ## How does Trunk Tools help with submittal review? TrunkSubmittal, Trunk Tools' submittal review agent, reads every new submittal against the applicable spec sections and prior RFI responses, flags what's non-compliant, and drafts a response to the trade partner before an issue ever reaches the design team or architect. In Trunk Tools platform data, projects using TrunkSubmittal have seen median cycle time drop from around 55 days to about 14 days, a 74% reduction. Further, the average time saved by a project engineer with fewer than five years of experience is 1.54 hours per submittal review on a large project, scaling from around 30 minutes on a simple submittal to 180 minutes on one requiring 12 or more spec requirements checked. ## Frequently asked questions **What is a submittal in construction used for?** A submittal proves that the actual product and installation plan a subcontractor intends to use matches the project specifications, so the design team can catch a mismatch before it's ordered or installed. **What is the difference between an RFI and a submittal in construction?** An RFI asks a question to clarify a drawing or spec. A submittal proposes a specific product, material, or method for approval against a spec that's already written. One resolves ambiguity; the other confirms compliance. **Who approves a submittal in construction?** The general contractor runs the first-pass review, but final compliance approval belongs to the architect or engineer of record. **What happens if a submittal is rejected?** A rejected submittal is returned to the subcontractor with the compliance gap noted, revised, and resubmitted, which restarts the review clock and can delay procurement if the item has a long lead time. **How many submittals does a typical construction project have?** Volume depends on project size and scope, but large commercial jobs regularly generate thousands of individual submittals over the project lifecycle. *Last updated August 21, 2026\.* *Sources: Trunk Tools platform data; Trunk Tools case studies and customer interviews.* ### Frequently asked questions #### What is a submittal in construction used for? A submittal proves that the actual product and installation plan a subcontractor intends to use matches the project specifications, so the design team can catch a mismatch before it's ordered or installed. #### What is the difference between an RFI and a submittal in construction? An RFI asks a question to clarify a drawing or spec. A submittal proposes a specific product, material, or method for approval against a spec that's already written. One resolves ambiguity; the other confirms compliance. #### Who approves a submittal in construction? The general contractor runs the first-pass review, but final compliance approval belongs to the architect or engineer of record. #### What happens if a submittal is rejected? A rejected submittal is returned to the subcontractor with the compliance gap noted, revised, and resubmitted, which restarts the review clock and can delay procurement if the item has a long lead time. #### How many submittals does a typical construction project have? Volume depends on project size and scope, but large commercial jobs regularly generate thousands of individual submittals over the project lifecycle. --- ## /blog/what-is-an-rfi-in-construction/ ### What is an RFI in construction? > An RFI in construction is a formal written question to the design team when drawings or specs don't give the field enough information to build. Here's how RFIs work, what fields they need, and how long responses take. An RFI in construction, short for Request for Information, is a formal written question a contractor sends to the design team when a drawing or a spec section doesn't give the field enough information to build correctly. The architect or engineer's written answer becomes part of the official project record, carrying the same weight as the drawings and specs it clarifies. Search "rfi meaning in construction" or "what is rfi in construction" and you'll find generic definitions borrowed from procurement, where an RFI is closer to a vendor questionnaire. An RFI for construction is different: not a sales tool, but a documented request that keeps a project moving without anyone guessing at dimension, intent, or code compliance. ## What triggers a construction RFI? Most RFIs in construction come from one of three places: a drawing that contradicts the specs, a detail that's missing entirely, or a field condition nobody could anticipate from a desk. A foundation wall hitting rock where the geotechnical report promised soil. A mechanical riser colliding with structural steel nobody flagged in coordination. Each becomes a question the contractor cannot answer alone and must route through the design team before work proceeds. ## What role does an RFI play in the project record, and what fields does it need? An RFI in construction isn't just a question and answer. It's a paper trail. If a dispute surfaces over cost, schedule, or scope, the RFI log is often the first place both sides look, because it documents what was unclear, when it was raised, and how it was resolved. To hold up as a record, a construction RFI needs a project name and number, a unique RFI number, the spec section or drawing sheet in question, a clear statement of the issue, a proposed solution if one exists, and a response-needed-by date. Skip a field and the design team usually sends it back, which restarts the clock. ## How does the RFI review workflow work, and how long should a response take? The RFI in construction moves through a consistent chain: a subcontractor or field team raises the question, a project engineer drafts it, the general contractor submits it, and the architect or engineer of record answers before it routes back to the field. Standard contract language, including the AIA A201 general conditions, sets no fixed number of days for that response; it calls for "reasonable promptness" unless the parties negotiate a specific limit, typically 7 to 15 calendar days in practice. In Trunk Tools platform data across active projects, the median RFI response wait is 6.3 days, inside most contractual windows. The real cost isn't just the roughly 30 minutes a project engineer spends finding the right spec section, framing the question, and formatting it, which adds up to hundreds of hours on a project running 900 RFIs. It’s also the 5–15 hours project managers and project engineers spend analyzing the response, cross-referencing documents, and determining the impacts of the response across many other scheduled activities that touch multiple trade partners. ## Are submitted RFIs always necessary? An embarrassing moment for a General Contractor is submitting a question that already has an answer. In Trunk Tools platform data, an estimated 17.2% of draft RFIs are already answered by previous RFI responses sitting in the project record, meaning the question never needed to be submitted. Architects or design teams might issue concise, snappy responses pointing the submitter to the project documents. A second failure mode is vague framing or a missing spec reference, which sends the RFI back for clarification and adds days to an already slow process. ## What happens after the RFI response comes back? The response isn't the finish line. A project engineer or project manager typically spends 5 to 15 hours cross-referencing specs, submittals, drawings, and the schedule to figure out what the answer changes on the project. Miss one conflict with an already approved submittal, and the result is rework. Trunk Tools platform data suggests this analysis window is where the largest share of time can be returned to the project team, with the potential to recover 80% to 90% of it. ## When does an RFI escalate to a change order, and how is it different from an RFP or RFQ? Most RFIs resolve with clarification alone. An RFI in construction becomes the seed of a change order when the answer reveals a scope, cost, or schedule impact outside the original contract, which is why flagging that impact on a well-formed RFI matters: it's the earliest warning a clarification might turn into a change. An RFI is also easy to confuse with an RFP or an RFQ. An RFP, a Request for Proposal, asks a firm to propose an approach and a price for scope not yet awarded. An RFQ, a Request for Quote or Request for Qualifications depending on context, asks for pricing or credentials on defined scope. All three show up on a construction project, but only the RFI is a daily, high-volume workflow tied directly to build execution. ## How does Trunk Tools help project teams manage RFIs? TrunkRFI, the RFI agent built on Cortex, Trunk Tools' construction intelligence layer, scans the full document set, including drawings, specs, and every prior RFI, before a draft reaches the design team, and flags the ones that don't need to go out. When an RFI still needs to be sent, the agent drafts it, leaving the project engineer a few minutes of review instead of a 30-minute build and recovering an estimated 20 to 25 minutes per RFI. The agent also analyzes the response once it comes back, cross-referencing it against the project record to surface what changed and what to do next. Torcon's Brian Laustsen said it directly: "I would like this on every single project I am ever on." Suffolk's Will Lapointe put it another way: "I asked TrunkRFI a question this morning and it helped us completely eliminate the need for an RFI that was asked by the trade." ## Frequently asked questions **What does RFI stand for in construction?** RFI stands for Request for Information. In construction, it refers to a formal question sent to the design team to clarify a drawing or a specification. **What is the meaning of RFI in construction?** An RFI in construction is a documented request for clarification when project drawings or specs don't give the field enough information to proceed correctly. **What is an RFI in construction used for?** It's used to resolve conflicts between drawings and specs, fill in missing details, and document field conditions the design team couldn't have anticipated, while creating a record of the decision. **Who is responsible for answering a construction RFI?** The architect or engineer of record answers the RFI, though it typically routes through the general contractor first and back again once answered. **How many RFIs does a typical construction project generate?** Volume varies by project size and complexity, but active projects with meaningful RFI activity can generate hundreds to well over a thousand RFIs over the life of the project. *Last updated August 21, 2026\.* *Sources: AIA A201, General Conditions of the Contract for Construction; Trunk Tools platform data; Trunk Tools customer interviews with Suffolk, Torcon, Cleveland Construction, and Gilbane.* ### Frequently asked questions #### What does RFI stand for in construction? RFI stands for Request for Information. In construction, it refers to a formal question sent to the design team to clarify a drawing or a specification. #### What is the meaning of RFI in construction? An RFI in construction is a documented request for clarification when project drawings or specs don't give the field enough information to proceed correctly. #### What is an RFI in construction used for? It's used to resolve conflicts between drawings and specs, fill in missing details, and document field conditions the design team couldn't have anticipated, while creating a record of the decision. #### Who is responsible for answering a construction RFI? The architect or engineer of record answers the RFI, though it typically routes through the general contractor first and back again once answered. #### How many RFIs does a typical construction project generate? Volume varies by project size and complexity, but active projects with meaningful RFI activity can generate hundreds to well over a thousand RFIs over the life of the project. --- ## /blog/what-software-do-gcs-use-for-submittal-reviews/ ### What software do general contractors use for submittal reviews? > Most GC submittal software logs and routes packages — it doesn't compare them to the spec. Here's how Procore, Autodesk Forma, Bluebeam, and AI-first tools like TrunkSubmittal actually differ. General contractors typically rely on some combination of manual processes and software for submittal reviews. Even on a project with modern project management software in place, a person, usually an early career project engineer or assistant project manager, still does the time-intensive comparison work: opening the submittal, pull up the relevant spec section, checking for any relevant RFI responses, and cross-referencing all these documents. Most existing software offerings organize that process rather than replacing it. ## What does manual submittal review actually look like? In practice, "manual review" doesn't mean working outside of software. It means a PE or APM opens the submittal, usually a PDF, inside whatever platform the project already runs, most often Procore, Autodesk Forma, or Bluebeam, pulls up the relevant spec section in a second window, and reads the two side by side to confirm the product, model number, or installation method actually matches what the spec calls for. The platform logs that the submittal came in, routes it to the right reviewer, and tracks its status. It doesn't do the comparison itself. That part still depends on a person, package after package, and it's where most of the time in submittal review actually goes. ## Broad project management platforms: Procore and Autodesk Forma Procore and Autodesk Forma (the platform formerly known as Autodesk Construction Cloud) are what most general contractors already use to manage the project. The appeal of either platform is that nothing about the submittal process lives in a separate system from the rest of the job. The tradeoff is that the review itself is still manual: the submittal log tells a project engineer what needs to be submitted by trade partners, but someone still has to open each submittal package and check it against the spec requirement line by line. ## Document markup specialists: Bluebeam Bluebeam organizes submittal packages by trade or spec section, routes each one through a defined reviewer sequence, and applies standardized stamps, approved, approved as noted, revise and resubmit, or rejected, so review decisions look the same no matter who's reviewing. Studio Sessions let multiple reviewers mark up and comment on the same submittal in real time, and linking a submittal directly to the drawing sheet it affects keeps field and office looking at the same current version instead of two different copies. The core product is built around markup, routing, and stamping rather than compliance checking. Someone still has to know what the spec requires before marking anything up, and there is no automated linking to relevant RFIs that might amend project specifications. ## AI-first compliance review: Trunk Tools Trunk Tools is one of the vendors building AI-first tools for construction, and TrunkSubmittal is its submittal compliance review agent. Instead of a person comparing the submittal to the spec by hand, TrunkSubmittal reads the submittal against the applicable spec sections and relevant RFI responses and flags what's non-compliant before it reaches the architect. In Trunk Tools platform data, around 55% of reviewed submittals carry a significant compliance gap, and another 35% to 40% carry a minor or moderate one, so an automated first pass tends to catch real issues rather than rubber-stamping paperwork nobody actually checked. TrunkSubmittal can be added as a step directly inside the submittal workflow teams already run in Procore or Autodesk Forma, writing the compliance report and status back to the project management system instead of requiring PEs and APMs to work from a separate tool. It works from the project's uploaded document set, serves as a first pass ahead of the architect's review, and a person still makes the final call before anything goes out. ## What should actually drive the decision? Category matters less than what the software actually does with the submittal once it arrives. A few questions are important to consider regardless of which type of tool you're looking at: Does it read the submittal's content and compare it against your spec sections and prior RFIs, or does it just track that a file was uploaded? Does it check against RFI responses in addition to specifications? Does someone still have to retype information back to the project management system? Pricing model is worth asking about, too. Some newer AI-assisted tools, including tools added onto older project management platforms, bill based on credits consumed, which means the cost is genuinely hard to predict before construction even starts, and it quietly discourages a team from using the tool as often as they should. A flat, predictable rate for unlimited usage removes that friction entirely, since the incentive shifts to making the tool worth using constantly rather than metering how often it gets touched. ## Will the field actually use it? Software that never gets adopted doesn't save anyone time, no matter which category it falls into. Will project engineers and assistant project managers use the software consistently instead of working from email and paper? With AI agents, the tool only earns its keep if the team trusts the output enough to act on it instead of re-checking everything by hand anyway, which usually comes down to whether the vendor’s tools have been tested against an evaluation dataset from real construction projects and trained the general contractor’s project teams to leverage the tool. ## Which one should a general contractor actually use? The realistic setup on most projects is layered rather than single-tool: a broad PM platform like Procore or Autodesk Forma to log and route every submittal, plus either a markup tool for manual review or an AI-first tool like TrunkSubmittal to take on the actual spec comparison. The question worth asking isn't "which software?" It's "who or what is actually completing the first-pass review?" If the answer is an early-career project teammate doing it from scratch on every submittal, that's where the time and the risk both concentrate, and it's the gap AI-first tools exist to close. ## About TrunkSubmittal Projects using TrunkSubmittal have seen median submittal cycle time drop from around 55 days to about 14 days, a 74% reduction, with the share of "stuck" submittals, the ones that take more than 60 days to close out, falling to between 0% and 4%. PEs and APMs save between 30 minutes and 3.5 hours per submittal review, depending on the complexity of the package received. Elliot Christiansen, SVP of Operations at Cleveland Construction, described the effect on staff this way: "TrunkSubmittal takes a PE or APM with little to no experience in the industry and gives them five-plus years of experience to work with. It drives efficiency, catches things some of our most senior PM staff doesn't look for, and ensures we aren't just passing paper to the architect to review." Cleveland Construction saved more than 790 hours and over $60,000 across four projects using TrunkSubmittal, and the faster reviews have already generated referral business from architects who noticed the difference. ## Frequently asked questions **Do general contractors need special software for submittal reviews?** Not necessarily. Many still review submittals manually inside whatever project management platform they already use, comparing each one against the spec by hand. Dedicated tools speed that comparison up rather than replace the underlying process. **What's the difference between a project management platform and a submittal review tool?** Platforms like Procore, Autodesk Forma, or Bluebeam log, route, and track the submittal workflow. A dedicated AI-first review tool like TrunkSubmittal, focuses on comparing the submittal's content against the spec and prior RFI responses as well. **Does Bluebeam replace a submittal management system?** No. Bluebeam organizes, routes, and stamps submittals as they move through review, but on its own it doesn't compare submittal content against your spec requirements the way an AI compliance tool does. **What is TrunkSubmittal?** TrunkSubmittal is an AI-first compliance review tool available to general contractors, built by Trunk Tools. It reads incoming submittals against the applicable spec sections and prior RFI responses and flags non-compliance before a submittal reaches the architect, and it can run as a step inside your existing Procore or Autodesk Forma workflow, writing the compliance report and status back to your project management system. *By the Trunk Tools team. Last updated August 27, 2026\.* *Sources: Trunk Tools platform data; Trunk Tools case study with Cleveland Construction; Procore, Autodesk Forma, and Bluebeam product pages.* ### Frequently asked questions #### Do general contractors need special software for submittal reviews? Not necessarily. Many still review submittals manually inside whatever project management platform they already use, comparing each one against the spec by hand. Dedicated tools speed that comparison up rather than replace the underlying process. #### What's the difference between a project management platform and a submittal review tool? Platforms like Procore, Autodesk Forma, or Bluebeam log, route, and track the submittal workflow. A dedicated AI-first review tool like TrunkSubmittal, focuses on comparing the submittal's content against the spec and prior RFI responses as well. #### Does Bluebeam replace a submittal management system? No. Bluebeam organizes, routes, and stamps submittals as they move through review, but on its own it doesn't compare submittal content against your spec requirements the way an AI compliance tool does. #### What is TrunkSubmittal? TrunkSubmittal is an AI-first compliance review tool available to general contractors, built by Trunk Tools. It reads incoming submittals against the applicable spec sections and prior RFI responses and flags non-compliance before a submittal reaches the architect, and it can run as a step inside your existing Procore or Autodesk Forma workflow, writing the compliance report and status back to your project management system. --- ## /guides/ai-vendor-questionnaire/ ### The Ultimate AI Vendor Questionnaire: What to Ask Before You Buy > A practical questionnaire for construction leaders evaluating AI vendors — covering operational fit, technical depth, long-term viability, and data security. Construction leaders are bombarded with AI promises, but most lack the framework to separate transformative technology from hype. This guide gives you the exact questions to ask any vendor — across operational fit, technical depth, long-term viability, and data security — so you can invest with confidence and put AI to work where it matters most: on the jobsite. ## How to use this questionnaire 1. **Before** your next vendor meeting or RFP, share this guide with your evaluation team and align on the questions. 2. **During** the demo, ask these questions directly. Watch for specificity — vendors with real depth welcome scrutiny. 3. **After** the evaluation, score each vendor against the framework and compare results side-by-side. Let the data, not the demo, drive the decision. ## Not all AI is created equal Before diving into the questions, it helps to know that “AI” covers a wide spectrum: 1. **White-label wrappers** — branded interfaces on top of general-purpose models like ChatGPT or Claude, with no construction-specific intelligence. 2. **Prompt engineering layers** — lightweight construction framing on foundational models, still without industry training at scale. 3. **Adapted but incomplete** — some fine-tuning or custom pipelines, but weak preprocessing of drawings, specs, and schedules. 4. **Workflow-integrated construction AI** — agents trained on real construction documents, triggered automatically, and built to offload tedious project work. The questionnaire is designed to show you where any vendor sits on that spectrum. ## What’s in the full PDF The downloadable questionnaire expands each question with **why it matters**, **what “good” looks like**, and space for a **vendor response**, organized into: - Functionality and use case - Technical depth and construction fit - Long-term viability - Commercial model - Data privacy and security - Compliance, legal, and risk management It also includes a simple scoring guide so your team can classify vendors as worth partnering with, worth using only at a lower price, or not worth pursuing. Download the PDF for your RFP folder, or keep this page open as you work through vendor evaluations. ### Frequently asked questions #### What should construction companies ask AI vendors before buying? Ask about operational fit (does it solve a real jobsite or office workflow?), technical depth (construction-trained models, multimodal reasoning, preprocessing), deployment model (vendor-maintained agents vs. DIY prompts), pricing predictability, data privacy and isolation, and compliance (SOC 2 Type II, encryption, AI governance). #### How can you tell real construction AI from a white-labeled chatbot? Look for construction-specific training and preprocessing across drawings, specs, submittals, and RFIs; automatic agent triggers from your project management system; multi-file multimodal reasoning; and turnaround measured in minutes. White-label wrappers and prompt-only layers cannot reliably cross-reference project documents or read drawings. #### Why does data privacy matter when evaluating construction AI? Project data often includes proprietary pricing, means and methods, and owner-sensitive information. Strong vendors train only with explicit permission, logically isolate each project, use zero-retention agreements with third-party model providers, and can show SOC 2 Type II controls plus encryption at rest and in transit. #### How should teams use an AI vendor questionnaire? Align the evaluation team on the questions before demos or RFPs, ask them directly during vendor conversations, score answers side-by-side, and let the framework — not the demo — drive the decision. --- ## /guides/build-vs-buy-ai-construction/ ### Build vs. buy AI for construction: how to decide > Should construction companies build their own AI or buy a construction AI platform? A decision framework covering drawings, documents, pricing, and adoption — with the workflows where each approach actually works. Construction companies deciding between building their own AI tools and buying an AI platform built for construction have to take into account the specific workflow they're trying to improve, the quantity and type of documents that workflow includes, and whether the team has the capacity to prepare clean data before asking AI to act on it. There is no universal answer. Most of the leading firms evaluating AI today end up doing both, building for some workflows and buying for others. ## What build vs. buy means for AI in construction "Build" means standing up your own tools on top of foundational models like the ones behind ChatGPT, Claude, or Gemini, then prompting them to handle a construction workflow such as daily log generation, RFI drafting, or contract review. "Buy" means licensing a platform a vendor has already built, trained, and validated for specific workflows. The question now comes up in nearly every procurement conversation, technology committee review, and RFP construction teams run in 2026\. ## The case for building your own AI tools for construction ### Pros of building AI in-house 1. **Full flexibility to customize.** A team can shape a tool to its exact workflows instead of adapting its process to fit someone else's product. 2. **Puts your own project data to work.** The company controls how its data is used, on its own terms. 3. **Not limited by a vendor's roadmap.** Internal priorities decide what gets built next, not a vendor's release schedule. 4. **Fewer point solutions to manage.** A strong internal platform can reduce the number of separate tools a company has to buy, manage, and integrate. ### Cons of building AI in-house 1. **No construction context built in.** Foundational models arrive with no pre-programmed knowledge of construction, so an internal team has to teach the model what "good" looks like, submittal by submittal, spec section by spec section. 2. **Weak performance on construction drawings.** Drawings communicate through geometry, symbols, and revision clouds. Vision models that read them accurately take years of focused, construction-specific training to build, and general-purpose models are still weak at it. The buyer question "can AI read construction drawings?" is really a question about how much time, effort, and investment the vendor has put in. 3. **Unpredictable, consumption-based spend.** Most AI is priced by the token or credit, making spend hard to forecast as usage scales, which complicates budgeting and pressures margins. 4. **Shifts the burden to inexperienced teams.** Building in-house moves the ongoing work of maintaining and troubleshooting AI systems onto staff who may be new to it, and every iteration consumes more tokens. 5. **Untested rather than proven.** A tool built in-house is validated for the first time on a company's own live projects, not across hundreds of other jobsites. [MIT's NANDA initiative studied enterprise AI adoption in 2025](https://cloudelligent.com/wp-content/uploads/2026/02/v0.1_State_of_AI_in_Business_2025_Report.pdf) and found that AI initiatives built with specialized outside vendors or implementation partners succeeded roughly 67% of the time, compared with roughly 33% for AI tools built internally. That gap tends to widen in specialized industries like construction, where the underlying data is messier and the workflows are more idiosyncratic than in general back-office software. ## The case for buying a construction AI platform ### Pros of buying a construction AI platform 1. **AI purpose-built for construction.** Many AI companies founded by people who come from the construction industry are developed specifically for common workflows, not adapted from general-purpose AI use. 2. **Reads construction drawings** and connects them to the rest of a project's documents, something generic AI still struggles with. 3. **Predictable annual pricing.** For some vendors, a subscription is a flat annual fee rather than metered by token, which matches how construction companies already budget and contract. 4. **Support for change management.** Some vendors provide customer support and hands-on AI change management consultation, which is usually the hardest part of any technology rollout, not the technology itself. 5. **No burden of building or maintaining agents.** Project engineers and superintendents spend their time on the job instead of tinkering with AI experiments. ### Cons of buying a construction AI platform 1. **A crowded market.** Many products only solve one or two workflows, which risks tool overload and can hurt adoption if teams end up juggling too many logins. 2. **Limited influence over the roadmap.** A single company's input is never the only factor shaping what a vendor builds next. 3. **Hard to verify in a demo.** It can be genuinely difficult from a 30 minute demo to tell a proven agent trained on real construction data from a thin wrapper around a general-purpose model. 4. **Vendor risk.** Some startups get acquired or wind down, which can disrupt service. ## Why many contractors choose both build and buy for AI In Trunk Tools platform data, project teams routinely lose 30% to 50% of their day searching for information buried across disconnected documents, and submittal review alone can consume 50% to 60% of an assistant project manager's time. Common, repeatable challenges at that scale are perfect for AI tools for construction. The furthest-ahead firms buy a platform for document-heavy, high-volume workflows with a trained, validated agent, then reserve internal development for the workflows unique to how they run projects and their business. The starting point either way is the same: get the underlying project data clean and structured enough for AI to use before asking any system, built or bought, to act on it. ## Where Trunk Tools fits Cortex, Trunk Tools' AI platform for construction, is built specifically to read, connect, and act on the documents on a project, including the drawings that general-purpose AI struggles to interpret. Agents like TrunkSubmittal and TrunkReview arrive pre-trained and validated on real construction projects, so a team is not testing an unproven build on its own live jobsites. Pricing is predictable and annual, not metered by token, which matches how construction companies already budget and contract. Elliot Christiansen, former SVP of Operations at Cleveland Construction, put it this way when asked why his team didn't just build agents on top of the AI already available in its document storage platform: "What Trunk Tools will build over the next three years is something we'll never be able to do with build-your-own agents in Box. It's making our project teams far more efficient than we could on our own." ## FAQ **Should construction companies build their own AI or buy a platform?** It depends on the workflow. Buy for document-heavy, high-volume workflows like submittal review, RFI drafting, and drawing review, where trained and validated platforms already exist. Consider building only for workflows that are truly unique to how a specific company runs its projects, and only with a team that has the capacity to maintain what it builds. **What are the risks of building AI in-house for construction?** The main risks are unpredictable, consumption-based AI spend as usage scales, a lack of employees with sufficient AI and machine learning experience, weak performance on construction drawings, and shifting the ongoing burden of building and maintaining AI systems onto staff who may be new to it. **Why do generic AI models struggle with construction drawings?** Drawings communicate through geometry, symbols, spatial relationships, and revision clouds rather than plain text. Training a vision model to read them accurately, including changes an architect never clouded, takes years of focused, construction-specific data labeling and development, making it quite expensive. **How is AI usually priced, and why does that matter for construction budgets?** Most AI tools charge per token or credit consumed. That model makes spend hard to predict as adoption grows across an organization, which complicates annual and project-level budgeting in a way that construction's fixed-price and GMP contract structures are not built to absorb. **Can construction companies combine build and buy?** Yes, and many leading firms do. They buy a platform for high-volume, document-heavy workflows and reserve internal development, if any, for the workflows unique to their business. **What is a construction AI platform?** A construction AI platform is software built specifically to read, connect, and act on the documents and drawings on a construction project, as distinct from a general-purpose AI model like ChatGPT, Claude, or Gemini, which arrives with no construction context and no ability to read drawings accurately. A construction AI platform typically ships with pre-trained agents for common workflows (submittal review, RFI drafting, drawing review, spec analysis), predictable annual pricing, and change-management support to help teams adopt it. **Which AI is best for construction?** The right answer depends on the workflow. For document-heavy, high-volume workflows like submittal review, RFI drafting, and drawing review, a trained construction AI platform (like Trunk Tools' Cortex) will outperform a general-purpose model that hasn't seen construction data. For narrow, company-specific workflows, an internal build on a foundational model may fit better, provided the team has capacity to maintain it. Most leading contractors combine the two. --- *Sources: MIT NANDA initiative, "The GenAI Divide: State of AI in Business 2025"; Trunk Tools platform data; Cleveland Construction case study, trunktools.com. Last updated September 2026\.* ### Frequently asked questions #### Should construction companies build their own AI or buy a platform? It depends on the workflow. Buy for document-heavy, high-volume workflows like submittal review, RFI drafting, and drawing review, where trained and validated platforms already exist. Consider building only for workflows that are truly unique to how a specific company runs its projects, and only with a team that has the capacity to maintain what it builds. #### What are the risks of building AI in-house for construction? The main risks are unpredictable, consumption-based AI spend as usage scales, a lack of construction context that the internal team has to supply from scratch, weak performance on construction drawings, and shifting the ongoing burden of building and maintaining AI systems onto staff who may be new to it. #### Why do generic AI models struggle with construction drawings? Drawings communicate through geometry, symbols, spatial relationships, and revision clouds rather than plain text. Training a vision model to read them accurately, including changes an architect never clouded, takes years of focused, construction-specific development. #### How is AI usually priced, and why does that matter for construction budgets? Most AI tools charge per token or credit consumed. That model makes spend hard to predict as adoption grows across an organization, which complicates annual and project-level budgeting in a way that construction's fixed-price and GMP contract structures are not built to absorb. #### Can construction companies combine build and buy? Yes, and most leading firms do. They buy a platform for high-volume, document-heavy workflows and reserve internal development, if any, for the narrow set of workflows unique to their business. #### What is a construction AI platform? A construction AI platform is software built specifically to read, connect, and act on the documents and drawings on a construction project — as distinct from a general-purpose AI model like ChatGPT, Claude, or Gemini, which arrives with no construction context and no ability to read drawings accurately. A construction AI platform typically ships with pre-trained agents for common workflows (submittal review, RFI drafting, drawing review, spec analysis), predictable annual pricing, and change-management support to help teams adopt it. #### Which AI is best for construction? The right answer depends on the workflow. For document-heavy, high-volume workflows — submittal review, RFI drafting, drawing review — a trained construction AI platform (like Trunk Tools' Cortex) will outperform a general-purpose model that hasn't seen construction data. For narrow, company-specific workflows, an internal build on a foundational model may fit better, provided the team has capacity to maintain it. Most leading contractors combine the two. --- ## /guides/why-trunk-tools-vs-generic-llms/ ### Why Trunk Tools vs. Generic AI > Generic AI models weren’t built for construction. Here’s where they fall short — and how Trunk Tools closes the gaps on drawings, workflows, pricing, and adoption. Generic AI models, sometimes referred to as a “foundation models”, weren’t built for construction, and the gaps show up in important ways: they aren’t trained on construction data, can't reliably read construction drawings, don’t connect your documents or workflows, have unpredictable costs, and put the burden on you to learn prompt engineering and agent building. ## Generic AI isn’t trained on construction data General-purpose large language models (LLMs), like ChatGPT, Claude, or Gemini, are trained on an impressive amount of data that is publicly available on the internet. However, construction data in drawings, specs, submittals, and RFIs is normally proprietary and largely absent from what LLMs have access to. As a result, they struggle the moment a question or task requires connecting multiple documents, processes, and people the way an experienced project manager or superintendent would. ## Reading a drawing isn't reading text One specific implication of this lack of training data is the [known limitations with construction drawings](https://aecv-bench.com/), arguably the most critical documents on a project. A construction drawing communicates through geometry, symbols, line weights, and spatial relationships, not sentences. A swing arc means a door opens one way; the same opening without an arc means something else entirely. Ask multiple general-purpose AI models to count the doors on a single floor plan, on a single sheet, and you’ll get a wide range of responses that all conflict with what an experienced reviewer would count. Reading text on a PDF drawing alone, in the title block or markups, does not solve this critical problem for AI adoption among construction teams. ## No preprocessing or agent handoffs for connected workflows A generic LLM has no persistent understanding of your project. Every question forces it to re-read and re-interpret the raw documents from scratch, because nothing was structured or connected ahead of time into a project-specific knowledge graph. The cost of reprocessing the same documents over and over shows up in your usage bill, growing right along with your document set. Further, without this connected knowledge graph for each project, even valuable self-coded tools fail to close loops across a real construction workflow. For instance, two separate skills or agents to build a submittal register and review trade partner submittals should have seamless handoff given the connected workflow. With generic AI models, each tool runs without a shared understanding of the project to link them. ## Pricing and enablement costs work against you Generic AI models bill on a credit-based consumption model: you're charged for the text and documents you put in and the output the AI generates. It's nearly impossible to predict how many credits a question or task will take, which makes billing unpredictable, a problem for a business that needs to know its costs for the year and its project budgets well before construction begins. That unpredictability discourages your team from using the tool for fear of hitting a limit. ## Building it yourself is a multi-year bet Some technology teams look at a generic model and assume they can build the construction layer themselves. In practice, to overcome the aforementioned challenges, you would need to hire machine learning engineers, label training data to input into the models, and build a vision model to unlock AI for reading construction drawings. To build and maintain custom agents, team members must learn adequate prompt engineering and agent configuration, and relearn every time the underlying model changes. It's the same reason most GCs don't build their own scheduling or accounting software: some problems are worth buying purpose-built solutions for. Beyond building, the AI era is still fresh, and most construction workers will require significant training and enablement to navigate this change. Foundational model providers are not qualified to provide this change management support. They can’t train your project teams, and they certainly won’t show up to your jobsites. ## How Trunk Tools is different Trunk Tools closes each of those gaps by design. We've trained proprietary models on real construction data since 2021 so our models learn the relationships between drawings, specs, submittals, and RFIs that a generic model never sees. That includes a vision layer trained on more than 400 object types and 2 million-plus labels specifically to read geometry and symbols in drawings the way a builder does. Cortex, Trunk Tools' construction intelligence layer, preprocesses each project's full document set once, up front, into a knowledge graph connecting every drawing, spec, submittal, and RFI before anyone asks a question or any agent runs. That shared understanding is what lets our agents hand off to each other automatically instead of running in isolation. For example, TrunkReview detects a new bulletin the moment it lands in the project management system, surfaces every change, including the ones the architect didn't cloud, and hands that finding straight to TrunkRFI with full context preserved, so the agent drafting the RFI isn't starting from scratch either. Trunk Tools also prices with one predictable, flat annual rate for unlimited usage and users, so cost never depends on how many questions your team asks or how many credits a task happens to burn. And because software alone doesn't drive adoption, our customer success managers onboard your team, train them, and even visit your jobsites to ensure success. None of this requires your team to learn prompt engineering or agent configuration. Trunk Tools' agents are field-ready from day one of onboarding. As one Suffolk superintendent put it: "I can focus on strategy and higher-level tasks with the time I've gained back." ### Frequently asked questions #### Why isn’t generic AI enough for construction? Generic models aren’t trained on proprietary construction data, struggle to read drawings as geometry and symbols, lack a project knowledge graph for connected workflows, bill unpredictably on consumption, and leave prompt engineering and change management to your team. #### Can general-purpose AI models read construction drawings? Not reliably. Drawings communicate through geometry, symbols, line weights, and spatial relationships. Text extraction from title blocks or markups is not the same as understanding the sheet the way a builder does. #### How is Trunk Tools different from ChatGPT or other foundation models? Trunk Tools trains proprietary models on construction data, includes a vision layer for drawings, preprocesses each project into Cortex (a knowledge graph), runs agents that hand off across workflows, prices with a flat annual rate, and supports field adoption with customer success — without requiring prompt engineering. --- ## /guides/why-trunk-tools-vs-pms-ai/ ### Why Trunk Tools vs. the AI built into your project management system > PMS-embedded AI often falls short at scale. Here’s why — and how Trunk Tools is built differently for construction data, drawings, pricing, and adoption. Most project management systems (PMS) have added AI features in the last couple of years: a chat box, a search bar, a few "agents." Since your PMS already holds much of your project data, it's tempting to assume that's enough. In reality, PMS-embedded AI usually falls short of adoption at scale for five reasons: the models underneath are rarely trained on construction data, the pricing model is unpredictable, training and change management get billed as expensive add-ons, project documents were never preprocessed into anything resembling a project knowledge graph, and don’t handle construction drawings well. ## A hard hat on a generic AI model Most AI features inside a PMS are general-purpose models, like ChatGPT, Claude, or Gemini, with a cost markup: the same technology available to any industry, pointed at your construction documents. These models weren't trained on drawings, specs, submittals, and RFIs as a connected system, because construction data is proprietary and largely absent from what's publicly available on the internet. As a result, they struggle the moment a question or task requires connecting multiple documents, processes, and people the way an experienced project manager or superintendent would. ## Pricing and enablement costs work against you Many of these features run on a credit-based consumption model: you're charged for the text and documents you put in and the output the AI generates. Some even charge you daily credits merely to store your data in their AI infrastructure before any work is actually done. It's nearly impossible to predict how many credits a question or task will take, which makes billing unpredictable, a problem for a business that needs to know its costs for the year and its project budgets well before construction begins. That unpredictability discourages your team from using the tool for fear of hitting a limit, and it gives the vendor no reason to make the tool more efficient, since the more credits you burn, the more they earn. Rollout usually costs extra, too. Training and change management are often sold as a separate statement of work, so the vendor gets paid whether or not the field ever adopts the tool. ## No preprocessing, no real knowledge graph An AI chat window that finds a spec section isn't the same as a system that understands how that section relates to the RFI that amended it, the submittal meant to satisfy it, and the bulletin showing where it is to be installed. That requires preprocessing: structuring unstructured data across project documents, extracting the relevant information, and mapping each data point to every other relevant one before anyone uses AI. In this scenario, a door tag is already linked to its schedule, spec section, and any open RFIs. Skip that step and the model has to re-extract everything at every query, which drives up both inaccuracy and cost. A PMS running a generic model with no additional training can't build that knowledge graph, so its AI can’t accurately execute construction-specific workflows it was never built for. ## Failing to meet construction teams where they are Construction teams are busy and construction documentation is excessive. AI that only works when someone remembers to prompt it won't get adopted at scale. A better model triggers automatically: a new submittal, RFI response, or bulletin landing in the project management system should kick off an AI-powered review on its own, so the team starts from a thorough first pass instead of a blank chat window. Generic AI also has [known limitations with construction drawings](https://aecv-bench.com/), arguably the most critical documents on a project. Unless AI can read the drawing itself, not just the text in a title block or a markup, it's inherently limited for teams who live in the drawings. In Trunk Tools platform data, roughly 10% to 20% of meaningful drawing revisions go unclouded by the architect, meaning a text-only tool will never catch them. ## How Trunk Tools solves these challenges Trunk Tools combines the best of foundational AI models with our own proprietary models, built specifically for construction data and workflows since 2021, using real project data from hundreds of projects with our customers' explicit permission. That training data is always deidentified and aggregated, so nothing proprietary leaves a project record. Before a project begins, we ingest and structure data into a project "brain" we call Cortex, so agents and queries produce reliable answers instead of best guesses. Trunk Tools prices with one predictable, flat annual rate for unlimited usage and users, so our incentive is to make the tools valuable enough that customers adopt them portfolio-wide, not to meter every question. Training and change management are part of that same commitment: our customer success managers onboard your team, train them, and meet with them as often as it takes to drive real adoption. We even come to your jobsites to deliver training in person at no additional cost. An AI feature bolted onto your project management system will always be limited by a model that was never trained on construction data or workflows. Trunk Tools was built to unlock what AI can do specifically for your projects. *Last updated August 21, 2026.* ### Frequently asked questions #### Is the AI in my project management system enough? Usually not for portfolio-scale adoption. PMS AI is often a general-purpose model with a markup, unpredictable consumption pricing, limited preprocessing into a project knowledge graph, weak drawing understanding, and change management sold as an expensive add-on. #### What’s the difference between PMS AI and a construction AI platform? A construction AI platform like Trunk Tools trains on construction data, preprocesses project documents into a knowledge graph (Cortex), triggers agents from document events, reads drawings with purpose-built vision, and includes flat pricing plus adoption support — rather than bolting a chat box onto the system of record. #### Why does preprocessing matter for construction AI? Without structuring drawings, specs, submittals, and RFIs into a connected project graph up front, the model re-extracts context on every query. That drives up cost and error rates and prevents reliable cross-document workflows.