7 Essential Business Contract Clauses Missouri Business Owners Need

The boilerplate nobody reads — until it's the only thing that matters

Illustration: The boilerplate nobody reads — until it's the only thing that matters

Most contracts get signed without much ceremony. A vendor sends a subcontract, a landlord sends a lease, a new hire gets an offer letter with an arbitration agreement stapled to the back. Everyone skims the parts that matter to them — price, dates, job title — and signs.

The clauses that decide what actually happens when something goes wrong rarely get a second look. They sit in the "standard terms" section, copied from whatever template was lying around. And then, months or years later, a payment doesn't arrive, a tenant stops mining the coal they promised to mine, or a company decides it can change the rules of an agreement whenever it wants — and suddenly those ignored paragraphs are the entire case.

Missouri courts have spent more than a century sorting through exactly these disputes, across industries as different as agricultural lending, coal mining, IT staffing, school construction, and long-term care. The fact patterns vary wildly, but the underlying lesson doesn't: the clauses that feel like formalities are usually the ones that end up controlling the outcome.

Here are seven of them, with the cases that prove it.

Spell out the whole deal — in writing
Define "done" with a bright line, not a ballpark
Build in a real default-and-termination process
Make your dispute-resolution clause actually work
Put a price on late payment
Set — and defend — your notice deadlines
Don't let "we can change this" undo everything else

1. Spell Out the Whole Deal — In Writing

A surprising number of contract disputes don't turn on what a clause means. They turn on whether there was ever an enforceable agreement to begin with — because the terms that mattered most were never actually written down.

When There's Nothing to Point To

Yoest v. Farm Credit Bank of St. Louis, 832 S.W.2d 325 (Mo. App. 1992), is a cautionary tale about exactly this. The Yoests were longtime family farmers who'd borrowed from Central Production Credit Association (CPCA) every year since the 1960s. When CPCA pushed them toward shorter-term notes, the Yoests claimed they'd struck a deal with the Farm Credit Bank: CPCA's short-term notes would get rolled into a long-term FLB loan, in exchange for the Yoests obtaining a separate subordination. When that roll-over never happened, they sued for breach of contract.

The case never got past a motion to dismiss. As the court put it,

"[t]here is nothing in the pleading to show whether or not the alleged contract was oral or written, nothing to show the terms of the notes, the amounts involved or time period of the terms."

To state a breach of contract claim in Missouri, a plaintiff has to plead "an agreement between parties capable of contracting; mutual obligations arising under the agreement in respect to a definite subject matter; valid consideration; part performance... and damages measured by the contract."

Without a document — or at least specifics — there was nothing for a court to enforce.

The Yoests also tried a second angle: because they were members of the CPCA cooperative, and because CPCA had been advising them for years, they argued the relationship was something more than an ordinary lender-borrower arrangement — something closer to a fiduciary duty. The court rejected that too. A fiduciary relationship requires specific facts: that one party, "because of age, state of health, illiteracy, mental disability or ignorance," became subservient to the other, surrendered control of their property, and lost their independence. Decades of borrowing money and taking advice from a loan officer doesn't get you there. If a business relationship is supposed to carry obligations beyond the ordinary — advisory duties, exclusivity, anything resembling "we'll look out for you" — that has to be written into the agreement. Courts won't read it in from the vibe of a long relationship.

When the Writing Doesn't Say What the Conversation Said

Comp & Soft, Inc. v. AT & T Corp., 252 S.W.3d 189 (Mo. App. 2008), shows the flip side. Here, there was a written contract — it just didn't include everything the parties had talked about.

CSI placed IT consultants with AT&T. Because AT&T's procurement rules required it to contract only with "preferred" vendors, a company called RSI was inserted as an intermediary. AT&T's business manager and CSI's recruiter had directly negotiated rates, benefits, and — informally — the terms under which AT&T could later hire CSI's consultants. None of that made it into the written Subcontract between RSI and CSI. What did make it in was a clause incorporating, by reference, a separate General Agreement between AT&T and RSI — one CSI had never signed.

