An AI tool is a clerk, not a superintendent, not an architect, and not a contract administrator. Used that way, it can save time. Treated as an authority, it can help you build the wrong thing on the strength of a very confident paragraph.

The companion article, “Where AI Helps,” covers the good uses: summaries, draft transmittals, and searching a folder, always checked against the source PDF. This article is the other half: the places where you should not trust the answer, no matter how polished it looks.

It cannot tell you which drawing is current

Current is not a property of a PDF’s contents. It is a filing rule. The current set is the set in 02_Drawings_Current, with a date, put there by a person who moved yesterday’s sheets into Superseded.

A chatbot can read a title block or compare two files you upload. It does not know whether a later bulletin arrived this morning, or whether the official set is the packet in the folder and not the attachment in an email. Google’s own help for Gemini in Drive notes that a folder summary might not include every file in the folder. A tool that has not looked at every file cannot certify that you have the latest set. Look in the current-set folder. If that folder is messy, fix the folder.

It should not approve a submittal, or pretend it already did

Approval is a decision by the design team, or by whoever the contract names. A stamp, a status, and the notes on a returned copy are the record. An AI description of a product data sheet is not a review, and it is not “approved as noted.”

Do not ask a tool to approve, reject, or “stamp” a submittal, and do not let it generate a professional seal or signature. Do not let it fill the status column in your log unless a person has read the returned copy and entered that status.

Watch for two failure modes (I will not invent a statistic for either). First, the model skips markups, revision clouds, handwritten notes, or the comments that make an “approved as noted” different from a clean approval. Second, it invents a sheet number, a dimension, a model number, or a “per spec” claim that is not in the source. If those notes never reach the installer, you can still build the wrong thing.

It should not be the last word on contract or notice language

Do not let a chatbot be the final author of a notice, a change-order letter, a claim narrative, or a reading of your contract. It can draft a plain-language outline for you to edit. A person who understands the job, and a construction attorney when the dollars or the rights matter, should finish anything you would have to defend later.

This is not legal advice, and the tool’s advice is not legal advice either. Arizona prompt-pay clocks, preliminary notices, and lien waivers have specific statutory forms and deadlines. A confident summary of A.R.S. § 33-992.01 or the Prompt Payment Act is still something to check against the statute, the contract, and counsel. See the pay-app checklist (Arizona Pay App and Lien Waiver Packet Checklist) for a filing habit, not a legal opinion. The statutes named here are Arizona’s. Other states differ, so check your own state’s rules.

A question you would have asked a lawyer should not be pasted into a consumer chatbot as a shortcut. When in doubt, ask the lawyer.

Other places to keep a human in the loop

  • Logs and drawing lists. If you let a tool rewrite an RFI log, a sheet index, or a transmittal list, a person verifies every number and date before anyone uses it.
  • Quantities, dimensions, and “what the spec requires.” Read the spec and the sheet. The model is good at sounding like it already has.
  • Engineering or code judgments. A tool should not be the source of a structural, mechanical, electrical, or code decision.
  • Anything under an NDA, and full drawing sets. Even on a business plan, think before you upload an entire set, a bid tab, or owner correspondence. Follow the contract.
  • The pour / cover-up review. Open RFIs are a human check the afternoon before. Do not ask a summary to certify that “nothing is open for Level 1.”

The twice-weekly cadence still belongs to you or to the person you hire to keep the file. If you want help keeping that file honest, including a simple rule for where AI may assist and where it may not, I can set up the job file, run the logs on a retainer, or prepare closeout. The files stay yours. The current set stays a human rule.

If you want help, not just a checklist

Some jobs run fine on a clean file and a superintendent who gives the log fifteen minutes twice a week. Others do not: revisions are moving fast, closeout is already behind, or the field simply has no hours left for paperwork.

That is where I come in. I set up the job file, run the logs on a retainer, or prepare closeout before the scramble starts. Your files stay yours, and there is no software contract to sign.

Email travis@builtonrecord.com Get the free Job File Kit