Claude CoWork for Construction Project Managers

Want the complete Claude setup for the business side of contracting?

The Contractor Claude Vault is a 40-prompt vault for the small-business side of construction work — estimates, change orders, daily logs, customer paperwork, payment reminders, sub coordination. Useful in addition to PM-specific work, especially for solo and small-firm GCs and remodelers.

One-time $29, instant download. Get the vault →

What is Claude CoWork?

Claude CoWork is the practice of using Claude as a persistent, knowledgeable co-worker embedded in your daily construction project management workflow. This is not about asking a chatbot a one-off question and hoping for the best. It is about configuring Claude with your project context, company standards, and communication preferences so that every interaction produces output you can actually use.

Claude-native prompts. The prompts in this guide use Claude's native XML tag structure (<context>, <instructions>, <format>, <avoid>) for more precise, consistent output. These tags help Claude parse your intent with less ambiguity. They work in ChatGPT too, but are optimized for Claude.

Think of Claude as the most organized project engineer you have ever worked with, one who never forgets your reporting templates, knows your contract language inside and out, and can draft a progress report, RFI, or change order in seconds. The difference between PMs who dabble with AI and those who gain a real edge comes down to setup and consistency.

This guide walks you through setting up Claude specifically for construction PM work, the five workflows that will save you the most time, and the prompting techniques that separate generic output from production-ready content.

Install the Construction Project Manager Plugin

This guide works on three Claude surfaces. The plugin is the fastest path on two of them. Pick whichever you use:

If you're on Cowork (desktop or mobile app)

Claude Cowork is Anthropic's agentic workspace — Claude completes work autonomously and returns finished deliverables. The Construction Project Manager plugin packages the workflows below as native skills and slash commands.

Open the Cowork plugin directory in your desktop app.
Filter by Cowork, search for "Construction Project Manager", and click Install.
The plugin's slash commands and ambient skills are now available in any Cowork task.

If you don't see the plugin in the directory yet, install via custom marketplace: paste https://github.com/alexclowe/awesome-claude-cowork-plugins in your Cowork plugin settings.

If you're on Claude Code (CLI)

Install from your terminal:

claude plugin add alexclowe/awesome-claude-cowork-plugins/construction-pm

The plugin's slash commands and skills load on next session.

If you're on Claude.ai (web chat only)

Plugins aren't directly installable on the web chat surface. You have two options:

Use the prompts in this guide directly in a Claude Project (covered in the next section). Same outputs, more typing.
Upload the plugin's skills as a zip via Settings → Features → Custom Skills (Pro/Max/Team/Enterprise plans). Higher friction; only worth it if you want the auto-activating skills, not the slash commands.

What the plugin gives you (any surface)

Slash command	What it does
`/project-estimate`	Generate detailed cost estimates with labor, materials, equipment, and contingency breakdowns
`/change-order`	Draft change order documentation with scope, cost impact, and schedule adjustments
`/progress-report`	Create structured progress reports covering schedule, budget, safety, and quality metrics
`/rfi-response`	Draft clear RFI responses referencing specifications, drawings, and project requirements

Auto-activating skills (no command needed — Claude applies them when relevant):

Construction Management — Cost estimating, schedule management, project controls, building codes, and contract administration
Stakeholder Communication — Owner presentations, architect correspondence, subcontractor coordination, and meeting minutes

The plugin works standalone for one-off tasks. Pair it with the surface-specific setup below for persistent context across every task — that combination is the full Claude CoWork setup.

Setting Up Claude for Construction PM Work

Surface note: The Project setup below is for claude.ai web users. Cowork users have their own task-context mechanism (set context once when starting a Cowork task). Claude Code users get the plugin's ambient skills automatically — no Project setup needed. The workflows themselves are surface-agnostic — paste the prompts wherever you're working. The key to getting consistently useful output from Claude is using Claude Projects. A Project lets you set custom instructions that persist across every conversation, so you are not re-explaining your company and project details every time.

Step 1: Create a Construction PM Project. In Claude, click "Projects" and create one called something like "My Construction Projects."

