Custom AI: Build a Building Knowledge Assistant with Claude Projects

For Facilities Managers

Tools: Claude | Time to build: 1–2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for document analysis and report writing — see Level 3 guides

What This Builds

A persistent AI assistant that knows your specific building — the equipment, the vendors, the SOPs, the tenant quirks, the compliance calendar. Every conversation starts from shared context: instead of explaining "we have a 22-year-old Trane chiller on the roof and our HVAC contractor is Williams Mechanical" every time, your building assistant already knows all of it. Ask it anything and it answers from your building's perspective, not a generic one.

Prerequisites

• Comfortable using Claude for writing and document analysis (Level 3)
• Claude Pro subscription ({{tool:Claude.price}}/month at {{tool:Claude.url}})
• Key building documents ready: equipment list, vendor contacts, SOPs, compliance calendar, floor plans or space descriptions
• Time to build: 1–2 hours initially; 15 minutes to add documents later

The Concept

A Claude Project is like having a building manager's assistant who has read your entire facility documentation binder. Every time you start a conversation in the project, that assistant already knows your building's equipment, your vendors, your procedures, and your compliance requirements. Ask it to draft a work order, write a tenant notice about the HVAC being down on the 4th floor, or explain what your chiller warranty covers — and it answers with your specific building in mind, not a generic example.

Build It Step by Step

Part 1: Create the Project

1. Log into Claude at {{tool:Claude.url}} and find Projects in the left sidebar
2. Click New Project
3. Name it: "[Building Name] — Facilities Assistant"
4. You'll see two sections: Project Instructions (the system prompt) and Knowledge (documents)

Part 2: Write Your Building Instructions

Click Edit Project Instructions and fill in your building's specifics:

You are the Facilities Assistant for [Building Name], managed by [Your Name/Company].

Building details:
- Address: [address]
- Size: [square footage, number of floors]
- Type: [corporate office / mixed-use / etc.]
- Year built: [year]
- Number of occupants: [approximate]

Key systems:
- HVAC: [describe your systems — RTUs, chiller, boiler, zones]
- Electrical: [service size, any notable features]
- Plumbing: [domestic, chilled water, steam, etc.]
- Fire suppression: [wet pipe, dry pipe, FM200, etc.]
- Elevators: [number, make/model, service company]
- Emergency generator: [capacity, fuel type, what it covers]
- BAS: [building automation system type]

Key vendors (with contact):
- HVAC: [company, contact, phone]
- Electrical: [company, contact]
- Janitorial: [company, contract hours]
- Security: [company]
- Elevator: [company]
- [add others]

What you help with:
1. Drafting tenant and building communications specific to this building
2. Writing work order descriptions and maintenance notes
3. Drafting vendor correspondence
4. Creating building-specific SOPs and checklists
5. Preparing report narratives for this building's management
6. Answering questions about building systems and procedures

Always reference specific systems, vendors, and contacts from our building when relevant.
Always frame advice from the perspective of managing [Building Name] specifically.

Part 3: Upload Your Building Knowledge

Click Add to Project Knowledge and upload your key building documents:

1. Equipment list or asset register (Excel or PDF)
2. Vendor contact list
3. Key SOPs (fire evacuation, emergency procedures, HVAC controls guide)
4. Compliance calendar (if documented)
5. Floor plan or space description (even a text description of each floor helps)
6. Current vendor contracts (key terms and service scope)

Part 4: Test with Real Tasks

Start a conversation in the project and test:

Draft a notice to tenants on floors 3 and 4 about tomorrow's quarterly HVAC filter replacement. We'll need access to their mechanical closets between 7am and 11am. Our HVAC contractor is Williams Mechanical.

Write a work order for the emergency generator monthly test. Generator is a 200kW Kohler diesel in the basement mechanical room. Include test procedure, documentation requirements, and who to notify.

Does it use your building's specific information? If not, refine the instructions to be more explicit.

Part 5: Add Recurring Workflows

Add specific workflow instructions for tasks you do repeatedly:

For tenant communication drafts:
- Always use our building's name in the subject line
- Standard sign-off: "Thank you for your patience — [Your Name], Facilities Manager, [Building Name]"
- Keep notices under 150 words — our tenants don't read long emails

For work order descriptions:
- Format: System Name | Location | Problem Description | Priority | Assigned To
- Always include safety precautions for electrical or mechanical work

Real Example: Three Tasks in One Morning

Setup: Building assistant project contains equipment list, vendor contacts, and 3 key SOPs

Task 1: "Draft an urgent tenant notice — we just had a water pipe burst on the 2nd floor ceiling. It's affecting offices 201-212. Our plumber is already on site. ETA to restore is 3 hours." → Response: A professional, empathetic notice with your building name, specific office numbers, and realistic ETA — ready to send in 2 minutes

Task 2: "Create a work order for the plumber to repair the 2nd floor domestic water line. Location is ceiling above office 205, near the mechanical shaft. Williams Plumbing, emergency rate." → Response: A formatted work order with correct location details, emergency designation, and documentation requirements

Task 3: "Write an incident report for this morning's water pipe burst. It happened at 8:47am. No injuries. Affected 12 offices, estimated $3,500 cleanup cost." → Response: A properly formatted incident report with your building address, correct time, affected area, and response actions — ready for your insurance company

What to Do When It Breaks

• Responses feel generic and don't reference the building: The project instructions aren't specific enough. Add more details about specific systems, vendor names, and floor layouts
• Claude doesn't use the uploaded documents: Check files uploaded successfully. Try asking directly: "Based on our vendor contact list, who is our elevator service company?"
• Instructions are outdated: When vendors change or systems are replaced, update the project instructions — outdated information is worse than no information
• Project runs out of context: Keep conversations focused on one topic per chat; start new chats for unrelated tasks

Variations

• Simpler version: Skip the project setup and use a detailed context paragraph at the start of each Claude conversation — copy-paste your building details every time. Works but requires more setup per conversation.
• Extended version: Add your building's recent maintenance history as a document — Claude can then reference "the last time we serviced the chiller was September 2025" in its responses

What to Do Next

• This week: Build the project and upload your 3 most important documents; test on 5 real tasks
• This month: Add all major vendor contracts and SOPs; refine instructions based on where responses need improvement
• Advanced: Create a second project for your capital planning work — with current deferred maintenance list, budget history, and approved capital plan as knowledge documents

Advanced guide for facilities manager professionals. Review your organization's data security policy before uploading sensitive building documents to Claude — consider what level of detail is appropriate to share with a cloud AI service.