AI content specialist & trainer
I teach models the difference between writing that sounds finished and writing that is true.
For eight years I checked gas-utility maps against field packets. The question was whether the record could stand, not whether a sentence sounded complete. I use that check on AI-generated text: name the source, mark the words doing the work, and repair only what fails.
Domain
Gas distribution GIS. Service lines, LocusView as-builts, GE Smallworld, ArcGIS, and the field packet that either confirms the feature or holds it.
Craft
Evaluation, labeling, and rewrite. I mark what is unsupported, what cannot be followed, and what is only fluent, then I put the sentence back in an order a person can use.
Use
Training examples and corrected drafts for a second reader: a mapper, a coordinator, a reviewer. The test is whether they can act, not whether the first glance feels done.
Essays
- Scoring AI utility prose
Six checks I use before I trust a sentence about a service line.
- The as-built sentence is not the attribute
A summary can sound like a record and still leave the feature unchanged.
- A rubric for procedure models
If the model cannot name the stop, it has not written a procedure.
Recent posts
All posts- How Atmos Energy uses GIS
What I actually did with Atmos maps — service lines, as-builts, and a hold when they did not match.
- ArcGIS in plain words
What people mean when a job posting says ArcGIS.
- Checking a service line on the map
Three things to compare, and when to stop.