← Back to AI Legal Lab
Insight
Generative AI for Legal WorkContract ReviewLegal Outsourcing

Using Generative AI to Summarize Contracts: Instructions and Example Prompts for Your Position and Audience

Hello, I'm Noriaki Asato, Representative Attorney at LegalAgent.

When bringing generative AI into legal practice, one of the easiest uses to start with is "summarizing contracts." When you receive a lengthy services agreement you have never seen before, there are times when you are unsure where to begin reading. In such situations, having the AI first summarize the outline of the whole makes it easier to grasp the overall picture of the contract in a short time.

For example, imagine that a business department has asked you to check SaaS terms of use sent by a business partner. Reading them in order from Article 1 takes time, and it is also hard to see which clauses deserve the most attention. If you first instruct the AI to "summarize the whole in about 10 lines," you can start examining the main text with a sense that the conditions for suspending the service and the limitation of liability need attention.

Grasping the overall picture and the role of summaries

With a contract you are reviewing for the first time, you cannot tell which parts matter more, and you tend to read everything from beginning to end with the same weight. Reading evenly not only takes time; there is also a risk of using up your concentration before you reach the clauses that deserve the most attention.

Having the AI prepare a summary makes it easier to grasp the structure of the entire contract, and the summary can be used as a map of where to spend your time. For a services agreement, you can identify burdensome clauses in advance, such as the scope of the entrusted services, acceptance of deliverables and ownership of intellectual property rights, before moving on to a close reading of the main text.

If you position a summary not as "a substitute for reading the main text" but as "a guide for reading the main text efficiently," it becomes easier to use it safely. I believe it is important to divide the roles: use the summary to grasp the broad outline, and always go back to the original text to confirm important clauses that bear directly on your decisions. How to split a contract that is too long to enter in one go is covered in "Pasting Long Contracts into Generative AI: The Basics."

Types of instructions by purpose and position

Even for the same contract, clearly conveying for whom and for what purpose the summary is being prepared makes the output more useful in practice. Types of instructions that are easy to use selectively in practice include the following.

  • Grasping the overall picture: an instruction to summarize the entire contract concisely within 10 lines
  • Focusing on your company's position: an instruction to summarize only the clauses likely to be unfavorable to your company, for example as the customer or as the service provider
  • Sharing with non-specialists: an instruction to summarize for members of a business department, breaking technical terms down into plain language
  • Organizing the main issues: an instruction to summarize only specific important clauses, such as damages, termination and ownership of intellectual property rights
  • Comparison with standard transactions: an instruction to list whether there are clauses unfavorable to your company compared with a general transaction template

For example, when reviewing a non-disclosure agreement (NDA), you make your position explicit: "Our company is the party receiving confidential information. Please summarize the agreement focusing on the obligations that are burdensome for the receiving party." This makes it more likely that items directly tied to your company's obligations, such as the restriction on use for other purposes and the obligation to return information after the agreement ends, will appear in the summary.

Example prompts for practical use

First is a basic form that has the AI organize the contract under set items. It conveys your company's position at the outset and has the AI organize, in one go, the obligations and the points to note as seen from that position.

You are an assistant with extensive experience in corporate legal work.
Please summarize the contract I am about to paste in the following format.
Our company is [the customer / the service provider, etc.].

1. Summary of the whole (within 5 lines)
2. Type of contract and the role of each party
3. Main obligations our company bears
4. Clauses that should be read with particular care (3, with reasons)

Please add a brief explanation in parentheses to any technical terms.

[Paste the contract here]

Next is an applied form that assumes the summary will be shared with members outside legal. It breaks down technical terms and narrows the content to the issues the business department needs in order to make decisions.

Please prepare a summary of the contract I am about to paste, to be shared
with a person in charge in a business department who is not familiar with
contracts. Please observe the following points.

- Avoid technical terms, and if you use one, explain it in parentheses
- "What our company promises under this contract," in no more than 3 points
- List 2 "points we would like the business department to decide"
- Copy "amounts, periods and termination conditions" accurately, exactly as worded in the original text

Finally, please name just 1 clause that legal should check in particular.

[Paste the contract here]

The key point is to specify in advance that the AI should "copy the original wording as is" for parts where paraphrasing could make the conditions ambiguous, such as amounts and notice periods for termination. Even with an instruction to copy, however, figures or wording may still be output incorrectly. Before sharing the summary with the business department, check the amounts, periods and termination conditions transcribed into it against the original text.

Requests that anticipate later work

A summary is useful on its own, but adding instructions that anticipate the work that follows makes it a more practical tool.

Having the AI present "the order of priority of the clauses to read" together with the summary makes it easier to decide the order in which to read the main text. If you specify, "After summarizing the whole, please list the clauses in descending order of importance from our company's position as the customer," you can plan to check the acceptance and damages clauses first.

In addition, if you instruct the AI, together with the summary, to "put the concerns in the form of questions that can be asked of the business department as they are," you can produce a first draft of text for a hearing. If the summary of SaaS terms of use yields a question to the business department such as "Shall we ask the counterparty about compensation if the service is suspended?", it becomes easier to move forward with confirmations with the business department.

When comparing and reviewing several contracts, standardize the framework of the summaries. Lining up summaries with the same structure of items makes it easier to compare differences between contracts, such as the caps on damages and the subcontracting clauses.

Mistakes when using summaries and how to prevent them

The thing to be most wary of when using a summary is deciding on the content of a contract by reading the summary alone. A summary is convenient, but detailed conditions such as exceptions to exemptions and the scope of damages may be reduced to a single line. Even if the summary says "there is a damages provision," the amount of damages your company may bear differs greatly depending on whether the cap is equivalent to the monthly usage fee or there is no cap at all. The more important the clause, the more you should always go back to the original text and check it.

If you ask for a summary without conveying your company's position, the result tends to stay at a safe generality. Just adding a word on whether you are the customer or the service provider, or the disclosing party or the receiving party, makes it more likely that what the contract means for your company is reflected. You also need to take care not to trust article numbers or quotations that appear in the summary as they are. Anthropic's technical documentation also explains that language models, including Claude, may generate content that is factually incorrect or inconsistent with the text they were given. Because article numbers or content that do not exist may be presented, always check article numbers and specific wording in the text against the original contract.

A contract normally states the counterparty's name and the transaction amount. Before pasting a contract, confirm what may be entered in light of the contractual terms of the service you use, the confidentiality obligations owed to the counterparty and your internal information management rules. For the points to check, see "Understanding Training Opt-Outs for Business Use of Generative AI."

Support for clause review after summarizing and for internal adoption

For full-scale review of the clauses after you have grasped the key points through a summary, we provide support through legal outsourcing. For designing the introduction of generative AI in legal departments, please see support for generative AI use in legal departments.

Related articles

Articles connected to this topic.

Insight / 2026.11.14 Pasting Long Contracts into Generative AI: The Basics of Summarizing and Splitting Insight / 2026.11.13 Examples and Templates for Generative AI: Contract Review Formats and Precautions Insight / 2026.11.12 Follow-Up Questions for Generative AI: Refining Contract Reviews

Services connected to this topic

Legal outsourcing Ongoing legal team support for contract review and legal operations. Generative AI legal consulting Terms, privacy, copyright, AI governance, and internal AI use rules.
View AI Legal Lab articles