Case History 22 === Liz: [00:00:00] Welcome to the GBA Case History series, brought to you by the GBA Podcast. My name is Elizabeth Brown, and I'm the principal geotechnical engineer at JLT Consultants Abi: And I'm Abi Corbett, a project consultant at SME. Today's episode is a really good one. We're diving into GBA Case History 22, which is basically a masterclass in what happens when communication disappears, documentation saves your butt, and someone decides rock walls are just as good as retaining walls Liz: Spoiler alert, they're not Abi: Not even close. So Liz, can you walk us through this one? What's the setup? Liz: All right, so picture this: a hillside, a condo project, an architectural firm that's also the developer, and a constructor in charge. So already we've got a lot of [00:01:00] hats being worn Abi: And none of them are hard hats apparently Liz: Ha, correct. So GBA member firm, who is our geotechnical heroes, they get hired to evaluate slope stability and provide recommendations for site development and foundations. Really a pretty standard start to a project Abi: Plus they've worked with this architect before, right? Liz: Oh, absolutely. I mean, long-term client, so really they felt confident and comfortable, maybe a little too comfortable working with this client Abi: Mm, yes. The classic, "We've worked together forever. What could go wrong?" energy. Liz: Oh yeah, I think we've all been there at some point, right? Abi: Oh, yeah Liz: So the member firm does their subsurface exploration and finds that the slopes are stable as they are, but, and this is a big but, deep cuts across the slope would likely [00:02:00] cause serious slope stability problems Abi: And of course, deep cuts were planned Liz: Well, of course. So this project, they were gonna have some 12-foot cuts for lower parking levels, and the architect's preliminary plans called for some retaining walls along the entire height of these cuts Abi: And the geotechnical project manager is gonna give a whole list of recommendations, right? Liz: Oh yeah, of course, and they're pretty solid. I mean, hey, limit cuts to one building width at a time, build and backfill each retaining wall before starting the next cut, install a survey control line uphill and monitor it daily, install interceptor drains at the toe and top of slope, and, and of course, have the member firm observe the cut slopes regularly Abi: Basically giving, "Hey, this is risky. Do it carefully, [00:03:00] and pretty please let us watch." Liz: Exactly. And they added the classic geotechnical disclaimer, "If design parameters change or differing conditions are encountered, call us before proceeding." Abi: I feel like is the geotechnical equivalent of, "Text me when you get home," and then nothing Liz: Right, nothing. Three months of silence. Nothing. Then the constructor calls, but not about the slope stability. They call to ask if on-site soils could be used for compacted fills Abi: So the project manager sends a geologist, gets the answer, and says, "Nope, only imported fills." And then guess what? More silence Liz: Oh, a lot more silence. Eight months of silence. Not a peep. Then the architect calls [00:04:00] asking for a visual reconnaissance of an adjacent parcel. The project manager says, "Sure, but follow the same recommendations and call us when grading starts." Abi: And then five years of silence Liz: Yeah, five years. This is crazy Abi: I feel like there should be some sort of horror movie on this, like The Silence: A Geotechnical Thriller. Dun, dun, dun. five years later, the member firm gets a letter from an attorney. I just feel like it's never a good sign when you get that Liz: No, never. And five years later, it's like, what project are we talking about, right? Like, you've, we've definitely moved on. Abi: Seriously Liz: So the condo association's attorney says that substantial earth movement has damaged one unit and it's threatening four more[00:05:00] Abi: So they're implying the member firm should have known and done more? Liz: Yep. So the project manager rushes to the site and discovers rock walls Abi: Wait, not retaining walls Liz: Nope, not retaining walls, rock walls. Just stacked boulders, no engineering, no structure, no reinforcement, no drainage, you know, none of those things that, uh, the engineers told them to do Abi: So we're pretty much relying on landscaping stones to hold up a hillside at this point Liz: Exactly. So what ends up happening is that one rock wall had actually pushed outward and it had broken through the wood frame wall of a condo unit. So wall tips over and breaks down a wall of this house Abi: That's feels like worst case Liz: And [00:06:00] the member firm's documentation showed they were never called for, for construction observation and that rock walls were never part of any plan that they saw Abi: So where do we go from here? Liz: All right. So the CEO of the member firm steps in, of course, and full on is like, "We're not taking this lying down." So he tells their attorney to call the condo association's lawyer and say, one, "Contact us before filing any claims." Two, "We had no involvement in the failure." And three, this is pretty bold, "If you sue us, we'll counterclaim for a frivolous suit." Abi: Ooh, I kinda like that Liz: Oh, yeah. So their insurer agrees and even retains the member firm's attorney to help Abi: So they're gonna meet with the condo association's lawyer, review the files, and everyone agreed [00:07:00] the member firm is blameless Liz: Exactly. The association then sues the architect, the constructor in charge, the joint venture, and the city Abi: And then the city thinks about cross-complaining against the member firm Liz: Oh, yeah. So the CEO is like, "All right, well, we're gonna repeat the same strategy. Don't sue us. We'll counterclaim." So they met, they reviewed all the files and the documentation, and again conclude the member firm is blameless Abi: So ultimately, no suit here, right? Liz: Yeah. No, no suit, right? Like that's what we want, right? Their documentation of what had happened really saved them Abi: Documentation, documentation, documentation. We hear it all the time, but it is so important Liz: Absolutely is Abi: Okay, Liz, this case history I feel like has [00:08:00] excellent lessons. Let's break them down Liz: All right, so number one is be wary of casual clients. So clients who don't understand geotechnical risk or who prioritize profit over quality, they can create huge problems. And in the geotechnical world, retaining walls can be high risk, so cutting corners can be very dangerous Abi: Yeah, I feel like that's the start of a lot of these case histories. Someone's just assuming that going for a lower price won't affect quality, and we all know the balance has to balance All right, so lesson two, use go, no-go and stay, don't stay analysis. That means don't just evaluate whether to take the project at the start. You need to evaluate the entire time on whether it makes sense to stay involved as the project [00:09:00] progresses Liz: Exactly. I think everyone knows of the go, no go, right? Like, it's a fairly common thing. I think in this case, the, the stay, don't stay analysis of, hey, you know, if things aren't going well in the project and they're not having you fulfill your responsibilities or they're starting to cut corners, um, having that conversation of, hey, should we stay in this project, or do we need to, you know, cut ties and leave to protect our liability and risk? Abi: Yeah, and really those conversations can even facilitate next steps. It doesn't necessarily mean you're going to completely remove yourself from the project, but maybe there's a couple conversations that need to be had Liz: Right, and it forces those conversations at that point. Abi: Absolutely Liz: Which kind of leads us to number three is failure to communicate is unacceptable. So I mean, really, the project manager should have followed up. In this case, silence is not [00:10:00] golden in geotechnical engineering. Uh, that project manager probably be like, "Oh, you know what? Like, I know they're under construction and we haven't heard from them. Maybe we should reach out or do a drive-by or something." Abi: Yeah, this is one of those situations where it's not the whole no news is good news type thing. Liz: All right Abi: y- you wanna know what's going on. that being said, the fourth kind of lesson here is being blameless isn't always enough. In this case, it was, and the documentation and proactive legal strategy saved them. But they had to have that documentation and proactive legal strategy to make being blameless work Liz: Right, and it goes back to if it's not documented, it didn't happen, right? So making sure that you have that documentation to, to protect yourselves really Abi: Absolutely Liz: So lesson number five, [00:11:00] propose complete service. So from site selection to project completion, even if clients decline offering services, it shows professionalism Abi: Plus, offering those complete services might keep you involved in the project a little bit more, and maybe the silence doesn't become such a a huge issue Liz: Yeah, that's true Abi: So that kind of leads into the sixth lesson, press clients for expanded services. Because anytime construction observation is available, we can prevent some disasters Liz: Right, like in this case, if they would've pressed and reached back out, they would've seen, "Oh, hey, you're not building retaining walls, you're building rock walls," and it could've been addressed before everything was actually done and constructed Abi: I agree 100%. Honestly, one of my favorite parts of this case history is the member firm's representative saying that they should [00:12:00] have warned more explicitly Liz: Yes, like adding bold warnings in the report. "Do not alter the suggested sequence without specific guidance," or, "Do not use anything other than a retaining wall," or something, right? Just trying to make those really important items a little bit more explicit. Abi: Yes. Like, do not do something obviously bad. Seriously, don't. Liz: Right. And they could have called the architect periodically, "Hey, how's the project going? Who's doing your site observation? Do you have any questions?" Just being more proactive Abi: Definitely. That one phone call might have revealed the rock walls. Okay. So Liz, what would you say your biggest takeaway is? Liz: I think on this one, really my biggest takeaway is that communication and documentation are everything. [00:13:00] And really, if you suspect a client might take shortcuts, then that means you need to be even more proactive and on top of things to really protect your risk and liability Abi: I like that a lot. And we have to remember, rock walls are not retaining walls Liz: Correct Abi: That's all we have for today's episode. Case History 22 is such a great reminder of why geoprofessionals need to stay engaged, stay communicative, and stay documented Liz: And why clients should listen to their geotechnical engineers. And this concludes this episode of the Case History series, brought to you by the GBA podcast. I hope you were able to take away some useful information that will help you and others at your firm make good risk-based decisions in the future. If this episode resonated with you or if you have a potential case history, we want to hear your story. [00:14:00] Email us at info@geoprofessional.org or comment on our LinkedIn post