ACP Revit Architecture cheat sheet
ACP Revit Architecture · Keep the key ideas within reach.
Modeling
Levels define vertical reference planes; walls, floors, and roofs use base and top constraints tied to levels.
A wall's location line (wall centerline, finish face exterior, etc.) determines which reference plane aligns with the drawn line.
Join geometry: use Modify > Join to control how intersecting elements clean up; Switch Join Order reverses which element's cut prevails.
The Cut Geometry tool is required to cut a roof or wall with a void; opening by face is used for openings in floors, roofs, and walls.
Constraints: align and lock (padlock) elements to reference planes or levels to maintain design intent; over-constraining causes errors.
Roof by footprint uses sketch lines on a level; roof slope is set by defining slope arrows or setting the slope value on sketch lines.
Stairs: run width, riser height, and tread depth are set in type properties; the actual riser count is calculated from total rise and max riser height.
Curtain walls: grids are placed by number or distance; mullions are applied to grid segments or borders; panels can be replaced by doors or custom families.
Documentation
View templates control view-specific settings (scale, detail level, visibility/graphics overrides, annotation categories) and can be assigned to multiple views.
Tags are view-specific annotations; a tag's leader and text position are adjusted per instance, while the tag type controls the label and appearance.
Schedules are tabular views of model elements; they can be placed on sheets, and their fields, filters, sorting, and formatting are set in the Schedule Properties dialog.
Dimensions: temporary dimensions appear during placement; permanent dimensions are added with the Dimension tool and can be constrained (locked).
Sheet setup: titleblocks are families; viewports on sheets can be aligned and locked; guide grids help align views across sheets.
Keynotes annotate elements with standardized text from a keynote file; they are placed with the Keynote tool and can be tagged by element or by material.
Revisions are tracked in the Sheet Issues/Revisions dialog; revision clouds and tags are placed in views and appear on sheets based on revision settings.
Collaboration and Project Management
Worksharing: enable worksharing to create a central model; users create local copies and synchronize with central to share changes.
Worksets are used to divide a project for visibility control and to organize elements; each element belongs to a workset.
Element borrowing occurs when a user edits an element owned by another; ownership is requested and granted on save/sync.
Linked models: use Manage Links to control link visibility, coordination, and reload; shared coordinates are used to align models.
Project base point and survey point: the project base point defines the project origin; the survey point defines the real-world coordinate system.
Phasing: phases (existing, new construction, demolition) are assigned to elements; phase filters and graphic overrides control display per view.
Design options: create option sets and options to study alternatives; the primary option is visible by default; options can be accepted into the main model.
Family Creation and Content
Family templates: choose the correct template (e.g., Generic Model, Door, Window) to inherit required categories and parameters.
Reference planes and lines: reference planes are used for constraints and dimensioning; reference lines are used for angular parameters and rotation.
Parameters: family parameters (type/instance) are created in the Family Types dialog; shared parameters are stored in an external file for scheduling and tagging.
Constraints: dimension and lock geometry to reference planes; use the Family Types dialog to test parameter values and flex the family.
Form creation: extrude, blend, revolve, sweep, and swept blend are solid forms; voids cut solids; each form has a visibility setting.
Nested families: load one family into another; associate parameters to control nested components; use shared parameters for scheduling nested elements.
Formulas: parameters can be driven by formulas using arithmetic and conditional statements (if, and, or); units must be consistent.