Hard Hat AI

Hard Hat AI Built by builders. Powered by AI. Train like a superintendent. Hard Hat AI was built on the jobsite. So we built the tools. Then we built the training.

Win with AI tools built for the jobsite.
👷‍♂️ Field-tested courses.
🧠 Smart agents.
đź›  Real results.
👇 Join the training that’s changing the game. We’re Shawn and Catherine — a builder and a strategist who got tired of watching good supers burn out doing work that AI could handle. Now we’re giving it all back to the field. Let me know if you want to add a call-to-act

Punchlists don’t need a war room—just structure. Here’s how I turn raw notes into an owner-clean punchlist in minutes wi...
09/26/2025

Punchlists don’t need a war room—just structure. Here’s how I turn raw notes into an owner-clean punchlist in minutes with ChatGPT.

Paste this (table output):

Turn these notes into a punchlist table.

Columns:
Item | Location/Room | Trade | Priority (H/M/L) | Owner-Critical (Y/N) | Due Date | Status (Open/Done) | Notes/Photos

Group by room/area and sort Owner-Critical items to the top.
Keep it concise and field-ready.

NOTES:
[Paste your raw notes here]

Auto-assign to subs (WhatsApp/Email):

Create a message to [Trade / Company] listing their punchlist items with
Location, Item, Due Date. Ask for photo verification on completion and
to reply “DONE + photo” using this filename format:
[Project]-[Room]-[Trade]-[Item]-YYYYMMDD.jpg
Tone: professional, concise.

Daily focus list (for standup):

From the table, filter Owner-Critical = Y and Priority = H due in the next 72 hours.
Output a short “Today’s Focus” list grouped by trade with checkboxes.

Closeout package:

Generate an owner-facing summary: total items, % complete by trade,
remaining Owner-Critical items, and ETA to 100%. Bullet format.

Avoid these mistakes

One giant list → Group by room/area

No accountability → Trade-tag + due date

No evidence → Photo verification + naming convention

Want my Punchlist Master Sheet + pre-written sub messages?
Comment PUNCH or DM me “PUNCH.”

Toolbox talks don’t need 30 minutes and a lecture voice. They need clarity and sign-offs. Here’s how I knock them out in...
09/25/2025

Toolbox talks don’t need 30 minutes and a lecture voice. They need clarity and sign-offs. Here’s how I knock them out in 2 minutes with ChatGPT and get on with the build.

Paste this (universal talk template)

Create a toolbox talk / JHA for [TASK] at [LOCATION] on [DATE].
Audience: mixed-trade crew (English + Spanish). Include bullet sections: Scope, Hazards, Required PPE, Controls/Procedures, Permits/LOTO, Housekeeping, Emergency plan (address + supervisor phone),and a sign-off line for each worker (Name, Company, Time).Keep it short, respectful, jobsite-ready.

Common tasks (copy/paste one line into [TASK]

Ladder work & elevated platforms

Silica dust (cutting concrete/CMU)

Hot work (permit required)

Trenching & excavation

Interior demo with live utilities

Roof work / fall protection

Need it bilingual? Add this:

Provide the talk in English, then Spanish. Keep construction terms accurate.

Sign-in sheet (table output)

Generate a sign-in table with columns:
# | Name | Company | Task | Time | Supervisor Initials

What to avoid

Paragraph walls → Use bullets

“Be careful” → List the control (guardrails, spotter, wet cut, vacuum)

No emergency info → Add site address + lead’s phone

Learn it today. Put it to work tomorrow.Here’s the 30-minute starter that turns ChatGPT into a real jobsite partner—no t...
09/24/2025

Learn it today. Put it to work tomorrow.
Here’s the 30-minute starter that turns ChatGPT into a real jobsite partner—no tech talk.

Framework: Train → Task → Check

Train: give project context (tenant, city, phase, constraints)

Task: tell it the sections you want

Check: 1 pass, send, then save the prompt as a template

Copy/Paste Starters (use these today)

1) 7-Day Look-Ahead (Scheduling) – 10 min

Create a 7-day superintendent look-ahead for [Project, City].
Include: inspections (by day), deliveries (item + ETA), crew needs by trade,
hold points, and 1 risk per day with mitigation. Bullet format, field-ready.

2) Scope of Work (Trade-Ready) – 10 min

