Field-to-Finish — Civil 3D Study Guide
Autodesk Civil 3D · Survey Module

Field-to-Finish

A practical study guide for surveyors starting their first as-built project — from raw field data to a clean, plotted deliverable.

Civil 3D 2022+ Survey Workflow As-Built Design
01

What Is Field-to-Finish?

Field-to-Finish (F2F) is Civil 3D’s automated system for translating raw survey field codes into finished CAD geometry — points, figures (linework), and blocks — in a single step. Instead of manually drawing lines between shot points after importing, you define rules up front so the software draws everything for you.

Think of it as a translation layer: your field crew shoots a point and types a code like EP (edge of pavement). F2F sees that code, drops the correct point symbol on the correct layer, and connects it to the next EP shot with the correct linestyle — automatically.

▸ Why this matters for an as-built
An as-built survey documents what was actually constructed vs. what was designed. Speed and accuracy are both critical. F2F lets you go from a raw data file to reviewable linework in minutes, not hours.

What F2F Automates

Point Symbols

Drops the correct marker block (manhole, iron pin, tree, etc.) based on the field code.

Layer Assignment

Places each point and figure on the correct layer defined in your point style or figure prefix database.

Figures (Linework)

Connects sequential shots of the same code into polylines, respecting begin/end codes.

3D Breaklines

Optionally converts figures into surface breaklines for TIN surface generation.

02

Key Concepts & Terminology

Survey Database (SDB)

A folder-based repository that stores all networks, figures, and imported data for a project. One project = one SDB.

Field Book (FBK)

A text file containing raw traverse observations (directions, distances, angles) from a total station or field controller.

Point Group

A named filter or collection of points in the drawing. Controls visibility, labeling, and surface inclusion.

Figure

A polyline entity in the survey database connecting sequential shots of the same code. Becomes CAD linework.

Figure Prefix Database

The F2F lookup table that maps field codes to layers, linetypes, colors, and figure styles.

Code Set Style

Controls how point codes are rendered in the drawing — which marker block to use, label placement, etc.

Network

A logical grouping of survey observations within a database — typically one network per day of fieldwork or per setup.

Control Points

Known coordinates (benchmarks, monuments) used to orient the survey into the project coordinate system.

Common Field Codes to Know

CodeMeaningFigure Behavior
EPEdge of PavementBegins/continues EP figure
CLCenterlineBegins/continues CL figure
TC / BCTop/Bottom of CurbParallel curb figures
MHManhole (center)Single point, MH block inserted
CBCatch BasinSingle point, CB block inserted
BLDBuilding CornerConnects corners into closed polygon
IP / MONIron Pin / MonumentSingle point marker
TRETreeSingle point, tree block
EOP / BOPEnd/Begin of figureStops or restarts a figure string
▸ Field Code Consistency
Your F2F settings only work if the field codes in your data file exactly match what’s defined in your Figure Prefix Database. Case sensitivity and spelling matter. Coordinate with your field crew before data collection.
03

The F2F Workflow Overview

Here is the high-level sequence you’ll follow every time. Each step is detailed in later sections.

1 — Create Survey Database

Set up a new SDB folder linked to your project. Choose your coordinate zone and units here.

2 — Configure F2F Settings

Assign your Figure Prefix Database and Code Set Style to the database before importing any data.

3 — Import Field Data

Bring in your .fbk, .raw, .csv, or total station file into a network inside the database.

4 — Process / Run F2F

Civil 3D reads codes, generates figures, inserts blocks, assigns layers. Output appears in the drawing.

5 — Review & Edit Drawing

Check linework for breaks, mismatches, or offset figures. Fix problem codes in the event editor.

6 — Attach to Template & Plot

Insert or xref into your template, verify styles are applied, check paperspace viewports, and publish.

04

Creating a New Survey Database

The Survey Database (SDB) is the backbone of everything. It lives on disk as a folder and is separate from your DWG. You link a DWG to an SDB, not the other way around.

Step-by-Step

  1. Open your project DWG (your template-based file). Make sure it’s in your project folder.

  2. Open the Toolspace palette. Click the Survey tab (the level icon). If the Survey tab isn’t visible, go to Home → Palettes → Toolspace.

  3. In the Survey tab, right-click Survey DatabasesNew local survey database…

  4. Name the database (e.g., ProjectName_Survey). Choose a location inside your project folder structure.

  5. Click OK. The new SDB appears in the tree.

  6. Right-click the new SDB → Open survey database. This links it to your current drawing session.

▸ Pro Tip — Naming Convention
Use a consistent naming convention like PROJ-2025-Survey so it’s obvious which database belongs to which project. Avoid spaces in database names.

After Creating — Set Database Properties

Right-click the SDB → Properties. Review these settings:

PropertyWhat to Set
Coordinate ZoneYour state plane or local projection (e.g., NAD83 Alaska 5001)
Angular UnitsDegrees, minutes, seconds (DMS) or decimal degrees
Distance UnitsUS Survey Feet or Meters — match your fieldwork
DirectionNorth azimuth or bearing — match your traverse notes
▸ Critical — Set This First
Set your coordinate zone and units BEFORE importing any data. Changing these after import can corrupt your point coordinates or require a full re-import.
05

