ACP Revit Structural common mistakes
ACP Revit Structural · Understand the traps and how to avoid them.
Copying and pasting structural elements between levels instead of using Copy to Levels or the clipboard with 'Constrain' and level offsets set, so new framing lands at the wrong elevation or loses its host association.
Candidates treat Revit like a 2D drafting tool and paste in a plan view, where the paste inherits the active view's work plane rather than the intended level. The exam then presents a section or 3D question where the geometry is visibly at the wrong height.
What to do instead
Use the Copy/Paste Aligned > Select Levels by Name command, or Ctrl+C then Paste Aligned to Selected Levels, and verify the resulting elevation in a section or by checking the element's Reference Level and Offset instance parameters. Practise the three aligned-paste variants until the level-selection dialog is second nature.
Leaving analytical elements unloaded or out of sync with the physical model, then answering analysis questions as if the analytical model automatically matched the physical geometry.
The analytical model is a separate set of elements with its own alignment tools and load status; candidates who rarely open the Analytical Model view or run the Analytical Alignment tools assume the two are always identical.
What to do instead
Before any analysis question, check the Analytical Model category visibility and run Analytical Alignment to verify physical-to-analytical consistency. Learn where the analytical model can be enabled or disabled per element and how boundary conditions and loads attach to analytical nodes rather than physical geometry.
Building documentation views by annotating in a single enlarged plan and then duplicating it, so tags, dimensions, and view-specific overrides appear on the wrong sheets or at the wrong scale.
Duplicating a view with detailing carries annotations across, and candidates do not distinguish Duplicate, Duplicate with Detailing, and Duplicate as Dependent, nor do they check the view's Detail Level and Discipline before annotating.
What to do instead
Choose the duplicate type deliberately: Dependent for identical content that must stay in sync, Duplicate with Detailing only when annotations should carry over. Set View Scale, Detail Level, and Discipline immediately after creating a view, and confirm sheet placement before tagging.
Assuming a structural column or beam will join, cut, or clean up with adjacent geometry automatically, and failing to use Join Geometry, Cut Geometry, or the beam/column join order controls.
Revit's automatic join behaviour depends on element category, material, and the order of creation; concrete beams and columns behave differently from steel, and candidates expect uniform results.
What to do instead
Learn the Structural tab's beam and column join tools and the 'Switch Join Order' command. Test a small mock-up with steel versus concrete framing to see which joins are automatic, and use Unjoin Geometry to inspect what is actually joined before answering.
Editing a system family type directly in the project to satisfy a one-off condition, permanently altering every instance of that type across the model.
The Type Properties dialog is easy to reach and candidates under time pressure change a type rather than creating a duplicate, not realising the change propagates model-wide and can break schedules and sheets.
What to do instead
Always Duplicate the type before modifying type parameters, and give it a descriptive name. When a change is instance-specific, use instance parameters or a view-specific override instead. Review the Project Browser's Families branch to confirm no unintended types were modified.
Creating a truss, brace, or connection family with the wrong family template or wrong category, so it cannot host to structural framing or will not appear in structural schedules and filters.
Candidates pick Generic Model or a metric/imperial mismatch because the template list is long, and the resulting family lacks the structural category behaviour needed for hosting and scheduling.
What to do instead
Start structural content from the Structural Framing, Structural Columns, or Structural Connections templates as appropriate, and set the family category and parameters before adding geometry. Verify hosting by placing the family on a beam in a test project and checking it appears in a structural framing schedule.
Ignoring worksets, central model location, and file ownership when answering coordination questions, treating a workshared model as if it were a standalone file.
Many practice models are single-user, so candidates never internalise that editing a workset-owned element, borrowing, or synchronising with central governs what other team members can see and change.
What to do instead
Review the Collaborate tab: worksets, Synchronize with Central, Reload Latest, and the Worksharing Monitor. Know that elements are owned per workset and per user, that 'Editable' status controls who can modify, and that linked models are coordinated through Copy/Monitor rather than direct editing.
Answering schedule and quantity questions from a manually counted plan instead of building or checking a schedule, and not noticing that schedule filters, phases, and design options change the totals.
Schedules feel slower than visual counting under exam time pressure, and candidates overlook that Phase Created/Phase Demolished and design options exclude elements from a schedule's results.
What to do instead
Build a quick structural framing or column schedule with the relevant fields, then apply filters and check the Phase and Design Option columns. Learn to read the schedule's grand totals and to verify a count by isolating categories in a 3D view with a section box.
Setting up a project with the wrong template, units, or levels, then trying to correct level names, elevations, and shared coordinates after modelling has begun.
Candidates rush past the initial template selection and the Manage > Project Units and Coordinates dialogs, not realising that renaming levels later breaks views, and that moving a project after acquiring coordinates shifts the model.
What to do instead
Before modelling, confirm the structural template, project units, and level naming convention, and create levels from a section or elevation view so they generate floor plans. Handle shared coordinates with Acquire Coordinates or Publish Coordinates deliberately, and verify with the Spot Coordinate tool.
Answering view and visibility questions by hiding elements with the temporary Hide/Isolate command or the eye icon, rather than using Visibility/Graphics overrides that persist and are documented.
The temporary hide is the fastest visible control in the interface, so candidates use it reflexively and do not distinguish it from category overrides, filters, and view templates that actually control what prints.
What to do instead
Practise the Visibility/Graphics dialog, view filters, and view templates as the primary tools, and use Reveal Hidden Elements to inspect what is hidden and why. Know that temporary hide resets on view close or reload, while V/G overrides and filters persist and travel to sheets.