5 More Case Histories Refreshed

GBA Publications Committee .

Learn from others. Don’t repeat the mistakes of the past! GBA Case Histories are being used by our members for loss prevention discussions in support of professional development and mentoring.

That is why GBA case histories are so valuable, and why GBA is updating them all, while adding new ones, too. Five more Case Histories have been re-issued.

GBA CASE HISTORY 76 (download):
“No good deed goes unpunished” was the lesson learned by this Member Firm, whose project manager did a favor for a friend. When the friend failed to follow the project manager’s recommendations, the friend forgot that the project manager had ever made them and filed suit.

GBA CASE HISTORY 77 (download):
What happens when a disgruntled homeowner sues a housing developer for mold-induced illnesses? The homeowner and her attorney walk away with a large sum of cash, while two engineering firms and their insurers walk away with that much less.

GBA CASE HISTORY 78 (download):
The driller that the GBA member retained refused to listen to the member’s instructions because he thought he knew better. After almost drilling through the UST he was relieved of command and the project had to be shut down. But the member and his client were able to communicate, and, because of that, they got everything back on track, achieving project completion on time and under budget.

GBA CASE HISTORY 79 (download):
Be careful what you wish for, GBA Case History 79 points out, documenting a Member Firm’s first (and almost last) attempt to lead a design/build project: removal and replacement of a major UST system at a public facility.

GBA CASE HISTORY 80 (download):
The soils were soft in several areas, as the member’s report pointed out, and the client wanted some additional help. “Send an engineer,” came the request, and the member obliged. The member’s engineer visited the site and prepared a report with recommendations. The client said it followed the recommendations, but problems occurred nonetheless. And that’s why the client sued, saying the problems should not have happened. A trial judge agreed with the member, but the developer appealed…and won.

GBA Case Histories are FREE to all Members.

Access GBA’s Entire Library of Case Histories: HERE