010: Contractual and Information Risks

Darian Macey

Welcome back to Mastering Defence Infrastructure, DECNet Pro members, and anyone tuning in on Spotify and Apple Podcasts. We’re thrilled to have you with us as we tackle yet another critical topic in Defence project management.

Jessica Bottlebrush

Absolutely, Darian. And hey, if you’re new here, don’t stress. We’ve got a lot of ground to cover, but we’ll make it accessible for everyone, whether you’re just starting out or you’ve been managing Defence projects for years.

Darian Macey

Right. Let’s quickly get you up to speed. In Phase 2 so far, we’ve explored the DIPRAC framework—that’s Defence Infrastructure Project Risk And Contingency—and unpacked key risk areas like geographic and environmental concerns, stakeholder coordination challenges, and, of course, technical and delivery risks. Each one comes with its own unique pitfalls, particularly in Defence contexts.

Jessica Bottlebrush

And today, we’re diving into two risks that don’t always get enough attention—Contractual Risks and Information Risks. These are, kinda sneaky, you know? They’re embedded right there in your contracts and project data.

Darian Macey

They are. Often overlooked but massively consequential. Contractual risks include things like liability clauses, fitness for purpose obligations, or unclear definitions that can entirely shift project dynamics. Information risks, on the other hand, tie back to how you collect, store, and interpret critical data throughout a project lifecycle. Overlooking either could derail your timelines, your costs, or both.

Jessica Bottlebrush

And not in a fun way! We’re talking about those headaches that creep up because the tiny details weren’t caught early enough. But hey, that’s why we’re here, right? To unpack it all and help everyone navigate these risks better.

Darian Macey

Let’s start with the topic of contractual risks. Within the Defence Facilities Suite of Contracts, there are three critical clauses that can significantly impact contractors and project owners if they’re overlooked or misunderstood. These are the areas where small mistakes—or not paying close enough attention—can lead to major consequences.

Jessica Bottlebrush

Okay, start with the big one. Unlimited Liability—it sounds, honestly, a bit terrifying.

Darian Macey

It can be, if you're not careful. Unlimited Liability essentially means—well—there’s no cap on the financial consequences if something goes wrong. Let’s say a contractor unintentionally causes damage to infrastructure that’s part of a classified Defence operation. Without limits on liability, the contractor could be on the hook for—potentially—millions, even billions, in damages.

Jessica Bottlebrush

Wait, billions? That’s a lot to—uh—take in. No wonder it makes contractors super cautious during bids.

Darian Macey

Exactly. It drives up pricing significantly because contractors need to protect themselves against those worst-case scenarios. And even then—uh—there’s still a level of risk they can’t fully avoid. Now, compare that to commercial contracts in other industries. These are often capped at, say, two or three times the contract value. Defence contracts? A different story entirely.

Jessica Bottlebrush

Yeah, that’s—I mean, that’s huge. What about Fitness for Purpose? That one always feels like a bit of a trap.

Darian Macey

It kind of is, if it’s not defined clearly. Fitness for Purpose effectively means that the contractor guarantees the works will fulfill their intended purpose. Now, here’s the catch—

Jessica Bottlebrush

There always is one.

Darian Macey

There is. If the purpose isn't clearly defined in the contract, you could find yourself locked into what amounts to an open-ended obligation. An example? Say you’ve built a hangar, but later, someone decides it should double as a facility for drones. Suddenly, it doesn’t meet the new requirements, and you’re holding the bag, so to speak.

Jessica Bottlebrush

Oof. So you’d just… end up footing the bill to make it right?

Darian Macey

Pretty much.

Jessica Bottlebrush

That's a nightmare. And it’s all because no one pinned down what “fitness” actually meant upfront?

Darian Macey

Correct. Getting clarity on roles, responsibilities, and technical specifications early can save so many headaches. Now, on to the third big one—Consequential Loss. That’s another tricky clause because—well—it excludes what are considered indirect losses. Imagine project delays, lost revenue, reputational damage—

Jessica Bottlebrush

All the knock-on effects, basically.

Darian Macey

Exactly. But here’s the thing—what’s considered “indirect” versus “direct” isn’t always black and white. Contractors might assume they’re off the hook for certain damages, only to find out, through litigation, they’re not. There’s a grey area that courts might interpret differently than the parties intended.

Jessica Bottlebrush

