GDOT as-built GIS submittals checklist for contractors and PMs

This checklist is written for contractors, project managers, and design teams who must prepare GDOT as-built GIS submittals for roadway, utility, and ITS work in Georgia. It lists the deliverables GDOT cites, the exact spreadsheet fields for ITS and linear features, the positional accuracy expectation, QA steps to catch common rejections, and a recommended folder and manifest that speeds review and reduces iterations. Where GDOT contract language is specific, the paragraph cites the original GDOT source documents so you can validate requirements.

Deliverables at a glance

• Completed as-built CADD files, organized and annotated by construction phase
• One overall final CADD file for as-built utility plans where required
• Electronic design calculations and supporting files
• Full-size scanned plan images as TIF files and a full-size PDF of the entire plan set
• ITS and device inventory spreadsheet with required columns and coordinates
• Linear features with begin and end latitude and longitude values
• Submission manifest that maps filenames to deliverable descriptions

GDOT contract provisions require submission of completed as-built CADD files and PDFs of as-built plan sheets, and some projects request a single final CADD file for utility as-builts. See GDOT Programmatic Technical Provisions and the Transform I-285/SR 400 contract attachments for example language and file expectations GDOT Programmatic Technical Provisions Volume 3 and I-285 and SR 400 Improvements — Volume 3.

CADD and electronic design files: required contents and packaging

Prepare CADD deliverables so GDOT reviewers can read them without conversion guesswork. The goal is a complete, documented electronic design bundle that matches the as-built paper plans and GIS exports.

• Provide native CADD files for each construction phase and any export copies GDOT specifies.
• Include all electronic calculations used to derive design geometry or quantities, with filenames that reference the related plan sheets or feature IDs.
• Keep layer naming and attributes consistent. Document your layer naming standard in a short readme so reviewers can map layers to expected features.
• When a contract requests a single overall CADD file for utilities, assemble and QA the final utility geometry and attributes into that file before submission to reduce review rounds (GDOT Programmatic Technical Provisions Volume 3).

Practical tips

• Export a read-only copy in the CAD version GDOT specifies and keep an editable master in your archive.
• Create a short layer map document that lists the layer name, the types of features on that layer, and required attributes.
• Run an attribute completeness report and fix any empty required fields before file export.

ITS device and linear feature inventory: exact spreadsheet fields

GDOT ITS and device inventories expect a structured spreadsheet. Including the exact columns and keeping coordinate values numeric helps reviewers validate the submission quickly. Contracts for ITS and toll related work describe required fields and precision expectations (GDOT General Provisions — SR 21 at I-95 Diverging Diamond Interchange).

• Example required columns: FeatureID, FeatureType, RoadwayName, StationBegin, StationEnd, LatBegin, LonBegin, LatEnd, LonEnd, Manufacturer, Model, InstallationDate, Notes
• Point devices should include a single Lat and Lon. Linear features must include begin and end Lat and Lon values.
• Include device-specific fields when requested, such as pole or mast arm ID, mounting height, power source, and communication type.

Spreadsheet formatting tips

• Keep latitude and longitude in separate numeric columns. Avoid text formatting that can change on save.
• Declare the datum and coordinate reference system in a header row. If the contract allows different datums, state which one you used.
• Provide both Excel and CSV exports when in doubt, so reviewers can open the file without formula issues.

Positional accuracy and QA/QC steps

GDOT requires latitude and longitude values for device inventories and linear features to be accurate to two feet in many contracts. Linear features must include begin and end lat and long values so reviewers can independently verify geometry and stationing (GDOT General Provisions).

Run this QA routine before packaging files for submission. These steps address the most frequent reasons packages are returned.

1. Coordinate verification: compare reported lat and long to GNSS survey points or your control network. Flag any point more than two feet from the control value.
2. Begin and end checks: confirm each linear feature begin point lies at the stated station and the end point lies at the stated station end.
3. Topological integrity: ensure lines do not have gaps or unintended overlaps and that device points snap to the intended linear feature within tolerance.
4. Attribute completeness: run a null-field report and fill missing Manufacturer, Model, Station, or Roadway fields.
5. File integrity: open the exported files in a fresh GIS or CAD instance to confirm layers and attribute tables survive export and that shapefiles or geodatabase exports include all expected fields.

Verification examples

If a camera is listed at Station 12+34.56 on Main Street and the spreadsheet shows LatBegin and LonBegin that are 10 feet away from your GNSS stake at that station, correct the coordinate or update the station value. If a signal span wire is represented as a single line but begin and end coordinates are missing, supply both points so the reviewer can match geometry to stationing.

Image and PDF requirements: TIFs and full-size plan PDFs

GDOT often requires full-size scanned plan images in TIF format plus a full-size PDF containing the entire as-built plan set as a condition of final acceptance on large projects. Provide every as-built sheet as a high quality TIF and combine the set into a single PDF so reviewers can use raster or PDF formats (I-285 and SR 400 Improvements — Volume 3).

