Look, I get it. You’ve heard the AI hype. You’ve sat through the presentations about how artificial intelligence will revolutionize construction. You’ve nodded along while someone explained machine learning and neural networks and a bunch of other stuff that made your eyes glaze over.

But here’s the thing: you don’t need to understand how the engine works to drive the truck.

This post is for the contractor who wants to try AI this week. Not next quarter. Not after some big company initiative. This week. On your phone. During your lunch break if you want.

No IT department. No software purchases. No twelve-step implementation plan. Just practical wins you can grab right now.

Before We Start: The C.L.E.A.R. Framework

Every prompt in this post uses a simple framework I teach in my workshops. It’s called C.L.E.A.R., and it’s the difference between getting garbage output and getting something you can actually use.

C – Context: Give the AI the background it needs. What’s the situation? What led to this moment?

L – Length and Limitations: Tell it how long the output should be and what to avoid. “Keep it under 200 words” or “Don’t use technical jargon.”

E – Examples: Show it what good looks like. A sample format, a similar email you liked, or just describe what you’re going for.

A – Audience: Who’s going to read this? A client? Your crew? A GC? The AI writes differently for each.

R – Role: Tell the AI who to be. “Act as a construction project manager” gets way better results than no direction at all.

You don’t need all five elements every time. But the more you include, the better your results. Now let’s put it to work.

Win #1: Turn Your Rambling Voicemail Into a Clear Email

You know that supplier who left you a four-minute voicemail about a delivery change, a pricing update, and something about a backordered part? Instead of listening to it three times and taking notes, try this:

Use your phone’s voice transcription (most phones do this automatically now), copy the text, and paste it into ChatGPT or Claude with this prompt:

Role: Act as my executive assistant who understands construction supply chains.

Context: A supplier left me this voicemail about our current project. Here’s the transcription: [paste transcription]

Audience: I need to respond to this supplier professionally. We have a good relationship and I want to keep it that way.

Length and Limitations: Give me a bullet-point summary of the key items first, then draft a response email under 150 words. Don’t add any commitments I didn’t make.

Examples: The email should be friendly but businesslike. Something like how you’d write to a supplier you’ve worked with for years.

Time to learn: 2 minutes Time saved per use: 5-10 minutes Satisfaction level: Surprisingly high

Win #2: Write That Awkward Email You’ve Been Avoiding

Every contractor has one sitting in their mental inbox. The email to the GC about the schedule slip. The note to the client about the change order. The message to that sub who keeps showing up late.

You know what you need to say. You just don’t want to spend twenty minutes finding the right words.

Role: Act as an experienced construction project manager who’s good at difficult conversations.

Context: I need to send an email to our general contractor. The situation: we discovered unforeseen conditions during demo that will add three days to our timeline. This isn’t our fault, but I need to communicate it without damaging the relationship or accepting blame we don’t deserve.

Audience: The GC’s project manager. We’ve worked together on two previous projects and generally have a good relationship.

Length and Limitations: Keep it under 200 words. Be direct but professional. Don’t be apologetic for something that isn’t our fault, but don’t be defensive either.

Examples: I want the tone to be matter-of-fact, like I’m sharing information rather than delivering bad news. Similar to how you’d tell someone about a weather delay.

The AI gives you a draft. You tweak it to sound like you. You hit send. Done.

I’ve watched superintendents go from dreading these conversations to knocking them out in five minutes flat.

Win #3: Decode That Spec Section Nobody Understands

Somewhere in your current project is a spec section written by an engineer who gets paid by the word. Dense paragraphs. Weird cross-references. Language that seems designed to confuse.

Role: Act as a senior construction superintendent who’s been reading specs for 25 years.

Context: I’m working on a commercial project and need to understand this specification section: [paste spec section]

Audience: Write this for me and my foreman. We’re experienced but don’t speak engineer.

Length and Limitations: Break this down into plain English. No jargon. Don’t add requirements that aren’t actually in the spec, and don’t skip anything that is.

Examples: Format it as: first a one-paragraph summary of what this section requires, then a bullet-point checklist of specific things we need to do, then a list of common mistakes that would get us in trouble with the inspector.

This one has saved more arguments on jobsites than I can count.

Win #4: Generate Interview Questions for That New Hire

You need to hire a project engineer. Or a foreman. Or an estimator. The resume looks good, but you want to actually figure out if this person knows their stuff.

Role: Act as an experienced construction hiring manager who’s good at spotting people who exaggerate their experience.

