How to Create a Setting Out Schedule from CAD Drawings

Why most setting out problems start at the desk, not on site

By the time an engineer is standing on site with a total station or GNSS rover, the damage is often already done. Wrong easting and northing columns. Coordinates still in a local CAD UCS that never got transformed to the national grid. Point IDs that don't match the drawing. These are desk errors, and they're painfully common.

A setting out schedule sounds simple — it's just a list of points with coordinates. But getting from a CAD drawing to a clean, reliable, site-ready schedule involves more steps than most people expect, and each one is a chance for something to go quietly wrong.

This guide walks through the full process: extracting coordinates from CAD, structuring the schedule correctly, validating it before anyone leaves the office, and handing it over in a format that actually works on site.

Step 1: Understand what coordinate system the drawing is in

Before you extract a single coordinate, you need to know what system the drawing is using. There are three common situations:

• National grid (OSGB36/ETRS89): Coordinates will typically be in the hundreds of thousands of eastings and millions of northings for GB. These can go directly to a GNSS rover with the right projection applied.
• Site grid: A local coordinate system, often set up so the origin sits conveniently on or near the site. Common on large civils and infrastructure projects. Requires a known transformation to get to national grid — usually via control points.
• Arbitrary CAD space: The drawing was modelled in CAD without any real-world reference. Coordinates are essentially meaningless until tied to physical control.

Check the drawing title block, the project BIM execution plan, or ask the design team. Do not assume. Transforming from the wrong datum is one of the most expensive mistakes in setting out.

Step 2: Extract coordinates from CAD properly

Manual copying of coordinates from a CAD drawing — clicking on a point, reading the coordinate display, and typing it into a spreadsheet — is a guaranteed way to introduce errors. Even experienced engineers make transcription mistakes, especially across hundreds of points.

Use CAD's built-in extraction tools instead:

• AutoCAD DATA EXTRACTION (DATAEXTRACTION command): Lets you extract attribute data from blocks, including X, Y, Z coordinates and any associated attributes like point IDs or descriptions. Export directly to CSV or Excel.
• AutoCAD POINT export: If your setting out positions are stored as POINT objects, use a script or the LIST command selectively, or better, a custom LISP routine that writes all point coordinates to a text file.
• Civil 3D COGO points: If the project uses Civil 3D, COGO points can be exported directly to a point file in multiple formats (PNEZD, PENZ, etc.) via the Points menu.
• Third-party tools: Plugins like Bricsys, ProgeCAD, or specialist survey software can batch-export point data cleanly.

The output format matters. Aim for a comma-separated file with clearly labelled columns. At minimum you want: Point ID, Easting (Y), Northing (X), Elevation (Z), Description.

Watch the axis convention. In maths and CAD, X is typically east-west and Y is north-south. In surveying and GNSS equipment, it's often the opposite. Swapped axes are one of the most common causes of points being set out in the wrong location entirely.

Step 3: Structure the schedule for site use

A raw CSV export is not a setting out schedule. Before it goes anywhere near site, clean and structure it so that any engineer — including someone who didn't prepare it — can pick it up and use it confidently.

A well-structured setting out schedule should include:

• Point ID: Unique, meaningful, and matching the drawing. Avoid duplicate IDs — they cause confusion about which point is which.
• Easting and Northing: Clearly labelled, in metres, to at least three decimal places for survey-grade work.
• Elevation / RL: Where relevant. Clearly note if these are design levels, finished surface levels, or pile cut-off levels.
• Description: What the point represents — pile centre, fence post, structure corner, etc.
• Drawing reference: Which drawing the point came from and the revision number. When designs change, you need to know which points need updating.
• Status column: Set out / not set out / revised / as-built. Keeps the schedule useful throughout the project lifecycle.

Colour coding is helpful for readability on screen, but don't rely on it — the schedule may be printed in black and white, or opened in software that strips formatting.

Step 4: Validate before you go to site

Validation catches the errors that extraction and formatting steps can introduce. Do this at the desk, not on site.

Practical checks to run:

1. Plot the points: Paste the coordinates back into CAD or QGIS and overlay them on the original drawing. If any points sit obviously in the wrong place, you'll see it immediately.
2. Check ranges: Are all eastings and northings within a sensible range for the site? A single typo can put a point miles away. A quick MIN/MAX check in Excel takes seconds.
3. Check for duplicates: Two points with the same ID but different coordinates, or the same coordinates with different IDs, both cause problems. Use Excel's conditional formatting or COUNTIF to flag them.
4. Cross-reference point count: How many points are on the drawing? How many are in the schedule? If the numbers don't match, something's missing or something was double-extracted.
5. Check elevations are realistic: If the site sits at roughly 45m AOD and your schedule contains a point at 4500m, that's almost certainly a units issue — coordinates in millimetres rather than metres, or a data entry error.

Step 5: Issue it in a format that works on site and beyond

The schedule should be issued as a controlled document — dated, versioned, and tied to a specific drawing revision. When designs change, a new version should be issued and the superseded one clearly marked.

For site use, consider how the setting out engineer will consume the data. Most modern GNSS rovers accept point files directly — PNEZD or CSV uploads via the data collector software (Trimble Access, Leica Captivate, etc.). Confirm the format your equipment expects before you structure the file.

A growing number of teams are also adding What3Words references to each point in the schedule — a three-word address that lets anyone navigate to a specific point with a phone, years after the survey was done. It's particularly useful for maintenance access, audits, and handover documentation where the original survey equipment is long gone.

If coordinate processing and field setting out isn't something you want to handle in-house, Streamtech Setting Out takes CAD drawings and coordinate schedules, processes them into clean point lists, sets them out on site with GNSS, and records every point with What3Words — creating a lasting location record that stays useful long after the project finishes.

The schedule is a living document

Setting out schedules get amended. Designs change, points get added, levels get revised. Build the habit of treating the schedule as a live document with version control, not a one-off export. Keep the master copy in a shared location, log every revision, and make sure site teams are always working from the current version.

The extra discipline at the preparation stage — checking the coordinate system, extracting properly, validating before going to site — is what separates setting out that runs smoothly from setting out that generates expensive rework. Most of the problems are entirely preventable, and they're prevented at the desk.