Redline Wars

Last year, a deal I cared about almost died over a single clause. Ninety-three redlines came back from legal. The one that nearly ended the negotiation was about a risk that, in this specific engagement, would almost never materialize. Meanwhile, the thing that actually mattered, a data portability provision worth hundreds of thousands in future switching costs, went untouched.

That is the problem with how most organizations handle legal and procurement. Two protective functions, calibrated to different risks, operating in parallel instead of in partnership.

In this episode, I break down why procurement addresses commercial risk and legal addresses legal risk, and why that distinction is why the two functions never report to each other. Then I walk through the five patterns that turn legal review into a redline war: risk theater, the broken sequential review model, redlines without commercial context, risk tolerance mismatch, and unclear escalation paths. Each one is fixable. None of them are fixed by telling people to get along.

If you are a General Counsel, a Legal Operations leader, a CPO, or a business stakeholder who has ever watched two protective functions fight each other to a draw, this episode is for you. The goal is not peace. The goal is protecting the same thing together.

The Other Side of the Table. What Your CPO Wishes You Knew.

---

New episodes every Monday. 

Subscribe wherever you listen. 

Website: https://procurexcellence.com 

Email: robert@procurexcellence.com 

Topics covered: vendor proposals, procurement rejection, discovery process, risk management, mission-driven purchasing, stakeholder alignment, supplier relationships

Transcript

SPEAKER_00 0:00