Write a Scope of Work for [Trade] on [Project, City].
Sections: General Conditions, Schedule, Hold Points/Inspections, Coordination,
Materials/Standards, Code/ADA notes, Submittals, Rough-in Tasks, Closeout,
As-Builts, Punchlist responsibility, Manpower/Equipment, Exclusions,
Plan References (sheet + detail tags). Headings + bullets. Professional.

3) Punchlist (Owner-Clean) – 10 min

Turn these notes into a punchlist table with: Item, Location/Room, Trade,
Priority (H/M/L), Owner-Critical (Y/N), Due Date, Status (Open/Done), Notes/Photos.
Group by room/area.

Common mistakes (and fixes)

“Write a report” → List the sections you want

No plan refs → add sheet/detail tags (A-102, E1.01…)

No deadline → include a Needed-By date to drive decisions

Paperwork eats your evenings. It shouldn’t.Here are 3 fast wins supers are automating with ChatGPT—no tech talk.1) 7-Day...
09/23/2025

Paperwork eats your evenings. It shouldn’t.
Here are 3 fast wins supers are automating with ChatGPT—no tech talk.

1) 7-Day Look-Ahead (Scheduling)

Create a 7-day superintendent look-ahead for [Project, City].
Include: inspections (by day), deliveries (item+ETA), crew needs by trade,
hold points, and 1 risk per day with mitigation. Bullet format, field-ready.

2) Scope of Work (Trade-Ready)

Write a Scope of Work for [Trade] on [Project, City].
Sections: General Conditions, Schedule, Hold Points/Inspections, Coordination,
Materials/Standards, Code/ADA notes, Submittals, Rough-in Tasks, Closeout,
As-Builts, Punchlist responsibility, Manpower/Equipment, Exclusions,
Plan References (sheet + detail tags). Headings + bullets. Professional.

3) Punchlist (Owner-Clean Closeout)

Turn these notes into a punchlist table with: Item, Location/Room, Trade,
Priority (H/M/L), Owner-Critical (Y/N), Due Date, Status (Open/Done), Notes/Photos.
Group by room/area.

Avoid these time-killers

Vague asks → List the sections you want

No plan refs → Add sheet/detail tags (A-102, E1.01, etc.)

No deadline → Include a Needed-By date to drive decisions

Want your boss to notice? Ship clear, short, decision-ready reports—fast.What bosses actually care about: Inspe...
09/22/2025

Want your boss to notice? Ship clear, short, decision-ready reports—fast.

What bosses actually care about:

Inspections: result + next step

Risks/Holds: what blocks the schedule

Tomorrow’s Plan: who/what/where, by trade

Copy/paste prompt (Daily Report)

Write a superintendent daily report for [Project] in [City]. Weather [temp/conditions]. Sections (bullet format): work completed by trade, inspections (result + next steps), deliveries, manpower (trade + headcount), issues/RFIs (with sheet refs) delays/mitigation, safety notes, photos taken, and tomorrow’s plan by trade.

Keep it concise, professional, inspector-ready.

Subject lines that get opened

[Project] — Daily Update [MM/DD] (Inspections + Tomorrow)

[Project] — Risks/Holds & Plan for [MM/DD]

3 mistakes to avoid

Paragraph walls → Use bullets

“Please advise” → Ask for a decision

No sheet refs → Add them (A-102 / E1.01, etc.)

Still the last one out? that’s not a badge of honor—it’s a broken process. here’s the 10-minute nightly close that gets ...
09/21/2025

Still the last one out? that’s not a badge of honor—it’s a broken process. here’s the 10-minute nightly close that gets you home on time.

Train → Task → Check

Train with project, city, scope, and today’s highlights

Task with exact sections you want

Check once, send, save the prompt as a template

copy/paste starters

Daily Report (10 min)

Write a superintendent daily report for [Project] in [City]. Weather [temp/conditions].
Sections (bullet format): work completed by trade, inspections (result + next steps), deliveries, manpower (trade + headcount), issues/RFIs (with sheet refs),
delays/mitigation, safety notes, and tomorrow’s plan. Field-ready and concise.

Owner/Inspector Email (2–3 min)

Write a status email for [Project] summarizing today’s inspections, deliveries,
manpower by trade, open issues/RFIs (with sheet refs), and tomorrow’s plan.
Add next steps and a subject line.

Punchlist (5 min)

