Key Takeaway
An assistant connected to your project documents answers PM questions in seconds with a citation to the spec section, RFI or submittal, and respects project-level access.
A superintendent calls from site. The door hardware sub wants to substitute a different closer because the specified one has a 10-week lead time. Is that allowed? Did the architect already address it in an RFI? Was there a submittal that locked in the product?
The answer exists. It’s somewhere in Section 08 71 00, or in RFI 112, or in a submittal response from four months ago, or in an email thread that never made it into the project management system. Finding it takes the project manager an hour, maybe two. Then the next question comes in.
Why project information is so hard to find
A mid-size commercial project generates thousands of documents. The project manual alone can run past a thousand pages across dozens of spec sections. Add drawings, RFIs, submittals, change orders, meeting minutes and daily reports, and the volume grows every week the job runs.
Platforms like Procore and Autodesk Construction Cloud keep those documents organized. They’re good at storing, routing and tracking status. Their search is mostly keyword-based, and keywords break down fast in construction. The spec says “door closer.” The RFI says “overhead closer.” The sub’s email says “the LCN unit.” A keyword search for one won’t reliably find the others.
There’s also the problem of answers spread across documents. A substitution question might need the spec section, the substitution procedures in Division 01, a related RFI and the approved submittal. No single document holds the answer. The PM has to assemble it.
Experienced PMs carry a lot of this in their heads. That works until they move to another project, go on vacation or leave the company. Then the knowledge leaves with them.
What the assistant does
The assistant we build connects to your project documents and answers questions in plain language, with citations to the exact source.
Plain-language questions, cited answers
A PM types: “Can the hardware sub substitute the closer on the second-floor doors?” The assistant pulls the relevant spec section, the substitution requirements from Division 01, any RFIs that mention closers or those door numbers, and any related submittals. It answers with what the documents say and links each statement to its source: spec section and paragraph, RFI number, submittal number and revision.
If the documents don’t answer the question, the assistant says so. It doesn’t fill gaps with a plausible guess. For a PM, “I couldn’t find this, here’s what’s closest” is far more useful than a confident wrong answer.
Search that understands construction language
The assistant matches on meaning, not only exact words. A question about “fire-rated door frames” finds content about “labeled hollow metal frames.” A question about a room number finds the drawings, finish schedule entries and RFIs that reference that room. It understands the structure of a project manual, so it knows that Part 2 of a spec section covers products and Part 3 covers execution.
Connected to your project management system
The assistant pulls RFIs, submittals and their status directly from your project management platform, so answers reflect the current state of the job. If an RFI is still open, the answer says it’s open. If a submittal was revised and resubmitted, the assistant cites the latest approved version and notes that earlier versions exist.
Search across past projects
The same assistant can search completed projects. A PM starting a new hospital job can ask how a specific infection control requirement was handled on the last one, or which RFIs came up repeatedly on similar buildings. Lessons learned stop living only in close-out binders.
Where people stay in control
The assistant answers questions. It doesn’t make decisions. Approving a substitution, responding to an RFI or accepting a submittal stays with your PMs and the design team, following your normal process.
Access follows your project permissions. A sub’s coordinator who only has access to their own scope sees only those documents. Owner-confidential information, pricing and internal notes stay restricted to the people cleared to see them. We build that permission layer into the assistant itself, so nobody gets an answer drawn from a document they can’t open.
What it takes to build this properly
A demo of document Q&A is easy. Upload ten PDFs to a chatbot and ask questions. A tool your PMs rely on during a live project is a different build.
Document quality. Specs arrive as clean PDFs, scanned pages, or exported Word files with broken formatting. Drawings carry information in title blocks, schedules and callouts, not paragraphs. The ingestion pipeline needs to handle all of it and keep track of which revision each document is.
Revision control. Construction documents change constantly. Addenda, bulletins, ASIs and change orders supersede earlier content. The assistant needs to know what’s current and say clearly when it’s citing superseded information.
Citations that hold up. PMs need to verify an answer in seconds. Every claim links to a specific location in a specific document. If the citation doesn’t support the answer, the tool can’t be trusted.
Permissions. Mirroring the access rules from your project management platform, per project and per user, is one of the harder parts of the build. It’s also the part that makes the tool safe to deploy company-wide.
Freshness. New RFIs and submittals arrive daily. The assistant syncs with your systems on a schedule so it’s working from today’s documents, not last month’s.
What we need from you
- Access to your document storage and project management platform.
- A few active or recently completed projects to start with.
- A PM or two to test the assistant with real questions and flag where it falls short.
You don’t need to reorganize your documents first. Handling the mess is part of the build.
How the build works
You describe the problem in plain language. We work with you to turn it into a clear spec and scope, including which systems to connect and which projects to start with.
You get a fixed price tied to what gets delivered, agreed before any build work begins. You don’t pay for hours.
AI agents do the build, supervised by senior engineers who own the architecture, the integrations and the review of every piece of code. You get a production-grade assistant, deployed and connected to your systems, ready for your PMs to use on live projects. Delivery takes days to weeks, not months.
Frequently asked questions
Does this work with Procore or Autodesk Construction Cloud?
Yes. We connect to the platforms you already use through their APIs, along with shared drives or document storage where your project files live.
What happens if the assistant gives a wrong answer?
Every answer includes citations, so PMs can verify it before acting. When the documents don't clearly answer a question, the assistant says so instead of guessing. Users can flag bad answers, and we use those flags to improve retrieval.
Can subcontractors or owners use it?
They can, with access limited to the documents they're allowed to see. Most companies start with internal PMs and superintendents, then extend access once permissions are tested.
Is our project data used to train AI models?
No. Your documents stay in an environment you control and are not used to train third-party models.