Context: I’m hiring a project engineer for my electrical contracting company. We do commercial and industrial work, projects ranging from $500K to $5M. The candidate claims three years of experience.

Audience: These questions are for me to ask during an in-person interview.

Length and Limitations: Give me ten questions total. At least three should be situational questions that reveal whether they’ve actually done the work. Avoid generic questions you could ask anyone in any industry.

Examples: Include questions like “Walk me through how you handled a situation where…” rather than just “Tell me about your experience with…”

Print them out. Bring them to the interview. Look prepared.

Win #5: Turn Meeting Notes Into Action Items

You just walked out of an owner meeting. Your notebook has fifteen scribbled items. Half of them are assigned to someone. You’re not sure who said what about the HVAC timeline.

Take a photo of your notes (or type out the highlights) and try this:

Role: Act as a project coordinator who’s excellent at organizing meeting documentation.

Context: I just finished an owner meeting for a commercial renovation project. Here are my rough notes: [paste or describe notes]

Audience: This summary will be emailed to all meeting attendees: the owner, architect, and our project team.

Length and Limitations: Keep the summary under one page. Focus only on decisions made and action items. Don’t add anything that wasn’t discussed.

Examples: Format it with three sections: Key Decisions, Action Items (with responsible party and deadline for each), and Open Items to Address at Next Meeting.

Send it to the attendees. You look organized. People know what they committed to. And you didn’t spend thirty minutes reformatting your chicken scratch.

Win #6: Create a Quick Safety Toolbox Talk

It’s Monday morning. You need a toolbox talk. You’ve done ladder safety fourteen times this year. Everyone’s bored. You’re bored.

Role: Act as a construction safety manager who knows how to engage crews that have heard it all before.

Context: I need a toolbox talk about working in hot weather for my electrical crew. We’re doing an industrial project in Kansas in July.

Audience: My crew is experienced. They’ve heard generic safety talks a hundred times. I need something that actually gets their attention.

Length and Limitations: Keep it to five minutes of speaking time. No corporate safety jargon. Make it feel like a conversation, not a lecture.

Examples: Include one specific real-world story about heat illness on a construction site. End with two or three questions I can ask the crew to get them talking instead of just nodding.

Fresh content in sixty seconds. Actually engage your crew instead of reading from the same laminated card.

Win #7: Get a Second Opinion on That Tricky Situation

This is the sleeper hit that most people don’t think about.

You’ve got a situation. Maybe it’s a difficult client request. Maybe it’s a crew conflict. Maybe it’s a contract clause that doesn’t quite cover what’s happening on site.

Role: Act as a construction consultant with 30 years of experience who’s seen every kind of project conflict.

Context: Here’s a situation I’m dealing with: The owner is asking us to accelerate the schedule by two weeks without a change order. They’re implying future work depends on us “being team players.” My gut says we should push back, but I don’t want to lose the relationship.

Audience: Just me. I’m thinking through this decision.

Length and Limitations: Give me a balanced perspective. I don’t want you to just tell me what I want to hear. Point out what I might be missing on both sides of this decision.

Examples: Structure your response as: what the risks are if I push back, what the risks are if I don’t, questions I should ask before deciding, and how you’d approach the conversation if I decide to push back.

The AI doesn’t replace your judgment. But it can surface considerations you might have missed. It’s like having a project manager on call at 10pm when you’re stewing over a problem.

The Secret Nobody Tells You

Here’s what I’ve learned delivering AI workshops to hundreds of contractors: the people who get the most value start small.

They don’t try to transform their entire estimating process on day one. They start by using AI to write one email. Then they try summarizing one document. Then they experiment with one new application.

Those small wins build confidence. That confidence builds curiosity. That curiosity builds competence.

And now you’ve got a framework. C.L.E.A.R. works for everything: emails, documents, meeting prep, you name it. The more specific you get with each element, the better your results.

Your Homework (If You Want It)

Pick one thing from this list. Just one. Try it this week.

When you use the C.L.E.A.R. format, notice how much better the output is than when you just type a vague question. That difference is the whole game.

If it saves you ten minutes, try another one next week. That’s the whole strategy. Small wins that stack up.

The contractors who are going to thrive in the next ten years aren’t the ones who wait for perfect AI solutions. They’re the ones who start messing around with imperfect tools and figure out what works.

Why not be one of them?

Carl Britton Jr. is the founder of Iron Thread Consulting and delivers AI workshops for construction trade associations including NECA, SMACNA, and MCA chapters nationwide. With 20 years in construction and 15 years in technology, he speaks construction, not tech. Learn more at ironthread.online.