How to Review a Service Agreement with AI

A service agreement sets the terms for almost every ongoing business relationship: hiring an agency, bringing on a consultant, signing up with an IT provider, or renewing a vendor contract. They range from two pages to sixty, and the details that actually decide how the relationship works, what is included in scope, when either side can walk away, and who is on the hook if something goes wrong, are often spread across several sections that do not sit next to each other. AI can read the agreement in minutes and give you a clear, plain-English picture of what it commits each side to before you sign.

AI can explain how pricing, fees, and other commercial terms work, but it cannot determine whether they are competitive for your industry, or whether a liability cap is appropriate for your level of risk. Those are questions for someone who understands your business and your industry. But it can get you from "I don't know what I'm agreeing to" to "I know exactly what to check before I sign" in under twenty minutes. This tutorial shows you how.

What you will learn

• Get a plain-English summary of any service agreement in under two minutes
• Confirm exactly what is and is not included in scope before a dispute starts
• Extract the fee structure, payment terms, and invoicing conditions
• Check termination rights, notice periods, and what happens to work in progress
• Identify liability caps, indemnities, and other clauses that shift risk between the parties
• Spot one-sided or unusually restrictive clauses before you sign
• Know which situations call for legal advice rather than AI alone

In this guide

• Who is this for
• How AI reviews service agreements
• Common service agreement clauses you will encounter
• Before you review a service agreement with AI
• Step 1: Upload your service agreement
• Step 2: Get a plain-English summary
• Step 3: Confirm the scope of services
• Step 4: Check the fee structure and payment terms
• Step 5: Review termination rights and notice periods
• Step 6: Check service levels and performance standards
• Step 7: Review the change control process
• Step 8: Check intellectual property ownership
• Step 9: Review limitation of liability and indemnification
• Step 10: Check governing law and dispute resolution
• Step 11: Ask for a consolidated risk summary
• Step 12: Decide what to do next
• Worked example
• Common service agreement red flags
• Questions to ask the other party
• Common mistakes
• When AI is enough and when it is not
• Privacy and document security
• Before you sign: checklist
• Prompts you can copy
• Frequently asked questions
• What you learned
• Next step
• Related tutorials

Who is this for

This tutorial is written for people who receive or issue service agreements but do not review them professionally. That includes:

• Business owners engaging an agency, consultant, or contractor
• Freelancers and consultants sending their own service agreements to clients
• Procurement and operations staff reviewing vendor or supplier contracts
• Startup founders signing master service agreements with software or infrastructure providers
• Anyone renewing, amending, or extending an existing service agreement

If you negotiate commercial contracts professionally or work in a legal or procurement team, the clause-by-clause prompts in Steps 3 through 9 may still be a useful starting framework for less familiar agreement formats. If your document is a broader commercial contract rather than a service-specific agreement, see How to Review a Contract with AI for the general workflow.

How AI reviews service agreements

Before getting into steps, it helps to understand what the AI is actually doing when it reads your service agreement.

LearnByAI uses Retrieval-Augmented Generation (RAG). It does not answer from general knowledge about what service agreements typically say. It reads your specific document, finds the relevant clauses, and answers based on what is actually written there. You can read more about how AI document chat works.

When you ask what is included in scope, the AI finds the scope of services clause in your agreement and explains it. It does not give you a generic description of what a service agreement usually covers. For a wider set of ready-to-use prompts that also apply to service agreements, see the Contract Review Prompts library.

AI handles this well	A human professional is still needed
Finding and explaining the scope of services clause	Advising whether the price and commercial terms are competitive
Extracting fee structure, invoicing terms, and payment triggers	Assessing whether a liability cap is adequate for your risk exposure
Identifying termination rights and notice periods	Negotiating terms on your behalf
Flagging one-sided liability, indemnity, or renewal clauses	Advising on interaction between a master agreement and its statements of work
Summarising service levels and what happens if they are missed	Assessing enforceability of specific clauses in your jurisdiction

Keep that distinction in mind throughout this tutorial.

Common service agreement clauses you will encounter

Most service agreements are built from the same set of core clauses, whether the provider is a solo consultant or a large IT vendor. Knowing what each one does before you start asking questions makes the review faster and helps you spot anything unusual.

