About Revit Club

Independent Revit guides on families, parameters, views and sheets, written by Andrew Mercer.

Revit Club is an independent guide to Autodesk Revit for people who need a model that produces consistent drawings. I'm Andrew Mercer, and I write it around one question: when you change something in Revit, what else changes with it? A parameter can feed a schedule, a family type can appear across the whole project, and a visibility override can hide a problem in one view without fixing anything in the model.

What the guides cover

Families: system, loadable and in-place families, building a family from a template, then loading it and placing it in a project.
Views & sheets: the Project Browser and view-level graphics such as halftone.
Modeling: building elements and their edits, such as putting a door into a curtain wall.
Setup, licenses & versions: what Revit costs, what moves the price, and the hardware it needs before you install.
BIM basics: what building information modeling means inside Revit, and how to choose between Revit and AutoCAD for your drawings and models.

How I write a Revit guide

I start with the scope of a change. Before a guide moves on to sheets, it names the type or instance information involved, because that choice decides how far an edit travels. A local override and a model change can look identical on screen. They behave very differently the next time a colleague opens the drawings or revises the data behind a schedule.

Autodesk documentation is my reference for how a feature behaves. Project-specific coordination needs its own checks, so a guide explains what Revit does and leaves sign-off on your model with your team.

About Andrew Mercer

Andrew Mercer, with grey curly hair and dark-rimmed glasses, in a light blue shirt outside a concrete building entrance — Andrew Mercer, Revit BIM documentation editor at Revit Club

My role here is Revit BIM documentation editor. I work on the part of Revit where a model turns into documents: families, types and parameters, view templates and visibility, schedules and sheet coordination, and keeping linked models consistent with the drawings that use them.

The reader I have in mind wants a model that produces consistent documents and stays understandable to colleagues. That's why I give room to distinctions like instance versus type parameters. Picking the wrong one takes a second; finding every view and schedule it touched takes much longer.

Revit Club is not affiliated with Autodesk, Inc. Autodesk, Revit and AutoCAD are registered trademarks or trademarks of Autodesk, Inc.