Configuring F2F Settings

This is the step most beginners skip — and then wonder why their import produces no linework. F2F settings must be assigned to the database before data comes in.

Access Survey Database Settings

  1. In the Survey tab, right-click your SDB → Edit survey database settings…

  2. The Survey Database Settings dialog opens. Navigate to the Field to Finish section in the tree on the left.

Figure Prefix Database

This is the core lookup table for F2F. It maps every field code to drawing behavior.

  1. Under F2F settings, find Figure prefix database. Click the dropdown or browse button.

  2. If your template came with a figure prefix database (common in firm templates), select it here.

  3. If you need to build one: go to Survey tab → Survey Databases → right-click → Figure Prefix Databases → New.

Building or Editing the Figure Prefix Database

Double-click a Figure Prefix Database to open the editor. Each row is one field code:

ColumnPurpose
NameThe exact field code (EP, MH, CL, etc.) — case sensitive
Figure StyleControls how the figure looks (solid, dashed, etc.)
SiteWhich Civil 3D site to place figure geometry in
LayerThe CAD layer for this figure’s linework
BreaklineYes/No — adds figure to surface as a breakline
3D GeometryWhether to preserve elevation in the figure polyline

Code Set Style

The Code Set Style controls point symbol appearance for each code. Think of it as the visual theme layer on top of F2F.

  1. Still in Survey Database Settings, find Code set style.

  2. Assign the code set style from your template. If your template has a Survey-Standard code set, select it.

  3. This controls which block symbol gets dropped at each shot (circle for EP, manhole symbol for MH, etc.).

▸ Template Assumption
Since your template already has styles built out, your main job here is just selecting the right Figure Prefix Database and Code Set Style from the dropdowns — not creating them from scratch.

Other Important F2F Settings

# In Survey Database Settings → Field to Finish:

Process linework during import  =  Yes   # runs F2F automatically on import
Insert figure objects           =  Yes   # creates polylines in the drawing
Insert survey points            =  Yes   # drops point markers
Current point group             =  All Points (or your group)
Lot line closure tolerance      =  0.05 ft  # adjust to your accuracy standard
06

Importing Field Data

With the database configured, you’re ready to import. Civil 3D supports several input formats. The most common for total station as-builts are .fbk (field book), .raw, and plain .csv coordinate files.

Import via Survey Network

  1. In the Survey tab, expand your SDB → right-click NetworksNew network…. Name it by date or crew (e.g., Day1_MainSt).

  2. Right-click the new network → Import field book… (for .fbk files) or use the appropriate import option for your file type.

  3. Browse to your data file. Review the import settings dialog — confirm units and direction match your database settings.

  4. Click OK. Civil 3D processes the traverse, adjusts, and if “Process linework during import” is on, runs F2F automatically.

Import CSV/TXT Coordinate File (No Traverse)

For GPS-collected as-builts or data already reduced to coordinates:

  1. Go to Home → Import → Import Survey Data or use IMPORTSURVEYDATA command.

  2. Select your survey database and network.

  3. Choose Point File as the data type.

  4. Select your file format (PNEZD, PENZ, etc.) to match your CSV column order.

  5. Confirm F2F is enabled in the options, then import.

▸ PNEZD vs PNEZD(comma)
Civil 3D has multiple CSV format definitions. PNEZD means Point#, Northing, Easting, Elevation, Description. Check your actual CSV column order before selecting a format — a mismatch will place all your points in the wrong location.

Setting Control Points (if using raw traverse)

If importing a field book with a traverse, you need to set your control points first so the traverse closes to your project coordinate system:

  1. Expand Networks → right-click Control PointsAdd control point…

  2. Enter the point number, Northing, Easting, Elevation, and description for each known monument.

  3. These will be used automatically during import to orient and adjust the traverse.

07

Running F2F & Reviewing Output

If F2F ran automatically during import, you should already see linework and point markers in your drawing. If not, or if you need to re-run it after changes:

Manually Run F2F

  1. In the Survey tab, right-click your NetworkProcess linework…

  2. In the dialog, confirm the Figure Prefix Database is correct.

  3. Click Process. Figures are generated and inserted into the drawing.

What You Should See in the Drawing

Point Markers

COGO point objects at each shot location, with the correct symbol and label style applied from your template.

Figure Polylines

3D polylines connecting sequential coded shots. These are Survey Figure objects — not plain polylines.

Layer Organization

Each code’s linework should be on its own layer as defined in your Figure Prefix Database.

Blocks

Symbol blocks for manholes, trees, monuments, etc., inserted at the correct rotation and scale.

Checking the Event Viewer

After import, always check the Event Viewer for warnings and errors:

