How to Talk to AI: A Maintenance Professional's Guide to Prompt Engineering

A technician types "why is my pump vibrating" and gets back a list of nine possible causes. All of them are true. None of them help. So he decides the tool is useless and goes back to what he was doing.

The tool was not the problem. It answered the question it was asked, which was a very general one, so it gave a very general answer.

Here is the thing worth knowing. You do not need to learn any tricks. You need to tell it what you would tell a good technician who just walked onto your site and has never seen the plant before.

Say what you would say to a stranger

Compare the two.

Weak: "Why is my pump vibrating?"

Better: "A centrifugal pump moving cooling water has started vibrating in the last two weeks. It runs about 16 hours a day. We checked alignment last month and it was fine. The vibration is worse when the discharge valve is throttled. What are the most likely causes, and what should I check first?"

The second one takes maybe forty seconds to type. The answer you get back is worth ten times more, because now the tool has something to work with.

You do not need to be tidy about it. You can ramble. What matters is that the details are in there.

Tell it why you are asking

This one surprises people, and it is one of the clearest bits of current advice from the people who build these tools.

Saying who the answer is for changes the answer. "Explain this for a new apprentice" and "explain this for a plant manager who wants to know the cost" produce two very different replies to the same question.

So add a line. Say what you are going to do with it.

Ask for the shape you want

If you need a checklist, ask for a checklist. If you need six lines you can paste into a work order, say six lines. If you want a table, say table.

Otherwise you get a wall of text and you end up rewriting it, which cost you the time you were trying to save.

One small trick. Say what you want rather than what you do not want. "Write it in short plain sentences" works better than "do not be too technical".

Give it permission to say it does not know

This is the most important line in this article, especially for maintenance work.

These tools will sometimes make things up. They do it in a calm, confident voice, which is exactly what makes it dangerous. A made up torque figure looks the same as a real one.

So add this to the end of anything that matters: "If you are not sure, say so instead of guessing."

It genuinely helps. The tool becomes more willing to tell you it does not have the answer, which is far more useful than a confident number you then act on.

It does not make the tool safe. Never take a torque value, a clearance, a pressure rating, or a safety step from an AI answer without checking it against the manual or the standard. Use it to work out what to look for. Use the document to confirm.

Show one example when the format matters

If you want work order notes written a particular way, do not describe the style. Paste one that is already written the way you like it, then ask for the next one to match.

One good example does more than a paragraph of instructions. Start with one. Only add a second if the first did not do the job.

Longer is not better

There is a habit of writing very long prompts, full of instructions, in the belief that more must be better.

It is not. The people who build these tools now say the same thing plainly: over long, over stuffed prompts often make results worse, not better. What helps is the right detail, not more detail.

A few of the old tricks have also quietly stopped mattering. You used to be told to start with "act as a senior reliability engineer" or to wrap everything in tags. With current models that is mostly unnecessary. Just say clearly what you want and who it is for.

Fix it in the second message

Most people treat the first answer as final. If it misses, they give up.

You are having a conversation. Say what was wrong with the answer and ask again. "Too general, this is a 40 year old pump and we have no vibration kit." "That is for a different type of seal." "Shorter, and skip the introduction."

The second answer is usually the good one. Expecting the first to be perfect is the single most common reason people conclude these tools do not work.

Watch what you paste in

Before you upload or paste something, ask whether you would mind it ending up outside the company.

Client drawings, contracts, incident reports with names in them, anything marked confidential. Keep those out of free tools. Free accounts may use what you type to train their systems. Paid business accounts usually do not, but check your own site's rules rather than guessing.

Asking how a mechanical seal fails is fine. Uploading a customer's drawing is not.

A prompt you can steal

This shape works for most fault finding, and you can keep it in a note on your phone.

Here is the equipment and what it does. Here is what changed and when. Here is what I have already checked and what I found. Here is what I want from you and who it is for. If you are not sure about anything, say so rather than guessing.

Fill in the blanks and you will be ahead of most people using these tools.

The part that stays yours

None of this makes the tool an engineer. It has never seen your plant, it does not know your history, and it cannot hear the noise.

What it can do is help you think. It will remind you of causes you had not considered, explain a standard in words you can use, and turn your rough notes into something readable in a fraction of the time.

The judgement is still yours. It always was.