When AT&T hired a batch of CSI's consultants and a dispute arose over fees, CSI argued it had a direct oral agreement with AT&T based on those early conversations. The court disagreed: "a valid written contract merges all prior and contemporaneous negotiations on the subject." The Subcontract — and the General Agreement it incorporated — was the deal, full stop. The earlier conversations didn't survive.

There's a second wrinkle worth noting: that incorporated General Agreement also let AT&T assign its administrative duties to a third party (which it later did, adding yet another company, ProcureStaff, into the payment chain). CSI was bound by terms in a document it had never negotiated, simply because its own contract pointed to it. If your agreement incorporates someone else's terms "by reference," those terms are part of your deal — whether or not anyone on your side has actually read them.

When "More or Less" Meets a Specific Number

The oldest case in this roundup makes a related point about describing what's being sold. In McGhee v. Bell, 170 Mo. 121, 70 S.W. 493, 59 L.R.A. 761 (Mo. 1902), a seller conveyed land described in the deed as containing "eighty acres, more or less." He'd told the buyers — an elderly, illiterate couple — that the tract held "not less than eighty acres," and "nearer ninety or one hundred." He'd personally walked them around boundaries that included a neighbor's land. His own prior deed to the same property described it as "fifty acres, more or less," and he'd specifically instructed the scrivener to write "eighty" instead. The actual survey came back at 61 acres.

"More or less" language is completely normal — land is often irregular, inventory counts fluctuate, and nobody expects laser precision in every description. But that qualifier doesn't erase a specific representation that turns out to be false. The court allowed the buyers to keep the land and receive a price reduction proportional to the shortfall. If you're making — or receiving — a specific numerical representation about quantity, acreage, square footage, unit count, or capacity, get the actual number into the contract. A vague qualifier elsewhere in the document won't undo a specific promise that didn't hold up.

The throughline: whether it's 1902 or 2008, agriculture or IT staffing, the contracts that survive a dispute are the ones where the actual deal — what's being exchanged, on what terms, with what numbers — lives in the document itself. If your business is still operating off a combination of an old template, a few emails, and "well, that's what we always agreed to," that's worth fixing before it becomes the subject of litigation rather than a quick phone call.

2. Define "Done" With a Bright Line, Not a Ballpark

Once the deal is written down, the next question is: how do both sides know when an obligation has been satisfied? This sounds obvious until you're staring at a contract that defines the trigger in two different ways at once.

Webbe v. Keel, 369 S.W.3d 755 (Mo. App. 2012), is a tidy example. The buyers and sellers entered a contract for deed: a $30,000 sale price, a $3,000 down payment, and the $27,000 balance payable in "144 (one hundred forty-four) months" at $300 per month. The contract said the buyers would get their deed within ten working days after "the last payment is made, number 144."

Ninety months in, the buyers sued for the deed. Their math: 90 payments × $300 = $27,000 — exactly the financed balance. As far as they were concerned, they'd paid what they owed.

The problem is that 90 payments isn't 144 payments, and the contract didn't say "deliver the deed once $27,000 has been paid." It said payment number 144. The buyers argued this was a "genuine issue of material fact" that should go to a jury — that there was a real "difference of opinion" about the purchase price. The court wasn't persuaded: "[d]isputed contract terms are not necessarily ambiguous," and "contract interpretation is a question of law" for a judge, not a factual dispute for a jury. As for the apparent oddity that 144 payments of $300 (plus the down payment) added up to more than the stated $30,000 price, the court pointed out that the time value of money is a "judicially-known concept" — money paid over fourteen years is worth less than the same total paid today, so a financed price exceeding a cash price isn't some hidden ambiguity. It's just how financing works.

