Short notes for operations people who think contracts are legal’s problem. They are not. Half the arguments you will have with a client in year two are already decided in two documents signed in year zero, and you will be the person living with the result. This is general information, not legal advice; your lawyers have the last word on wording.
Two documents, two jobs
The Master Services Agreement (MSA) is the umbrella. It sets the terms that apply to everything the two companies do together: confidentiality, data protection, intellectual property, liability limits, indemnities, insurance, audit rights, termination, dispute resolution and governing law. It is negotiated once, often over months, and rarely read again until something goes wrong.
The Statement of Work (SOW) hangs under the MSA and describes one specific piece of work: what is being done, where, for how many people or transactions, to what standard, for what price, from which date. A client can have one MSA with you and ten SOWs, one per process or site. Each SOW inherits the MSA’s terms unless it says otherwise, and a well-drafted MSA says which document wins in a conflict. Find that clause. It matters more than it looks.
Opinion: the SOW is the document an ops head should know line by line. The MSA is the one you should know by outline.
What lives in a SOW
- Scope. Which activities are in, which are out. Silence is read against the vendor, because the client will assume it is included.
- Volumes and assumptions. Expected contacts per month, working hours, languages, channels, tools, who provides what. If your price assumed 50,000 contacts and the client sends 65,000, the assumptions section is your only defence.
- Service levels. The metrics, how each is calculated, the measurement window, the data source, and which exclusions apply (client system downtime, force majeure, unannounced campaigns).
- Commercials. Pricing model (per FTE, per transaction, per resolved case, blended), rate card, minimum commitment, volume bands, annual escalation, payment terms.
- Governance. Who attends weekly and monthly reviews, how escalations work, who can approve changes.
- Change control. How a request that is outside scope is priced and accepted.
- Transition and exit. What happens at start and at end, including who owns documentation and how the knowledge comes back out.
SLA credits, worked through
This is where contracts touch your month-end. Many agreements put a share of monthly fees “at risk” against service levels. Say the monthly fee is ₹3 crore and 10% is at risk. Maximum exposure is ₹30 lakh a month. The SOW might split that across three metrics, each carrying ₹10 lakh. If you miss service level in a month, you lose that metric’s credit, perhaps in steps: a small miss costs a quarter of it, a big miss costs all of it. Some contracts add earn-back, where a good following month recovers some of the credit. Some cap total credits per year. Some include a bonus side for exceeding targets.
Two blunt lessons. One: measure exactly as the contract measures, not as your own dashboard does. Service level with or without short abandons, calculated daily or monthly, on offered or on answered calls; these definitions change the number. Two: when the credit is big, the temptation to massage reporting is big. Do not. Misreporting turns a commercial problem into a trust and legal problem, and it is the sort of thing that ends contracts.
Clauses that surprise people
Termination for convenience. Can the client leave without cause, and with how much notice? Can you? A one-sided right changes how much to invest in the account.
Minimum commitment. If the client promises nothing and you hire 200 people for them, your risk is large. Look for a minimum volume, a ramp-down notice, or a clause covering stranded costs such as hiring and training costs not yet recovered.
Liability cap. Often tied to fees paid in some period, such as twelve months. Some items, like breach of confidentiality or data protection, may be carved out of the cap. Check what is carved out, because a data incident can exceed a year’s margin by a wide stretch.
Audit and subcontracting. Clients usually reserve audit rights and restrict passing work to a third party without consent. If you plan to use another site or a partner, read this before, not after.
Penalty wording. In India, courts look at whether a stated sum for breach is a reasonable pre-estimate of loss. Section 74 of the Indian Contract Act, 1872, deals with this, and the result is generally that the claimant receives reasonable compensation not exceeding the amount named. How it applies to a particular SLA credit scheme is a legal question. Do not assume either that credits are always enforceable as written or that they are unenforceable.
Scope creep and the change request
A client’s operations manager asks for “one more report”, then “a small weekend pilot”, then “just add the Gujarati queue”. Each seems trivial. Together they are another team’s worth of work, unbilled. The fix is dull and effective: say yes to the need, send a written change request describing the work and price, and wait for approval before starting. The commercial discipline is not rudeness. It is what lets you keep saying yes.
Finally, read the SOW when it is signed, not when it is disputed, and hold a short kick-off for team leaders so they know which metrics carry money. Operations teams that know their contract run better accounts, and they negotiate renewals from facts, not from memory.
Figures and names in the examples are illustrative.
Leave a Reply