Resources
Use cases
Every example on this page comes from a real BIM Monkey session on a working residential project or firm template — not a staged demo. Each one is broken down the same way: the need an architect actually had, what BIM Monkey did about it, and the result at the end of the session.
Start a new project
The need: a new project opens as a template full of placeholders. Filling it in eats the first day.
- Populated the cover sheet from real project data — scope, address, parcel, zoning, SEPA note
- Read the surveyor's name and license number off a CAD title block image
- Caught the wrong building code (commercial IBC on a residential project) and fixed it
Result: permit-ready site plan package in about 30 minutes.
Bring standards over from another project
The need: the new file is missing the firm's filled regions, dimension types, and text styles.
- Copied 38 filled-region types and 2 dimension types from a sibling project open in the same session
- Renamed all 26 legacy-prefixed types to firm standard — zero failures
Result: full asset library in under a minute, instead of rebuilding piece by piece.
Clean up a messy file — safely
The need: years of CAD imports left 107 line styles and stray text types nobody dares delete.
- Checked every style for actual usage before touching anything
- Deleted only the 42 with zero references; built the missing text-size ladder
- Reported a prioritized gap list of what the template still needs
Result: 107 line styles down to 62 — all firm-standard — with nothing broken.
Turn a fix into a one-click script
The need: the same cleanup gets re-explained on every project.
- Saved the session's work as ribbon scripts the whole team can run — zero token cost
- Safe to re-run: already-done work just reports “already exists”
Result: firm standards become buttons, not tribal knowledge.
Make a surgical edit
The need: flip one floor's hatch direction — without changing the shared material used everywhere else.
- Flagged that a direct edit would flip every floor in the project
- Duplicated pattern, material, and floor type; swapped only the one element; verified visually
Result: one floor changed. Nothing else touched.
Get a straight answer about what Revit allows
The need: link project info text across sheets so it updates everywhere from one edit.
- Flagged up front that the required API doesn't exist in this Revit build — verified, not guessed
- Laid out two options with tradeoffs; did everything the API allows; gave click-by-click steps for the one manual piece
Result: no dead ends, no broken output — a clear path and an honest constraint.
What to ask
| When you're… | Try asking |
|---|---|
| Starting a project | “Populate the cover sheet from this survey PDF.” |
| Inheriting a messy file | “Audit line styles and text types — delete unused non-standards.” |
| Repeating yourself | “Save that as a script for the team.” |
| Editing carefully | “Change this one element — tell me first what else it touches.” |
| Sanity-checking | “Audit this template against our standards.” |
| On a deadline | “Check door swings and egress notes against code.” |