A California GC lost hours setting up drawing sets and chasing detail references by hand. We built a drawings module that indexes a set on upload and turns every reference into a link, then tested it on a real permit set: 122 references, zero false links.
The problem
Picture the first week of a new project. A 200-sheet permit set arrives as a stack of PDFs. Before anyone can use it, a project engineer has to name, number and file every sheet. That alone takes about six hours.
Then the daily work starts. A floor plan shows a small bubble marked 5/A501. That bubble is a callout: it means “the detail for this spot is drawing 5 on sheet A501.” Every time someone follows one, they leave the plan, hunt for sheet A501 and scroll to detail 5. A set has hundreds of these, and every RFI, submittal and field question leans on them.
That was everyday life at a California GC we work with. Their drawings, RFIs, submittals and field records lived in separate tools that did not match how the team actually ran projects.
Auditing the situation
We started where we always do: mapping how the work really moves. We followed a drawing set from the day it arrived to the day the drawing log went out, and marked every step where hours leaked.
Before: how a drawing set moved
- Where time leaks
- 1
The permit set arrives
About 200 sheets, delivered as PDFs.
- 2
Set up the sheets by hand
Name, number and file every sheet before anyone can use the set.
~6 hoursBottleneck - 3
Follow callouts by hand
See 5/A501 on a plan, find sheet A501, scroll to detail 5. Hundreds of times per set.
Every dayBottleneck - 4
Answer questions from the drawings
Search 200 sheets for a note or spec, from memory.
Bottleneck - 5
Type up the drawing log
Rebuild the sheet list and Exhibit C by hand for every issue.
~3 hoursBottleneck
How we fixed it
Instead of adding one more tool, we started building the GC its own project management platform, module by module, around how the team works. We began with drawings, because that is where the most hours were leaking.
- Upload a set and it is indexed automatically: every sheet named, numbered and filed.
- Every callout becomes a link. Tap 5/A501 on the plan and you land on the detail.
- Ask the drawings a question and get an answer that points to the exact spot on the sheet.
- Compare revisions side by side, with changes highlighted.
- Export the drawing log and Exhibit C in one click.
Where AI does the work
AI now handles the reading and linking that used to fall on people. The team still makes every call; it just stops doing data entry.
After: the same set, with AI in the loop
- AI does the work
- 1
Upload the permit set
Drop in the PDFs, all 200 sheets at once.
- 2
AI reads every title block
Each sheet is named, numbered and indexed as it uploads.
Target: under 5 minAI - 3
AI links every callout
Bubbles like 5/A501 become links that open the right detail.
122 tested, 0 falseAI - 4
Ask the drawings
Questions are answered from the real set, with the exact sheet region cited.
AI - 5
Export the drawing log
The sheet list and Exhibit C, generated from the index.
Target: under 30 sec
Tested on a real set
Before calling it done, we tested callout detection on a real, anonymized commercial permit set, not a demo.
122
real drawing references tested
97.5%
linked to the right sheet
0
false links
Zero false links means the software never turned unrelated text on a sheet into a fake callout. When a link appears, it goes where the drawing says it should.
Setting up a 200-sheet set took around six hours; the target is under five minutes. The drawing log and Exhibit C took three hours by hand; the target is under thirty seconds.
The contractor owns the application. RFIs and submittals, tied directly to the drawings, are in build now.