
Your Client Agreed, But Can You Prove It?
Why verbal agreements fail in projects, and how written records, follow-up emails, and registers prevent disputes and confusion.
Chapter 1
Imported Transcript
Michael
Have you ever had a brilliant, friendly chat with a client where you've both agreed on exactly how a project's gonna run, only to find out six months later that neither of you remembers it the same way? It's a classic trap. When you've got a ripper relationship with a client, it's dead easy to get informal. You're talking regularly, making decisions on a quick phone call, agreeing to things during meetings, and you just assume everyone understands exactly what's going on. But remember that classic eighties flick where a teenager dials into a military supercomputer, thinking he's just playing a harmless simulation? The computer didn't have the context, and acting on that misunderstood information nearly kicked off a global disaster. Undocumented project communication's a bit like that. When people act on information without properly understanding what was actually intended, you're setting yourself up for a catastrophe. So, the big question's this: how do we make sure project knowledge belongs to the project, rather than just floating around in people's heads or buried in personal inboxes? The truth's that relying on memories is a massive risk. Two honest people can walk out of the exact same meeting with completely different takes. You might think, "The client approved it," while they reckon, "I said it sounded reasonable, but I didn't approve it." Fast forward a few months, and that distinction's a bloody big deal. People forget the context, too. A deadline with strict conditions suddenly turns into a hard promise without 'em. And what happens when a project manager changes? A new client PM might rock up, take one look at the schedule, and say, "Show me where this was agreed." Take a scenario we've probably all seen. A client PM, let's call him John, tells you over the phone not to worry 'bout the full monthly report, just send the preliminary results. Your PM says no worries, but nothing's written down. Three weeks later, John moves on, and his replacement's demanding to know why the final report's late. If you've just got "John told us not to," you're in for a rough trot. I've even seen first-hand the absolute chaos that unfolds when a project relies on one person's memory, and that project manager unexpectedly passes away. All those undocumented agreements turn into a serious nightmare overnight. So, what's the fix? You've gotta create a written, searchable communication record. Follow up your verbal conversations in writing. It doesn't have to be a formal legal document. Just shoot over a quick email saying, "Thanks for the chat, just confirming my understanding that," and list what was decided, who's doing what, and any due dates. This gives the client a chance to correct you straight away, which a good client PM'll always appreciate. You aren't doing this to be adversarial or to prep for a court battle; you're doing it so you've both got the exact same understanding. Don't just rely on your personal inbox, either. With communication spread across Teams, Slack, text messages, and site meetings, important records need to be somewhere the whole project team can find 'em. Use a correspondence register if the project's big enough, give things meaningful subject lines, and particularly document the bad news. We'd love to just write down approvals, but we've also gotta record delays, mistakes, and warnings. If a milestone's gonna be missed 'cause the client didn't supply survey info on time, you'll want that documented beforehand, not reconstructed after the fact. Make sure you're also following the project's contractual communication requirements, 'cause sometimes a casual message just won't cut it. The big lesson here's simple: if it matters, put it in writing. Don't rely on memory, don't rely on relationships, and definitely don't assume everyone's gonna stick around 'til the absolute end of the job. Your practical action step for today's to look at the last important phone call you've had with a client and send a polite, quick summary email just to confirm the details. Create enough written history that if a newbie joined the project tomorrow, they'd instantly know what was discussed, what was decided, why, and what everyone agreed to do next. If you're keen to dig deeper into this, check out my related posts, like Document All Changes, Variations and Agreements, Why You Need a Single Decision Maker in Client Communication, and The Importance of Good Communication. You'll find all the details over at My Project Lessons dot com. Thanks heaps for listening, and I'll catch ya next time!