Watch your best estimator for an hour. She opens an RFQ package and reads the drawings. Then she spends most of her morning typing part numbers into the quote sheet and material grades into the costing spreadsheet, with quantities, finishes, and tolerances going in one cell at a time.

The part of her job that makes you money is the ten minutes where she looks at a weldment and says, "This will fight us in the fixture. Add two hours." The typing wears her out, and many skilled people in your office spend their days the same way.

When AI does the first pass, the software takes the typing and she keeps the ten minutes. Here is how three jobs change, and how to explain it to your team.

41.43%of manufacturers give frontline workers no AI trainingNAM Q2 2026 Outlook Survey
25.24%train workers on data and reading AI outputsNAM Q2 2026 Outlook Survey
71%of US adults expect AI to mean fewer US jobs over 20 yearsPew Research Center, 2026

How three jobs change

The estimator

With AI doing the first pass, the RFQ comes in with the draft already done. The software pulls the line items from the drawings and matches material to your price list. It also attaches past quotes for similar parts.

Anything it could not read clearly, like a smudged callout or a note that contradicts the title block, sits flagged at the top.

She reviews the draft and fixes the two line items it got wrong. She adds the two hours for the fixture, because the software does not know your fixtures the way she does. Then she sets the margin and sends it.

The quality manager

Before: She checks every compliance packet page by page, comparing each heat number on each MTR against the receiving log and each grade against the PO. Most of it matches. She checks it all anyway, because the one value that does not match comes back as a customer complaint.

After: The software builds the packet and checks every value against its source document. It marks matching values as matched, with a link to where each came from. The mismatches go at the top of her list, like a heat number on the MTR that does not appear on the receiving form or a grade that differs from the PO.

She reviews the flagged mismatches first and decides what each one means, then spot-checks the rest before she signs. Her signature means what it always did, and her attention went where the risk was.

The coordinator

Before: She lives in the shared inbox, where cert requests, PO changes, drawing revisions, and "where's my order" emails arrive mixed together. Most of her day goes to reading and sorting before any real work starts.

After: The software reads, sorts, and routes incoming requests. It matches a routine cert request to the job and drafts a reply, or it summarizes a change order and sends it to the right person. The coordinator gets what does not fit, like a customer who wants a partial shipment on a job that is not split or a rev change on a part that is already cut.

Those exceptions are where you win or lose customers. They were always the part of the job that needed her.

Reviewing well takes training

Reviewing a draft is a different skill from building one. When you build from scratch, you think about every line because you have to. When you review, it is tempting to skim, and the urge grows when the draft is right nine times in a row. The tenth draft is the one that matters, and it will look exactly as confident as the other nine, because the software sounds just as sure when it is wrong.

Teach your reviewers to work in the same order every time:

  1. Flags first. Check anything the software marked as unsure or mismatched before anything else.
  2. Critical fields next. These are the values where a mistake causes real harm. On a cert packet that is usually the PO, the part number and revision, the heat number, and the country of origin. On a flow line pressure test record, it is the test pressure and hold time. Check each one against its source, even when it is not flagged.
  3. A random spot check. Pick a few unflagged values a day and check them anyway.
  4. A one-line reason for every fix, such as "wrong rev, customer sent B on the 12th." Those lines show you which mistakes keep coming back.

Then watch for rubber-stamping. A reviewer who approves 40 drafts in ten minutes without opening the attachments has turned the safety step into decoration. Track minutes per review alongside the fixes. A number that drops close to zero will usually show it first.

What manufacturers train frontline workers on about AI percent of all manufacturers surveyed, Q2 2026
No AI training at all41.43%
Introductory or awareness level40.00%
Data, analytics, or reading AI outputs25.24%
Using AI for quality, production, maintenance, or logistics21.43%
Operating AI-enabled machines or software18.57%
Advanced or role-specific13.33%

Source: NAM Q2 2026 Manufacturers' Outlook Survey, question 19. Respondents could pick more than one answer. 7.62% were uncertain.

