Case study
(opens in a new tab)Structural engineering · New York City
From spreadsheets and compliance reminders to the software the firm depends on.
At a glance
- 650+
- Properties monitored
- 18,900+
- Documents indexed
- 250+
- Filings extracted with zero errors
Illustrative. No client data is shown.
Chapter 01
Where it started
SAS works under two of New York City’s most demanding compliance regimes: facade inspections under Local Law 11 (FISP) and parking structure inspections under Local Law 126 (PIPS).
Every building in the portfolio carries its own cycle of inspections, filings, and Department of Buildings deadlines. Tracking it all meant spreadsheets, calendar reminders, and institutional memory, and preparing a single filing meant hours in project folders, DOB records, and document templates.
Chapter 02
One view of the whole portfolio
We built an operations dashboard: one view of the firm’s properties and clients, with role-based access for the team.
Department of Buildings records are checked automatically, so each property’s status stays current without anyone looking it up by hand. More than 650 properties are monitored this way.
Chapter 03
Documents that find themselves
Project documents are indexed, so the right file turns up from a plain-language search instead of a dig through folders.
Records pulled from the Department of Buildings are read the way a person would read them, checked at every step, and land as structured data ready for reports. More than 18,900 documents are indexed, and over 250 filings have been extracted with zero errors.
Chapter 04
Deadlines that come to you
Filing tracking and deadline monitoring for Local Law 11 and Local Law 126 run on their own across the portfolio.
Deadlines surface themselves instead of living in calendar reminders, and filings start from generated drafts rather than blank templates.
Chapter 05
An assistant that answers from the firm’s own files
An internal AI assistant, trained on the firm’s own data and in production at the firm.
It searches the indexed project documents and answers in plain language, so questions that used to interrupt a senior engineer get answered in seconds.
Chapter 06
How we rolled it out
It started as a paid pilot. We automated one process first, and it ran in parallel with how the firm already worked for two to four weeks, with the outputs compared before anything switched over.
Then the new process took over, and the rest was built out from there.
Your firm
Your business probably isn’t a structural engineering firm. That’s the point. Nothing here came off a shelf. Built around your operations, yours would look entirely different.