What made this case easy to resolve — on summary judgment, without a trial — was that the trigger was an event: payment number 144. Imagine instead the contract had said the deed transfers "once the buyer has paid the purchase price." That phrasing invites exactly the argument the buyers tried to make here, because "purchase price" could plausibly mean the $30,000 sticker price, the $27,000 financed balance, or the $46,200 total of all 144 payments plus the down payment.

This isn't just a real estate issue. Any agreement with installment payments, milestone-based delivery, retainer drawdowns, or staged service engagements should ask the same question: is the trigger for the next obligation — delivery, release of collateral, final invoice, contract termination — defined by a countable event (payment 12 of 12, milestone 3 of 4, the third renewal date) or by a dollar figure that interacts with fees, interest, or partial payments in ways that aren't obvious until someone does the math differently than you expected? The fix is almost always the same: pick the event, name it specifically, and let the dollar amounts be a description rather than the operative trigger.

Illustration: 2. Define "Done" With a Bright Line, Not a Ballpark

3. Build In a Real Default-and-Termination Process

Every contract assumes both sides will perform. Every good contract also answers the question nobody wants to think about at signing: what happens when one side doesn't?

When the Lease Says What Happens Next

Brooks v. Gaffin, 95 S.W. 418, 196 Mo. 351 (Mo. 1906), involved a coal mining lease with conditions that read like a small business's worst nightmare of fine print: the lessee had to mine "in good faith and with all proper expedition," hit specific monthly extraction quotas (16,000 bushels in season, a quarter of that in the off-season, or pay for the shortfall), make monthly settlements by the 20th of each month, and have the mine surveyed twice a year at his own expense.

The lease also had a forfeiture clause: on "nonperformance of or noncompliance with any of the terms or conditions," the lease would forfeit at the lessor's option, and the lessor could "re-enter and take possession of the premises on ten days' written notice." The lessee would then have to "surrender the peaceful and full possession of the premises" without any further notice or demand.

The lessee breached — the court noted it "was not seriously contended" that he hadn't. The lessor served the ten-day notice and, when the lessee didn't leave, sued in ejectment to recover possession. The lessee's position was essentially that ejectment — a lawsuit to physically recover real property — wasn't the right tool for a contract breach, even one with a forfeiture clause.

The Missouri Supreme Court disagreed, and the language it used is worth remembering:

"parties have a legal right to make their own contracts, and, so long as they violate no inflexible rule of law, courts must give effect to them, and cannot relieve either party from the effects and consequences of his own contract."

The right to re-enter, the court held, is a "necessary incident" of a forfeiture condition — it doesn't even need to be separately spelled out, though here it was anyway. Breach the conditions, get the notice, lose the premises.

For any small business that leases space, equipment, or territory — or grants a license with performance minimums attached (minimum throughput, minimum sales volume, minimum royalties) — this case is the blueprint for what a default clause should do. It should say what counts as a default, what notice is required, how long the other side has to fix it (if at all), and exactly what happens next. Courts in Missouri have been enforcing these clauses as written for well over a century. The flip side is equally true: if your lease or license doesn't spell this out, you may be stuck arguing about what remedy you're even entitled to, in addition to whether a breach occurred.

When "For Cause" Gets Tested

Default clauses aren't just a real-estate or commercial-lease concept — they show up in every employment contract that isn't pure at-will, usually as a "termination for cause" provision. Keveney v. Missouri Military Academy, 304 S.W.3d 98 (Mo. 2010), shows both how that clause gets litigated and where its limits are.

Keveney was a teacher under a written contract terminable for cause. He noticed bruises on a student, reported his suspicion of abuse to three supervisors — each of whom had a statutory duty to report it — and was told his job would be in jeopardy if he pushed the issue. He pushed anyway. He was fired the same day.

