Your PM is standing on the jobsite at 4 PM. The owner's rep just asked him to reroute a conduit run that wasn't in the drawings. He writes "conduit reroute per owner request, 3 hrs extra" in his field notebook, takes a photo of the area, and keeps moving. Three weeks later, your office manager is trying to turn that note into a formal change order narrative that the GC's project manager will actually approve.

She spends 90 minutes pulling context from the original RFI, cross-referencing the spec section, estimating the labor burden, and writing something coherent. The GC's PM responds: "Not enough justification. Resubmit." Another two hours gone. Change order still unpaid.

This happens on every job. Contractors leave 3–5% of contract value on the table in undocumented or under-justified change orders. On a $2M subcontract, that's $60K–$100K in legitimate work that never gets paid because the narrative wasn't strong enough.

Claude changes this. Here's the exact workflow a 40-person MEP subcontractor we worked with built in one afternoon.

---

Why Change Order Narratives Are Hard

The problem isn't that your PMs can't write — it's that turning field observations into formal change order language requires a specific format, specific language, and specific structure that most field people were never trained on.

A strong change order narrative needs to:

• Reference the contract section or drawing number that establishes scope
• State the changed condition clearly (owner direction, unforeseen condition, design conflict)
• Quantify the labor, material, and time impact with specificity
• Attach the cause to the effect without sounding adversarial
• Use the right industry terminology (PCO, COR, CCD, ASI — depending on the contract)

Most field notes don't have any of this. They have "extra work north stairwell 4.5 hrs" and a blurry photo. The translation gap is what kills change orders.

Claude closes the gap because it can take raw, messy field input and produce a properly structured narrative in under two minutes — as long as you give it the right context.

---

The Setup: What You Need

You don't need an enterprise system to do this. What you need:

• A Claude Pro subscription ($20/mo) or Claude Team ($30/mo per seat)
• A simple Google Form or typed input template your PMs fill out in the field
• A Claude Project with your company's standard change order format loaded in

That third piece is the key. Claude Projects let you create a persistent workspace with documents and instructions that every conversation inherits. Set it up once, and every PM on your team gets the same starting point.

What to load into your Claude Project:

1. Your standard change order format (the Word doc or PDF you always use)
2. A one-page "how we write COs" note with language preferences (do you say PCO or COR? Do you itemize labor by trade or lump it?)
3. Two or three approved change orders from past jobs as examples
4. Any client-specific requirements if you work repeat contracts

Loading these in takes about 30 minutes the first time. After that, Claude knows your format.

---

The Workflow: From Field Note to Narrative

Here's the exact process the MEP sub uses today.

Step 1: PM fills out a simple input form

When a potential change event happens, the PM enters four things into a shared Google Form (connected to a spreadsheet the office sees):

• Job number and project name
• Date of the event
• What happened in plain English (2–5 sentences)
• What extra work it caused (labor hours by trade, materials if known)

No legal language. No format requirements. Just what happened and what it cost. The form auto-emails the response to the project coordinator.

Step 2: Project coordinator pastes the input into Claude

The project coordinator opens the Claude Project (already set up with the company's format and examples) and pastes the field input with this prompt:

"Using our standard PCO format, write a change order narrative for the following field event. Include: scope of work change, cause, contract reference if applicable, and labor/material impact. Keep it factual and professional."

Claude returns a complete narrative in 60–90 seconds. The coordinator reviews it, adjusts any numbers or context she has from the RFI log, and the first draft is done.

Step 3: Cross-reference the RFI log

For anything more than a day-rate extra, the coordinator pulls the relevant RFI or submittal response from the project folder and adds any contract references Claude missed. She pastes those into the Claude conversation:

"Here's the RFI response that triggered this change. Update the narrative to reference RFI #47 and section 16050 of the spec."

Claude updates the narrative. One more review pass, and it goes into the formal CO package.

The result: What used to take 90 minutes per event now takes 15–20 minutes. The narratives are stronger because they're consistently structured. And because they go out faster, the GC's PM sees them while the work is still fresh — not three weeks later when context has evaporated.

---

What Good Claude Output Looks Like

Here's an example. The PM's field note:

"Owner rep (Mike Hansen) asked us to reroute 4" EMT conduit run in mechanical room to avoid conflict with new structural steel. Ran approximately 40 LF additional conduit plus 2 additional 90-degree bends. 2 electricians, 6 hours total."

Claude output (in the company's PCO format):

PCO #14 — Conduit Reroute, Mechanical Room, Level 2

Date of Event: [Date]
Directed By: Owner's Representative, Mike Hansen
Reference: RFI #[xx] pending — verbal direction on site

Description of Change:
At the direction of the Owner's Representative, the electrical subcontractor was required to reroute a 4" EMT conduit run within the Level 2 mechanical room to avoid a conflict with newly installed structural steel not indicated on the electrical drawings issued for construction.

Scope of Extra Work:

• 40 LF additional 4" EMT conduit installation
• 2 additional 90-degree LB fittings
• Labor: 2 electricians × 6 hours = 12 man-hours

Impact:
This work was performed at Owner direction and constitutes a change to the contracted scope of work under Section 16.050 of the Electrical Specifications. This PCO will be followed by a formal COR once final material quantities are confirmed.

That's a narrative that gets processed, not kicked back for "insufficient justification."

---

What It Doesn't Do

Claude won't catch every billing opportunity. If your PM forgets to write down the extra, Claude can't generate it. The tool only works as well as the field input it receives.

It also won't generate cost figures you don't provide. If you paste in "6 hours extra" without a labor rate, Claude will flag that gap or use a placeholder — it won't invent numbers. Good. That's what you want.

And it's not a substitute for reviewing your contracts. The prompt you feed Claude should be matched to your specific contract type. AISC, AIA, ConsensusDocs, custom GC agreements — they all have different language conventions. Load the relevant sections into your Claude Project for the contracts you work on repeatedly.

---

The Compounding Effect

One MEP subcontractor ran this workflow for six months. They logged 47 change events across four jobs. Of those, 43 resulted in approved PCOs. Previous rate on the same types of events: roughly 60%.

The difference wasn't that the events changed. The difference was that every narrative came out formatted correctly, referenced the right contract sections, and went out within 48 hours of the event — not three weeks later when everyone had forgotten what happened.

That's 3 additional approved PCOs per job. At an average PCO value of $8,500, that's $25,500 per job that would have evaporated into "we should have documented that better."

You already did the work. Claude helps you get paid for it.

---

Getting Started

You don't need an AI consultant to set this up. Here's what to do this week:

1. Start a Claude Team account ($30/mo per seat, or Pro at $20/mo if it's just you)
2. Create a new Claude Project called "Change Order Drafts"
3. Upload your standard CO format, two or three approved COs as examples, and a short note on your preferred language
4. Write a standard prompt and save it in a shared doc your team can copy-paste
5. Run one real change event through it and compare the output to what your coordinator would have written

If it's not faster and stronger in 30 minutes, something's wrong with the setup — not the concept.

When you're ready to connect this to your actual project management system, automate the routing, or build a full change event tracking workflow — that's where the architecture matters. That's our work. Book a discovery call at cloudbeast.io/schedule and we'll map it out.