Step 2: Set your custom instructions. In the Project settings, add instructions like:

You are my construction project management assistant. Here is my context:

<business-profile>
- Name: [Your Name], [Your Company]
- Role: Project Manager
- Project types: [Commercial / Residential / Industrial / Infrastructure / Renovation]
- Current project: [Project Name, Location, General Contractor or Owner info]
- Project value: $[X]
- Contract type: [Lump Sum / GMP / Cost-Plus / Design-Build]
- Key software: [Procore / Bluebeam / PlanGrid / MS Project / Primavera]
</business-profile>

<rules>
- When writing RFIs, follow our company's standard numbering format: [Project Code]-RFI-[Sequential Number].
- When writing reports, use clear section headers and bullet points for readability.
- Always note that specifications, code references, and cost figures need verification by the appropriate licensed professional.
</rules>

Step 3: Upload reference documents. Add your company's RFI templates, progress report formats, change order forms, scope of work examples, or specification sections to the Project knowledge base. Claude will reference these when generating content.

Step 4: Start every session inside this Project. This ensures Claude always has your context loaded.

Your Top 5 Workflows with Claude

1. Progress Reports That Keep Stakeholders Informed

<task>Write a weekly construction progress report for the owner.</task>

<context>
- Project: Meridian Office Tower, Phase 2 Interior Buildout, March 16-22, 2027
- Completed: drywall floors 3-5 (95%), MEP rough-in floor 6 (60%), elevator cab started, fire suppression floors 1-2 passed
- Delays: tile delivery pushed 5 days (supplier backorder), no schedule impact yet
- Safety: zero incidents, 47 consecutive days without recordable
- Upcoming: flooring floors 3-4 Monday, elevator inspection Thursday
</context>

<instructions>
- Sections: Executive Summary, Work Completed, Schedule Status, Safety, Issues/Risks, Upcoming
- Include % complete for major trades, note tile delay impact potential
- Professional concise tone, under 400 words
</instructions>

<avoid>Editorializing on subs, including cost details, or speculating without data</avoid>

Before Claude: 1.5-2 hours compiling notes and formatting. After Claude: 10 minutes to input field notes, 15 minutes to review.

2. RFIs That Get Clear Answers

<task>Draft an RFI regarding a conflict between structural and mechanical drawings.</task>

<context>
- Project: Meridian Office Tower, RFI: MOT-RFI-087
- Location: Floor 6, Grid C-D between lines 3-4
- Issue: S-601 shows 24"x24" column at C-3.5, M-601 routes 16" HVAC duct through same location
- Specs: 05 12 00 (Structural Steel), 23 31 13 (Ductwork)
- Impact: ductwork crew starting this area next Tuesday
</context>

<instructions>
- Standard RFI format: issue, references, suggested resolution, schedule impact
- Propose two resolutions for design team, note urgency, under 250 words
</instructions>

<avoid>Assigning blame, making engineering recommendations, or including cost implications</avoid>

Before Claude: 30-45 minutes per RFI. After Claude: 5 minutes to describe the conflict, 10 minutes to verify references.

3. Change Orders With Clear Justification

<task>Draft a change order request for unforeseen site conditions.</task>

<context>
- Project: Riverside Elementary School Renovation, CO: RES-CO-012
- Issue: asbestos tile found beneath VCT in east wing corridor, not in original hazmat survey
- Scope: ~2,400 sq ft abatement, corridors E-1 through E-4
- Quote: $18,750 (containment, removal, monitoring, disposal), 8-day schedule impact
</context>

<instructions>
- Sections: changed condition, original scope reference, justification, cost, schedule impact
- Reference hazmat survey, cite differing site condition clause, factual tone, under 350 words
</instructions>

<avoid>Implying surveyor negligence, including markup percentages, or making legal conclusions</avoid>

Before Claude: 1-2 hours drafting the change order narrative. After Claude: 10 minutes to input details, 10 minutes to review and add markup.