He sued for breach of contract, and the jury found in his favor, awarding $13,300. The school argued on appeal that he'd failed to perform his contractual duties (the alleged "cause" was disrespect toward his supervisors). But Keveney testified that while the conversation got heated, he wasn't disrespectful — and "[t]he jury is the sole judge of the credibility of witnesses and the weight and value of their testimony." The jury believed him, not the school. That's the first lesson: "for cause" is enforceable, but if the employee disputes the underlying facts, a jury decides who's telling the truth — and a termination letter written after the fact doesn't automatically win.

The bigger development in this case, though, is what the Missouri Supreme Court did with Keveney's separate wrongful discharge claim. Until this case, Missouri's "wrongful discharge in violation of public policy" tort — which lets an employee sue when they're fired for refusing to break the law — had only been available to at-will employees, on the theory that contract employees already had a contract remedy. The Supreme Court extended it to contract employees too, reasoning that "[a] discharge is 'wrongful' because it is based on the employer's attempt to condition employment on the violation of public policy," and that limiting the tort to at-will employees "illogically grants at will employees greater protection." The court was direct about the consequence: an employer in this situation "is liable for two breaches, one in contract and one in tort."

The takeaway for any business with "for cause" termination language: that clause governs your contractual relationship, and courts will let a jury sort out factual disputes about whether cause actually existed. But no termination clause — however broadly worded — provides cover if the real reason for the termination was retaliation for an employee refusing to do something illegal, or insisting that the law (here, mandatory child-abuse reporting) be followed. That exposure exists on top of, not instead of, whatever the contract says.

If your business operates under leases, licenses, or employment agreements that don't clearly walk through "what happens if this goes wrong" — or if you're already facing a dispute where the other side is leaning on (or ignoring) a default clause — it's worth having those provisions reviewed before a disagreement turns into litigation. A short conversation now is a lot cheaper than discovering the gap during a deposition.

4. Make Your Dispute-Resolution Clause Actually Work

Arbitration clauses have a reputation for being interchangeable boilerplate. Village of Cairo v. Bodine Contracting Co., 685 S.W.2d 253 (Mo. App. 1985), is a great illustration of why that reputation is wrong — because in this case, two contracts for the same project had two arbitration clauses that worked completely differently, and neither one did what the trial court initially thought it did.

The Village of Cairo hired Bodine Contracting to build a sewage system, split into two separate contracts: an Interceptor Contract (funded by the EPA) and a Collection Contract (funded by the Farmers Home Administration). Because each federal agency supplied its own boilerplate, the two contracts — for one continuous, intermingled construction project — ended up with arbitration clauses that pointed in opposite directions.

The Broad Clause That Almost Got Read Narrowly

The Interceptor Contract's arbitration clause covered "[a]ll claims, disputes and other matters in question arising out of, or relating to, the contract documents or the breach thereof." A separate provision said the contractor "will carry on the work and maintain the progress schedule during any arbitration proceedings."

When payment disputes led Bodine to stop work and both sides claimed the right to terminate, Bodine demanded arbitration. The trial court read the "carry on the work" language as a condition precedent to arbitration — since Bodine had stopped working, it had supposedly forfeited its right to arbitrate at all.

The court of appeals reversed. That provision, it held, wasn't a gatekeeper for the arbitration clause — it was a separate promise about how performance would continue during an arbitration that was already proceeding, covering work that wasn't in dispute. The right to arbitrate "all claims" was unconditional. Even if stopping work had been an unjustified breach, that would just be one more claim for the arbitrator to decide — not a forfeiture of the arbitration clause itself. As the court put it, only "[o]ne who flatly repudiates the provision for arbitration itself" loses the right to insist on it; an ordinary breach of the broader contract doesn't do that.

The Narrow Clause That Nearly Swallowed Itself

The Collection Contract took the opposite approach. Its clause said "[d]isputes on matters not governed by the contract documents... shall be arbitrated." The trial court reasoned — not unreasonably — that in a construction dispute, almost everything relates back to the contract documents in some way. Delay claims, change orders, defective specifications: all of it touches the documents. So under a literal reading, almost nothing was arbitrable.