Clause	Why it matters
Scope	Defines what is included, and what is not
Fees	Determines your payment obligations
Service levels	Sets performance standards and what happens if they are missed
Termination	Controls how and when either side can exit
Liability	Allocates financial risk if something goes wrong
Intellectual property	Determines who owns the work
Governing law	Determines which legal system applies

Scope of services. This defines exactly what the provider must deliver. It may sit in the main body of the agreement or in a separate statement of work (SOW) that the agreement incorporates by reference. Vague scope language is one of the most common sources of disputes.

Fees and payment terms. This sets out how much is charged, how it is calculated (fixed fee, time and materials, or a retainer), when invoices are issued, and what happens if payment is late.

Term and termination. This covers how long the agreement runs, whether it renews automatically, and the conditions under which either party can end it, whether for convenience, for cause, or both.

Service levels. Often shortened to SLAs, these set measurable performance standards, such as response times or uptime guarantees, and the remedy (usually a service credit) if the provider misses them.

Change control. This sets out the process for changing scope, fees, or timelines after signing, usually requiring a written change order agreed by both parties before new work begins.

Intellectual property. This determines who owns the deliverables created during the engagement, and whether the provider retains rights to reuse tools, templates, or methods it brought into the project.

Confidentiality. Many service agreements include confidentiality obligations directly rather than relying on a separate NDA. Check whether this section covers what you expect. If a standalone NDA was also signed alongside this agreement, see How to Review an NDA with AI for that document.

Limitation of liability. This caps how much either party can be required to pay if something goes wrong, and often excludes certain categories of loss entirely, such as lost profits or indirect damages.

Indemnification. This specifies who compensates whom, and for what, if a third party brings a claim connected to the services.

Key personnel clause. Common in consulting and professional services agreements, this names the specific individuals who will perform the work and requires the client's consent before the provider substitutes them. It matters because the value of the engagement can depend heavily on who is actually doing the work, not just which company is contracted.

Warranties. These are promises about the standard of the work, such as performing services with reasonable skill and care, or that deliverables will conform to agreed specifications.

Insurance. Many service agreements require the provider to hold specific types and levels of insurance, such as professional indemnity or public liability cover, for the duration of the engagement.

Subcontracting and assignment. This governs whether the provider can bring in subcontractors or transfer the agreement to another party, and whether your consent is required first.

Governing law and dispute resolution. This determines which country's or state's law applies and how disputes must be resolved, whether through courts, arbitration, or a mandatory escalation process first.

Not every service agreement contains all of these. The absence of a clause, particularly around liability, termination, or scope, is sometimes as significant as its presence.

Seeing a long list of clause types can feel daunting. Most commercial service agreements contain standard provisions that are widely used and routinely signed. The goal of this tutorial is to help you identify anything that is unusual, one-sided, or missing entirely, not to treat every clause as a potential problem.

Before you review a service agreement with AI

Scanned PDFs may reduce accuracy. If your agreement was scanned as an image rather than saved as a text-based PDF, the AI may not read it correctly. If the AI says it cannot find a clause you can see on screen, copy the relevant text into a Word document and upload that instead.

Check whether there is a separate statement of work. Many service agreements are structured as a master agreement plus one or more SOWs that set out the specific scope, fees, and timeline. If your provider sent both documents, upload both in the same session so the AI can read them together.

Length is not a guide to risk. A two-page consulting agreement can contain the same categories of risk as a forty-page managed services contract. Review each clause type regardless of document length.

Check for schedules and appendices. Fees, service levels, and named personnel are often set out in schedules or appendices at the back of the document rather than in the main clauses. Make sure these were included when the document was saved or scanned, and upload them together with the main agreement.

Work from a copy. For any signed agreement, keep the original in a secure location and upload a copy.

Received a revised version after negotiation? If the provider sent back a redlined or updated draft, see How to Compare Two Contract Versions with AI instead of reviewing it from scratch.

Step 1: Upload your service agreement

Go to the AI Legal Document Review page and upload your service agreement. If you have a separate statement of work, upload it in the same session. Once the documents are processed, you can start asking questions immediately.

Step 2: Get a plain-English summary

Start with a summary, not a specific question. The summary tells you the agreement's shape and purpose before you look at individual clauses.

Prompt to use:

Summarise this service agreement in plain English. Who are the parties, what services are being provided, what is the payment structure, and how long does the agreement run?

