How do I compare as-built rim and invert elevations with the design structure schedule with AI?
After storm or sanitary structures go in, the as-built survey comes back as a point file or PDF while the design rim and invert elevations live on a structure schedule and profile sheets. Differences of a tenth show up late, when the next run of pipe won't match. Have Claude or ChatGPT read the as-built shots and the design schedule into one table, and have Copilot in Excel or Gemini in Google Sheets flag structures whose rim or invert misses the design by more than the tolerance you set. Whether a structure must be adjusted, and whether the design should change, stays with the civil engineer of record.
Civil Engineer · Civil · Claude · ChatGPT · Microsoft Excel · Microsoft Copilot · Google Sheets
Content updated · Tool links listed below; vendor features and pricing change, so confirm with the vendor
Short answer
Use Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets: Claude or ChatGPT reads as-built survey points or structure tables into rows and proposes ID matches to the design schedule; Copilot or Gemini computes rim and invert differences, flags misses outside your tolerances, missing shots or design rows, and rim-to-invert depths that differ sharply from design. After storm or sanitary structures go in, the as-built survey comes back as a point file or PDF while the design rim and invert elevations live on a structure schedule and profile sheets. Differences of a tenth show up late, when the next run of pipe won't match. Have Claude or ChatGPT read the as-built shots and the design schedule into one table, and have Copilot in Excel or Gemini in Google Sheets flag structures whose rim or invert misses the design by more than the tolerance you set. Whether a structure must be adjusted, and whether the design should change, stays with the civil engineer of record. A person still checks: every flag with the inspector and contractor; field corrections, design revisions and anything stamped stay with the civil engineer of record.
AI tie-in
Tool: Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets
Claude or ChatGPT reads as-built survey points or structure tables into rows and proposes ID matches to the design schedule; Copilot or Gemini computes rim and invert differences, flags misses outside your tolerances, missing shots or design rows, and rim-to-invert depths that differ sharply from design.
Prompt 1
Read this as-built survey point file or structure table [upload]. Build a table with one row per structure: structure ID as written, rim elevation, each invert elevation with a label (in, out, direction) and the survey date. Copy elevations exactly and write NOT SHOWN instead of guessing. Then propose matches to this design schedule [paste: structure ID, type, design rim, design invert in, design invert out] with a confidence word (clear, likely, unsure). Do not decide whether a structure must be adjusted.
Prompt 2
Here are the headers and a few sample rows of my Design tab [paste: structure ID, type, design rim, design invert in, design invert out], my AsBuilt tab [paste: structure ID, rim, invert in, invert out, survey date] and my Tolerances tab I typed [paste: rim tolerance, invert tolerance]. Write Excel formulas (or a step-by-step Copilot plan) that match structures, compute rim and invert differences, flag differences outside my tolerances, missing as-builts or missing design rows, and rim-to-invert depths that differ sharply from design, and summarize by structure type. Use only my data; do not decide whether a structure must be adjusted.
Human check: Every flag with the inspector and contractor; field corrections, design revisions and anything stamped stay with the civil engineer of record.
The problem
Compare as-built rim and invert elevations with the design structure schedule with AI. This is a common, time-consuming task for a civil engineer.
What this workflow does
After storm or sanitary structures go in, the as-built survey comes back as a point file or PDF while the design rim and invert elevations live on a structure schedule and profile sheets. Differences of a tenth show up late, when the next run of pipe won't match. Have Claude or ChatGPT read the as-built shots and the design schedule into one table, and have Copilot in Excel or Gemini in Google Sheets flag structures whose rim or invert misses the design by more than the tolerance you set. Whether a structure must be adjusted, and whether the design should change, stays with the civil engineer of record.
How it works: AI drafts or analyzes. A person operates the tools, checks the work, and takes action.
Your checkpoint: The comparison only reflects the design schedule and as-built values you entered. Survey error, unsettled backfill and mismatched IDs can create false flags, and a clean row hasn't been checked for pipe slope between structures in the field. Field corrections, design revisions and anything stamped stay with the civil engineer of record.
Before you start
- Access to the named tool; confirm license, version and cost with the vendor.
- A small, non-confidential sample to try the workflow on first.
- A qualified person to review the output before it is used.
Tools and access
Follow the steps
- Export the design structure schedule (structure ID, type, design rim, design invert in and out, pipe sizes if shown) from the drawings or Civil 3D, and collect the as-built survey points or the surveyor's structure table for the same IDs.
- Have Claude or ChatGPT read the as-built source into an AsBuilt tab: structure ID as written, rim elevation, each invert elevation with a label (in, out, direction) and the survey date. It copies elevations exactly and writes NOT SHOWN instead of guessing.
- Have it propose matches from as-built IDs to design IDs where naming differs (leading zeros, MH vs STM), with a confidence word. You confirm the mapping.
- Have Copilot in Excel or Gemini in Google Sheets compute rim and invert differences per structure and flag differences outside the horizontal and vertical tolerances you type from your own QA rules or the contract.
- Flag structures surveyed with no design row, design structures with no as-built shot, inverted slopes between structures compared with the design flow direction you enter, and structures whose rim-to-invert depth differs sharply from design.
- Walk the flagged list with the inspector and contractor, decide field fixes versus design revisions, and keep the comparison with the as-built submittal.
Try a small example
Replace the bracketed fields with your own project details. No tested sample run is published for this workflow yet.
Sample input
Fill in the bracketed [fields] in the text below with your project data.
Starter prompt
Here are the headers and a few sample rows of my Design tab [paste: structure ID, type, design rim, design invert in, design invert out], my AsBuilt tab [paste: structure ID, rim, invert in, invert out, survey date] and my Tolerances tab I typed [paste: rim tolerance, invert tolerance]. Write Excel formulas (or a step-by-step Copilot plan) that match structures, compute rim and invert differences, flag differences outside my tolerances, missing as-builts or missing design rows, and rim-to-invert depths that differ sharply from design, and summarize by structure type. Use only my data; do not decide whether a structure must be adjusted.
Expected output
Not published yet. Treat any output as a draft and check it against the source documents.
Check the result
- Every value, citation or quantity traces back to a source document.
- Missing information is marked as missing, not filled in.
Limits and recovery
- The comparison only reflects the design schedule and as-built values you entered. Survey error, unsettled backfill and mismatched IDs can create false flags, and a clean row hasn't been checked for pipe slope between structures in the field. Field corrections, design revisions and anything stamped stay with the civil engineer of record.
- Check your organization’s data policy before sharing project files with third-party tools.
Stop or switch when: The source cannot be verified, permissions are missing, or the result contains unsupported facts.
Frequently asked questions
How does AI help with this?
Claude or ChatGPT, then Copilot in Excel or Gemini in Google Sheets: Claude or ChatGPT reads as-built survey points or structure tables into rows and proposes ID matches to the design schedule; Copilot or Gemini computes rim and invert differences, flags misses outside your tolerances, missing shots or design rows, and rim-to-invert depths that differ sharply from design. A person still checks: Every flag with the inspector and contractor; field corrections, design revisions and anything stamped stay with the civil engineer of record.
How do I how do I compare as-built rim and invert elevations with the design structure schedule with AI??
Export the design structure schedule (structure ID, type, design rim, design invert in and out, pipe sizes if shown) from the drawings or Civil 3D, and collect the as-built survey points or the surveyor's structure table for the same IDs. Have Claude or ChatGPT read the as-built source into an AsBuilt tab: structure ID as written, rim elevation, each invert elevation with a label (in, out, direction) and the survey date. It copies elevations exactly and writes NOT SHOWN instead of guessing. Have it propose matches from as-built IDs to design IDs where naming differs (leading zeros, MH vs STM), with a confidence word. You confirm the mapping. The full step list is above.
Does this use an AI agent or regular software?
It is labeled AI assists: AI drafts or analyzes. A person operates the tools, checks the work, and takes action.
What tools do I need?
Claude, ChatGPT, Microsoft Excel, Microsoft Copilot, Google Sheets. Confirm license, version and cost with the vendor, and try it on a small non-confidential sample first.
Has this workflow been tested?
Workflow guide · not independently tested. Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written.
Evidence and maintenance
Written from vendor documentation and practitioner use. Labels apply to the steps described here, not every feature of a product. Links were checked when the page was written.