The court of appeals called this out for what it was: a clause that announces an intention to arbitrate, then defines "arbitrable" so narrowly that it covers almost nothing — rendering the clause "virtually meaningless." That's not a narrow-but-valid scope; it's an internal contradiction, which is to say, an ambiguity. And ambiguous contract language gets construed against the party that drafted or supplied it — here, against Cairo, which had adopted and tendered the contract documents even though a federal agency had originally written the language. The court resolved the ambiguity in favor of arbitration, noting that the two contracts covered one continuous project where "the same act or omission... may amount to a breach of both contracts" and "the same evidence bears as proof on both" — meaning a split result (arbitration for one contract, litigation for the other, on overlapping facts) risked "contradictory results."

What This Means If You Have More Than One Agreement

Most small businesses don't draft their own arbitration language from scratch — it comes from whatever template, vendor form, or industry-standard document is in front of them. Village of Cairo shows three things worth checking. First, if your business operates under multiple related agreements covering one relationship or project — a master agreement plus statements of work, a prime contract plus subcontracts — check whether their dispute-resolution clauses actually match. Mismatched clauses on a single project can leave you litigating one piece of a dispute while arbitrating another. Second, broad "arising out of or relating to... or the breach thereof" language is far more predictable than a narrow carve-out, because narrow exclusions have a way of accidentally consuming the whole clause. Third, if you genuinely want a condition on the right to arbitrate — "you must complete an informal escalation process first," for example — say so explicitly, as a condition. Don't bury it inside an unrelated performance promise and hope a court reads it the way you intended. Here, even agencies of the federal government didn't get this right on the first pass.

5. Put a Price on Late Payment

Of all seven clauses on this list, this might be the one with the most direct dollar impact — and it's often a single sentence.

Penzel Constr. Co. v. Jackson R-2 Sch. Dist., 635 S.W.3d 109 (Mo. App. 2021), grew out of a renovation project at Jackson High School that went badly over budget and behind schedule, allegedly because the District's plans were defective. After years of litigation (this was the second trip to the court of appeals), a jury awarded Penzel $800,000 for breach of contract.

That $800,000 was just the starting point. The Prime Contract included a short clause — Section 7.2, echoed in Section 13.6.1 of the General Conditions — stating that "[p]ayments due and unpaid under the Contract shall bear interest from the date payment is due at the legal rate prevailing from time to time at the place where the Project is located." Both sides agreed that "the legal rate prevailing" worked out to 9% per year under Missouri's general prejudgment interest statute.

The District tried several ways to avoid this. It argued the claim wasn't "liquidated" — a prerequisite for prejudgment interest — because Penzel's damages were calculated using the "Modified Total Cost Method," an approach that relies on estimates. The court rejected that comparison: unlike speculative lost-profits claims, the MTCM measures actual costs already incurred, using "a recognized standard... readily ascertainable by computation," which is exactly what "liquidated" means. The District also argued that a separate statute — Missouri's "prompt payment" law for government contracts, which imposes its own penalty interest of 1.5% per month (18% annually) for bad-faith nonpayment — should somehow displace the contractual interest rate. The court didn't even need to resolve that question, because the 9% rate was due under the contract, independent of any statute.

And Penzel didn't have to choose. The court also upheld a separate award of prompt-payment penalty interest under section 34.057, on top of the contractual 9%. To get there, Penzel needed the jury to find that its written demand — an itemized letter listing categories of damages, hours, and rates — counted as an "invoice." The District argued the letter was really just an invitation to negotiate. The court disagreed, noting that an invoice is simply "an itemized list of goods or services... usu. specifying the price and terms of sale," and that prompt-payment statutes are remedial and should be read generously in the contractor's favor.

