[~/tomko.ai](/)civil.md

#Utility drawings, as structured records.

Civil 0.5

Civil reads what a utility drawing says — its annotations — and returns pipe runs, structures, notes and standards citations as records, with the source of each field and gap records for admitted candidates it could not resolve.

For engineering reviewers, QA/QC teams and principals reviewing utility design.

**[→ See a sample run](#what-comes-back)**

##The information is all there. It’s just scattered.

A utility review means pulling one object back together from a plan sheet, a profile, a note block and a standard.

Then doing it again for the next object.

And the next drawing.

And the next submission.

The same reconstruction work repeats across every drawing and every submission.

##What Civil does today

###Reads the drawing file.

Opens the DWG directly — no export, no intermediate format. Works from the drawing’s annotations, and distinguishes existing conditions from proposed design.

###Reassembles utility records.

Pipe runs come back as single records carrying diameter, material, grade, length, chainages and endpoint inverts. Structures are kept separate from pipes, and carry their inverts with elevation, direction and design state.

###Reads the notes, and the standards they cite.

Numbered items in a note block come back as separate records, each with its verbatim text. Standards cited in the drawing’s text are listed alongside the object that cites them.

###Shows where values came from, and where it stopped.

Records carry per-field provenance — the annotation, layer and entity a value was read from. A candidate Civil admitted but could not resolve comes back as a gap record with a plain-language reason, rather than being dropped quietly.

##What comes back

Illustrative examples. Not from a real project.

###A citation Civil identified, and one it could not.

STD-12|resolved|Trench Restoration Detail
STD-12.1|unresolved|—

resolved means Civil identified the standard and can show you its title. It does not mean the clause was read, and it does not mean the design complies.

Civil puts the citation and the title side by side. It does not compare them. Whether a detail titled Trench Restoration belongs against the note that cites it is the engineer’s call — Civil reports two facts and leaves that judgment where it belongs.

###A pipe run Civil would not guess at.

storm sewer · proposed

No structure could be found at one or both ends of this pipe.

-Missing: a structure label at the pipe end.

###A note, as a record.

Note 7 · General Notes · Sheet 3

“All trench backfill within the road right-of-way shall be compacted to 95% Standard Proctor Density.”

##What Civil does not do.

-**It does not check your design against municipal criteria.** Civil can tell you which standards a drawing cites. It does not read the clause, and it does not judge conformance.
-**It does not read the linework.** Civil works from what the drawing says. A structure drawn as a symbol with no text label is outside what it reads today.
-**It does not walk the network.** It can record which runs meet a structure. It does not follow flow to an outlet.
-**It does not do servicing, hydraulics, utility conflicts or constructability.**
-**And it never signs anything.** Civil is not CAD, not design software, and not engineering sign-off. Engineering judgment stays with the engineer.

##See it on one of your drawings.

Civil is early, and we are deliberate about who we work with.

[→ Run Civil on a drawing](mailto:build@tomko.ai)

Built by Tomko & Company.