Go to Toolspace → Survey tab → right-click SDB → View Survey Events. Common issues to look for:

  • Unrecognized codes (code exists in data but not in Figure Prefix DB)
  • Figure not closed (begin code with no matching end)
  • Point not found (control point reference that doesn’t exist)
  • Closure errors exceeding tolerance
08

Editing & Fixing the Drawing

F2F gets you 80–90% of the way there. The remaining work is cleanup — fixing figure breaks, adding missing linework, and verifying topology.

Editing Survey Figures

Survey Figures are not plain polylines. Use survey-aware tools to edit them:

  1. In the Survey tab, expand your network → Survey Figures. You’ll see a list of all figures by code.

  2. Right-click a figure → Zoom to figure to locate it in the drawing.

  3. To edit vertices: select the figure in the drawing → right-click → Edit survey figure vertices.

  4. To add a point to an existing figure: right-click the figure in Toolspace → Insert point into figure.

▸ When to Use Plain Polylines Instead
For minor cleanup linework (connecting a broken curb line by 1 foot, closing a building outline), it’s often faster to draw a plain polyline on the correct layer rather than fighting the survey figure editor. Just make sure the layer matches the figure style layer.

Re-running F2F After Code Edits

If your field crew used inconsistent codes and you need to edit the raw data:

  1. In the Survey tab → right-click your network → Edit field book (for .fbk imports).

  2. Correct the code entries in the text editor.

  3. Save and re-import, or right-click network → Re-process field book.

Common Fixes

ProblemCauseFix
Line stops mid-runCrew typed EOP (end) too earlyEdit field book, remove EOP code
Linework on wrong layerCode not in Figure Prefix DBAdd code to FPD, re-process
Building outline not closedLast shot missing CLS codeAdd CLS in field book or close manually
Lines cross each otherCrew shot out of sequenceRe-order points in figure editor
Points missing symbolsCode not in Code Set StyleAdd code to Code Set Style
09

Connecting to Your Template

Since your template is already built out with styles, paperspace frames, and a document structure, this step is about verification — making sure the survey output inherits the correct styles and appears correctly in your layout.

Working in the Same DWG

If you opened your template DWG and linked the survey database to it, your point and figure styles should already be applying from the template. Verify:

  • Point label styles match your firm standard
  • Figure layers match your template layer list
  • Point groups are assigned to the right styles

Xref Approach (if survey is a separate DWG)

Some workflows keep the survey DWG separate and xref it into the final deliverable. In this case:

  1. Complete all F2F processing and cleanup in the survey DWG.

  2. Open your template/deliverable DWG.

  3. Go to Insert → Attach → browse to the survey DWG → attach as Overlay (not Attachment) to avoid chain references.

  4. Set the xref to the correct insertion point and scale (usually 0,0,0 at 1:1 if coordinates match).

Paperspace Viewport Checklist

  1. Double-click inside a viewport to activate it (model space through viewport).

  2. Set the viewport scale using the scale dropdown in the status bar (1″=20′, 1:500, etc.).

  3. Pan to center your survey area. Lock the viewport: right-click the viewport border → Display Locked → Yes.

  4. Freeze unnecessary layers within the viewport using the layer manager (VP Freeze column) — this won’t affect other viewports.

  5. Return to paperspace (double-click outside viewport) and verify your title block, north arrow, and scale bar are correct.

▸ Annotation Scale
Make sure your drawing’s Annotation Scale matches your viewport scale. This controls the size of point labels and linetype gaps. Set it in the status bar at the bottom of the screen before finalizing the layout.
10

Real-World As-Built Checklist

Use this before submitting or plotting your first as-built. Work through each item top to bottom.

Database & Import

  • Survey database created in project folder with correct name
  • Coordinate zone and units set correctly before import
  • Figure Prefix Database assigned with all expected codes
  • Code Set Style assigned matching template styles
  • Control points entered with correct coordinates
  • Field data imported with no critical errors in Event Viewer
  • Unrecognized code warnings resolved (codes added to FPD or field book corrected)

Linework & Drawing Cleanup

  • All EP figures are continuous — no unexplained gaps
  • Curb figures (TC/BC) run parallel without crossing
  • Building outlines are closed polygons
  • Utility features (MH, CB, valve) have correct symbols at correct locations
  • All figure linework is on correct layers
  • No rogue linework on layer 0 or wrong layers
  • Survey points visible and labeled with correct style

Layout & Deliverable

  • Paperspace viewport scale is correct and locked
  • Annotation scale matches viewport scale
  • Title block filled in (project name, date, drawn by, scale)
  • North arrow pointing correctly
  • Scale bar present and accurate
  • Unused layers frozen or turned off in viewport
  • Drawing plotted/published to PDF and visually reviewed
  • PDF checked — no missing text, correct line weights, all symbols visible
▸ Final Review Habit
Always do one final zoom-extents pass in paperspace before plotting. Look for any points or linework that has landed far outside your project area — this usually means a bad coordinate in the raw data that needs to be removed or corrected.

Civil 3D Field-to-Finish Study Guide Autodesk Civil 3D 2022+ · Survey Module