What a good response looks like:

This is a Managed IT Services Agreement between Northgate IT Services Ltd ("Provider") and Meridian Freight Solutions Ltd ("Client"). The Provider will deliver helpdesk support, server monitoring, and cybersecurity monitoring for the Client's 45 users. The fee is £3,200 per month, billed monthly in advance. The initial term is 24 months, after which the agreement automatically renews for successive 12-month periods unless either party gives 90 days' written notice.

If the summary does not match what you understood before receiving the agreement, that is your first flag. A 60-second summary catches a mismatch before you go further.

Also pay attention to whether the agreement renews automatically. Many service agreements renew unless notice is given before a specific deadline, and it is worth knowing that from the outset rather than discovering it later.

Step 3: Confirm the scope of services

Whether the agreement covers what you actually need is the single most important thing to check, and it affects how you read every clause that follows. Confirm this before reviewing fees, liability, or anything else.

Prompt to use:

What exactly is included in the scope of services under this agreement? What is explicitly excluded, and is the scope defined in this document or in a separate statement of work?

What a good response looks like:

Section 2 defines the in-scope services as helpdesk support for 45 named users, monitoring of three on-premise servers, monthly patch management, and monthly cybersecurity reporting. Section 2.3 explicitly excludes hardware procurement, on-site emergency response outside business hours, and any work related to migrating to new systems, which is billed separately under a project statement of work.

Scope exclusions are as important as inclusions. If the excluded items are things you assumed were covered, that gap needs to be resolved before signing, not discovered later when you need the work done.

Step 4: Check the fee structure and payment terms

Once scope is confirmed, check what you are actually paying for it and under what conditions.

Prompt to use:

What is the fee structure under this agreement? Is it a fixed fee, time and materials, or a retainer? When are invoices issued, when is payment due, and what happens if payment is late?

What a good response looks like:

Section 4 sets a fixed monthly fee of £3,200, invoiced in advance on the first business day of each month. Payment is due within 30 days of the invoice date. Section 4.5 states that late payment accrues interest at 4% above the Bank of England base rate, and the Provider may suspend services if payment is more than 14 days overdue.

The suspension right is worth noting. A short late payment window that allows the provider to suspend services can create operational risk if an invoice is disputed rather than simply late.

Step 5: Review termination rights and notice periods

Termination terms determine how easily either side can exit, and what happens to fees and work in progress if they do.

Prompt to use:

How can this agreement be terminated? Can either party terminate for convenience, and what notice period applies? What happens to fees for work already completed if the agreement ends early?

What a good response looks like:

Section 8 allows either party to terminate for convenience with 90 days' written notice. Either party may also terminate immediately for material breach if the breach is not remedied within 14 days of written notice. Section 8.4 states that fees for services performed up to the termination date remain payable, and any fees paid in advance for periods after termination are refunded on a pro-rata basis.

A longer notice period reduces your flexibility to change providers, so consider whether it aligns with your business needs. If it does not, this is a specific point to raise before signing.

Step 6: Check service levels and performance standards

If the agreement includes service levels, this is where you find out what the provider is actually committing to, not just describing.

Prompt to use:

What service levels does this agreement guarantee? What are the specific response or resolution times, do they apply at all hours or only during business hours, and what happens if the Provider misses them?

What a good response looks like:

Section 5 guarantees a 4-hour response time for critical incidents, defined as a full system outage, and one business day for standard requests. These service levels apply during business hours only, Monday to Friday, 9am to 6pm. Section 5.4 provides a service credit of 5% of the monthly fee for each missed critical response time, capped at 20% of monthly fees in any given month.

Check whether the guaranteed hours match how your business actually operates. A business-hours-only service level on a system that needs to run continuously is a mismatch worth raising directly with the provider.

Step 7: Review the change control process

Scope and fees agreed at signing rarely stay fixed for the life of a long-term service agreement. The change control clause governs how changes happen.

Prompt to use:

What does this agreement say about changing the scope, fees, or timeline after signing? Is a written change order required, and who needs to approve it?

What a good response looks like:

Section 6 requires any change to scope, fees, or deliverables to be documented in a written change order signed by an authorised representative of both parties. Verbal instructions or emails requesting additional work do not constitute an approved change under this section.