Turn these notes into a punchlist grouped by room/area with trade tags,
location, pass/fail checkbox, owner-critical flag, and due dates.

Avoid these mistakes

“Write a report” (too vague) → list the sections

No sheet refs → slows decisions

No needed-by date → drift

You don’t burn out swinging a hammer—you burn out typing at 9PM.Here’s how I cut the admin without cutting quality.Frame...
09/20/2025

You don’t burn out swinging a hammer—you burn out typing at 9PM.

Here’s how I cut the admin without cutting quality.

Framework: Train → Task → Check

Train ChatGPT with project, city, scope, and today’s highlights

Task it with the exact sections you need

Check once, send, and save the prompt as a template

Copy/Paste starters

1) Daily Report (10 minutes max)

Write a superintendent daily report for [Project] in [City]. Weather [temp/conditions].
Sections (bullet format): work completed by trade, inspections (result + next steps),
deliveries, manpower (trade + headcount), issues/RFIs (with sheet refs),
delays/mitigation, safety notes, and tomorrow’s plan. Field-ready and concise.

2) RFI (decision-ready)

Subject: RFI- # # # – [Issue] at [Location] (Needed by [DATE])
Refs: [Sheet/Detail refs]
Request: Confirm [model/spec] + electrical/mechanical requirements.
Options: A) ____ (pros/cons) B) ____ (pros/cons)
Please approve A or B by [DATE] to hold schedule.

3) Punchlist (owner-clean)

Turn these notes into a punchlist grouped by room/area with trade tags,
location, pass/fail checkbox, owner-critical flag, and due dates.

Avoid these time-killers

“Write a report.” → List sections

No sheet refs → forces hunting

No Needed-By → decisions drift

First fast win with AI? Emails.Status updates, inspection requests, vendor follow-ups—done in minutes without sounding r...
09/19/2025

First fast win with AI? Emails.

Status updates, inspection requests, vendor follow-ups—done in minutes without sounding robotic.

Use this structure: Context → Sections → Send

Context: project, city, who it’s to, today’s highlights

Sections: bullet points you want (inspections, deliveries, manpower, next steps)

Send: quick edit, subject line, done

Copy/Paste Starters

1) Owner/PM Daily Update

Write a professional status email to [Owner/PM] for [Project, City] dated [DATE].
Include bullet sections: inspections (result + next steps), deliveries, manpower by trade,
open issues/RFIs (with sheet refs), delays/mitigation, and tomorrow’s plan.
Tone: direct, concise, field-ready. Include a clear subject line.

2) Inspector Scheduling (with Needed-By)

Draft an inspection request email to [Authority/Inspector] for [inspection type] on [Project].
Provide preferred dates/times, scope area, plan/sheet refs, access notes, and a Needed-By date tied to [power/CO].
Professional tone + subject line.

3) Vendor Price/ETA Check

Write a vendor email requesting price and lead time for [item/qty] delivered to [address].
Include Needed-By date, alternates if OOS, and a “reply with” checklist (price, lead time, freight, cut sheets).
Keep it short and clear.

Subject lines that get opened

[Project] — Daily Update [MM/DD]

Action Required: [Inspection] on [Date] (Needed-By [Date])

Lead-Time Check: [Item] Needed by [Date]

Avoid these mistakes

Paragraph walls → Use bullets

No Needed-By date → Add one

Vague asks → List what you need in a checklist

Old-school grit. New-school tool.ChatGPT is a power tool—use it like a drill: set the bit (context), set the depth (form...
09/18/2025

Old-school grit. New-school tool.
ChatGPT is a power tool—use it like a drill: set the bit (context), set the depth (format), pull the trigger (prompt), check the cut (quick edit).

Three 60-second drills

1) Daily Report

Write a superintendent daily report for [Project] in [City]. Weather [temp/conditions].
Sections (bullet format): work completed by trade, inspections (result + next steps),
deliveries, manpower (trade + headcount), issues/RFIs (with sheet refs),
delays/mitigation, safety notes, and tomorrow’s plan. Field-ready and concise.

2) RFI (decision-ready)

Subject: RFI- # # # – [Issue] at [Location] (Needed by [DATE])
Refs: [Sheet/Detail refs].
Request: Confirm [model/spec] + electrical/mechanical requirements.
Options: A) ____ (pros/cons), B) ____ (pros/cons).
Please approve A or B by [DATE] to hold schedule.

