Export Revit model warnings to a spreadsheet

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command 'iwr -useb https://bimcli.com/install.ps1 -OutFile $env:TEMP\bim-install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File $env:TEMP\bim-install.ps1'

Every Revit model accumulates warnings. bim-cli exports all of them — with element IDs — to a spreadsheet in one command. Sort by category, assign to team members, track resolution over time.

Revit's own warnings dialog lists issues but can't export them cleanly — you scroll, you screenshot, or you copy rows one by one, and the element IDs don't come with you. bim reads the same warning set through the API and writes it as structured rows, so the audit becomes a spreadsheet you can filter, assign, and diff against last week's.

Export all warnings to Excel

bim revit warnings-export | bim excel write warnings.xlsx

{"path":"warnings.xlsx","sheet":"Data","rows":47,"columns":["description","severity","element_ids"],"applied":true}

Each row contains the warning text, its severity, and the failing element IDs. bim excel write takes the rows from the pipe. The file opens in Excel immediately.

Share with the team via Google Sheets

bim revit warnings-export | bim google sheets append --spreadsheet <id-or-url> --with-header

The first run writes headers; subsequent runs append. Use a separate sheet per audit date to track progress over time.

Filter before writing

bim revit warnings-export | jq '[.[] | select(.severity=="Error")]' | bim excel write errors.xlsx

bim revit warnings-export | jq 'group_by(.description) | map({description: .[0].description, count: length}) | sort_by(-.count)'

Agent use

An agent can audit model health as part of any workflow:

bim revit warnings-export | bim excel write audit.xlsx

No Revit dialog boxes, no manual steps. The agent reads the output and summarizes warning categories, flags high-count issues, or compares to a prior baseline.

Install

iwr -useb https://bimcli.com/install.ps1 -OutFile $env:TEMP\bim-install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File $env:TEMP\bim-install.ps1

powershell.exe -NoProfile -ExecutionPolicy Bypass -Command 'iwr -useb https://bimcli.com/install.ps1 -OutFile $env:TEMP\bim-install.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File $env:TEMP\bim-install.ps1'

Then ask your assistant to run bim describe --json. See what the installer does.