Without a documented change control process, informal requests for extra work can create disputes later about what was actually agreed and what should be billed. Confirm your team knows to route change requests through this process.

Step 8: Check intellectual property ownership

This clause determines who owns what the provider creates during the engagement, and it is frequently misunderstood by both sides.

Prompt to use:

What does this agreement say about intellectual property? Who owns the deliverables created during the engagement, and does the Provider retain rights to any tools, templates, or pre-existing methods used to deliver the services?

What a good response looks like:

Section 7 states that ownership of custom deliverables transfers to the Client upon full payment. Section 7.3 clarifies that the Provider retains ownership of any pre-existing tools, scripts, monitoring templates, or methodologies used to deliver the services, and grants the Client a non-exclusive licence to use them for the duration of the agreement only.

The licence being limited to the term of the agreement, rather than permanent, matters if any part of your operations depends on tools the provider built using its own pre-existing framework.

Step 9: Review limitation of liability and indemnification

This is where risk is allocated between the parties if something goes wrong. Read it carefully, particularly for services connected to data, security, or critical operations.

Prompt to use:

What does this agreement say about limitation of liability and indemnification? Is there a cap on the Provider's liability, does it apply to all types of loss, and are there any carve-outs for specific risks such as data breaches?

What a good response looks like:

Section 9 caps the Provider's total liability at the fees paid in the preceding 12 months. Section 9.3 excludes liability for indirect or consequential loss, including lost profits, in all circumstances. There is no carve-out increasing the cap for losses arising from data breaches or security incidents, meaning the general cap applies even where a security failure originates with the Provider's monitoring service.

A liability cap with no step-up for the exact risk the provider is being paid to manage, in this case cybersecurity, is worth flagging. Ask whether that carve-out can be added or the cap raised for that specific category.

Step 10: Check governing law and dispute resolution

The governing law clause is easy to overlook because it usually sits near the end, but it has real consequences if a dispute arises.

Prompt to use:

Which country's or state's laws govern this agreement? How must disputes be resolved, and is there a required escalation process before either party can go to court or arbitration?

What a good response looks like:

Section 14 states that this agreement is governed by the laws of Scotland. Disputes must first be escalated to a director-level meeting within 14 days of either party raising a formal issue. If unresolved, either party may commence proceedings in the courts of Edinburgh, Scotland.

If the governing law is a jurisdiction you do not operate in, your rights under the agreement may differ from what you would expect under your own country's law. A mandatory escalation step before litigation is common and generally useful, since it forces a conversation before legal costs start.

Step 11: Ask for a consolidated risk summary

Once you have worked through the individual clauses, ask the AI to pull it together into a single practical summary.

Prompt to use:

Based on this service agreement, what are the three to five most important things I should be aware of or consider before signing? Rank them by practical impact on my business, and focus on clauses that are unusual, one-sided, or could create practical problems.

What a good response looks like:

Four points stand out. First, the service levels apply only during business hours, which may not match round-the-clock operational needs. Second, the 90-day termination notice period is longer than typical and limits flexibility to exit. Third, the liability cap does not increase for data breach or security incidents despite the Provider's cybersecurity monitoring role. Fourth, the intellectual property licence for the Provider's pre-existing tools ends when the agreement ends, which could disrupt operations if not renewed in time.

This summary gives you a practical starting point for any conversation with the provider or with a lawyer.

Step 12: Decide what to do next

After Step 11, you are in one of three positions:

• The agreement looks standard. Scope is clear, fees and termination are reasonable, and the risk allocation feels appropriate. Proceed.
• There are specific clauses to query or negotiate. You have identified points, such as an SLA mismatch or a liability gap, that you want changed or explained before signing. Use the AI's output as the basis for that conversation.
• You need a lawyer. The contract value is significant, the term is long, or the liability exposure feels wrong for your situation. Take your AI session notes into that meeting. You will get more from the hour.

Worked example

Here is a complete walkthrough.

Situation: Priya Nair, founder of Meridian Freight Solutions Ltd, a small logistics company, is asked to sign a 24-month managed IT services agreement with Northgate IT Services Ltd before her current provider's contract expires. She uploads the agreement to LearnByAI the evening before her call with Northgate.

Initial summary prompt:

Summarise this service agreement. Who are the parties, what services are being provided, what is the payment structure, and how long does the agreement run?

AI response:

This is a Managed IT Services Agreement between Northgate IT Services Ltd ("Provider") and Meridian Freight Solutions Ltd ("Client"). The Provider will deliver helpdesk support, server monitoring, and cybersecurity monitoring for 45 users. The fee is £3,200 per month, billed monthly in advance, for an initial term of 24 months, automatically renewing for successive 12-month periods unless either party gives 90 days' written notice.

What this tells her: The 24-month term with a 90-day notice window means she needs to calendar the cancellation deadline well in advance, roughly eight months before the second anniversary, or she will be locked in for another year.

Follow-up prompt:

What exactly is included in scope, and what is explicitly excluded?

AI response:

Section 2 covers helpdesk support for 45 named users, monitoring of three on-premise servers, patch management, and monthly cybersecurity reporting. Section 2.3 excludes hardware procurement, on-site emergency response outside business hours, and system migration work, which is billed separately under a project statement of work.

What this tells her: Her logistics operation runs a night shift, and after-hours on-site support is excluded. That is a gap worth raising directly, since her previous provider included limited after-hours coverage.

Follow-up prompt:

What service levels does this agreement guarantee, and do they apply at all hours?

AI response:

Section 5 guarantees a 4-hour response time for critical incidents and one business day for standard requests, both measured only during business hours, Monday to Friday, 9am to 6pm. A missed critical response generates a service credit of 5% of the monthly fee, capped at 20% in any month.

What this tells her: The guaranteed response times do not cover her night shift at all, which confirms the scope gap found in the previous step is not a one-off omission but a consistent limitation across the agreement.

Follow-up prompt:

What does this agreement say about limitation of liability? Is there a cap, and does it cover data breaches or security incidents?

AI response:

Section 9 caps the Provider's total liability at the fees paid in the preceding 12 months, approximately £38,400. Indirect and consequential losses are excluded entirely. There is no separate carve-out increasing the cap for data breaches or security incidents.

What this tells her: Northgate is responsible for her cybersecurity monitoring, but if a breach happens on their watch, her maximum recovery is capped at roughly £38,400 with no adjustment for the sensitivity of the service. Given her business handles customer shipment and billing data, this cap may be too low relative to her actual exposure.

Follow-up prompt:

Which country's laws govern this agreement, and how must disputes be resolved?

AI response:

Section 14 states the agreement is governed by the laws of Scotland. Disputes must first go to a director-level meeting within 14 days. If unresolved, either party may bring proceedings in the courts of Edinburgh, Scotland.

What this tells her: Meridian Freight operates in England, so Scotland is an unfamiliar jurisdiction for her. This is not necessarily a problem, but it is a detail worth raising with a lawyer if a dispute ever looks likely.

What to verify manually: Priya should ask a lawyer whether the liability cap is adequate given the cybersecurity scope, confirm whether after-hours coverage can be added as a paid extra, and check whether Scots law creates any practical disadvantage for her if a dispute arises.

Common service agreement red flags

Not every unusual clause is a dealbreaker, but certain patterns are worth pausing on before you sign.

Scope described only in general terms. Language like "IT support services as reasonably required" with no defined deliverables or user counts makes disputes about what was promised far more likely.

No remedy for late or missed service levels. An SLA with a target but no defined consequence for missing it is effectively unenforceable in practice.

Termination available to only one party. If the provider can terminate for convenience but the client cannot, or vice versa, that asymmetry is worth understanding before signing.

Liability cap with no adjustment for the core risk. A general liability cap that does not increase for the specific risk the provider is being paid to manage, such as data security or safety-critical monitoring, may leave you underprotected.

Automatic renewal with a long notice window. A 90-day or longer notice period combined with automatic renewal can lock you into another full term if the cancellation date is missed.

Unrestricted subcontracting. If the provider can subcontract any part of the services without your consent, you may end up relying on a party you never vetted.

Uncapped time-and-materials billing. If fees are billed on a time-and-materials basis with no estimate, budget ceiling, or requirement to seek approval before exceeding it, costs can run well past what you expected.

Indemnification that runs only one way. If only the client is required to indemnify the provider, and not the other way around, the provider carries none of the risk for its own errors.

Questions to ask the other party

Once you have completed your review and identified anything unusual, these questions give you a way to raise specific concerns directly, before signing.

On scope: "Can we add a defined after-hours or emergency response tier, even at an additional cost?"

