The gap between getting nothing useful out of AI and getting something genuinely helpful almost always comes down to the prompt. Most builders who have tried ChatGPT once and walked away unimpressed are not running into a model problem. They are running into a briefing problem.
We see this every week in construction firms across the country. An estimator types a half sentence into the chat box, gets a generic response, and writes the whole tool off. Then a project manager on the same team types three paragraphs of real context and the output is immediately useful for an RFI response, a subcontractor email, or a toolbox talk.
Prompting is also changing. The skill used to live entirely inside a chat window, where you typed a request and got a reply. It is now moving into global instructions, meta prompts, and agent configurations that govern AI working across your inbox, your drive, and your project files.
The surface area is different. The fundamentals are the same. Here are the practices that hold up whether you are typing in a chat box or setting up an AI agent to run across your systems.
Give it the context a new hire would need
The most common prompting failure in construction is underbriefing. People type a single line, hit enter, and expect the model to know which project, which client, which trade, and which audience. It cannot guess any of that.
Treat the AI like a capable new hire on day one. Spell out who you are, what the project is, who the output is for, and what a good answer looks like. A prompt that opens with “I am a project manager on a hospital expansion in Western Pennsylvania, responding to an RFI from our mechanical sub about a hanger detail conflict” will beat a prompt that opens with “write me an RFI response” every time.
Role Play: Tell it who to be
A short role assignment changes output quality in a noticeable way. A prompt that starts with “You are a senior superintendent with twenty years of commercial experience, writing a toolbox talk for a steel erection crew on fall protection in cold weather” produces something closer to what a real super would say than a generic safety brief.
Roles work because they compress a huge amount of implied context into one line. You are telling the model what tone to take, what vocabulary to use, and what priorities to weigh. For safety content, JHAs, or field communication where voice matters, this is the single highest-leverage move you can make.
Use the “Given, do” structure
A clean prompting pattern we teach every client is “Given ABC, do XYZ.” You hand the model the context first, then ask for the output.
In practice that looks like: “Given these notes from today’s OAC meeting and last week’s action items, produce a clean summary with outstanding owners and due dates in a table.” The model does not have to guess at the source material or the format. It reads the context, then executes.
This pattern also maps directly onto agent configurations. When you set up standing instructions for a tool that summarizes meetings or drafts RFIs, you are doing the same thing at scale. You are telling the agent what inputs to expect and what outputs to produce.
Tell it what you want, not what you do not want
A quirk worth knowing: AI models respond better to positive instruction than to prohibitions. If you tell a model “do not sound too casual,” you often get something still casual. If you tell it “write in a professional, measured tone appropriate for a client-facing email,” you get closer to what you actually want.
The same is true for format. “Do not use bullet points” works less reliably than “write this as three short paragraphs.” Lead with the thing you want to see on the other side.
Show it an example
When you need output that matches a specific tone, voice and style, paste in an example. Maybe a toolbox talk you liked, a closeout email you wrote last month, or a scope section from a proposal that read the way you wanted.
One example is usually enough to lock in voice, length, and structure. Two or three is even stronger. This is called few-shot prompting, and it is the fastest way to get AI to sound like your company rather than the internet.
Have a conversation, not a transaction
Most people treat AI like a search engine. They type once, read the output, and move on. That leaves most of the value on the table.
Treat the model like a collaborator. Tell it what worked, what missed, and what to fix. A follow-up like “this is closer, but the tone is too formal for a sub we have worked with for ten years, loosen it up and shorten the opening” will often produce a second draft that is genuinely usable.
Where this is going
The practices above started in chat windows. They are now the building blocks of something bigger.
Global instructions and meta prompts are the new frontier. These are the standing rules you give an AI tool or agent so it knows how to behave across every task it does for you. A global instruction might say “you are assisting the preconstruction team at a commercial GC in Western Pennsylvania, use measured and professional language, when summarizing meetings always output owners and due dates in a table, when drafting RFIs always include the drawing reference and the date received.”
The agent then carries that context into every interaction. You stop rewriting the same setup every time. The fundamentals do not change.
Context, role, examples, positive framing, and iteration still do all the heavy lifting. They just move upstream, from the individual prompt into the standing configuration of the tool.
This is what makes prompting worth taking seriously right now. The people who learn to brief AI well in a chat window are the same people who will be setting up capable agents next year. The skill compounds.
Where to start Monday morning
Pick one workflow you already do every week. An RFI response, a toolbox talk, or a meeting summary is a good starting point. Write a prompt that includes your role, the project context, an example of the output you want, and the format you need.
Run it, review it, and tighten it. Do that three times on the same workflow and you will have a prompt you can reuse. Do it across five workflows and you will have a prompt library that pays you back every week.
That is how prompting stops being a trick and starts being a skill. And it is how builders get ready for what is coming next.
