How to Review a No-Oral-Modification and Signed Variation Path

Finance is about to book a Slack “yes” as the new fee. The heading says no oral modification. The sentence only says “in writing.” There is no signature and no named role. The 25-minute job is to split writing from signature, name who may sign a change, and refuse to treat chat as the order form.

In September 2026, Sable — Ops at a 21-person UK SaaS — has Finance’s yes on a £4,400-a-month workflow-analytics vendor. Clause 16.2 says variation must be “in writing.” No “signed.” No named role. The AE Slack: “Yes — extra workspace at the same per-seat price.” Finance booked that number. The invoice is list. Legal said the NOM heading is a lock. Sable has Friday.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

Why does “in writing” alone leave a hole?

A heading is not a path. Circle the variation sentence and write two blanks: writing, and signed. If the paper only says “in writing,” write “signature silent.” Do not treat “No oral modification” as the lock Legal promised Sable.

Freeze the packet — the exact file set that will be signed: MSA — the master services agreement —, order form, any change-control schedule. Then read the words after the heading. Rock Advertising [2018] UKSC 24 is still the England-and-Wales structure in 2026: clause 7.6 required writing and a signature. An oral payment deal a judge found as a fact still failed those formalities.

Sable’s clause 16.2 stops at “in writing.” Walker Morris on Integral Petroleum [2022] EWHC 659 (Comm) is the warning: “may be amended… in writing” was ambiguous and blocked summary judgment. Do write “signed: silent.” Do not let the heading close the hunt.

How do you name who may sign a change?

Name a role who may sign a change, not any account manager. Circle “authorised representatives,” a title, or a spend threshold. If none of those words exist, write “role: none.” Rock’s oral conversation was with a credit controller. That is why a named variation role belongs here.

Lord Sumption’s third reason for a NOM clause is so a company can police who agrees a change — see the English-law definition note. HCR colour: name who may approve and at what seniority. Do write the role or “role: none.” Do not treat the AE’s Slack “yes” as the deal. If the fight is whether this person can bind the Ltd at all, that is who can sign a contract for the company — a different hunt.

What does a silent email box mean on Friday?

Name email and e-sign, or accept a fight. Write three boxes: email in / out / silent; e-sign in / out / silent; chat or Slack named or not. Silent is not a rule. Silent is the Friday dispute when the list invoice arrives.

In practice, “in writing and signed” can be an email exchange signed on behalf of both parties if the clause does not insist on manuscript ink or the same document — the Buckles note on the Enterprise / C&S emails. If you want to stop email variations, say so. Slack is still unnamed on Sable’s paper.

The Law Commission 2019 statement is structure only: an electronic signature can execute a document if the person intends to authenticate and the contract’s formalities are met. Do mark e-sign in, out, or silent. Do not assume DocuSign “will do” because the heading looks strict.

Why does last quarter’s Slack habit not rewrite the deal?

Course of dealing will not quietly rewrite the deal. Write that on the log. Sable’s “we always agree extras in Slack” is a habit, not a new order form. Do not treat last quarter’s chat as the price Finance already booked.

In GSY Hospitality [2025] EWHC 3231 (TCC) an expert treated informal no-challenge conduct as an £800k cap variation. Failing to apply the NOM and Rock Advertising was an error of law. HFW (10 February 2026) repeats the line: do not assume informal discussions or conduct will vary the contract. Land formalities in that SPA are other paper.

Estoppel stays narrow. Jones Day on Rock Advertising restates the limit: estoppel cannot destroy the certainty the clause was bought for. Do not mark Sable’s thread estoppel-in or out. A posted or click-accept policy update bypasses signed writing — a different hunt.

How do you put price and scope on a change-control form?

Refuse to pay list-versus-Slack as if a form already existed. A change-control form is a one-page order: what changes, impact on fees, timeline, and spec, signed by the named roles before work or invoice. For example, Sable’s “same per-seat price” against a list invoice is what that form was meant to catch.

HCR colour: signed change order before the change takes effect. Sprintlaw (12 November 2025): if the contract sets a written process, a casual “we’ll do that” probably will not cut it. A variation still needs consideration or a deed (Blake Morgan). Do attach the form. Do not let Finance pay as if Slack rewrote the order form. A pitch deck that might survive an entire-agreement box is a different hunt.

When to keep, tighten, or train the team?

Keep only when the path is complete: writing and signed, named variation role, email and e-sign named in or out, course-of-dealing hole closed, change-control form for price and scope, and the team told Slack is not the path. Anything less is tighten or train — not a green light on this paper.

Workflow: writing + signature → named variation role → email/e-sign named → course of dealing will not rewrite → change-control form for price/scope → keep / tighten / train. Tighten means add “signed,” name the role and channels, and attach a one-page form. Train even a Rock-grade NOM if Finance already booked Slack as the price.

Success bar: Verify the one-page log before Finance books Slack as the fee. “We have a NOM” is not that sentence on Sable’s paper. Counsel — a qualified lawyer, not the chatbot — still owns a silent signature or a payment that treats chat as the order form.