BIM Guide for Architects

BIM means different things depending on who’s asking. To a software vendor, it’s a feature list. To a client, it’s a promise that clashes get caught before they reach site. To the architects and BIM coordinators actually running models day to day, it’s neither — it’s a discipline of decisions: how you structure levels, name families, split work between disciplines, and keep a federated model honest as a project moves from concept to construction documentation.

This guide exists because most BIM content online stops at definitions. It explains what a Level of Development is, but not what LOD to demand from a structural consultant at DD stage on a mid-rise residential project. It explains clash detection, but not how to run a coordination meeting that actually resolves clashes instead of just logging them.

I coordinate BIM workflows daily, both on live projects at Waseelah Ansari Associates and as an instructor at WAA Skill Studio, and this is where I’m collecting the practice-based resources I wish existed when I started — workflow breakdowns, coordination checklists, and honest notes on what Revit, Navisworks, and the standards actually require versus what teams get away with skipping.

If you’re an architect or BIM coordinator looking for something you can use on Monday morning rather than a glossary entry, you’re in the right place.