MARKSET built for Missouri American Water
Live through Thursday, December 3
First draft, built on guesses. It comes from public information and our best guess at how the job runs. Nothing here came from inside American Water. The plant, the equipment and the job history are made up.
Plant maintenance to the office

Fix it once. Write it up once.

A tech's rough note goes in. The work-order close-out, parts request, follow-up work and equipment history come out, ready for the tech to check. Same crew, less typing, better records.

Try it on a sample job

Pick a job, then press a button. Each note is written the way we'd expect one to come off the floor.

The tech's note

These drafts were written ahead of time to show the format. There's no box to type in on purpose: real notes shouldn't go into this page. A real version would use your own approved tools and your own records.

How a job moves, today and with this

The left column is our guess. We haven't seen how it works at your plants.

Our guess at today

The fix is the fast part
1
Fix the problem
What was wrong and what got done lives in the tech's head, or on a scrap of paper.
2
Write it up later
End of the job or the shift, sometimes more than once: the work order, the log, a text to the supervisor.
3
The office comes back with questions
Which machine? What part number? How many hours? By then it's the next day and another job.
4
The pattern gets missed
"Pretty sure this is the third time" stays a hunch, because nobody has time to dig through old records.

With an assistant behind the crew

Same people, same judgment
1
Fix the problem, same as now
Say or type a rough note on the way out, in your own shorthand.
2
Missing details get caught right away
It asks for the part number while the old part is still in your hand.
3
The tech checks the draft
Close-out, parts and follow-up work are written up. Nothing gets filed until a person reads it and fixes it.
4
The history speaks up
Past work on that machine gets pulled up, so the supervisor sees a repeat failure with the dates in front of them.

What we guessed

If you do this work, this is the part to mark up. A wrong answer here is useful: it tells us what to rebuild.

Where the write-up goes

We guessed a work-order system, plus a paper log or a text to the supervisor.

If it's all one place, the "write it once" pitch gets weaker.

What the office asks about

We guessed machine ID, part numbers, hours and the cause of the failure.

If they never come back with questions, the "What will the office ask?" button goes.

Whether anyone uses the history

We guessed repeat failures are known on the floor but hard to prove from the records.

If the records already show it, the history button goes.

What techs carry

We guessed a company phone or tablet. We don't know if it has Copilot.

If there's no device on the floor, the note gets written up at a shared computer instead.

Inside your AI policy

American Water's published AI policy (updated July 20, 2026) shapes how this would work.

Built around Copilot

The policy names Microsoft Copilot as the generally acceptable tool, and it's the one it allows with confidential information. A pilot would start there, with nothing new installed.

Reviewed first

The policy sends new AI use cases to the AI Governance Committee. A pilot would go through that review before any real job touched it.

A person checks everything

The tech reads every draft and the supervisor makes the calls. Nothing gets filed or ordered on its own.

No real records until then

No company records come to us for a demo. Every job on this page is invented.

Who built this

MarkSet is a St. Louis company that builds AI tools for construction and engineering firms. We've trained a St. Louis mechanical contractor's project managers on AI, and tested an estimating workflow against their past bids. This isn't an American Water product, and nobody at American Water asked for it.

Next step: tell us what's wrong with it. Twenty minutes with someone who knows how a job gets closed out would tell us whether this is worth building. Write to Dylan at [email protected].