So it’s less about what the clause says and more about how it could get read later? That’s a bit of a gamble, isn’t it?

Darian Macey

It is. But in some cases, you can negotiate tighter definitions upfront or seek to include specific exclusions. Those strategies can make a world of difference down the line.

Jessica Bottlebrush

Yeah. It’s kinda like having a road map—you’re still driving, but at least you know where you’re headed.

Darian Macey

Exactly. And as we’ll see, that’s where negotiating tailored risk distribution comes into play. It’s not about avoiding risk entirely—it’s about being intentional about how you allocate it.

Jessica Bottlebrush

Alright, intentional risk allocation—you mentioned that’s key. So, let’s dig into the practical side of it. What strategies can project owners and contractors use to balance these risks effectively?

Darian Macey

Good question. One effective approach is through provisional sums and latent conditions clauses. These mechanisms are all about addressing the unknowns in a contract proactively.

Jessica Bottlebrush

Okay, but break that down for us. How do provisional sums actually work?

Darian Macey

Sure. Provisional sums are essentially placeholders in your contract budget for items with uncertain scope or cost. Let’s say you’re excavating and suspect there might be old infrastructure buried underground. Instead of locking in a fixed price, you allocate a provisional sum. If you find something, the cost to address it comes from that reserve. If not, no money spent.

Jessica Bottlebrush

So it’s kinda like reserving a “just in case” fund?

Darian Macey

Exactly. It gives both parties flexibility and ensures the contractor isn't gambling on unknowns. But here's the kicker—properly scoping and defining those sums early on is critical, or you risk disputes down the line.

Jessica Bottlebrush

What about latent conditions clauses? Are they in the same ballpark?

Darian Macey

They are. Latent conditions deal specifically with what's hidden—literally underground in many cases. Think unexpected asbestos, contaminated soil, or, you know, that ancient infrastructure no one knew was there. These clauses clarify how those risks get shared between the owner and contractor. For fair distribution, you need clear definitions of what qualifies as a latent condition.

Jessica Bottlebrush

Right, so it’s about drawing the line on who owns what part of the risk. But what about bigger decisions? Like choosing the right procurement model?

Darian Macey

Ah, yes. Aligning contract terms to actual project certainty is huge. For projects with a lot of unknowns, a Managing Contractor model can make more sense. It puts the focus on collaboration and gives contractors the ability to refine scopes and approach risks iteratively as new information emerges.

Jessica Bottlebrush

And D and C —Design and Construct—that’s the opposite, right? Higher responsibility on the contractor?

Darian Macey

Exactly. D and C works best when the project scope is well-defined upfront. The contractor takes on more risk but has greater control over design outcomes. Ultimately, the trick is matching the procurement model to the level of certainty you have at the outset.

Jessica Bottlebrush

Makes sense. It’s like trying to use the right tool for the job, rather than forcing it to fit.

Darian Macey

Precisely. The more upfront effort you put into getting the right structure and clauses in place, the better equipped you'll be to navigate those inevitable challenges as the project unfolds.

Jessica Bottlebrush

Thinking about everything we just discussed—provisional sums, latent conditions, and matching the right procurement method—it got me wondering about another layer: information risks. Darian, this one feels like the silent sabotage—you don’t notice it until things start going wrong.

Darian Macey

Exactly, Jessica. Information risks often come from data we assume is complete or accurate but isn’t. Defence infrastructure projects are incredibly complex, and even small gaps can snowball into major issues.

Jessica Bottlebrush

Like asbestos, right? It’s the classic example of a hidden problem that can derail projects completely.

Darian Macey

Absolutely. Asbestos is a big one. Assume you’re rehabilitating an old Defence site. The original building survey might say there’s no asbestos, but further down the line—say during demolition—you, uh, discover fragments buried deep in the soil. Suddenly, your timeline stretches, your costs balloon, and local regulations come into play, adding even more red tape.

Jessica Bottlebrush

And the contamination. Oh, I mean, soil contamination is another nightmare. Like, you think it’s clean until you’re halfway through excavation.

Darian Macey

Yes, it can lead to layers upon layers of challenges. From stoppages in construction to expensive remediation processes, it’s one of those risks that’s rarely solved cheaply or quickly. And these aren’t isolated issues; they’re shockingly common.

Jessica Bottlebrush

