CSI Spec Summary
Paste a CSI MasterFormat section number or text; get a structured summary: scope, Part 1/2/3 highlights, submittal checklist, common pitfalls, adjacent sections that travel with it.
The old paradigm is out. The new paradigm is AI. AI automation is InTouch AI — and the paperwork that wakes you at 3 AM stops being your job. You describe it. AI runs it.
Submittals, RFIs, drawing revisions, sub COIs, lien deadlines, project status — point it at your Sheets and Drive and walk away.
InTouch AI is a general-purpose automation platform with AI at its center — not bolted onto the side. A general AI-native engine does what a specialized construction-software bolt-on does, and then does the next workflow too. The reverse never happens: a config-era tool can't grow an AI core. Below is what InTouch does to construction workflows, built from example skills and jobs in the InTouch Hub. The same platform runs every other industry and handles the workflows we haven't bothered to publish yet.
These examples are real YAML jobs and AI skills. They read the Google Sheets and Drive folders you already maintain and digest to whatever channel you live in. Backed by 25+ years of Fortune-500 production, RBAC, audit trails, and an encrypted credential vault — AES-256, referenced by name, never pasted into a job, never exposed even to the AI itself. Your service account JSON is locked behind the same trust floor that ran in production before "AI automation" was a phrase.
Starting points, not shrink-wrap. Every project has its own paperwork rhythm; you adapt the job to yours. Read the README and the YAML before you run it — then make it your own.
The config-era checklist is dead. A spreadsheet you update once a week is not a system; it's a liability with your name on it. Here's what the old way costs you every night:
You've got 80 open submittals across 4 active projects. Nobody knows which ones are aging past 21 days. The submittal log spreadsheet gets updated once a week, maybe.
The architect drops rev 4 into the shared Drive folder. Three days later your sub is in production on rev 3. The change order conversation that follows is not fun.
You've got 30 subs across active jobs. Six COIs expire each month. Nobody's watching. One incident on a sub with lapsed coverage is a six-figure exposure.
Preliminary notice 20 days in CA, 40 in FL, no notice required in some states. Filing windows 30/60/90/120 days. Miss one and you forfeit lien rights on a job you're owed money on.
30 RFIs landed in your inbox this morning. Which need urgent attention? Which are routine clarifications? Which are cost-impacting? You're triaging at 7 PM after the field calls stop.
Wednesday morning the owner wants a status update on three projects. You spend two hours assembling open RFIs, pending submittals, change orders in flight, and projected closeout dates.
Stop reading specs line by line. Paste the document, get a structured read back.
Paste a CSI MasterFormat section number or text; get a structured summary: scope, Part 1/2/3 highlights, submittal checklist, common pitfalls, adjacent sections that travel with it.
Pre-signature read of a CO. Plain-English breakdown: what scope changes, cost impact, time impact, hidden waiver clauses, what's negotiable. Flags blanket settlement language and acceleration disclaimers.
Pre-screen a vendor submittal against the spec excerpt it's submitted under. Flags missing data, spec mismatches, and substitution requests. Saves a PM 20 minutes per package by surfacing the obvious gaps before formal review.
Ballpark a bid from your scope + unit costs. Returns line items, subtotals (direct + OH + profit + contingency), risks that could blow the number, and what's missing. Sanity check, not a full estimate.
Don't start from a blank page — find it in the Hub and run it. Each job is ready to install, point at your setup, and run in your own language. Scheduled or trigger-driven, each one watches the Google Sheets/Drive you maintain (or the Gmail labels you set up) and digests to the channel you choose — without you ever opening it.
Polls a Drive folder for new and revised drawings. Detects file additions and modified-time changes via Sheet-backed state. Digest by project. (Companion drawing-rev-watcher handles Gmail-attached drawings for machine shops.)
Polls Gmail for new RFI emails. Each one classified by Claude — trade, priority, likely cost/schedule impact, suggested reviewer. Logged to a Sheet, digest to the PM.
Daily digest of pending submittals — aging by 14/21/28 days, plus items past their target return date. Reads a SubmittalLog Sheet you maintain.
Daily digest of subcontractor Certificate of Insurance expirations in 30/14/7-day windows. Catches lapses before a sub is on your jobsite with no coverage.
Daily reminder of upcoming lien deadlines you've entered. The job does NOT compute deadlines from state rules — you enter the dates your attorney or lien-service vendor gave you; the tool just reminds you 30/14/7/3/1 days out.
Weekly per-project roll-up: open submittals, open RFIs, pending COs, urgent items needing attention. Reads three companion Sheets and produces a one-screen digest per active project.
Grab the free Personal edition of InTouch AI. Browse the InTouch Hub, pick the jobs and skills you want, click Install. Or drive it from the REST API.
Each job has placeholders — Sheet IDs, Drive folder IDs, credential names, recipient publishers. Read the README, point it at your real sources, verify locally. Stop configuring. Start describing what you want.
This is the contract, now intelligent: tell it what to do, when, what to do when it works, what to do when it doesn't, and who to notify. Attach a daily/hourly/weekly schedule. InTouch AI runs the job, sends the digest to your channel (email, Slack, Discord, Teams), and logs every run. The old "doesn't work" clause was a dumb rule — retry three times, email a log. Now it's an assessment: it reads the failure, knows a Drive token expired or a Sheet moved, smart-retries or refreshes the credential, and surfaces the one sentence that matters. "It broke. Here's why. I fixed it." You didn't write the job line by line — so it debugs it for you.
No spin. Here's exactly where the line is:
The old way is dead. Find it and run it: Personal edition is free. Install it on your laptop or office server, paste your service account JSON into the encrypted vault, point it at your project Sheets and drawings folder — and let it run.