On service levels: "Can the response time guarantees be extended to cover our operating hours rather than standard business hours?"

On liability: "Can the liability cap be increased specifically for losses connected to data security, given the nature of the services provided?"

On termination: "Can the notice period be shortened, or can we add a right to terminate for convenience with less notice after the initial term?"

On subcontracting: "Does the provider intend to subcontract any part of these services, and can we require consent before that happens?"

Raising these questions directly and specifically is more productive than objecting to the document in general terms. The AI's clause-by-clause output gives you the language to be precise.

Common mistakes

Reviewing the master agreement without checking the statement of work. Scope, fees, and timelines are often defined entirely in the SOW, not the master agreement itself.

Asking one broad question instead of one per clause. A single "what should I know about this contract" prompt produces a shallower answer than asking about each clause in turn.

Trusting the AI's answer without checking the clause. The AI references specific sections, and it can occasionally misread complex cross-referenced clauses, so confirm anything important against the actual document.

Uploading a scanned image PDF. Scanned agreements are images rather than text, so the AI cannot read them reliably.

Assuming the provider's standard paperwork is negotiable-neutral. Templates drafted by the provider are written from the provider's perspective by default, and asymmetries are common even in reputable vendors' standard terms.

When AI is enough and when it is not

For most routine service agreements, AI gives you a solid foundation: you understand what is in scope, what you are paying, how to exit, and where risk sits.

A human lawyer is worth the time when:

• The contract value or term length is significant. A multi-year agreement with a substantial monthly fee carries more downside if the terms are wrong.
• The services involve sensitive data or safety-critical systems. Liability and indemnity terms matter more when a failure could cause real financial or operational harm.
• The agreement combines a master agreement with multiple statements of work. Interactions between the two can create gaps or conflicts that are easy to miss.
• The governing law is unfamiliar. If the agreement is governed by the law of a jurisdiction you do not operate in, the AI cannot tell you whether specific clauses are enforceable there.
• The AI identifies one of the red flags listed above. Those are the specific patterns most likely to cause problems if not addressed before signing.

Use AI to arrive at that conversation well-informed, not to skip it. For AI-assisted legal document review, see the AI Legal Document Review page.

Privacy and document security

Before uploading a service agreement, consider what it contains.

LearnByAI processes documents in session-isolated storage. Your files are not shared with other users and are not used to train AI models. Even so:

• Service agreements often include pricing, rate cards, and internal contact details. Review what the document reveals before uploading.
• Check the agreement itself before uploading it. Some agreements restrict how the document may be shared or stored, and uploading to a third-party platform may technically fall within those restrictions.
• For agreements connected to active disputes or renegotiation, consult your legal or procurement team before uploading.
• If the agreement includes an appendix listing named employees or personal data, consider whether that section needs to be reviewed separately.

Read the Security page and Privacy Policy for a full explanation of how documents are stored and processed.

Before you sign: checklist

• Confirmed the scope of services, including what is explicitly excluded
• Checked whether a separate statement of work applies and reviewed it alongside the main agreement
• Reviewed the fee structure, invoicing terms, and late payment consequences
• Confirmed termination rights, notice periods, and what happens to fees for work in progress
• Confirmed whether the agreement renews automatically and noted the cancellation deadline
• Checked service levels, the hours they apply, and the remedy if they are missed
• Confirmed a written change control process exists for scope, fee, or timeline changes
• Reviewed intellectual property ownership and any licence limitations on provider tools
• Checked the liability cap and whether it is adequate for the specific risk being managed
• Confirmed the governing law and dispute resolution process
• Asked a lawyer about any clause that concerns you or where the contract value is significant

Prompts you can copy

Prompts 1 through 10 follow the tutorial workflow in order. Prompts 11 through 14 are optional follow-up questions you can use at any point when relevant.