Which brings us to FeeMaster right? That tool sounds like a bit of a game-changer for figuring out where the gaps are.

Darian Macey

It can be. FeeMaster essentially allows you to assess the quality of the data inputs you’re relying on for your project. It’s, uh, like holding a magnifying glass over the early stages of your planning process. It has a checklist that prompts you to rank how complete, accurate, or outdated your information is, giving you a score to pinpoint weak spots before you even get started.

Jessica Bottlebrush

Wait, really? So you run your project data, it tells you where the problem is, and then what?

Darian Macey

That’s when you adjust the plan. Think of it as a proactive tool. If it flags issues in geotech reports, for example, you know to investigate further before contractors start mobilizing. The same with environmental baselines—catching those early means fewer nasty surprises mid-project.

Jessica Bottlebrush

Right, because by then, the budgets and timelines are already locked. So fixing it is gonna cost way more.

Darian Macey

Exactly. The major impact of information gaps is that they ripple across the entire project lifecycle. You could have teams ready to go, machinery in place, and then—boom—you hit an unanticipated delay. It drains morale, blows budgets, and undermines project confidence.

Jessica Bottlebrush

And it can even, uh, put the project’s future in doubt. I’ve seen examples where things got paused indefinitely because the risks—well, they just kept piling up.

Darian Macey

Precisely. Handling information risks early is all about preventative measures. It’s much easier to address shortcomings while still in the planning phase. Once dirt hits the shovel, fixing those gaps becomes exponentially harder and costlier.

Jessica Bottlebrush

Yeah, so the moral is: don’t skimp on the homework upfront. It’s always worth it in the long run.

Darian Macey

Building on what we just discussed about addressing risks early, tools like FeeMaster really emphasize the need to gather accurate, comprehensive information as soon as possible. It’s all about creating a strong foundation, because without it, the entire project can be jeopardized.

Jessica Bottlebrush

Right, so think surveys and testing?

Darian Macey

Exactly. Site surveys, environmental testing, geotechnical studies—they’re the basics. But you’d be surprised how often people skip these steps or treat them as afterthoughts. Taking shortcuts here can—I mean, it can lead to massive oversights.

Jessica Bottlebrush

Yeah, and then you’re left scrambling halfway through a project. No thanks. But what else can teams do to stay ahead?

Darian Macey

Well, documenting assumptions is key. Anytime you craft a tender or negotiate a contract, it’s critical to outline the assumptions you’re working under. For example, if your geotech report assumes stable soil conditions but no borehole tests were done, make sure that’s explicitly stated in the document. That way, if something unexpected crops up, your position is protected.

Jessica Bottlebrush

So it’s all about transparency. Spelling out what you know—and what you don’t know—before signing anything?

Darian Macey

Exactly. It’s a safeguard—for both parties, really. Ambiguity is what leads to disputes down the line, so the clearer you are upfront, the smoother things go later. But even beyond contracts, this practice builds trust. Clear communication shows that you’ve done your homework and aren’t trying to shift hidden risks onto someone else.

Jessica Bottlebrush

Yeah, it’s like saying, “Here’s the full picture—we’re all on the same page.” It’s such a simple step, but it sounds like it can save a lot of drama.

Darian Macey

Exactly. It’s not just a best practice—it’s a project-saver.

Darian Macey

Taking all that into account, let’s look at how these principles apply in real life—specifically with Project Ironclad. It’s a prime case study for seeing how risks unfold and are managed in complex Defence projects.

Jessica Bottlebrush

Okay, quick recap. We’ve got unlimited liability, fitness for purpose challenges, and some incomplete geotech and contamination data. So, uh, where did it all start going wrong?

Darian Macey

It really began with the initial contract negotiations. Unlimited liability, for example, should have been capped or better defined from the outset. When you leave an open-ended liability clause, I mean, you invite inflated costs because contractors are forced to price for every worst-case scenario.

Jessica Bottlebrush

And those worst-case scenarios? They can blow up fast, right? Like, you’re suddenly dealing with, I don’t know, surprises buried deep in the fine print.

Darian Macey

Precisely. Unlimited liability is like carrying an umbrella with no handle—it’s not doing much to actually protect you. Negotiating reasonable caps would’ve shifted the focus to collaboration instead of caution.

Jessica Bottlebrush

What about fitness for purpose? That feels like a classic Defence project hurdle.

