Defend the Margin Without Losing the Project

Project managers protect margin by negotiating changing economics early, with evidence, options, and a clear connection to project outcomes. 

It’s never the right time to raise a cost issue. There’s always a reason to wait for a calmer week, and the longer a PM waits, the harder the ask becomes because it “should have been brought up earlier”. Timing does most of the damage here. Six weeks earlier, the same conversation is a scheduling problem you try to solve together. Six weeks later, it’s a bill one side pays or the other side eats, and by then alternatives are likely gone. 

Each time we work with a client, we have them complete prework, to better understand their negotiations. During our prework, we often hear that the PMs who get through this with margin and the relationship both intact bring the same core elements: A cost record, a second option, and a reason the customer benefits from settling it now.  

Margin erodes when work outpaces the agreement 

Individually, none of this seems worth a phone call. A field decision adds labor. An approval slips, and crews sit idle waiting on it. A supplier revises pricing days before installation, or a customer asks for support that looks minor but sets up a cost structure nobody priced. Any one of them is easier to absorb than to raise, and that’s usually the right call in the moment. 

The problem comes when those reasonable one-off decisions begin to add up. If the team repeatedly completes extra work without adjusting the commercial terms, that work starts to look like part of the original agreement. By the time the accumulated cost is large enough to raise, the project has already absorbed it, and the other party may reasonably believe it was included from the beginning. 

Establish the economic baseline before there is a dispute 

 The record is only worth something if it exists before you need it. That means a baseline you can use during delivery, not a document nobody opens after kickoff. It gives you a way to tell a change from a misunderstanding, and a real added cost from an estimate that was thin to begin with. Most of it fits on a page: 

1. Original scope and explicit exclusions. 
2. Pricing assumptions, quantities, rates, and allowances. 
3. Customer and supplier commitments. 
4. Required approvals, access, information, and decision dates. 
5. Billing codes, change procedures, and documentation requirements. 
6. Schedule activities that drive labor, equipment, or overhead cost. 
7. Known risks and the party responsible for each risk. 

Document the economics in real time 

The baseline covers what was supposed to happen. From there, it’s a matter of tracking what moves away from it, and the timing on that matters more than most people expect. A note written while the event is still in front of you takes two minutes. Reconstructing the same thing six months later can produce a record that’s entirely accurate, and the customer still has no way to check it. They’ll assume you built it to win the argument. 

So, for each one, get down what happened and what caused it, when it happened, who you notified, what decision it needs, and what it does to cost, schedule, quality, safety, or risk. Then attach the proof: approved drawings, quantities, time logs, supplier notices, photos, written direction. 

Most of this never leaves your own files. It exists so that when the conversation does happen, you and the customer are working from the same set of facts rather than two memories that drifted in useful directions. 

Negotiate the cause, not only the price 

A request framed only as, ‘We need more money,’ invites a yes or no answer. A stronger discussion explains what changed, why the change matters, and which project objective the proposed adjustment protects. 

Use a sequence like this to turn a margin discussion into a project decision with financial consequences: 

1. Confirm the shared facts and the relevant contract or scope baseline. 
2. Explain the changed condition and its operational effect. 
3. Show the cost or schedule calculation with clear assumptions. 
4. Connect the request to quality, safety, continuity, speed, or another shared project goal. 
5. Present options and ask for a defined decision. 

Create options before urgency removes leverage 

 Having the facts is a start. What the customer wants next is a way out of the problem, and you have more of those to offer while the schedule still has slack in it. Once the work has to happen, the only question left is who pays for it. Bring it up earlier, and there’s usually more than one reasonable answer: 

1. Keep the current plan and approve the documented adjustment. 
2. Change sequence, method, specification, or scope to reduce the cost. 
3. Share a defined cost when both parties contributed to the condition. 
4. Exchange timing, volume, access, payment, or another commercial term. 
5. Use an alternate supplier, material, or delivery approach when feasible. 
6. Approve an interim step while technical validation continues. 

Protect the relationship without giving away the economics 

The hesitation at this stage is usually about tone. Raising cost feels like it will strain a relationship the job still depends on, so the ask gets softened until the customer isn’t sure anything was really asked. 

Surprises do more damage than firmness does. A customer who hears about the cost after it’s been absorbed has no way to evaluate it and no chance to help solve it. Vague agreements work the same way, just more slowly, since both sides leave the conversation with a different understanding of what was settled. 

Firmness and collaboration, though, can coexist. State the issue early, invite the other party to test the evidence, acknowledge legitimate constraints, and work together on options. Stay clear about the financial effect. A positive tone should not make the commercial position ambiguous. 

Use concessions as trades 

Most of these conversations end with the project team giving ground somewhere, which is a normal outcome. The question is what the concession buys in return. 

A smaller adjustment might be worth it if the customer commits to approvals inside three days. Reduced scope can be traded for a schedule the crew is able to staff. Guaranteed volume, revised access, and improved payment terms all carry real value to a project, and any of them can justify movement on price. 

The trade has to be worked out before the meeting, not during it. Before the conversation, define the ideal outcome, the acceptable range, the point at which the project should escalate or decline, and the commitments that could justify movement.  Preparation is what separates a trade from a discount handed over under pressure. 

A practical example of margin protection 

Take a supplier who raises the price of a critical component a few weeks before installation. The project needs the material and a delay hits the schedule, so flat refusal is not a credible position. Agreeing on the spot moves the entire problem onto the project. 

The project manager starts with the original quote and works out how much of the increase traces to input costs that genuinely moved. She prices the schedule effect of going to a different supplier, which tells her what continuity is worth. Then she brings three options to the table: hold the original price for the quantity already committed, split the verified increase in exchange for a longer volume commitment, or move to an approved alternative on a revised delivery plan. 

The tone stays cooperative and the position stays firm. The supplier has real constraints, the project needs the material to arrive, and neither of those facts requires the project to absorb the full increase. 

A project margin negotiation checklist 

1. Confirm the scope, commercial terms, and approval process. 
2. Build the cost and schedule baseline before work begins. 
3. Track changed conditions and notify stakeholders promptly. 
4. Quantify the effect with transparent assumptions. 
5. Identify the other party’s constraints and decision authority. 
6. Prepare multiple operationally sound options. 
7. Define what the project needs in return for any concession. 
8. Record the final decision, owner, timing, and financial effect. 

Treat project economics as an active negotiation 

None of this is difficult on its own. Any experienced PM can keep a record while the details are fresh, raise an issue while the schedule still has room in it, and bring more than one answer to the table. The issue is that all of it competes with delivery for attention, and delivery tends to win. Margin doesn’t usually disappear in a single bad decision. It goes a little at a time, absorbed by people who meant to raise it later and then didn’t. 

The economics of a project keep moving long after the contract’s signed, which makes them worth managing as deliberately as anything else on the job. That’s what keeps the work, the risk, and the money pointed in the same direction while conditions change underneath them. 

SNI works with project teams on the commercial side of delivery: getting evidence in order, building options that hold up, and running these conversations before they happen for real. If margin is leaving your projects one small change at a time, contact us and we’ll talk through what that looks like on your work.  

Frequently asked questions about protecting project margin