Understanding Classes
Learn how classes control object appearance, attributes, hierarchy, and visibility across a scenic drafting file.
What to notice
Classes are the graphic control system of a Vectorworks file. They do not hold the drawing the way design layers do; they define how objects look, organize, and show, gray, or hide across saved views, viewports, and drawing contexts.
A strong class system lets a file stay visually legible even as the drawing becomes dense. Line weights, fills, textures, and visibility can be managed consistently instead of adjusted object by object.
Scenic drafting depends on that control because drawings mix architecture, dimensions, scenic objects, masking, notes, and 3D elements. Classes let those categories behave predictably across views.
The workflow
Name: Use class names as structure
Hyphenated class names create hierarchy, so related drawing categories can stay grouped and searchable.
Class names should describe graphic purpose, not only object type.
Style: Let classes carry attributes
Class attributes are powerful because they standardize linework, fills, and textures across objects.
Use at Creation turns the class into a style rule instead of a label.
Visible: Control what the drawing shows
Class visibility can clarify a drawing without moving objects to a new layer or deleting information.
Visibility is one of the main ways classes support documentation views.
Class naming hierarchy
Class hierarchy: Class naming hierarchy
See how hyphenated names group related classes and make a file easier to scan.
S-Ground Plan
S-Walls
S-Trim
Dimension
Class attributes: Class-controlled or manually overridden
Check the difference between an object that follows class attributes and one that has been manually styled.
Class-controlled objects revise globally.
Manual overrides can hide drafting standards.
Visibility can be managed without moving geometry.
One guiding idea
Classes make a drawing easier to trust because graphic standards stop depending on memory.
01 Classes describe graphic behavior
A class is not a place where an object lives. It is a set of graphic and visibility instructions that can travel with that object across the file.
That difference is what separates classes from design layers. Layers organize drawing planes. Classes organize how objects appear and whether they are visible in a given view.
02 Use at Creation keeps standards intact
When class attributes are used at creation, an object can inherit the correct line weight, fill, color, texture, or visibility behavior automatically.
That makes the drawing more consistent and easier to revise. Instead of selecting dozens of objects to fix a graphic standard, the class can carry the standard for the whole category.
Supporting material
Related resources and quick references stay close to the article so the writing can keep moving without hiding the practical details.
Related resources
Quick reference
The five-square demonstration transcript is brief, so avoid inventing missing steps.
Modeling in None is a Brandon workflow standard and should be framed as such.
Potential exam questions
These prompts are written for study or LMS use. They are intentionally presented without answers so they can support learning, review, or Canvas integration without giving the result away on the page.
Question 01 of 03
What is the primary role of a class in Vectorworks?
A. To control object appearance and visibility
B. To create a sheet layer
C. To change the project origin
D. To publish a PDF
Question 02 of 03
What does Use at Creation support?
A. Class-based attributes applied automatically to new objects
B. Automatic viewport cropping
C. Layer stacking order
D. Sheet title block numbering
Question 03 of 03
Why use hyphenated class names?
A. To create readable class hierarchy
B. To force all objects onto the None class
C. To convert classes into symbols
D. To prevent class visibility changes
What to notice
Classes are the graphic control system of a Vectorworks file. They do not hold the drawing the way design layers do; they define how objects look, organize, and show, gray, or hide across saved views, viewports, and drawing contexts.
A strong class system lets a file stay visually legible even as the drawing becomes dense. Line weights, fills, textures, and visibility can be managed consistently instead of adjusted object by object.
Scenic drafting depends on that control because drawings mix architecture, dimensions, scenic objects, masking, notes, and 3D elements. Classes let those categories behave predictably across views.
The workflow
Name: Use class names as structure
Hyphenated class names create hierarchy, so related drawing categories can stay grouped and searchable.
Class names should describe graphic purpose, not only object type.
Style: Let classes carry attributes
Class attributes are powerful because they standardize linework, fills, and textures across objects.
Use at Creation turns the class into a style rule instead of a label.
Visible: Control what the drawing shows
Class visibility can clarify a drawing without moving objects to a new layer or deleting information.
Visibility is one of the main ways classes support documentation views.
Class naming hierarchy
Class hierarchy: Class naming hierarchy
See how hyphenated names group related classes and make a file easier to scan.
S-Ground Plan
S-Walls
S-Trim
Dimension
Class attributes: Class-controlled or manually overridden
Check the difference between an object that follows class attributes and one that has been manually styled.
Class-controlled objects revise globally.
Manual overrides can hide drafting standards.
Visibility can be managed without moving geometry.
One guiding idea
Classes make a drawing easier to trust because graphic standards stop depending on memory.
01 Classes describe graphic behavior
A class is not a place where an object lives. It is a set of graphic and visibility instructions that can travel with that object across the file.
That difference is what separates classes from design layers. Layers organize drawing planes. Classes organize how objects appear and whether they are visible in a given view.
02 Use at Creation keeps standards intact
When class attributes are used at creation, an object can inherit the correct line weight, fill, color, texture, or visibility behavior automatically.
That makes the drawing more consistent and easier to revise. Instead of selecting dozens of objects to fix a graphic standard, the class can carry the standard for the whole category.
Supporting material
Related resources and quick references stay close to the article so the writing can keep moving without hiding the practical details.
Related resources
Quick reference
The five-square demonstration transcript is brief, so avoid inventing missing steps.
Modeling in None is a Brandon workflow standard and should be framed as such.
Potential exam questions
These prompts are written for study or LMS use. They are intentionally presented without answers so they can support learning, review, or Canvas integration without giving the result away on the page.
Question 01 of 03
What is the primary role of a class in Vectorworks?
A. To control object appearance and visibility
B. To create a sheet layer
C. To change the project origin
D. To publish a PDF
Question 02 of 03
What does Use at Creation support?
A. Class-based attributes applied automatically to new objects
B. Automatic viewport cropping
C. Layer stacking order
D. Sheet title block numbering
Question 03 of 03
Why use hyphenated class names?
A. To create readable class hierarchy
B. To force all objects onto the None class
C. To convert classes into symbols
D. To prevent class visibility changes
Continue reading
Related articles
Tools & Technology
How to Create Trim Profiles in Vectorworks Using the Polyline Tool
Tools & Technology
Publishing Vectorworks Renderings for Presentation
Tools & Technology