Hey {{first_name | default: "there"}},
A few weeks ago I wrote about notice windows — the 7-day clock that kills claims before the work is even done. Some of you responded back to me on that one.
A common thread I kept getting: okay, so I sent the notice. But what do I actually say?
That's the harder problem.
THE LESSON
Most construction correspondence fails in one of two directions.
Too aggressive: the PM is frustrated, the letter reads like a legal filing, and the owner's team goes straight to their attorney. The legitimate issue gets buried in the posturing.
Too vague: "Please be advised that we are experiencing delays on the above-referenced project." Caused by what? With what impact? A letter that doesn't put the cause in the record might as well not exist.
I've sent both kinds. The aggressive ones felt satisfying for about 20 minutes. The vague ones felt safe at the time. Neither helped when it mattered.
Before I write any notice now, I force myself to answer four questions: What specifically happened? When did it happen? Who caused it? What is the measurable impact on cost or schedule? If I can't answer all four, the letter isn't ready to go out.
That exercise — answering those four questions before drafting — is the difference between a letter that reads like frustration and one that reads like a record. Once I have those answers, the drafting almost writes itself. The tone problem mostly disappears when the content is specific enough.
This is also exactly where AI becomes useful. Not to generate the anger or figure out the strategy — that's your job. But once you have those four answers, AI can take them and produce a letter in the right register every time. Professional, specific, neutral, defensible. The input quality determines the output quality. Vague inputs produce vague letters. Specific inputs produce letters that hold up.
Write every notice like it's going to be read by a mediator in 18 months. Because sometimes it is.
THE TOOL
The Construction Correspondence Drafter in the PM Edge Toolkit works exactly this way.
It asks you for those four inputs before it drafts anything. What happened, when, who caused it, what the impact is. Then it structures the letter so the cause is in the record, the impact is stated, and the tone stays professional. It covers RFIs, delay notices, notices to cure, CO cover letters, preliminary notices, and owner update letters — and it tells you which document type you actually need for the situation, so you're not sending the wrong letter at the wrong moment.
The discipline of gathering those four inputs before you open the workflow is half the value. By the time you're answering the questions, you already know what the letter should say. The AI handles the format, the register, and the language. You handle the facts.
$29. One-time. Lifetime updates.
INDUSTRY PULSE
On my radar:
• Construction disputes are taking longer to resolve — Average dispute resolution on commercial projects has stretched to 14 months in 2026, up from 11 months in 2023. The best defense is still the contemporaneous paper trail — not the claim letter you write when it's already gone sideways.
• Trimble acquires Document Crunch — Trimble is buying the AI contract-analysis platform that flags risk clauses automatically. Automated document review is heading into every PM's platform as a subscription feature. The firms learning to do this now won't pay for it when it's bundled into a renewal. (April 2026)
• Email is still your best paper trail tool — Courts and arbitrators have decades of precedent around email as written notice. If you're relying on Procore messages or Teams threads, verify whether your contract treats those as valid written notice before you need to find out the hard way.
Forward this to a PM who's ever sent a letter they regretted — or didn't send one they should have.
— Jesse
The PM Edge | pmedge.io