Darian Macey

It is. And the issue here was a lack of specificity. The contract didn’t clearly outline what “fitness” meant for the project. It’s a critical step—use cases and technical requirements need to be spelled out so there’s no ambiguity.

Jessica Bottlebrush

Yeah, ‘cause otherwise, you’re left guessing. And if the project scope changes halfway through, contractors are in this weird limbo, trying to make it all fit.

Darian Macey

Exactly. For Ironclad, they could’ve addressed this by involving technical advisors early on to define every potential use case. Fitness for purpose isn’t inherently risky—it’s the assumptions and gaps that make it problematic.

Jessica Bottlebrush

And then there’s the geotech and contamination data—this one’s kinda personal, I think. I’ve worked on projects where those gaps just snowballed. It’s not pretty.

Darian Macey

I’m not surprised. Geotech and contamination issues can derail entire timelines if they’re not thoroughly investigated upfront. For Ironclad, incomplete data delayed decision-making and risked compliance with environmental standards. They should’ve invested more in early, comprehensive site assessments. Spending more at that stage avoids a minefield of costs later.

Jessica Bottlebrush

So... basically, the big takeaway is that everything comes back to upfront effort, yeah? Clarity, definitions, planning—it’s just gotta happen early.

Darian Macey

That’s it, Jessica. What you do—or don’t do—in the early stages determines whether your project thrives or stumbles along the way. And Ironclad? It’s the perfect illustration of why foresight matters.

Darian Macey

So, Jessica, as we saw with Project Ironclad, the importance of addressing risks early on—whether it’s liability clauses, fitness for purpose definitions, or geotechnical data—can’t be overstated. Identifying these issues upfront can make all the difference between smooth sailing and a project that’s constantly firefighting.

Jessica Bottlebrush

Right. I mean, we’ve seen it over and over—projects that invest upfront in proper scoping and investigation? They just... I don’t know, they run smoother from start to finish.

Darian Macey

Exactly. And it's not just about the scoping. Documenting assumptions, engaging the right technical experts, setting fair contractual terms—these steps lay the foundation for success.

Jessica Bottlebrush

And don’t forget collaboration. When you’ve got transparency and open communication with Defence, it’s like—it smooths out so many bumps in the road, yeah?

Darian Macey

Absolutely. Collaboration ensures everyone’s working with the same level of understanding. It’s the glue that holds these processes together, keeping risks contained and manageable.

Jessica Bottlebrush

Honestly, the biggest headaches? They come when assumptions aren’t checked, or when people skip the nitty-gritty details. It’s always the tiny stuff that causes the biggest dramas later on.

Darian Macey

True. Clear documentation, proactive investigation, and a willingness to go the extra mile early on—that’s what pays dividends, every single time.

Jessica Bottlebrush

And hey, it’s not just about the projects either. It’s about building trust, right? Between contractors, project owners, Defence—it makes everything less combative in the long run.

Darian Macey

Exactly. Risks are inevitable, but how you approach them—early, with transparency and thorough preparation—that’s what really defines the outcome. And that mindset? It sets the tone for how all Defence projects should operate.

Jessica Bottlebrush

Alright, folks, as we’ve been discussing, preparation and collaboration are key to success. To wrap up this week, we’ve got just a few quick reminders for you.

Darian Macey

Yes, first, make sure you complete the quiz on the lesson webpage. It’s designed to reinforce the key points we covered—and trust me, it’s worth the time.

Jessica Bottlebrush

Definitely. And don’t forget the scenario-based exercise. Those are always great for applying these ideas to real-world situations. Oh, and—uh—jump into the forum to share your outcomes. It’s always interesting to hear how everyone approaches the same challenges differently.

Darian Macey

Precisely. Collaboration and shared learning are what make these exercises most valuable. Also, we’d genuinely love your feedback on how the lesson worked for you. Your input helps us refine these sessions and make them as useful as possible.

Jessica Bottlebrush

And hey, if you’re enjoying the course, why not recommend it to someone else in Defence infrastructure? Sharing it around helps us grow the community and, you know, make this knowledge available to more people.

Darian Macey

Absolutely. With that, we’ll call it a day. Thank you for joining us, and we look forward to having you back for the next episode of Mastering Defence Infrastructure.

Jessica Bottlebrush

Yeah, thanks everyone! Take care and see you next time.