A few years ago, a deal I cared about almost died over a single clause. It was a three-year technology agreement, mid-seven figures in total contract value, a supplier our program team had vetted very carefully, a product we actually needed, and an implementation window we could not afford to slip. My team had spent two months getting the commercial terms where they needed to be. The business was now ready, and the supplier was also ready. And then the contract hit legal review. Within a week, the red line came back. ninety-three track changes. Most of them were reasonable, a handful were essential. But the one that nearly ended the deal was a rewrite of the indemnification language. Our council wanted uncapped indemnity for a category of claims that, in this particular engagement, would almost never materialize. The suppliers council would not move. And then our council would not move. And for three weeks, two lawyers, who had never operated the underlying business, argued over an exposure that based on the actual service being delivered, was hypothetical at best. Meanwhile, the thing I was actually worried about, they did a portability provision that would determine whether we could ever switch providers without paying a ransom, went largely untouched by legal, because it was not in their standard red line template. It was not a cause that they typically fight. It was an operational risk, not a legal theory risk. And the distinction actually mattered. The deal eventually did close. The indemnification language landed somewhere reasonable after escalation to our general counsel and his counterpart at the supplier. But I walked away from that negotiation asking myself a question I've been asking ever since. Two of the most protective functions in any organization are legal and procurement. We both exist to keep the organization out of trouble. So why is it so often the case that we end up fighting each other instead of the actual risk? This is episode five of the other side of the table. I'm Robert Brindle, and today we're talking about the collision between legal and procurement, red line wars, risk tolerance mismatches, and how two protective, highly valuable functions can stop working in parallel and start protecting the same thing together. Let me start with something that took me years to fully understand. Legal and procurement are not the same function. I know that sounds obvious, but in a lot of organizations they get treated as interchangeable. A contract comes in, procurement and legal both review it, everyone signs off, and the deal goes through. If there's friction, leadership often chalks that up to personality. Either legal is being difficult or procurement is being political. Let's just get them in a room and hash it out. That framing is wrong, and it's part of what causes the collision in the first place. Here's the cleanest way to say it. Procurement addresses commercial risk. Legal addresses legal risk. Those are different risk families, and the instincts required to manage each one are different. That is also why in practice, these two functions do not report to each other. Legal sits under a general consul, typically reporting to the CEO or the board, while procurement sits under the COO or the CFO. That structural separation is deliberate and intentional. Each function needs the independence to raise its own flags without being filtered through the others' lenses. If legal reported into procurement, the commercial instinct to get the deal done would quietly soften the legal pushback. If procurement reported into legal, the conservative default would eventually choke the commercial velocity the business needs to operate. The org chart is designed to keep those tensions productive. Get more specific and the distinction gets sharper. Legal protects the organization from legal exposure, contract law, regulatory risk, liability theory, intellectual property. Procurement, however, protects the organization from operational and commercial harm, bad deals, supplier failure, scope that will not survive contact with reality, and commitments the organization will regret. When those functions work well together, the organization gets the benefit of both lenses. When they don't, the organization pays twice, once in friction, and once in missed protection. So let me walk through what actually goes wrong. These are five patterns I see over and over, and what it takes to break them. Number one, risk theater instead of risk management. Every legal department has a standard red line package. It's the set of clauses they always push on, the language they always strip out and the positions they're always anchored to. That package exists for good reason. It represents accumulated institutional knowledge, it keeps reviews consistent, and it creates predictability for the organization. But when that package gets applied to every contract, regardless of the actual deal, you get risk theater. Legal is pushing hard on the causes they always push on. Whether or not those clauses matter to this particular transaction. A ten thousand dollars subscription gets the same indemnification treatment as a ten million dollar implementation. A short term advisory engagement gets the same IP assignment scrutiny as a platform build. The clauses get fought because they are in a template, not because they represent the actual risk of the deal. I want to be careful here, because I'm not criticizing legal for having standards. Standards are essential. What I'm describing is when standards stop being a floor and start being a script. The craft of legal work at its best is knowing when to hold the line and when to collaborate. And that collaboration requires context that legal often does not have, because they are the last function to see the deal. Which brings me to pattern number two. The sequential review model is broken. In most organizations, a deal moves through stages. The business scopes it, procurement sources it, commercial terms get negotiated, and then at the end, Legal gets the contract. Their job at that point is to review the document and apply the standard red line package. Here's the problem with that model. By the time Legal sees the contract, all of the structural leverage is gone. Procurement has already negotiated the commercial terms, set the expectations with the supplier, and committed to a timeline. The business has already invested weeks of momentum. The supplier is already signed off on the scope. And now Legal walks in, raises a concern that would require a fundamental restructuring of the entire deal, and everyone looks at them as though they're the obstacle. Legal is not the obstacle. They are the late entrant in a process that should have included them earlier. If Legal had been in the room when I was negotiating the data rights framework, we would have aligned on that what matters before I anchored the commercial position. If Legal had reviewed the scope of work while I was while it was still being written, we could have structured the risk allocation of the language of the business, not retrofitted it into the contract after the fact. The sequential model makes Legal look slow, and the real issue is that they were handed a finished document and asked to edit the foundation. three red lines without commercial context. This is the pattern that creates the most heat in the room. Legal marks up a contract without knowing what trade-offs procurement has already made. They push back on a payment term without knowing that we conceded it in exchange for a better escalation cap. They strip out limitation of liability provision without knowing we accepted it in exchange for an uncapped indemnity on IP infringement. They rewrite a termination clause without knowing that the supplier has already told us on the record they will not accept that rewrite, and walking away means restarting a six month sourcing process. LEGAO is not doing anything wrong in any of these moments. They are doing exactly what their function expects. The failure is upstream. Procurement did not brief them, or procurement did brief them, but the brief was a summary instead of a narrative. The nuance did not transfer, and now two teams are negotiating the same deal from different starting points. The fix is not to send legal more documentation. It's to build a handoff that treats the deal as a single thing, with multiple protective lenses, not as a document that gets passed down an assembly line, which leads to number four risk tolerance mismatch. This one is subtle, and it's the one I've gotten the most times in my own career. Every organization has risk tolerance. It's not static, and it is not always articulated, but it does exist. A mission driven nonprofit has a different risk tolerance than a venture backed startup. A publicly traded company has a different risk tolerance than a private family business. Even in the same organization, there are different risk tolerances for different categories. We might accept more risk on a strategic innovation investment than on core infrastructure. The job of legal and procurement is to calibrate to that tolerance, but they do not always calibrate to the same version of it. Legal by training tends to default to the more conservative position. That's not a criticism, it is a feature of their profession. Their job is to prevent the worst case scenario, and they get evaluated on the problems they keep out of the organization, not the deals they help to close. Procurement by necessity tends to operate closer to the actual risk tolerance of the business, because we are accountable for both protecting the organization and enabling it to get things done. When these two defaults do not reconcile, you get deals that stall. Procurement pushes back because they know the business is willing to accept the risk, and the supplier will not move. And the meeting devolves into a debate over positions instead of a conversation about the organization's real tolerance. The organizations that get this right have done the work explicitly to define tolerance across deal categories, not in a risk register that sits on a shelf. In a shared framework that legal and procurement reference together, when a contract hits an edge case, when both functions are calibrating to the same version of the organizational tolerance, the disagreements get smaller and the escalations get faster. Which leads to number five. Unclear escalation paths paths. When legal and procurement disagree, who breaks the tie? In a lot of organizations, the honest answer is whoever has more political capital that week, or whoever the CFO trusts more, or even whoever happens to be in the room when the question gets asked. That's not governance, that's improvisation. The strongest operating models I've seen define in advance how legal and procurement escalate when they can't align. It you know, is it the general counsel and the CPO as peers? Is it the COO as a tiebreaker? Is it a standing risk committee that reviews contested terms on a set cadence? The mechanism matters less than the fact that one exists. Without a defined escalation path, every disagreement becomes a political event. People take sides, timelines stretch, the supplier wonders whether the organization can actually decide on anything, and both functions lose credibility because leadership starts to see them as bottlenecks instead of as partners. A clear escalation path does the opposite. It signals that the organization takes risk seriously enough to have a framework for it. It depersonalizes disagreements. It lets both functions advocate hard for their respective lenses, without the conflict feeling like a power struggle. Let me bring this home with a specific guidance by audience. If you're a general counsel or legal operations leader, partner with your procurement function before the contract shows up on your desk. Ask your CPO for a quarterly review of the categories where legal and procurement have been colliding the most, and what the root causes were. You will almost certainly find that the friction concentrates in a predictable set of deal types, and that most of it could have been resolved by aligning on risk posture upstream instead of relitigating it on every transaction. Consider embedding a legal resource in your procurement sourcing process for a high complexity for high complexity categories. The time your team spends early will save multiples of red line cycles later. And one more thing. When your team marks up a contract, give them the commercial context you have. A two page brief from procurement on the deal's trade-offs, done well, can cut redlining volume by half. If you're a CPO or procurement leader, own the brief. If Legal is showing up late or positioning conservatively, some of that is on them, but some of it's on you too. You have information legal does not. The commercial concessions you've already made, the operational risks the business is willing to absorb, the supplier dynamics that shape what is negotiable. Transfer that context deliberately. Do not send legal a contract with a note that says please review. Send them the contract with a narrative that explains what's been negotiated, what's open, what the business cares about, and where you need their judgment most. That framing changes how legal engages with the work. If you're in the business, a program lead or stakeholder watching legal and procurement argue about your deal resists the instinct to protect to pick a side. The friction you are seeing is usually not a personality problem, it's a process problem. If legal and procurement are in a red line loop on your contract, the most useful thing you can do is ask both functions together a simple question. What is the actual risk we are trying to prevent here? And what would make us both comfortable? That question forces the conversation out of positions and into interests, and it usually gets resolved faster than escalating to your VP. If you're a supplier and accounting exec, understand that when Lego enters the room, procurement has not suddenly become your enemy. A red line coming back hot is not a signal that the deal is dying. It's a signal that a protective function has opinions that have not been recorded yet internally. The worst thing you can do at that moment is to escalate to your champion on the business side and try to pressure legal to back off. That move tells procurement that you will use political pressure when you cannot get what you want through the process, and it poisons the trust we've already built. Instead, ask procurement what context would help Legal understand the deal better. Offer to get your console on a call with ours. Treat the legal review as part of the deal, not as an interruption to it. And if you're a CEO, COO or CFO, look at how legal and procurement are structured to work together in your organization. Are they separate reporting lines that meet at the contract? Or is there a shared operating model that defines how risk posture gets calibrated, how escalations get resolved, and how the two functions brief each other before the deal hits review? If it's the first, you are paying for friction you do not have to pay for. The fix is not expensive, it's a handful of process commitments and a cadence of joint review. And the payoff is measurable, faster deal cycles, cleaner contracts, and a lot less political theater between two functions that should be on the same side. Here is the thing that I want every listener to hold on to. Regardless of your function, legal and procurement are both protective. We both exist because organizations need a check on their own enthusiasm. But protection is not the same thing as resistance. The best version of this relationship is not two functions fighting each other to a draw. It's two lenses pointed at the same deal, catching different things, and then aligning on what matters. That is what it looks like when you stop having red line wars and start protecting the same thing together. Next episode we're shifting audiences again. We are going to be talking about what actually happens when a contract auto-renews, why those renewals are often the quietest way an organization bleeds value, and what it takes to build a renewal discipline management discipline that actually works. It's an episode for everyone who signs contracts and never thinks about them again until it's too late. Thanks for listening. I'm Robert Brindle, and this has been the other side of the table.