Civil 3D Fundamentals and Project Setup
The Object Model and the Toolspace
Civil 3D is built on a relational object model rather than on standalone drawings. Every object - point, surface, alignment, profile, corridor, pipe network - belongs to a named collection in the Prospector tab of Toolspace, and objects reference one another by name. A profile references an alignment and a surface; a corridor references an alignment, a profile, and an assembly. Understanding this dependency chain explains most behavior that confuses new users: deleting a surface silently breaks a profile, and renaming an object can orphan references elsewhere.
Settings Hierarchy and Styles
Settings cascade from Drawing Settings down through Feature Settings, Command Settings, and object-level overrides. Object styles control display; label styles control annotation; both live in the drawing or in templates. The classic exam trap is assuming a change made in Toolspace Settings will affect existing objects. It will not - settings govern the creation of new objects and the behavior of commands, while styles govern existing objects. A second common trap is confusing the drawing template with the company standards file; templates carry styles, settings, and often a predefined description key set.
Data Shortcuts and Working Folders
Large projects split into source drawings and sheet drawings, linked by data shortcuts stored in a working folder declared per project. Shortcuts are read-only references; to edit the source you open the source drawing, promote the shortcut, or use the Synchronize command after the source changes. Questions frequently test whether a shortcut contains geometry or a pointer - it is a pointer.
Rule of Thumb
Before starting any project, confirm three things: the drawing template is set, the working folder is set, and the coordinate system is assigned. A missing coordinate system is the single most common cause of downstream labeling and surface errors, and it cannot be retrofitted cleanly once surfaces and points exist.