Course

AI for Construction Project Engineers

Submittals, RFIs, coordination and the punch list, with the spec book doing the reading.

IntermediateConstruction

0/88 stops · about 2 hours · final quiz · certificate

Start course Sign in to save progress

Start with

• AI at Work: FoundationsStart from zero and finish with three things you can actually use.

Who this is for

Project engineers, assistant project managers and field engineers on commercial and hospitality builds. Every example follows Hany, a project engineer at a commercial general contractor on a hotel renovation, twenty years of high-end fit-out and deep MEP knowledge, four hundred submittals and a running RFI log.

You will be able to

• Turn a spec section into the submittal checklist and review a package against it
• Write RFIs that get answered on the first try and log them properly
• Prepare MEP coordination agendas and minutes with an owner and a date on every action
• Run the punch list from site photos to subcontractor packets and the closeout tracker
• Write the daily report and the weekly owner update without crossing into the PM's territory
• Keep the spec book, the registers and the correspondence rules in one Project

Stops

1. 1 The hotel job ProjectOne Project holding the spec book, the two registers and the rules, so every submittal chat starts already knowing the job. Set once
2. 2 SubmittalsPart 1 of a spec section becomes the checklist, the sub's package gets held against it, and the exceptions are written before the transmittal goes out. Daily
3. 3 RFIsThe question that comes back answered the first time: the sheet, the section, the field condition and a proposed resolution the architect can sign. Daily
4. 4 MEP coordinationClash notes and the look-ahead become the agenda, the meeting becomes minutes with a name and a date on every action, and a slip becomes an escalation. Weekly
5. 5 The punch listTwo hundred site photos and a voice note become a list by trade and floor, a packet per subcontractor, and a tracker that closes out. Weekly
6. 6 Daily reports and owner updatesField notes into the daily report at four o'clock, the owner update on Friday, and a clear line between what a project engineer states and what waits for the PM. Daily
7. 7 Spec compliance and product dataProduct data held against the spec line by line, a deviation memo the architect can decide on, and a code question that ends with you opening the code. Weekly
8. 8 Hany's weekThree routines on a timer, the desktop working while he is on the floor, and one spec section carried from checklist to closeout. Weekly

Final quiz