How to Review a Change-Control Procedure in an MSA and SOW

Clem, Ops at a 25-person UK product studio, is about to treat “we have a change-control schedule” as a lock. Finance missed the hidden risk. Knowing how to review a change-control procedure in an msa and sow is a 25-minute hunt: name who may raise and who may approve, write an IA clock, refuse Slack-start extra work, then add a named emergency lane or walk Friday.

September 2026. English law; exclusive courts of England and Wales. The packet — the exact file set that will be signed — is the vendor implementation SOW for a customer-facing portal rebuild, plus the MSA (master services agreement — the frame contract vendors hang order forms on) and Schedule 8, an exhibit — attached schedule or appendix — headed “Change Control.” 8.1: “Either party may raise a Change Request.” 8.2: good-faith discuss. No named Change Manager. No days.

8.4: “Customer may instruct Supplier to proceed immediately where Customer reasonably considers the change urgent.” The AE already wrote in #portal-rebuild: “Just start the extra SSO work — we’ll paper the change order Monday.” Last quarter a Slack dashboard extra arrived as an £18k invoice with no signed CO. Friday is booked.

A change-control heading does not stop extra work — and “as soon as reasonably possible” is not X days. MC Law (updated 15 August 2026): written CR → IA on scope, schedule, and price → both sides sign → no work until the CO is signed. Step 4 fails. Crown Call-Off Schedule 5 colour: Emergency Change then a Change Authorisation Note “as soon as reasonably possible.” Not X days.

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

Who may raise a change request — named roles, not “the parties”?

Circle Schedule 8.1. “Either party may raise a Change Request” names no role. Any AE, junior engineer, or Slack handle looks like the requester. Log a named raiser and a named approver on each side, or write “roles: none — fail.”

Do: name the people on this SOW and point back to the MSA process. Don’t: treat “the parties” as a role. ContractHQ: name who can sign COs; do not invent a second process. Chaindoc colour: a PM without contracting authority who “approves” is a fight. Stay on the CR workflow.

What does the impact-assessment clock cover?

Circle “discuss in good faith.” That is not a clock. An impact assessment (IA) is the written estimate of what the change does to scope, price, and date — plus who pays to write it. Log the days, the four contents, and who pays — or “clock: silent.”

Do: write a stated number of business days covering scope, price, date, and who pays the estimate. Don’t: leave “we’ll discuss.” For example, Crown colour — not this studio’s statute — uses 10 Working Days, and a Buyer-issued CR first gets a cost-of-preparing estimate. Omnivoo market band: 5–10 business days. TfL EOps Schedule 9 colour: supplier-proposed IA at supplier cost. Write the rule. In practice, a silent paper lets last quarter’s “assessment” arrive as a bill.

Is Slack or email a change order if work already started?

Extra SSO is already in flight. A change order (CO) is the signed instrument that modifies this SOW’s scope, price, or date. Slack in #portal-rebuild is not that form unless the procedure names the form and the role. Log “no work until signed” present or absent.

Do: refuse Slack-start; name the form; write unsigned work shall not be invoiced. Don’t: treat “paper it Monday” as a CO. ReviewMyContract (21 March 2026) colour: if the MSA requires a signed CO, an unsigned email may not create a pay obligation. Colour, not a verdict that last quarter’s Slack bound anyone. JD Woods: a CO modifies the SOW, not the MSA. Typical mistake: start now, paper later.

What does a usable emergency change path need?

Circle “Customer may instruct Supplier to proceed immediately.” That is a bypass with no named person and no paper-back clock. Log a named approver, written confirmation, and papered in X days — or treat it as a redline.

Do: name two individuals; require written confirmation (named email or e-sign, not Slack); then a formal CO in a stated number of days. Don’t: accept “as soon as reasonably possible” as a clock. TfL colour — a buyer ask, not a statute — wants an emergency IA in 2 Working Days and a CAN in 3. A studio ask is 5 business days. Fence: ITIL emergency / ECAB is operations change enablement, not a signed CO on Schedule 8.

Is this the signed-NOM lock or a whole-SOW tour?

Stay on the procedure. If the fight is whether Slack varied the MSA — writing plus signature, named variation role — that is a different hunt. If the fight is the whole SOW wrapper — deliverables, acceptance, exclusions, payment triggers — that is a different hunt. This page is the CR workflow.

Do: one sentence each, then come back. Don’t: spend Friday on a signed-writing walk or a six-checkpoint SOW tour. Signed-NOM: how to review a no-oral-modification clause. Whole-SOW tour: statement of work review checklist. A CO that edits MSA-level terms is an amendment, not this hunt.

When to tighten, add an emergency lane, or walk?

Tighten means named raiser and named approver on this SOW, IA days for scope, price, and date, who pays written down, and no work until both sides sign. Add emergency lane means a named person, written confirmation, and papered in X days. Walk Friday if “the parties” plus good-faith plus Slack-start plus proceed-immediately remain as a package.

Success bar: a one-page log plus one Friday pause sentence. Workflow: named roles → IA clock (scope / price / date / who pays) → no work until signed CO → emergency named + written + X days → not B55 / not B16 → tighten / add emergency / walk. Optional: upload the same file to document analysis for a first-pass — first machine pass extracting clauses before a human reads every page. A human still opens Schedule 8. Verify every High flag — an item scored high severity a named human still opens. Escalate to counsel — a qualified lawyer, not the chatbot.