• Scan at 300 DPI or higher to preserve text legibility and signatures. Name TIF files to match plan sheet numbers and your manifest entries.
• Embed a title block with project name, sheet number, revision date, and an as-built stamp where required by contract.

File naming, folder structure, and submission manifest

A consistent folder layout, predictable filenames, and a clear manifest reduce reviewer confusion and shorten review cycles. The manifest becomes the reviewers checklist and lets them confirm completeness at a glance.

Recommended folder structure

• /ProjectName_AsBuilt/
• /ProjectName_AsBuilt/CADD/ for native CAD files and the overall final CADD where requested
• /ProjectName_AsBuilt/PDFs/ for the assembled full-size PDF plan set
• /ProjectName_AsBuilt/TIFs/ for scanned plan sheet images
• /ProjectName_AsBuilt/GIS/ for exported shapefiles or geodatabase feature classes
• /ProjectName_AsBuilt/Inventories/ for ITS and device Excel and CSV exports
• /ProjectName_AsBuilt/Calculations/ for electronic calculations and logs
• /ProjectName_AsBuilt/Manifest/ for SubmissionManifest.xlsx and a short readme

Manifest template fields

• File name
• Relative path
• Deliverable category, such as CADD, TIF, PDF, Inventory, Calculations
• Short description and associated plan sheet numbers
• Primary contact and date created
• Coordinate system and datum declaration

Common rejection triggers and how to avoid them

• Missing or inconsistent coordinates — run coordinate verification and populate lat and long fields before export. If any point is off by more than two feet, resolve the source of error with survey staff.
• Disconnected linear geometry — validate topology and ensure begin and end coordinates match stationing and plan geometry.
• Incomplete attribute tables — enforce non-null checks for required fields, and use templates so crews cannot skip Manufacturer, Model, Station, or Roadway fields.
• Mismatched file names and manifest — generate an automated file inventory and compare it to the manifest before zipping the package for submission.
• Unreadable scans — scan at recommended DPI and open each TIF and PDF to confirm text and signatures are legible.

How DCBC LLC can support your GDOT as-built GIS submittal

DCBC LLC offers consulting and production services that map directly to each checklist task. The company lists GDOT as-built GIS submittals among its virtual and consulting services and can assist with CADD assembly, GDOT-compliant as-built GIS exports, 3-point level verification and roadway grade calculations, ITS inventory population and QA, and manifest preparation. See DCBC LLC services for details DCBC LLC services.

• CADD assembly and preparation of a single final utility CADD file where required
• GIS attribute population and export to shapefiles or geodatabase feature classes
• ITS inventory spreadsheet preparation, datum declaration, and coordinate QA
• 3-point level verification and roadway grade calculations to confirm field quantities and stationing
• Submission manifest and folder packaging matched to GDOT contract expectations

Frequently asked questions

What file types does GDOT require for as-built GIS submittals?

GDOT commonly requests native electronic design files, electronic calculations, full-sized TIF images of each plan sheet, and a full-size PDF of the entire plan set. Some contracts also require a single overall CADD file for utility as-builts. See Transform I-285/SR 400 and the programmatic provisions for example wording I-285 and SR 400 Improvements — Volume 3.

What columns must an ITS device inventory include and how accurate must lat and long values be?

At minimum include separate columns for latitude, longitude, station, roadway, device type, manufacturer, and model number. Linear features must include latitude and longitude values for beginning and end points. Latitude and longitude values are expected to be accurate to two feet in many GDOT contract provisions GDOT General Provisions — SR 21 at I-95 Diverging Diamond Interchange.

Does GDOT require a single overall CADD file for utility as-builts?

Some GDOT contracts require a single overall final CADD file for as-built utility plans. The programmatic technical provisions for large projects include explicit directions to submit final as-built utility plans as one overall CADD file where the contract documents call for it GDOT Programmatic Technical Provisions Volume 3.

What basic QA checks should a contractor run before submitting as-built GIS files to GDOT?

Run coordinate verification against survey control, confirm begin and end coordinates for linear features match stationing, validate attribute completeness, check topological integrity, and open exported files in a fresh GIS or CAD instance to confirm layers and attributes survived export. These steps address the most common rejection causes described earlier.

Can a contractor submit geospatial data in projected coordinates instead of lat and long?

GDOT guidance frequently uses latitude and longitude for ITS inventories, and contract language may request lat and long values accurate to two feet. If you need to submit projected coordinates, declare the projection and datum in the manifest and confirm acceptance with the GDOT project manager before final packaging. When in doubt, include both projected coordinates and lat and long columns so reviewers can validate quickly.

Final CTA — To discuss CADD assembly, GDOT-compliant GIS exports, 3-point level verification, or a submission manifest prepared to GDOT expectations, contact DCBC LLC at their official website DCBC LLC.