ACP Revit Architecture common mistakes
ACP Revit Architecture · Understand the traps and how to avoid them.
Editing a type parameter when the question asks for a change to only one instance, so the whole project changes instead of the single element.
Candidates memorise the Properties palette layout but never internalise the type-versus-instance split, and both parameter sets appear in the same palette with similar names.
What to do instead
Before answering, ask whether the change should propagate to all elements of that family type. If only one element changes, use instance parameters or element overrides; if all change, edit the type. Practise by toggling a shared parameter between type and instance and observing the effect.
Assuming a visibility setting in the family editor will hide geometry in the project, when the view's own category or filter settings override it.
The interaction between family visibility parameters, view discipline, view templates, and filters is layered, and candidates learn each layer in isolation rather than the resolution order.
What to do instead
Build a mental hierarchy: view filters and view templates act at the view level and take precedence over family-level visibility. When a question asks why geometry is hidden, check the view template and filters first, then the family's visibility settings.
Placing a section or elevation marker without checking the crop region and far clip, then failing questions about what is visible in the resulting view.
Candidates treat view creation as a single click and skip the properties that determine what the view actually shows.
What to do instead
After creating any view, inspect crop region, crop region visible, annotation crop, and far clip settings. Answer visibility questions by reasoning from those properties rather than from the geometry alone.
Using the wrong coordinate reference when linking a model, so the linked file lands at an unexpected location relative to project base point or survey point.
Shared coordinates, project base point, and survey point are three distinct concepts, and candidates conflate them because all three appear in the same location dialog.
What to do instead
Learn the distinction: the project base point anchors the model internally, the survey point anchors it to real-world coordinates, and Acquire Coordinates copies the linked model's survey position. For each linking question, identify which of the three the scenario is really about.
Answering workspace questions by describing a workflow that ignores worksets entirely, treating a central model as a simple file share.
Candidates who have only used standalone files have no mental model of central models, local copies, and element borrowing, so they default to file-copy reasoning.
What to do instead
Study the central/local model relationship: each user works in a local copy, synchronises with central, and owns elements or worksets. When a question mentions multiple simultaneous users, check whether the answer accounts for synchronisation and ownership.
Creating a family with a nested component but forgetting to associate the nested parameter, so the host family cannot control it.
Nested families look complete once loaded, and the association step is a separate action that produces no visible change until a parameter is tested.
What to do instead
After loading a nested family, open the host family's parameter dialog and explicitly link the nested parameter to a host parameter. Test by changing the host value and confirming the nested element responds.
Choosing a schedule field or filter that cannot produce the requested result because the needed parameter is a shared or project parameter that was never added.
Schedules only expose parameters that exist on the category, and candidates assume any property they can see in the palette is automatically available as a schedule field.
What to do instead
Before answering schedule questions, verify the parameter exists on the category and is shared if it must appear across projects. If the question requires a field that is absent, the correct answer is usually to add the parameter first.
Describing a sheet workflow that places views individually when the question hinges on view placement, title block parameters, or revision tracking across sheets.
Sheet composition is taught as drag-and-drop, so candidates miss the parameter-driven behaviour of title blocks and the revision schedule's relationship to sheets.
What to do instead
Treat sheets as containers with their own parameters and revision assignments. For any sheet question, identify whether it concerns view placement, title block instance parameters, or revision issuance, and answer only that layer.
Assuming a wall, floor, or roof will join cleanly without checking the join status or the structural versus architectural material assignment.
Candidates expect geometry to behave predictably and do not account for the explicit join and cut commands that control how elements interact.
What to do instead
Learn that joins are explicit states which can be joined, unjoined, or switched, and that material and function settings affect how elements cut each other. When a question shows unexpected geometry, check join status before assuming a modelling error.
Treating a design option or phasing question as a simple visibility toggle, ignoring that elements must be assigned to the correct option set or phase.
Design options and phases both hide and reveal elements, so they look like visibility settings, but they are assignment-based and cannot be fixed by toggling a checkbox.
What to do instead
For each element in question, identify its design option and phase assignment, not just its visibility. If an element appears in the wrong state, the fix is reassignment to the correct option set or phase, or adjusting the view's phase filter.