3) Punchlist (owner-clean)

Turn these notes into a punchlist grouped by room/area with trade tags,
location, pass/fail checkbox, owner-critical flag, and due dates.

Power-tool safety rules

Don’t say “write a report.” List the sections.

Always include sheet refs for clarity.

Add a Needed-By date or decisions drift.

RFIs that get answers—fast.If you’ve ever sent an RFI and waited a week, it’s usually because it didn’t ask for a decisi...
09/17/2025

RFIs that get answers—fast.
If you’ve ever sent an RFI and waited a week, it’s usually because it didn’t ask for a decision or missed the sheet refs. Here’s the field-tested formula.

3 rules to get a same-day answer

Cite the plans (sheet + detail).

Ask for a decision with a Needed-By date.

Offer 2 options with quick pros/cons (time/cost).

Copy/Paste Starters

A) Discrepancy RFI (elevation vs electrical)

Subject: RFI- # # # – Elevation vs Electrical at Expo Line (Needed by [DATE])

Issue: A-102 elevation shows [equipment/model]; E1.01 shows [table/no receptacle] at the same location.
Refs: A-102, Detail 3/A801; E1.01.
Request: Confirm correct equipment model and required electrical (voltage/phase/amps + NEMA plug).

Options:
A) Install receptacle and maintain E1.01 layout. (Pros: no millwork change; Cons: add branch circuit)
B) Install equipment per A-102 and revise E-sheets accordingly. (Pros: matches elevation; Cons: electrical revision)

Please approve Option A or B by [DATE] to hold [rough-in/trim] schedule.

B) Substitution RFI (lead time problem)

Subject: RFI- # # # – Proposed Substitution for [Model] due to lead time (Needed by [DATE])

Request: Approve [ALT MODEL] in place of [SPEC MODEL].
Attachments: Cut sheet + electrical/mechanical data.
Impacts: No change to clearances/codes; electrical identical.
Schedule: Alt is in stock; spec unit is [X] weeks out.

Please approve by [DATE] to avoid delay to [milestone].

C) Coordination RFI (roof curb / equipment schedule)

Subject: RFI- # # # – RTU Model vs Curb Size Coordination (Needed by [DATE])

Issue: M2.01 shows [RTU model]; equipment schedule M5.01 lists [different model]; curb detail [D #/M6.01] conflicts.
Request: Confirm final model + curb size and whether a curb adapter is required.

What not to do

“Please advise.” (Too vague)

No refs. (Forces them to hunt)

No Needed-By. (You’ll wait forever)

Supers: It’s not the work—it’s the paperwork.Burnout stops when the admin stops. Here’s the playbook I use so reports, R...
09/16/2025

Supers: It’s not the work—it’s the paperwork.
Burnout stops when the admin stops. Here’s the playbook I use so reports, RFIs, and emails take minutes—not your night.

Framework: Train → Task → Check

Train with project, city, scope, today’s highlights

Task with the exact sections you want

Check once, send, and save the prompt as a template

Copy/Paste starters

1) Daily Report

Write a superintendent daily report for [Project] in [City]. Weather [temp/conditions].
Sections (bullet format): work completed by trade, inspections (result + next steps),
deliveries, manpower (trade + headcount), issues/RFIs (with sheet refs),
delays/mitigation, safety notes, and tomorrow’s plan. Field-ready and concise.

2) RFI (plan discrepancy)

Draft an RFI for mismatch between A-102 elevation and E1.01 receptacle at the expo line.
Request model confirmation and circuit/amp/voltage, include two resolution options (pros/cons),
and ask for approval by [date]. Tone: concise, professional.

3) Punchlist

Turn these notes into a punchlist grouped by room/area with trade tags,
location, pass/fail checkbox, owner-critical flag, and due dates.

4) Owner/Inspector Email

Write a status email for [Project] summarizing: inspections, deliveries,
manpower by trade, open issues/RFIs, and tomorrow’s plan. Add clear next steps and a subject line.

3 mistakes to avoid

“Write a report” (too vague) → List sections

No sheet refs → cite them for clarity

No Needed-By date → decisions drift

Address

Austin, TX

Website

https://retaildeveloperinstitute.com/

Alerts

Be the first to know and let us send you an email when Hard Hat AI posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Shortcuts

Featured

Share