Accountability stays with people. Your quality manager signs the CoC. Your estimator commits to the price. If a bad packet ships, your customer will not accept "the AI did it," and you should not accept it either.

That is the right design, but it means people have to trust the tools enough to use them and distrust them enough to check. The review order above is how you hold that balance on a busy day.

Measure reviewers by what they catch

After you roll out AI, stop measuring people on how many pages they typed. That measure brings skimmed reviews and resentment. Measure what they caught instead. Count the drafts they fixed, the one-line reasons they wrote, and the critical errors that stopped at their desk.

Your most experienced people become more valuable, because they know what a wrong answer looks like.

When your people ask whether AI will replace them

Your people will ask whether this is how you replace them, a few of them out loud and most of them to each other in the parking lot.

US adults more concerned than excited about AI percent of adults
202137%
202238%
202352%
202451%
202550%
202652%

Source: Pew Research Center, survey of 3,488 US adults.

Answer it honestly, before they have to ask. The software does the first pass, and people verify, decide, and sign. We build the system that way on purpose. A person has to approve each item before it goes out the door, and that person is accountable for it.

Then say what you are going to do with the hours that come back. Look at your own backlog first. Put those hours on the work you have no one for today: quoting the RFQs you currently pass on, catching problems before they ship, and calling back the customer with the question nobody else can answer.

Do not promise what you cannot keep. If you are not sure how roles will shift in two years, say so. People can handle "I don't know yet, and I'll tell you when I do." They cannot handle finding out later that you knew.

Words to use when you tell your team

Here are a few lines you can use:

  • "The software does the typing. You do the thinking."
  • "Nothing goes out without your name on it, same as today."
  • "If it gets something wrong, you're the one who catches it. That's the job."
  • "We're doing this so you stop drowning in data entry, not so we can do without you."
  • "Tell me what's annoying about it. You're the one using it."

Avoid consultant words like "efficiency," "optimization," and "headcount." They land badly, even when you do not mean them the way people hear them.

What to do this week

  1. Shadow one estimator, one quality person, and one coordinator for an hour each. Write down how much of that hour goes to typing, copying, or sorting.
  2. Ask each of them, "If the typing were done for you, what would you spend the time on?" Write down the answers.
  3. Pick the one task where a mistake costs the most. List its critical fields. That list is where review training starts.
  4. Draft your own version of the message above. Change it until it sounds like you. Hold it until you know what you are rolling out and when.
  5. For each quote, packet, and customer reply, write down the person accountable for approving it.

Questions people ask

What does human in the loop mean for AI in manufacturing?

It means a person reviews and approves the AI's work before it counts. The software drafts quotes, cert packets, and replies, and a person checks them against the source documents and signs off. Nothing goes out the door until that person says yes.

How does AI change an estimator's job?

With AI doing the first pass, an RFQ arrives with line items pulled from the drawings, material matched to the price list, and similar past quotes attached. The estimator reviews the draft, fixes what is wrong, adds the judgment calls the software cannot make, sets the margin, and sends it. The estimator types far less and keeps every judgment call.

How should I tell my employees about AI?

Tell them before they have to ask: the software does the first pass, and people verify, decide, and sign. Say what you plan to do with the hours that come back, and do not promise what you cannot keep. Avoid words like efficiency, optimization, and headcount, which land badly on the floor.

Terms in this piece

First pass
the initial draft the software produces by reading documents and filling in values, before any person reviews it.
Verification
a person checking the software's draft against the source documents and correcting what is wrong.
Flag
a mark the software puts on a value it is unsure about or that does not match another document, so a reviewer checks it first.
Critical field
a value where a mistake causes real harm, such as the heat number or the part revision on a cert. The reviewer checks it every time, flagged or not.
Approval step
the point where a person must say yes before anything leaves the building. The software cannot skip it.
Human in the loop
a setup where a person reviews and approves the software's work before it counts.
AI
software that can read, write, and make first-pass decisions from documents and instructions, instead of only following fixed rules.