You've been handed a Vectorworks licence, a project number and a deadline, and your fingers keep reaching for Revit shortcuts. The file opens on a single design layer, two classes called None and Dimension, and nothing that looks remotely like a Project Browser. Somewhere in the next hour you will draw a wall, switch to a 3D view, and discover it isn't where you thought it was.
Here's the one thing that fixes most of it. Design layers hold the where. Classes hold the what. A design layer is a physical place in the building at a physical elevation, with its own drawing scale — ground floor, first floor, site, roof. A class is a kind of thing — walls, furniture, setting out, existing to be demolished — and it carries the graphic attributes and the on/off switch. Your AutoCAD layers are Vectorworks classes. Your AutoCAD model space, sliced into floors, is Vectorworks design layers. Get those two mapped the right way round and about eighty per cent of the confusion disappears before lunch.
The AutoCAD trap and the Revit trap, which are different traps
If you come from AutoCAD, the word "layer" is poisoned. You'll open the Organisation dialogue, see "Design Layers", and start making one called A-WALL and another called A-DOOR. Three days later you have forty design layers, no storeys, and a model that is completely flat because every object you drew sat at zero. Design layers are not for sorting things by type. They're for stacking the building.
If you come from Revit, the trap is the opposite. You arrive expecting the software to stop you doing stupid things, and it doesn't. Revit's whole personality is that a wall is a wall, lives on a level, and cannot be a bit of 2D decoration. Vectorworks will happily let you put a parametric BIM wall, a hand-drawn polyline and a block of scanned survey next to each other on the same design layer, in the same drawing, with no complaint. That isn't sloppiness built into the software. It's the point of it. Vectorworks assumes you're an adult with a deadline and that at RIBA Stage 2 you may genuinely want a loose line rather than a modelled construction build-up.
The cost of that freedom is that nothing is organising the file for you. You have to do it, once, at the start.
Hybrid objects: the plan and the model are the same drawing
The second concept that trips people up is that Vectorworks objects are hybrid. A wall, a door, a window, a column, a piece of furniture from the library — each one has a 3D body and a 2D plan representation, and you see whichever one the current view calls for. Switch to Top/Plan and you get the symbolic plan graphic: the door leaf and swing arc, the wall cut poché. Switch to a 3D view and the same object is a solid.
This is why there is no "go to the floor plan view" in the Revit sense. Top/Plan is a view mode, not a saved drawing, and every design layer is simultaneously plan and model. Once that lands, Vectorworks stops feeling like a broken BIM tool and starts feeling like a drawing board that happens to be three-dimensional.
It also explains a behaviour that drives new users mad: you draw a wall on the ground floor layer, go to 3D, and it's floating. Walls take their height and base from the storey the design layer is bound to. No storey, no sensible height. Which brings us to setup.
Set the file up in this order
A blank Vectorworks document is not completely empty — you get one default design layer and the None and Dimension classes — but it is close enough to empty that you are building from scratch. The supplied templates (Architect Metric, say) come with design layers, a class set and sheet layers already configured. In practice, a template someone in the office has already tuned beats both, so ask before you start. If you are starting clean, this is the order we teach, and the order matters because each step depends on the one above it.
1. Units and scale. Document Settings first, before a single line. Millimetres for a UK architectural file, with the display accuracy you actually want in dimensions rather than six decimal places of nonsense. Scale is set per design layer, not per document — 1:50 on the plan layers, 1:200 on the site layer if that suits. Viewports will rescale for output anyway, but the layer scale controls how big your text and symbols look while you work.
2. Storeys. This is the step everyone skips and everyone regrets. Create storeys for ground, first, roof, with their elevations, and define the level types within each one — finish floor, slab top, ceiling, and so on. Those level types are what walls and slabs bind to. Set them now and a wall drawn on the first floor knows where its base is, where its top is, and what happens when you move the storey 150mm because the slab build-up changed. Revit users: this is your Levels, except the binding is explicit and you choose which level a wall's top sticks to.
3. Design layers, bound to storeys. One or more per storey. Keep them boring: Ground Floor, Ground Floor Site, First Floor. If you need a separate layer for an imported survey, make it and bind it to nothing.
4. Classes. Now do the thing your AutoCAD brain wanted to do at step one. Classes for walls, glazing, furniture, structure, dimensions, text, existing, demolished. Set each class's pen weight, fill and hatch, then turn on "use class attributes" when you draw, so an object's appearance comes from its class rather than from whatever was last in the attributes palette. That is the whole payoff: change the class, change every drawing in the file at once. If your office has a BS 1192-derived naming convention, use it for class names — Vectorworks nests classes on hyphens, so a convention with separators gives you a tidy folded tree in the Organisation dialogue for free.
5. Wall styles — but later than you think. Here's a working method that saves a lot of pain and that we use on the Villa Tugendhat build in our own course: model the form with unstyled walls first. Get the plan right, get the heights and junctions right, get the thing standing up. Only once the geometry is settled do you replace those walls with proper wall styles carrying components — brick, cavity, blockwork, lining — each component assigned to a class. Build the construction into a wall style on day one and every plan change becomes a fight with component joins that don't matter yet.
6. Sheet layers, viewports, title block. Sheet layers are your paper. A viewport is a view of design layers placed on a sheet, with its own scale, its own layer visibility and its own class visibility. Make the sheets and the title block before you need them.
7. Saved views. Cheap to make, enormously useful. A saved view stores which layers and classes are on, the view direction and the render mode. Three or four of these — working plan, presentation 3D, survey only — will save you more clicking than any other habit in the software.
When something vanishes, check in this order
Objects disappear in Vectorworks constantly, and almost never because they've been deleted. What we've found is that running the same three checks, in the same order, turns a ten-minute panic into a five-second fix.
First, layer options. The View menu's layer setting controls whether you can see only the active design layer, or others greyed, or others shown and snappable. Draw a wall with "active only" on, forget, and your ground floor is simply not being displayed.
Second, class visibility. The object is there, its class is off. Classes can also be visible, greyed or invisible, and a viewport carries its own class settings that override whatever you've got on screen.
Third, elevation. Check the Z of the object and the storey binding of the layer. A wall drawn on an unbound layer sits at zero, which in 3D means it's buried in the ground floor slab.
If all three are clean, then worry.
Viewports are not paper space with extra steps
The closest thing to a revelation for AutoCAD users is what's inside a viewport. Double-click one and you're asked which part you want to edit: the Crop, the Annotations, or the design layers themselves. Crop is the shape of the window. Annotations is a drawing space that belongs to that viewport alone — dimensions, tags, callouts, revision clouds all live there, scaled to the viewport, invisible everywhere else. Put your dimensions in the annotation space, never on the design layer. It's the single cleanest habit in the software.
One more Vectorworks-specific control worth knowing early: in the quick preferences there's an auto display detail level for design layers. Flick it and your component-built walls stop showing their brick-cavity-block layers in plan and go back to a simple two-line wall. Issuing a planning drawing where the contractor's build-up shouldn't be legible? That's two clicks, not a redraw.
For render viewports, set the DPI on the viewport itself before you place it — a render viewport left at screen resolution will look soft on an A1 sheet and you won't notice until it's printed. On export, the PDF dialogue offers to write out design layers and classes as separate PDF layers. In practice, leave those unticked unless a consultant has specifically asked for a layered PDF; it bloats the file and confuses planners.
Importing DWG and RVT without inheriting a mess
The rule we give people migrating a live job: DWG layers come in as classes, not as design layers. Vectorworks will offer you both on import. Choose classes. Your AutoCAD file was organised by object type, and object type is what a class is. Then put the whole import on one design layer called something like Survey DWG, bound to nothing, and lock it.
Things that will not survive the trip, from experience rather than from any published compatibility list: hatches arrive as non-parametric geometry rather than live fills, so scaling them later is miserable; dynamic blocks arrive as plain symbols with the dynamism gone; and line weights depend entirely on whether the original file plotted by colour or by assigned weight — if it's colour-based, map the ACI colours to pen weights in the import dialogue or everything lands at the same hairline.
From Revit, IFC is usually the honest route for geometry you need to coordinate against, and it will arrive as solids with data attached rather than as editable Vectorworks walls. Don't try to convert it. Reference it, model your own, and let the IFC be the consultant's model it actually is.
As for how long the switch takes: for someone already fluent in Revit or AutoCAD, the honest answer from teaching this is a couple of weeks of real project work before the interface stops being in the way, and a project or two before your files are organised well enough that someone else could open them. The tools are not the hard part. The organising logic is, and it's one page of ideas — layers for where, classes for what, storeys underneath the lot, viewports on top.
Set the file up in that order and Vectorworks stops arguing with you.
