Where MSA overrides go to die.

The Master Service Agreement is a yard’s biggest revenue lever and its biggest revenue leak. The terms are negotiated. The signature is on file. And then, somewhere between the contract folder and the invoice, the rate disappears.

The anatomy of a quiet leak.

Here is a pattern that plays out at yards with any meaningful volume of MSA customers. A GC or operator is on a 12% discount from book. The dispatcher who quotes the job was hired six months ago. The MSA contract lives in a shared drive folder that nobody has a direct link to. The dispatcher quotes book rate — not out of carelessness, but because book rate is what’s visible.

The customer pays book rate. The bookkeeper sometimes catches it — if she remembers the customer is on MSA and has time to cross-check the contract before the invoice goes out. Sometimes she does not. The invoice goes out at book. The customer pays it. A few months later, somebody at the customer’s office catches the discrepancy. They dispute the last four invoices. Now the yard owes a credit, and the customer relationship has a friction point that did not exist before.

On a $400,000-per-year account at a 12% MSA, getting billed at book rate costs the customer $48,000 they were not supposed to pay. Getting it right means the yard earns $352,000 on that account. Getting it wrong — in either direction — means disputes, credits, and eroded trust.

The four-system problem.

The root cause is not inattention. It is data fragmentation. At a typical single-yard operation, MSA terms live in four different places, none of which talk to each other:

The contract PDF. The signed MSA lives in a shared drive, email thread, or filing cabinet. It is accurate the day it is signed. Nobody is reading it before every quote.

A spreadsheet per customer. Some yards maintain a customer-rate spreadsheet. It is maintained by whoever last updated it. It may be current. It may be three renewals out of date.

Dispatcher memory. The dispatcher who has been there five years knows which customers are on MSA and roughly what their rate is. New staff do not. Staff who have been there two years know some of them. This is not a system; it is institutional memory with an expiration date.

QuickBooks. Accounting sees the final invoice. By the time it arrives there, the rate has already been applied — or not. QuickBooks can flag the variance after the fact; it cannot prevent it.

The fix isn’t discipline.

Every yard that has this problem knows they have it. The common response is a procedure: “before quoting, check the MSA spreadsheet.” Procedures require the person to remember to follow them. Under time pressure — a dispatcher handling six calls in an hour during morning dispatch — the procedure gets skipped. Not every time, but often enough.

Discipline does not scale across staff turnover. A yard that has had three dispatchers in two years cannot rely on institutional knowledge of which customers are on MSA. The knowledge leaves when the dispatcher does.

The fix is making the customer record the single source of truth. The MSA rate lives on the customer. Every quote, every invoice, every standby line pulls from the customer record automatically. The dispatcher cannot quote the wrong rate because the system applies the override before the invoice is generated. There is no step where the override can be skipped, forgotten, or misremembered.

What this looks like at two scales.

At 50 units, the spreadsheet-with-VLOOKUP approach works. One dispatcher, a short customer list, a bookkeeper who knows the regulars. The cracks are manageable. They show up as credits and corrections a few times a year, not as a structural problem.

At 150 units, the same approach fails. More dispatchers, more customers, more MSA tiers, more rate renewals that need to be reflected across all the places the rate lives. The error rate does not go up by 3× — it goes up faster, because more handoffs mean more opportunities for the override to fall through.

EquipFlow attaches MSA overrides directly to the customer record in accounts and sites. Those rates flow to billing automatically — applied at the invoice, not entered by hand. The dispatcher quotes the job. The system applies the rate. The bookkeeper reviews the invoice. There is no spreadsheet to update, no procedure to remember, no override to lose.

The quiet compounding.

The MSA leak is not usually one big mistake. It is a thousand small ones per quarter — a quote at book instead of MSA, an invoice that goes out before the rate is checked, a credit that gets issued after the fact. Each one is small. Together they add up.

The yard that fixes this does not see a single dramatic improvement. They stop having the problem. The disputes stop. The credits stop. The bookkeeper stops spending time checking rates she should not have to check. The dispatcher stops getting calls from customers who are paying more than they agreed to pay.

That is what eliminating the conditions that allow small errors looks like. Not a dramatic turnaround — a leak that stops dripping.