Custom GPT: Build a Project-Aware AI Assistant for Your Construction Team

What This Builds

Instead of re-explaining your project to AI every time you open a chat, you'll build a Custom GPT that already knows your project's contract type, key contacts, preferred document formats, and common scenarios. Your project engineer can use the same assistant, and every RFI, change order, and email that comes out of it follows your company's standards automatically.

Prerequisites

• ChatGPT Plus subscription ($20/month)
• 5-10 key project documents ready: contract summary, spec highlights, contact list, preferred formats
• 60-90 minutes of uninterrupted time for initial build
• Your project engineer or APM available to test (optional but recommended)

The Concept

A Custom GPT is like creating a specialized version of ChatGPT that comes pre-loaded with your project's context, style preferences, and document templates. Think of it as training a new assistant who has already read your entire contract and knows exactly how you write RFIs. You set it up once, and then every conversation starts from that shared understanding. No more "for context, this is a GMP project for an owner who..." at the start of every session.

Build It Step by Step

Part 1: Prepare Your Source Documents

Before building the GPT, assemble your context files. These don't need to be perfect. Bullet points work fine.

File 1: Project Context (1 page)

PROJECT: [Project name and address]
OWNER: [Name, company, primary contact]
ARCHITECT: [Firm name, PM name, contact]
DELIVERY METHOD: [Lump Sum / GMP / Design-Build]
CONTRACT VALUE: $[amount]
KEY DATES: NTP [date], Sub Comp [date], Final [date]
OUR COMPANY: [GC name]
OUR PM: [Your name]
OUR PE: [PE name]
KEY SUBS: [List top 8-10 with trade, company, PM name]
PROJECT TYPE: [Office building / Medical / Retail / etc.]
FLOORS/SIZE: [X stories, Y,000 sq ft]

File 2: Document Style Preferences (1 page)

RFI STYLE: Formal. Reference spec first, then drawing. State conflict clearly. End with specific question.
CHANGE ORDER STYLE: State change event → why additional → specific cost → schedule impact.
MEETING MINUTES FORMAT: [ACTION - COMPANY - PERSON - DUE DATE]
EMAIL TONE: Professional and direct. Never emotional. Always factual.
OWNER COMMUNICATION: Proactive. Flag issues before owner asks. Always show we're in control.
SUBCONTRACTOR EMAILS: Firm but fair. Reference contract when relevant. Specific requests with deadlines.

File 3: Common Scenarios Reference (1-2 pages) List the 5-10 scenarios that come up most on your project type. For a commercial office project:

• RFIs to structural engineer about coordination conflicts
• Change orders to owner for tenant-requested changes
• Deficiency letters to subs for schedule or quality issues
• Weekly OAC meeting minutes format
• Owner report format and sections

Part 2: Build the Custom GPT

1. Go to chatgpt.com and make sure you're signed into ChatGPT Plus
2. Click your profile picture in the top right → My GPTs
3. Click Create a GPT (top right)
4. You'll see a split screen: left side is where you configure, right side is a preview

Step A: Configure Basic Info

• Name: "[Project Name] PM Assistant" or "Construction PM, [Company Name]"
• Description: "AI assistant for construction project management on the [Project Name] project"
• Profile Picture: Optional. You can generate one or skip it.

Step B: Write the System Instructions Click the "Configure" tab. In the Instructions box, paste this (customized for your project):

You are the AI construction project management assistant for [GC Company Name], specifically configured for the [Project Name] project.

PROJECT CONTEXT:
- Project: [Name], [Address]
- Owner: [Name/Company]
- Contract Type: [Lump Sum/GMP/Design-Build]
- Delivery: [Method]
- Our PM: [Your name]
- Our PE: [PE name]
- Architect: [Firm]

DOCUMENT STYLE:
- RFIs: Formal, reference spec section first, describe conflict precisely, end with specific question
- Change Orders: State change event, explain why it's additional scope, specific cost, schedule impact
- Emails: Professional, factual, never emotional, always reference contract when relevant
- Meeting Minutes: Use format [ACTION — COMPANY — NAME — DUE DATE]

