How to Structure a Technology Service Agreement
The most important page of a technology service agreement is usually the one nobody reads, and it is not the price. It is the page that explains what happens when the relationship ends. Almost every owner signs these documents while things are going well, and almost every dispute happens when they are not. A contract is a plan for the bad day, written on a good day.
This guide is for an owner or manager who has been handed a master services agreement, usually called an MSA, and needs to understand what each part is doing. It explains how a well-built agreement is organized, what each section should say in plain terms, what to ask the provider, and where the real risks sit.
One thing before anything else. This is general education and it is not legal advice. Contract terms and what a court will enforce depend on the jurisdiction, on the facts, and on the exact wording. Have a licensed attorney review any agreement before you sign it, particularly the sections on liability, data, and termination. What follows will make that conversation cheaper and faster, because you will know which questions matter.
The agreement is usually several documents, not one
Before reading any clause, find out how many documents you are actually signing. Most technology relationships are built in layers.
| Document | What it holds | How often it changes |
|---|---|---|
| Master services agreement | The durable legal terms such as liability, confidentiality, data, termination, and payment mechanics | Rarely |
| Service schedule or statement of work | What is being delivered, for whom, by when, with what service levels and fees | With each engagement |
| Order form or work order | Quantities, dates, and prices for a specific purchase | Often |
| Policies incorporated by reference | Security policy, acceptable use, data processing terms, support policy | Whenever the provider updates them |
The last row deserves attention. If the agreement says the provider's policies apply "as updated from time to time," then a document you never signed can change your obligations. Ask for the version in force on the date you sign, and ask how changes are announced and whether you can object.
Also find the order of precedence clause. When the MSA and a schedule disagree, one of them wins. It is normal for the specific schedule to win on commercial details and for the MSA to win on legal ones, but you should know which rule your document uses.
Scope, the section that decides most disputes
Most arguments about technology services are really arguments about scope. The owner thought a thing was included, and the provider thought it was extra. A good scope section removes that ambiguity by being specific in three directions.
What is included. List the systems, users, locations, and activities covered. "Support for the office network" is vague. "Monitoring, patching, and incident response for the firewall, two access points, and the switch at the Humacao office" is a scope.
What is excluded. Name the things you might reasonably assume are covered and are not. Hardware replacement, projects, after-hours work, training, third-party software support, and data recovery from systems the provider did not set up are common examples.
How changes are made. Scope will change. A good agreement has a written change process, with an estimate before work starts and a signature or approval from someone on your side. Be wary of any clause that lets the provider add chargeable work on its own authority.
Assumptions and dependencies
Good schedules state what the provider assumes about your environment. For example, that you have a supported operating system, that you will give timely access, and that a named person on your team can approve decisions. These are fair. They also tell you what you owe. If the provider's timeline depends on you supplying data by a certain date, find that clause now, not when the project is late.
Service levels, and how to read the numbers
A service level agreement, often called an SLA, is a measurable promise. The most common promises are about availability, response time, and resolution time. They are easy to misread, so it helps to translate them.
Availability in minutes
A percentage sounds precise until you convert it. For a 30-day month, which has 43,200 minutes, the allowed downtime at common targets is as follows.
| Availability target | Allowed downtime per 30-day month |
|---|---|
| 99.0 percent | about 432 minutes, or 7.2 hours |
| 99.5 percent | about 216 minutes, or 3.6 hours |
| 99.9 percent | about 43 minutes |
Then read the fine print. How is availability measured and by whom? Does scheduled maintenance count? Are the provider's upstream suppliers excluded? Is the measurement window monthly or yearly? A yearly window hides a bad month inside a good year.
Response is not resolution
A response time commits the provider to acknowledge a request. A resolution time commits them to fix it. Many agreements promise the first and are silent on the second. Ask which one you are getting, and ask how severity levels are defined, because the clock depends on who decides whether your problem is urgent. Define severity by business effect, such as "the payment system is down for all users," and not by the provider's internal categories.
Credits are not compensation
When a provider misses an SLA, the usual remedy is a service credit, a discount on a future invoice. Credits are often the sole and exclusive remedy, which means you cannot claim anything else for the same failure.
A hypothetical example shows the scale. Suppose your monthly fee is $1,000, and the agreement gives a 10 percent credit when availability falls below 99.9 percent and a 25 percent credit when it falls below 99.0 percent. If an outage costs you a day of sales worth several thousand dollars, the credit is $100 or $250. The credit does not cover your loss. It is a signal that the provider has an incentive to perform, not insurance. If a particular failure would hurt your business badly, ask about repeated-failure triggers that let you terminate without penalty.
Responsibilities, written as a two-column list
Shared responsibility is where things quietly fall through gaps. If the provider manages your backups and you manage your user accounts, who is responsible when a former employee's account is still active? A simple practice is to put the responsibilities in two columns, one for the provider and one for you, and read down the list looking for blank spaces.
Items that deserve a row include backups and restore testing, patching, user account creation and removal, license purchasing and renewal, monitoring and alert handling, security incident notification, change approval, and documentation. Any row where both columns say "shared" should be rewritten until one party owns the outcome.
Intellectual property and ownership of the work
For custom work, two questions control everything. Who owns what gets built, and what are you allowed to do with it?
There are usually three categories. Your pre-existing materials stay yours. The provider's pre-existing tools, templates, and know-how stay theirs. The new deliverables are where agreements differ. Some assign ownership of deliverables to the customer on payment. Others keep ownership with the provider and grant the customer a license. Both can be fair, but the details matter. A license that is non-exclusive, non-transferable, and terminates when the agreement ends may leave you unable to use something you paid for.
Ask the following.
- Do I own the deliverables, or do I hold a license? If a license, is it perpetual, and can it be transferred if I sell the business?
- Do I receive source code, configuration, and documentation, or only the running system?
- Does the provider reuse general techniques and tools across customers, and where is the line between that and my confidential information?
- Are open-source or third-party components included, and under what terms?
Without access to the configuration and the documentation, ownership on paper can still leave you dependent in practice.
Your data, and what happens to it
Data clauses are often the most consequential and the least read. They answer who owns your data, what the provider may do with it, where it is stored, and how you get it back.
Look for statements on the following.
- Ownership. Your data should remain yours, including data derived from your activity.
- Permitted use. The provider should use your data only to deliver the service. Be cautious about broad rights to use data for product improvement, analytics, or training of models, and ask for the specific terms.
- Location and subprocessors. Ask where data is stored and which other companies handle it on the provider's behalf.
- Return and deletion. You should be able to export your data in a usable format, on request, during and after the term. Ask for the format, the timeline, and whether there is a fee. Ask for confirmation of deletion, and how long backups persist.
- Regulated data. If you handle health records, payment cards, or personal data covered by law, the agreement may need additional terms. Which laws apply depends on your business and your location, and an attorney should confirm.
Security commitments
Security language ranges from specific to decorative. A statement that the provider uses "industry-standard security" tells you almost nothing. Better agreements name controls and duties. Look for multi-factor authentication on administrative access, encryption in transit and at rest, access limited by role, logging, background checks for staff with privileged access, and a schedule for patching.
Then look at incident handling. The agreement should say how fast you will be told about a suspected breach, who will tell you, and what information you will receive. A number such as "without undue delay and within 72 hours of confirmation" is more useful than a promise to "notify promptly." Also ask whether you can see an independent assessment, such as a third-party audit report, and whether the provider will complete a reasonable security questionnaire. Do not accept a claim of certification without asking to see the document.
Fees and everything adjacent to them
The price is rarely only the price. Read the fee section looking for the things that can move.
| Question | Why to ask |
|---|---|
| Is the fee fixed, per user, per device, or usage-based? | Growth can change the bill |
| Are third-party licenses and vendor charges included or billed separately? | Pass-through costs can exceed the service fee |
| Can the provider raise prices mid-term, and by how much? | Look for a cap or a notice period |
| What counts as out of scope and billed hourly? | Surprises hide here |
| What are the payment terms and late fees? | Cash flow and interest |
| Is there an onboarding or setup fee? | One-time costs |
| What is the minimum commitment? | You may owe fees for the whole term |
A practical habit is to ask the provider for an example invoice for a typical month and for a month when something went wrong. Compare the two.
Term, renewal, and termination
Check three dates. The start date, the length of the initial term, and the renewal rule. Automatic renewal is common and perfectly fair if you know the notice deadline. Put that deadline on a calendar the day you sign. Missing it can lock you in for another full term.
Termination has two flavors. Termination for convenience lets either side leave on notice, usually with a fee or a required notice period. Termination for cause applies when a party breaches the agreement. Look for how a breach is defined, whether there is a cure period, and what you owe afterward.
The part people skip is transition. A good agreement says what the provider must do when you leave. That means handing over documentation, credentials, domain and account control, and data, and cooperating for a defined period with the next provider. Ask who holds the administrator credentials and the domain registrations during the relationship. If the provider registered your domain in its own name, you have a problem to fix now.
Liability, indemnity, and insurance
These clauses are technical, and this is where attorney review earns its fee. In plain terms, a limitation of liability caps how much one party can owe the other, often to the fees paid in the prior 12 months. Exclusions for indirect or consequential damages mean lost profits and similar losses may be off the table entirely.
Questions worth raising include the following. Does the cap apply equally to both sides? Are there carve-outs, such as breach of confidentiality, data breach, or intentional misconduct, that sit outside the cap or under a higher one? Does the provider carry professional liability and cyber insurance, and will it show you the certificate? Does the provider indemnify you, meaning take responsibility for third-party claims, if the service infringes someone's intellectual property?
You may not win every one of these. Smaller providers often cannot accept unlimited exposure, and demanding it can make the service unaffordable. The goal is a cap that bears a sensible relationship to the risk and the fee.
A short checklist before you sign
- I know every document that forms the agreement, including incorporated policies.
- Scope names what is included, what is excluded, and how changes are approved.
- Service levels define measurement, severity, and the remedy, and I understand what the credits actually cover.
- Each responsibility has one owner.
- Ownership and license of deliverables are clear, and I will receive configuration and documentation.
- My data stays mine, can be exported, and will be deleted on request.
- Security duties and incident notification times are specific.
- Fees list pass-through costs, price increase limits, and the renewal notice deadline.
- Termination includes a transition plan and control of my domains and accounts.
- An attorney has read the liability, data, and termination clauses.
A note for small businesses in Puerto Rico
Disruptions that follow a storm or a long outage are exactly when an agreement gets tested. Ask how the provider handles a hurricane scenario. Do they maintain remote access to your systems if your office has no power or internet? What is their own continuity plan? Is your response time commitment suspended during declared emergencies, and if so, what do they still promise? If your customers or staff work in both English and Spanish, check whether support is available in both and whether documents will be provided in the language your team uses.
What to do this week
Pick the agreement in front of you, or the one you signed last year and never reread. Make a one-page summary with the term, renewal date, notice deadline, fees and pass-through charges, service levels, who owns the deliverables and data, and how you exit. If any of those lines is blank, that is your question list for the provider and for your attorney.
If you would like a second reader on a services schedule before it goes to counsel, we are glad to talk it through. InfraOps Base starts at $500 per month, with vendor and license charges billed separately, and the questions in this guide are the ones we expect customers to ask us.
Discuss your infrastructure requirements
Review the current service offer or schedule a conversation about the scope you need.
Stay in touch
Follow Ozcorp
Leave your details for occasional notes about new articles and Ozcorp updates.