Add it up: an $800,000 verdict, plus roughly 9% annual interest under the contract, plus roughly 18% annual penalty interest under the prompt-pay statute, plus over $630,000 in attorney's fees — all compounding from a payment due date in 2010, in a case decided in 2021. Eleven years of interest on two separate tracks, triggered substantially by one boilerplate sentence about "the legal rate prevailing."

For a small business — whether you're the one extending payment terms or the one waiting to get paid — the presence or absence of an interest-on-late-payment clause is rarely the headline issue at signing. But if a payment dispute drags on (and they often do), that clause is the difference between "we eventually got paid the amount we were owed" and "we got paid that amount plus a meaningful penalty for every month it took." If your business does work for a government entity in particular, it's also worth understanding what your invoices need to look like — itemized, with prices and terms — to qualify for prompt-payment protections under statutes like section 34.057.

6. Set — and Defend — Your Notice Deadlines

"You must report any problem within X days, in writing, or you lose the right to raise it." Versions of this clause show up everywhere — construction contracts, service agreements, supply contracts, SaaS terms. They're meant to keep small disputes from festering for years and then ambushing the other side. Penzel — the same case from Section 5 — shows both why these clauses matter and how easily they can be lost, not in the negotiation, but in the litigation.

The Jackson R-2 contract's General Conditions, Section 4.3.2, required that "[c]laims by either party must be initiated within 21 days after occurrence of the event giving rise to such Claim or within 21 days after the claimant first recognizes the condition giving rise to the Claim, whichever is later," by written notice. This is a textbook "use it or lose it" provision.

Here's where it gets interesting. In its petition, Penzel made the standard general averment that "all conditions precedent had been satisfied" — which Missouri's rules specifically allow a plaintiff to do without itemizing each one. The District's answer responded with a general denial. But the same rule that lets a plaintiff plead generally requires a defendant's denial to be specific: "[a] denial of performance or occurrence shall be made specifically and with particularity." Because the District's denial wasn't specific, the court held the District had effectively admitted that Penzel satisfied every condition precedent — including the 21-day notice requirement, and separately, the architect's-certificate requirements that triggered final payment.

The District tried a second route: pleading, as an affirmative defense, that "Penzel failed to perform its obligations under the contract" and that Penzel's claims were "barred by [Penzel's]... failure to perform conditions precedent." The court rejected this too, for a similar reason — these were "mere conclusions lacking any nexus to a particular fact." An affirmative defense has to identify the specific facts that support it; "[b]are legal assertions are insufficient." The District never said, in its pleadings, anything about the 21-day notice requirement specifically — so even though it tried to raise the issue at trial, by then it was too late.

The 21-day clause was real. It may well have been factually relevant. But procedurally, it never got a fair hearing, because the District's pleadings weren't drafted with anything like the precision of the clause it was trying to enforce.

This cuts both ways for a small business. If your contracts include notice-of-claim deadlines — and they should, if you want a way to cut off stale complaints — understand that enforcing them later requires more than saying "they didn't follow our process." When a dispute lands in litigation, you (or your attorney) need to plead the specific facts: what the deadline was, what notice you did or didn't receive, and when. A generic denial or a boilerplate affirmative defense may functionally waive the very protection the clause was supposed to give you. And if you're on the other side — the one who might be accused of missing a deadline — keep records that look like Penzel's letter: dated, itemized, in writing, sent to the right person. A clause is only as useful as the paper trail (and the pleading) that backs it up.

7. Don't Let "We Can Change This" Undo Everything Else

The last clause on this list might be the most counterintuitive, because it's usually drafted to protect the business that writes it — and it can backfire so badly that it takes the rest of the agreement down with it.

Baker v. Bristol Care, Inc., 450 S.W.3d 770 (Mo. 2014), is a Missouri Supreme Court decision, decided 4–3, and the split itself tells you how close this issue can be.