4. Cost Estimates and Budget Summaries

<task>Create a preliminary cost estimate summary for a tenant improvement project.</task>

<context>
- Project: Suite 400 TI, Apex Legal Group, 4,200 sq ft, downtown Portland, OR
- Scope: demo, 12 offices, 2 conference rooms, reception, ceiling, lighting, HVAC mods, 30 data drops, paint/carpet
- Quotes received: drywall ($38,500), electrical ($29,200), HVAC ($22,800), flooring ($16,400)
- Pending: fire protection, plumbing, millwork
</context>

<instructions>
- CSI division format, received quotes + allowances for pending trades
- Add general conditions, permits, contingency (10%), summary table with total
- Note firm quotes vs. allowances, narrative under 200 words
</instructions>

<avoid>Presenting allowances as firm, including fee/margin, or guaranteeing the total</avoid>

Before Claude: 2-3 hours organizing quotes and building the summary. After Claude: 10 minutes to input data, 15 minutes to verify figures.

5. Scope of Work Documents

<task>Write a scope of work for a painting subcontractor on a commercial project.</task>

<context>
- Project: Meridian Office Tower Phase 2, floors 3-6 corridors, lobbies, restrooms
- Surfaces: ~45,000 sq ft new drywall, 84 metal door frames, mechanical rooms (block walls)
- Spec: 09 91 00. Prime + 2 coats latex (drywall), semi-gloss (frames), block filler + 2 coats (mech rooms)
- Schedule: coordinate with flooring installer, off-hours on occupied floors 3-4
</context>

<instructions>
- Sections: inclusions, exclusions, material specs, schedule, quality standards
- Include surface prep, trade coordination, protection and cleanup requirements
- Professional contract language, under 400 words
</instructions>

<avoid>Specifying brands unless required by spec, including pricing, or omitting exclusions</avoid>

Before Claude: 1-2 hours writing detailed scope language. After Claude: 10 minutes to outline the scope, 15 minutes to review against specs.

Prompt Engineering Tips for Construction PMs

1. Always reference specific drawing and spec numbers. "See drawing S-601, grid C-3.5" gives Claude the context to write precisely. Vague descriptions produce vague output.

2. Specify your contract type. Lump sum, GMP, and cost-plus projects have different change order and reporting requirements. Tell Claude which applies.

3. Include schedule context. Noting "this is on the critical path" or "this has 5 days of float" changes the urgency and framing of any communication Claude drafts.

4. Upload your company templates. The fastest way to get Claude to match your format is to upload examples of your best reports, RFIs, and change orders to the Project knowledge base.

5. Use Claude for pre-meeting prep. Ask "Summarize the top 5 issues I should raise at tomorrow's OAC meeting based on these notes" to walk into meetings prepared.

6. Always verify technical details. Claude can draft the narrative, but you must verify all drawing references, specification sections, code citations, and cost figures before issuing any document.

Privacy & Compliance

Verify specifications and building codes. Claude does not have access to your project-specific drawings, specifications, or local building codes. All references to code sections, specification requirements, and drawing details must be verified against the actual project documents before issuing any RFI, change order, or report.

No engineering certifications. Claude cannot and does not provide engineering analysis, structural calculations, or design recommendations. Any document that requires a professional engineer's stamp must be reviewed and sealed by a licensed PE. Claude drafts the narrative; licensed professionals provide the technical validation.

Review with licensed professionals. Change orders involving structural modifications, life safety systems, or code compliance issues must be reviewed by the appropriate licensed architect or engineer before submission. Use Claude's output as a starting point, not a final product.

Confidential project data. Be cautious about pasting proprietary cost data, bid tabulations, or confidential contract terms into Claude. Use general figures when possible and reserve exact financials for your internal systems.

Going Further

Ready to build on this foundation? Check out these resources:

Browse our full collection of construction PM prompt packs and templates for ready-to-use resources
Run an AI readiness audit for your construction management workflow to identify your biggest opportunities
Explore AI-powered tools built specifically for construction professionals to automate even more of your workflow