RULES:
1. Never invent specific dollar amounts — ask the user to confirm costs before including in documents
2. Never invent specific dates — ask if needed
3. When drafting an RFI, ask for drawing numbers and spec sections if not provided
4. When writing a change order, always include a sentence starting with "This work is additional to the original contract scope because..."
5. All documents should be suitable for formal project records
6. If asked to write something that could create legal liability (termination, claim), note this and recommend the user have it reviewed

Step C: Upload Knowledge Files In the "Knowledge" section, click Upload files and upload your 3 context files from Part 1.

Step D: Set Capabilities Turn ON: Web Browsing (helpful for current spec standards), Code Interpreter (helpful for spreadsheet analysis if needed) Turn OFF: Image Generation (you don't need this)

Step E: Set the Conversation Starter buttons Add 4 starter prompts that your team will use most often:

1. "Draft an RFI for a conflict I found"
2. "Write a change order narrative"
3. "Help me write a professional email"
4. "Format these meeting notes as minutes"

Part 3: Test and Refine

Test your GPT with 3 realistic scenarios before sharing with your team:

Test 1: "I found a conflict between the plumbing and structural drawings at gridline B-3. The drain line runs through a beam. Draft an RFI."

Expected result: A formal RFI that says "[Your Project Name]" in the header, asks the right parties, and requests a specific response.

Test 2: "The owner wants to add power outlets to the conference room on Level 3. Our electrician quoted $4,200. Draft a change order narrative."

Expected result: A CO narrative that includes the project name, explains why it's additional scope, cites the $4,200, and asks you to confirm schedule impact.

Test 3: "Write a formal email to the plumbing sub who is 3 weeks behind on Level 2 rough-in."

Expected result: A firm, professional email referencing the project and requesting a specific recovery plan with a deadline.

If any test produces wrong outputs, go back to your Instructions and clarify.

Share with your PE: In your GPT settings, you can set visibility to "Only me" or "Anyone with link." For team use, set to "Anyone with link" and share the URL with your project engineer.

Real Example: The Riverside Medical Office Building

Setup: PM Carla created a Custom GPT for a 5-story, 120,000 sq ft medical office project. Uploaded project context doc, style preferences, and a sample RFI and CO from a previous project.

Input: Her PE, Marcus, opens the GPT every morning. When a new RFI comes in from the plumbing sub, he types: "The plumbing sub has a conflict between their piping layout and the HVAC ductwork on Level 3, north wing. The drawings don't show a solution. Draft an RFI to the MEP engineer."

Output: A complete, formatted RFI that references the project name, site address, owner contact, lists the correct drawing numbers from Marcus's message, and asks a specific question about the priority of systems and required coordination solution.

Time saved: Marcus spent 3 minutes on an RFI that used to take 20 minutes. The GPT was used 47 times in one month by Carla and Marcus combined, for a total estimated time savings of 8 hours.

What to Do When It Breaks

• GPT ignores your style rules → Go back to Instructions and make the rules more explicit: "YOU MUST always include [specific phrase] in every change order narrative"
• GPT invents project details you didn't provide → Add to Instructions: "Never invent specific names, amounts, or dates. Ask the user if you don't have this information."
• PE gets inconsistent results vs. PM → The GPT is shared but conversations are separate. Each person starts a fresh chat. That's fine, the project context is still loaded.
• Knowledge files seem ignored → Delete and re-upload the files; confirm they appear in the Knowledge section of your GPT configuration

Variations

• Simpler version: Instead of a Custom GPT, use Claude Projects (Level 3 guide), which gives you the same persistent context without the builder interface.
• Extended version: Build separate Custom GPTs for specific phases (Bidding/Preconstruction GPT, Field Operations GPT, Closeout GPT) with phase-specific knowledge

What to Do Next

• This week: Build and test the GPT with your 3 context files; run the 3 test scenarios
• This month: Track how many times it's used and which outputs needed editing. Use that feedback to refine the instructions.
• Advanced: Add your company's standard subcontract template as a knowledge file so the GPT can draft subcontract scope language that matches your specific format

Advanced guide for Construction Project Manager professionals. Custom GPTs require a ChatGPT Plus subscription. Project knowledge files may contain sensitive information. Set GPT visibility to "Only me" or "Anyone with link" (not public).