In the MSA
Confidentiality, IP, liability, indemnity, insurance, payment terms, term and termination, notice periods, audit rights, governing law.
MSA vs SOW: the standing terms and the specific engagement.
One agreement sets the rules that apply to every project. Each statement of work sets what is being built, by when, for how much, and what acceptance means.
Reloren is in development. It is not yet available to buy or sign up for. The workflow described here is what we are building. Tell us what you need.
EXECUTION RECORDHUMAN REVIEWED
SOURCE§ 4.2 · Executed agreement
“Provider shall deliver the agreed work and preserve evidence of completion.”
source-linked
OWNERServices operations, delivery, and finance teams
PROOFAttached
CLIENTDecision tracked
VALUEEvent ready
The signed language is only useful when the operating team can act on it.
A master service agreement carries the terms that should not be renegotiated for every project: confidentiality, intellectual property ownership, liability caps and exclusions, indemnity, insurance, payment terms, term and termination, notice, dispute resolution and governing law. It typically contains no scope and no fees, and on its own it usually obliges neither party to do any work.
A statement of work carries the engagement: deliverables, milestones, dates, assumptions, client dependencies, acceptance criteria, personnel, rates and fees. It incorporates the master agreement by reference, and its commercial life is independent. A SOW can complete or expire while the MSA continues, and a firm normally runs many SOWs under one MSA.
Which document is the home for each obligation
The division matters operationally because the two documents create different kinds of duty. The MSA creates standing duties that persist across every engagement, are often open-ended in time, and frequently have no natural owner in the delivery team. The SOW creates dated, scoped duties that a project manager can see and plan around.
Standing duties are the ones that get missed. An annual insurance certificate, a quarterly governance meeting, a security questionnaire response window, a notice of a subcontractor change and a data deletion duty on termination all sit in the MSA, all bind the firm, and none of them appear on a project plan built from the SOW.
In the SOW
Deliverables, milestones, dates, assumptions, client dependencies, acceptance criteria, staffing, rates and fees.
Contested
Renewal mechanics, service levels and change control appear in either. Check which one your template puts them in before assuming.
The order of precedence clause decides conflicts
When the MSA says invoices are payable in 45 days and the SOW says 30, the outcome is set by the order of precedence clause, not by which document is newer. Many MSAs put themselves first, so a favorable term negotiated into a SOW is quietly overridden. Others give the SOW precedence but only for a listed set of subjects such as scope, fees and schedule.
Read that clause before signing a SOW with non-standard commercial terms, and read it again when a change document conflicts with either. It is a short clause and it silently determines the answer to most contract questions that arise during delivery.
MSA-first
The SOW cannot vary standing terms unless it expressly says it is amending the MSA for that engagement.
SOW-first, limited
The SOW controls only on named subjects. Anything outside the list falls back to the MSA.
Silent
If no precedence clause exists, the conflict is a genuine ambiguity. Resolve it with an amendment rather than a shared assumption.
Two documents, two expiry clocks
The MSA and the SOW usually expire on different schedules, and the interaction produces two recurring problems. A SOW that runs past the MSA's expiration can leave active work with no governing terms. An MSA that auto-renews while every SOW under it has completed keeps a relationship, a notice obligation and often an insurance obligation alive that nobody is watching.
Survival clauses complicate it further. Confidentiality, IP assignment, indemnity, record retention and audit rights commonly survive termination of the MSA for a stated period, so obligations continue after the last SOW closes. Those surviving duties need an owner in the record just as much as the delivery work does.
Running both documents as one execution record
The operating requirement is a single view of what the firm owes this client, assembled from the MSA, every active SOW and every amendment, with each duty still pointing at the language that created it. A team that tracks only the SOW misses the standing duties. A team that tracks only the MSA has no delivery record at all.
Reloren is being built for exactly that: the MSA, its SOWs, order forms and amendments held as a linked set of versions, with each obligation keeping the document, page, clause and excerpt it came from, so delivery, acceptance, evidence and value events hang off the specific language rather than off a retyped summary of scope. It is not available yet. Until then, the cheapest version of this is one shared sheet that lists the standing MSA duties alongside the dated SOW ones, because the standing duties are the ones that go missing.
One portfolio view
Open, overdue, unowned and conditional obligations across both document types in one place.
Source stays attached
Every obligation keeps the document version, page, clause label and exact excerpt it came from.
Standing duties get owners
MSA obligations with no project home still receive an owner, a date or a triggering condition, and an evidence requirement.
From executed source to a defensible outcome.
The sequence stays visible even when the surrounding systems and team responsibilities differ.
Import the executed source
Add the signed MSA, SOW, order form, amendment, or email agreement. Reloren accepts PDF, DOCX, TXT, Markdown, and EML files up to 25 MB and retains the original as an encrypted contract version.
Review source-linked candidates
Local text extraction proposes obligation candidates with the document, estimated page, clause label, exact excerpt, and confidence. A person approves or rejects every candidate before it becomes active work.
Make the obligation executable
Assign an owner, due date or triggering condition, evidence requirement, acceptance requirement, and billable value. The operating record stays linked to the language that created it.
Record proof and client state
Attach project artifacts, email, URLs, files, notes, or client confirmation. Record whether the client decision is pending, accepted, disputed, rejected, or waived without rewriting earlier events.
Connect execution to value
Record billable, milestone, rate-change, renewal, credit, penalty, or recovered-value events. Export obligations, audit history, and commercial records for the systems that remain responsible for invoicing and accounting.
What to check across the MSA and SOW pair.
Most execution failures in a services relationship come from an obligation nobody could tell you the home document for.
The precedence clause
Know which document wins on a conflict, and whether that is limited to named subjects.
Both expiry dates
Record the MSA term and each SOW term separately, including any auto-renewal and its notice window.
The survival list
List which MSA clauses continue after termination and for how long, and give each surviving duty an owner.
The standing obligations
Insurance certificates, governance meetings, reporting cadences and audit responses rarely appear on a project plan and are the usual source of a breach nobody intended.
Change control
Confirm whether scope changes go through a change order, a SOW amendment or a new SOW, and who is authorized to sign one.
Know what this workflow does, and what remains elsewhere.
Reloren is in development and is not yet available to buy or sign up for; the scope below is what it is being built to do, and what it is deliberately not. Reloren is seller-side, post-signature contract execution software. It does not draft, redline, negotiate, sign, or provide legal advice. It does not score legal risk, manage buyer-side procurement, replace CRM, project management, PSA, ERP, or accounting systems, or issue invoices autonomously. Candidate extraction requires human review. Optional integrations are brokered through Composio; the core workflow works without them.
Questions people ask about MSAs and SOWs.
What is the difference between an MSA and a SOW?+
The master service agreement holds the standing legal and commercial terms that apply to the whole relationship. The statement of work holds the specific engagement: deliverables, dates, acceptance, staffing and fees. One MSA normally governs many SOWs.
Can you have a SOW without an MSA?+
Yes, but then the SOW has to carry the standing terms itself, including liability, IP, confidentiality and termination. A standalone SOW that omits them leaves those questions unanswered.
Which controls if the MSA and SOW conflict?+
The order of precedence clause decides. Many MSAs place themselves first, which means a term negotiated into the SOW does not take effect unless the SOW expressly amends the MSA for that engagement.
Does signing an MSA commit either party to work?+
Usually not. Most MSAs are framework agreements that create no obligation to buy or perform until a statement of work or order form is executed under them. Read the specific agreement, because some include minimum commitments.
What happens when the SOW outlasts the MSA?+
Active work can be left without governing terms. The usual fixes are an MSA extension, a survival provision covering SOWs in flight, or a clause stating the MSA continues for as long as any SOW remains open.
Where do renewals and service levels belong?+
Either document, depending on the template. Renewal mechanics and notice periods are commonly in the MSA, while service levels and credits are commonly in the SOW or a schedule. Check yours rather than assuming.
How should both be tracked after signature?+
As one linked set. The obligations that create risk come from both documents, so the record needs the MSA's standing duties and each SOW's dated deliverables in one view, each still pointing at its source clause.
Are your MSA duties and your SOW duties in one place?
Reloren is in development. If the standing obligations in your master agreement have no owner, tell us how that shows up.