Carla Baker was promoted from an hourly position to a salaried Administrator role at a long-term care facility. As part of the promotion, she signed two documents at once: an employment agreement (indefinite term, with specific limits on how Bristol could terminate her) and a separate arbitration agreement. The arbitration agreement was, on its face, mutual — both Baker and Bristol promised to arbitrate claims against each other, using AAA rules, with Bristol covering most of the costs. It also included one more sentence: Bristol "reserves the right to amend, modify or revoke this agreement upon thirty (30) days' prior written notice to the Employee."

When Baker later filed a class action over unpaid overtime, Bristol moved to compel arbitration. The trial court said no. The Missouri Supreme Court agreed — and the reasoning is worth understanding in detail, because it's not really about arbitration. It's about what a "promise" actually is.

The majority's logic: Bristol's mutual promise to arbitrate looked like real consideration — both sides giving something up. But the 30-day amendment clause didn't say amendments would apply only prospectively, and it didn't say amendments wouldn't affect disputes that were already pending. Read literally, Bristol could give 30 days' notice that, effective in a month, it was no longer bound by the arbitration framework — even as to a dispute already in arbitration. If a party can escape its own promise at will, that promise is "illusory," and "adding several illusory promises equals an illusory promise." Because Bristol's arbitration commitment was illusory, and continued at-will employment doesn't supply consideration on its own (a point covered in Missouri's broader line of arbitration-consideration cases), there was no enforceable arbitration agreement at all. Baker's overtime case proceeded in court.

The dissent makes the contrast even sharper. Judge Wilson walked through an extensive list of mutual promises Baker and Bristol had actually exchanged — the promotion itself, a raise, free housing, confidentiality and non-solicitation commitments from Baker, and a long list of arbitration-related commitments from Bristol, including fee-shifting and confidentiality of the arbitration process. He argued the 30-day clause should be read as prospective-only, because that's the only reading that makes the whole bargain make sense — and because the parties' own agreement said a court could "modify it to render it enforceable" if needed. He even pointed to a contrasting case, Pierce v. Kellogg, Brown & Root, where an arbitration agreement explicitly stated that amendments wouldn't apply "to disputes... for which a proceeding has been initiated" — and that language was enough to save the agreement.

The majority didn't adopt that reading. Three justices agreed with the dissent; four did not. That's the lesson in miniature: even when there's a strong, good-faith argument for reading an ambiguous modification clause sensibly, you may not get four votes for it.

For any small business with a document that reserves the right to change the rules later — an employee handbook, a customer terms-of-service agreement, a vendor master agreement, a subscription contract, a dispute-resolution policy — Baker points to two specific things that clause needs to say, in plain language: changes apply going forward only, from the date of the change, and changes do not apply to claims, disputes, or proceedings that already exist at the time of the change. Leave either one out, and you're not just risking that one provision. You may be handing a court — or, in a close case, a dissenting opinion — the argument that the entire agreement was never binding in the first place.

Illustration: 7. Don't Let "We Can Change This" Undo Everything Else

Pulling It Together

None of these seven clauses are exotic. A definitions section. A payment trigger. A default-and-termination provision. A dispute-resolution clause. An interest rate. A notice deadline. A modification clause. Every one of them shows up, in some form, in templates that get reused across hundreds of small business agreements without a second thought.

And every one of them, in the cases above, was the entire ballgame — for a family farm, a coal lease, a school construction project, an IT staffing arrangement, a teacher's job, and a healthcare company's entire workforce arbitration program.

If it's been a while since your standard contracts, leases, employee handbooks, or vendor agreements were actually reviewed against questions like these, that review is a lot less expensive before a dispute than during one. Our attorneys regularly help small businesses go through exactly this kind of checkup — not to rewrite everything from scratch, but to find the one or two sentences that, ten years from now, might be the only thing anyone's arguing about. If that sounds like something your business could use, reach out and let's take a look together.

This article is for informational purposes only and does not constitute legal advice. For advice specific to your situation, please consult a qualified attorney.