1. Summarise this service agreement in plain English. Who are the parties, what services are being provided, what is the payment structure, and how long does the agreement run?
2. What exactly is included in the scope of services under this agreement? What is explicitly excluded, and is the scope defined in this document or in a separate statement of work?
3. What is the fee structure under this agreement? Is it a fixed fee, time and materials, or a retainer? When are invoices issued, when is payment due, and what happens if payment is late?
4. How can this agreement be terminated? Can either party terminate for convenience, and what notice period applies? What happens to fees for work already completed if the agreement ends early?
5. What service levels does this agreement guarantee? What are the specific response or resolution times, do they apply at all hours or only during business hours, and what happens if the Provider misses them?
6. What does this agreement say about changing the scope, fees, or timeline after signing? Is a written change order required, and who needs to approve it?
7. What does this agreement say about intellectual property? Who owns the deliverables created during the engagement, and does the Provider retain rights to any tools, templates, or pre-existing methods used to deliver the services?
8. What does this agreement say about limitation of liability and indemnification? Is there a cap on the Provider's liability, does it apply to all types of loss, and are there any carve-outs for specific risks such as data breaches?
9. Which country's or state's laws govern this agreement? How must disputes be resolved, and is there a required escalation process before either party can go to court or arbitration?
10. Based on this service agreement, what are the three to five most important things I should be aware of or consider before signing? Rank them by practical impact on my business.
11. Does this agreement include a key personnel clause? If so, which individuals are named, and does the Provider need my consent to replace them?
12. Does this agreement require the Provider to carry insurance? If so, what type and at what level of cover?
13. Does this agreement allow the Provider to subcontract any part of the services or assign the agreement to another party without my consent?
14. Does this agreement contain any clauses that are unusually favourable to either party compared with the rest of the agreement? Explain why.

Frequently asked questions

Can AI review a service agreement?

Yes. AI can summarise the agreement, explain clauses in plain English, extract key obligations, and flag terms that look unusual or one-sided. It cannot provide legal advice or determine whether the agreement is appropriate for your specific situation.

Can AI identify unfair or one-sided clauses?

AI can point out clauses that look unusually restrictive, one-sided, or inconsistent with the rest of the agreement. Whether a clause is enforceable depends on the applicable law, and that judgment should come from a lawyer when the agreement carries real stakes.

Can I upload both the master agreement and the statement of work?

Yes. Uploading both together gives the AI more context, since many service agreements define scope, pricing, and deliverables inside a separate statement of work rather than the main document.

What types of service agreements work well with AI review?

Consulting agreements, IT and managed services agreements, marketing and agency retainers, software development agreements, and professional services agreements all work well. The same clause-by-clause approach applies whether you are reviewing a vendor contract, an MSA, or a standalone consulting agreement.

What if my agreement is a scanned PDF?

Scanned image PDFs can reduce accuracy because the AI has to rely on OCR to read them. A text-based PDF or DOCX file generally produces more reliable results.

What is a statement of work?

A statement of work, often shortened to SOW, sits under a master service agreement and sets out the specific scope, deliverables, timeline, and fees for a particular engagement. The master agreement provides the legal framework; the SOW fills in the project-specific details.

What clauses matter most in a service agreement?

Scope, fees, termination, service levels, and limitation of liability are the clauses most likely to cause problems if they are missed or misunderstood. Review each one individually rather than reading the agreement start to finish.

What you learned

• Most service agreements are built from the same set of core clauses. Knowing what each one does before you start asking questions makes the review faster and helps you spot anything unusual.
• Confirm the scope of services before reviewing anything else. Exclusions matter as much as inclusions, and a mismatch here affects how every other clause should be read.
• Check whether a separate statement of work applies. Scope, fees, and timelines are often defined there rather than in the main agreement.
• Service levels are only meaningful if they apply during the hours you actually need them and carry a real remedy when missed.
• A liability cap that does not adjust for the specific risk being managed, such as data security, may leave you underprotected relative to what the provider is actually responsible for.
• Termination notice periods combined with automatic renewal can lock you into another term if the cancellation deadline is missed.
• Governing law determines which legal system applies and how disputes are resolved. Check it before signing, particularly if the jurisdiction is unfamiliar.
• AI tells you what a service agreement says. A lawyer tells you whether the terms are appropriate for your specific business and risk level.

Next step

If you receive a revised version of a service agreement after negotiation, the next tutorial covers how to identify what changed and whether any changes shift risk in your direction.

How to Compare Two Contract Versions with AI

Related tutorials

These tutorials cover related tasks you may want to run alongside or after your service agreement review.

• How to Review a Contract with AI
• How to Review an NDA with AI
• How to Compare Two Contract Versions with AI
• How to Extract Key Dates and Deadlines from a Contract (coming soon)