Program, method, and information processing apparatus

Abstract

To reduce labor for confirming contents of a contract when a user who does not necessarily perform legal business exclusively such as a management layer confirms the contract.SOLUTION: Provided is a program for causing a computer to operate. In a storage unit of the computer, data of a contract and a result in which each clause of the contract is evaluated are stored. The program causes a processor of the computer to execute a step of providing a result evaluating each clause of the contract to a first user in arrangement order regardless of order of clauses of the contract.SELECTED DRAWING: Figure 15

Description

Technical Field

[0001] The present disclosure relates to a program, a method, and an information processing apparatus.

Background Art

[0002] In business activities, approvals are given for various agreements and applications both inside and outside the company while the business is being developed. For example, within a business operator, an approver makes a decision on what needs to be approved. In addition, regarding contracts both inside and outside a business operator, in recent years, due to the development of IT technology, those that were previously concluded on paper are gradually being concluded as electronic contracts.

[0003] In an electronic contract, a user of an electronic contract service electronically signs a contract document to be signed. Electronic contract services are provided by business operators in various ways, such as so-called party-signature types and so-called business-operator signature types (witness types). When concluding a contract using an electronic contract service, depending on the information identifying the parties to the contract, the contract document to be the subject of the contract may be made viewable between the parties to the contract while the conclusion process is proceeding. For example, when using an email address as the information identifying the parties to the contract to proceed with contract conclusion, one of the parties wishing to enter into the contract sends the contract document to the electronic contract service while specifying the email address of the other party. Then, the person who receives the contract document uses the electronic contract service to approve the contract document, etc., to proceed with the conclusion process by electronic contract.

[0004] The following Japanese Unexamined Patent Application Publication No. 2019-101539 (Patent Document 1) is a contract content evaluation apparatus that evaluates the contract content based on a contract document, and refers to contract clause evaluation information in which evaluation values are set for each contract clause and contract condition, and calculates the evaluation values for one or more contract clauses and contract conditions representing the contract content, and an evaluation means for evaluating the contract clauses, contract conditions, and the contract content based on the evaluation values calculated by the calculation means and the total of the evaluation values, is described as being characterized by having.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] Patent Document 1 describes evaluating the content of a contract. However, there is still room for improvement in the way the evaluation results are presented even with the technology of Patent Document 1. For example, there is room for improvement in reducing the labor of checking the content of the contract for users such as management who do not necessarily engage in legal work full-time.

Means for Solving the Problems

[0007] One embodiment shown in the present disclosure is a program for operating a computer. In the storage unit of the computer, contract data and the results of evaluating each clause of the contract are stored. The program causes the processor of the computer to present to a first user the results of evaluating each clause of the contract in an order regardless of the order of the clauses of the contract.

Effects of the Invention

[0008] According to the present disclosure, when a user such as management who does not necessarily engage in legal work full-time checks a contract, it is possible to reduce the labor of checking the content of the contract.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

DETAILED DESCRIPTION OF THE INVENTION

[0010] The following is an embodiment of the present disclosure. The description of the embodiment of the present disclosure will be made with reference to the drawings. Also, the same reference numerals are given to the same parts in the description of the embodiment of the present disclosure. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0011] <Overview of the First Embodiment> In this embodiment, a user who uses the system 1 operates a PC (Personal Computer) or the like and manages document data such as a contract document using an electronic contract service or the like.

[0012] Document data such as a contract document has, for example, the following types. The following are examples and are not limited thereto. · Confidentiality Agreement · Lease Agreement · Real Estate Sales Contract · Land Lease Agreement · Goods Sales Contract · Goods Lease Agreement · Employment Contract · Worker Dispatch Contract · Business Commission Contract · Transfer Security Agreement · M&A Agreement · Business Transfer Agreement · Joint Venture Contract · Software Development Contract · Contracts Related to Intellectual Property (License Contracts, etc.) · Copyright Transfer Agreement · Trademark License Agreement · License Agreement · Franchise Agreement · Board Meeting Minutes · Contract for Product Manufacturing · Contract for Architectural Design Drawings · Construction Work Subcontract Agreement · Insurance Contract · Consulting Contract · Agency Agreement

[0013] Document data such as contracts may contain information as follows. The following are examples and are not limited to these. · Subject matter of the contract and purpose of the contract The contract has a section describing the subject matter of the contract and the purpose of the contract. For example, if the contract is a real estate purchase contract, the address of the property, the use of the property, the purchase price, and the payment terms, etc. are included in the content. · Conditions of the contract and provisions of the contract The contract stipulates the conditions of the contract and the provisions of the contract. For example, if the contract is a real estate purchase contract, the delivery time, the delivery method, the obligations of the buyer, the responsibilities of the buyer, and the seller's guarantee, etc. are included in the content. · Information such as signature and date The contract may contain information such as signature and date. These pieces of information are important for determining the validity and timing of the contract.

[0014] The electronic contract service is a service for managing contracts. Specifically, it manages document data such as contracts held by the parties, including information such as who operated it at what time. In addition, the electronic contract service also has a function of managing document data agreed upon between the parties. The electronic contract service can, for example, manage information on the validity period of the electronic signature attached to the contract. Thus, the electronic contract service not only has basic functions related to contract management but also supports information sharing regarding contracts between the parties.

[0015] In this embodiment, an electronic contract refers to the exchange of electronic data obtained by digitizing a contract document over the Internet, with the contracting parties expressing their consent and affixing an electronic signature to the electronic data of the contract document. The contract document is typically a file of electronic data created using software for document creation and cannot be modified in content. The electronic data includes, for example, PDF files and the like. There are a contract document sender side and a contract document receiver side among the contracting parties. There is one or more approvers for approving the contract document in the electronic contract. Based on the contract document, the approver determines whether the contract can be concluded under the conditions indicated in the content of the contract document. When a contract is concluded between the parties through the electronic contract service, the above-mentioned electronic contract service may manage the contract document data related to the agreement.

[0016] Also, in this embodiment, the user who uses the system 1 may operate a PC (Personal Computer) or the like and perform a review of the contract document using a contract document review service or the like.

[0017] The contract document review service is a service for evaluating the contract document. For example, the contract document review service designates the contract document to be evaluated and performs the evaluation of the contract document. The contract document review service calculates, for example, an evaluation regarding the contract content, an evaluation regarding the contract risk, etc. for each clause of the contract document.

[0018] <1.1 Overall Configuration Diagram of the System> FIG. 1 is a block diagram showing an example of the overall configuration of the system 1 of this embodiment. As shown in FIG. 1, the system 1 includes a first device 10, a server 20 for an electronic contract service, a server 30 for a contract document review service, and a second device 70. In the system 1, the first device 10, the server 20 for the electronic contract service, the server 30 for the contract document review service, and the second device 70 are communicably connected to each other by a network 80.

[0019] The example of FIG. 1 shows a first device 10. The first device 10 indicates a device used by a first user. The first user refers to a user who uses the system 1. In this embodiment, the first user mainly refers to a user who uses a contract review service and checks a contract or an evaluation result of a contract, etc. within the system 1. The first user is, for example, a user who does not necessarily engage in legal work full-time, such as a management level, a project manager involved in a contract, a person in charge of contract negotiation, a person in charge of contract conclusion, etc. The first device 10 is realized by, for example, a PC, a smartphone, etc. The first device 10 provides an environment for operating the system 1 according to a program to the first user by executing the program.

[0020] It is assumed that the first device 10 is a device that receives an input operation from the first user.

[0021] The first device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage unit 16, and a processor 19.

[0022] The communication IF 12 is an interface for inputting and outputting signals so that the first device 10 can communicate with an external device.

[0023] The input device 13 is a device for receiving an input operation from the first user. The device for receiving an input operation is, for example, a pointing device such as a touch panel, a touch pad, a mouse, or a keyboard.

[0024] The output device 14 is a device (such as a display, a speaker, etc.) for presenting information to the first user.

[0025] The memory 15 is for temporarily storing a program and data processed by the program, etc. The memory 15 is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0026] The memory unit 16 is for storing data. The memory unit 16 is, for example, a flash memory or an HDD (Hard Disk Drive).

[0027] The processor 19 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0028] The example in FIG. 1 shows the server 20 of the electronic contract service. Hereinafter, the server 20 of the electronic contract service may be abbreviated and shown as the server 20.

[0029] The server 20 includes a communication IF 22, an input / output IF 23, a memory 25, a storage 26, and a processor 29.

[0030] The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with an external device.

[0031] The input / output IF 23 functions as an interface for an input device that receives input operations from users who use the electronic contract service and an output device that presents information to the users.

[0032] The memory 25 is for temporarily storing programs and data processed by programs, etc. The memory 25 is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0033] The storage 26 is for storing data. The storage 26 is, for example, a flash memory or an HDD (Hard Disk Drive).

[0034] The processor 29 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0035] Server 20 is a device that manages information such as information of users who use the electronic contract service and information of document data.

[0036] The example in FIG. 1 shows the server 30 of the contract review service. Hereinafter, the server 30 of the contract review service may be abbreviated and shown as the server 30.

[0037] The server 30 includes a communication IF 32, an input / output IF 33, a memory 35, a storage 36, and a processor 39.

[0038] The communication IF 32 is an interface for inputting and outputting signals so that the server 30 can communicate with an external device.

[0039] The input / output IF 33 functions as an interface between an input device for receiving an input operation from a user who uses the contract review service and an output device for presenting information to the user.

[0040] The memory 35 is for temporarily storing programs and data processed by programs and the like. The memory 35 is, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0041] The storage 36 is for storing data. The storage 36 is, for example, a flash memory or an HDD (Hard Disk Drive).

[0042] The processor 39 is hardware for executing an instruction set described in a program and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

[0043] The server 30 is a device that manages information such as information of users who use the contract review service and information of the results of evaluating the contract.

[0044] The example in FIG. 1 shows a second device 70. The second device 70 indicates a device used by a second user. The second user refers to a user who uses the system 1. In this embodiment, the second user mainly refers to a user who uses the contract review service in the system 1 and performs operations such as inputting information regarding the actions that the company should perform in the contract for the contract. The information regarding the actions that the company should perform in the contract is, for example, information regarding points that the second user wants the first user to confirm. The second user is, for example, a legal affairs person, a contract person, etc. The second device 70 is realized by, for example, a PC, a smartphone, etc. By executing a program, the second device 70 provides an environment for operating the system 1 according to the program to the second user.

[0045] Note that the functional configuration of the second device 70 is the same as the functional configuration of the first device 10 described below. Therefore, the description of the functional configuration of the second device 70 is omitted.

[0046] <1.2 Functional Configuration of the First Device 10> FIG. 2 is a diagram showing the functional configuration of the first device 10. The first device 10 includes an antenna 111, a first wireless communication unit 121, a processor 19, an operation reception unit 130, a storage unit 16, a memory 15, a display 132, an audio processing unit 140, a microphone 141, and a speaker 142.

[0047] The antenna 111 radiates the signal emitted by the first device 10 into space as radio waves. Also, the antenna 111 receives radio waves from space and supplies the received signal to the first wireless communication unit 121.

[0048] The first wireless communication unit 121 performs demodulation / modulation processing and the like for transmitting and receiving signals via an antenna 111 or the like so that the first device 10 can communicate with other communication devices. The first wireless communication unit 121 is a communication module for wireless communication including a tuner, a high-frequency circuit, etc., demodulates / modulates and performs frequency conversion on the wireless signals transmitted and received by the first device 10, and supplies the received signals to the processor 19.

[0049] The processor 19 controls the operation of the first device 10 by reading and executing a program stored in the storage unit 16. The processor 19 is realized by, for example, an application processor.

[0050] The operation reception unit 130 has a mechanism for receiving input operations of the first user. For example, the operation reception unit 130 is realized as a pointing device such as a mouse, a touch pad, a touch panel, a keyboard, a controller, a photographing means for sensing the movement of the end user's body as an input operation, etc. For example, the operation reception unit 130 senses the movement of a body part such as a hand or the expression of the end user's face as the movement of the end user's body, and receives the movement of these body parts etc. as an input operation. The operation reception unit 130 determines the type of operation such as whether the end user's operation is a flick operation or a tap operation based on the coordinates at which the end user touches a finger or the like on a touch panel or the like and receives the input operation.

[0051] The storage unit 16 is composed of a flash memory, a RAM (Random Access Memory), etc. Further, the storage unit 16 stores a program used by the first device 10 and various data received by the first device 10 from the server 20.

[0052] The display 132 displays data such as images, videos, texts, etc. according to the control of the processor 19. The display 132 is realized by, for example, a display device such as an LCD (Liquid Crystal Display), an organic EL (Electro Luminescence).

[0053] The voice processing unit 140 demodulates and modulates voice signals. The voice processing unit 140 modulates the signal provided by the microphone 141 and provides the modulated signal to the processor 19. Further, the voice processing unit 140 provides the voice signal to the speaker 142.

[0054] The microphone 141 receives voice input and provides a voice signal corresponding to the voice input to the voice processing unit 140.

[0055] The speaker 142 converts the voice signal provided by the voice processing unit 140 into voice and outputs the voice to the outside of the first device 10.

[0056] When the processor 19 operates according to the program, it exhibits functions as the input operation reception unit 191, the transmission / reception unit 192, the data processing unit 193, and the notification control unit 194. The input operation reception unit 191 performs processing to receive the input operation of the first user on the input device such as the operation reception unit 130. When the operation reception unit 130 is a touch device, for example, the input operation reception unit 191 determines the type of operation such as whether the operation of the first user is a flick operation or a tap operation based on the information of the coordinates where the first user touches the touch device with a finger or the like. The transmission / reception unit 192 performs processing for the first device 10 to transmit and receive data according to a communication protocol with an external device such as the server 20. The data processing unit 193 performs processing to perform calculations on the data received by the first device 10 according to the program and output the calculation results to a memory or the like. The notification control unit 194 performs processing such as displaying a display image on the display 132, outputting voice to the speaker 142, and generating vibration with a vibrator or the like as processing for presenting information to the user.

[0057] <1.3 Functional Configuration of the Server 20 of the Electronic Contract Service> Figure 3 is a diagram showing the functional configuration of the server 20 of the electronic contract service. As shown in Figure 3, the server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0058] The communication unit 201 performs processing for the server 20 to communicate with an external device.

[0059] The storage unit 202 stores various databases such as a user database 2021, a document data database 2022, and a document management database 2023.

[0060] The user database 2021 is a database for managing information of users who use the electronic contract service. Details will be described later.

[0061] The document data database 2022 is a database for managing information of document data in the electronic contract service. Details will be described later.

[0062] The document management database 2023 is a database for managing information of parties in the document data in the electronic contract service. Details will be described later.

[0063] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. By operating according to the program, the control unit 203 functions as a reception control module 2031 and a transmission control module 2032.

[0064] The reception control module 2031 controls the process by which the server 20 receives a signal from an external device according to a communication protocol.

[0065] The transmission control module 2032 controls the process by which the server 20 transmits a signal to an external device according to a communication protocol.

[0066] <1.4 Functional Configuration of Server 30 for Contract Review Service> Figure 4 is a diagram showing the functional configuration of server 30 for the contract review service. As shown in Figure 4, server 30 functions as a communication unit 301, a storage unit 302, and a control unit 303.

[0067] The communication unit 301 performs processing for the server 30 to communicate with external devices.

[0068] The storage unit 302 stores various databases such as a user database 3021, an argument database 3022, and a risk check database 3023.

[0069] The user database 3021 is a database for managing information of users who use the contract review service. Details will be described later.

[0070] The argument database 3022 is a database for managing information related to the arguments of the contract in the contract review service. Details will be described later.

[0071] The risk check database 3023 is a database for managing information related to the risk check of the contract in the contract review service. Details will be described later.

[0072] The control unit 303 is realized by the processor 39 of the contract review service reading a program stored in the storage unit 302 and executing instructions included in the program. By operating according to the program, the control unit 303 functions as a reception control module 3031, a transmission control module 3032, and a risk check module 3033.

[0073] The reception control module 3031 controls the processing for the server 30 to receive signals from external devices according to the communication protocol.

[0074] The transmission control module 3032 controls the process in which the server 30 transmits a signal to an external device according to a communication protocol.

[0075] The risk check module 3033 is a module that evaluates the risks of each clause of a contract for the server 30. The server 30 stores the results evaluated by the risk check module 3033 for each clause and the like in the risk check database 3023. Each record in the risk check database 3023 includes, for example, an item "risk check ID", an item "document data ID", an item "clause", an item "check result", and an item "priority". The server 30 stores, for example, the results evaluated by the risk check module 3033 in the item "check result". Details of each item will be described later. In addition, the risk check module 3033 may, for example, quantify the results evaluated for each clause and determine an evaluation value regarding the priority of the risk check with a three-level evaluation of low, medium, and high. The server 30 stores, for example, the evaluation value regarding the priority calculated by the risk check module 3033 in the item "priority". Also, the criteria for evaluating the priority of the risk check are, for example, as follows. The following is an example and is not limited to these. · If there are clauses in a contract with conditions unfavorable to the company side (for example, implementation of a significant price cut, remaining risks of causing losses to the company, etc.), it is determined that the risk of such clauses is high. · If there are clauses in a contract where the handling of confidential information is not properly regulated, since the risk of leakage of confidential information increases, it is determined that the risk of such clauses is high. · If there are clauses in a contract with legal deficiencies, it is determined that the risk of such clauses is high. · If no particular major problem is found in a clause, it is determined that the risk of such clause is low. In addition, the risk check module 3033 may calculate information such as comments and amendments using technologies such as machine learning based on the data accumulated in the past regarding the results evaluated for each clause. In addition, if the contract review service already has a function related to the risk check evaluation of the contract, such a function may be used.

[0076] Further, the server 30 may cooperate with the server 20 using an API or the like, and may automatically execute a risk check module 3033 or the like on the document data stored in the server 20.

[0077] <1.5 Conceptual diagram for explaining electronic contracts> FIG. 5 is a conceptual diagram for explaining electronic contracts. As shown in FIG. 5, the electronic contract system includes a user device 40 of the contract sender, a server 50 of the contract management service, and a user device 60 of the contract recipient.

[0078] First, the contract sender uploads the contract to the server 50 of the contract management service on the cloud by operating the user device 40 of the contract sender. The server 50 of the contract management service assigns an electronic signature of the contract sender to the contract committed by the contract sender to transmit.

[0079] The contract sender performs an operation to request the contract recipient to conclude an agreement. Specifically, the user device 40 of the contract sender receives an operation designating the contract recipient from the contract sender and transmits it to the server 50 of the contract management service. In the present embodiment, the user device 40 of the contract sender receives, from the contract sender, an operation of designating the respective email addresses of one or more contract recipients as information for identifying the contract recipient. The server 50 of the contract management service sends information for accessing the contract document to the recipient of the contract document to the email address of the recipient specified by the user of the contract document sender. In the present embodiment, the server 50 of the contract management service sends information for accessing the contract document to the device 60 of the user of the recipient of the contract document to the email address of the recipient specified by the user of the contract document sender. The information for accessing the contract document includes, for example, a link described as a URL (Uniform Resource Locator).

[0080] The recipient of the contract document performs an operation (such as clicking or tapping) to specify the information for accessing the contract document received on the device 60 of the user of the recipient of the contract document, and can check the content of the contract document on the server 50 of the contract management service online and conclude an agreement. The device 60 of the user of the recipient of the contract document presents a screen for receiving an operation indicating agreement with the contract document to the user of the device 60 of the recipient of the contract document, and receives an operation for agreement from the recipient of the contract document. If there is a defect in the contract content at this point, the server 50 of the contract management service may receive an operation from the recipient of the contract document indicating that the recipient does not agree to the contract.

[0081] The server 50 of the contract management service assigns the electronic signature of the recipient of the contract document to the contract document by receiving an operation from the recipient of the contract document indicating agreement with the contract document. The server 50 of the contract management service stores the contract document in a database for managing the contract document. Tampering with the contract document is prevented by the electronic signatures of both parties to the contract being assigned.

[0082] The present embodiment realizes such a cloud-based electronic contract service.

[0083] <2 Data Structure> FIG. 6, FIG. 7, and FIG. 8 are diagrams showing the data structure of the database stored in the server 20. FIG. 9, FIG. 10, and FIG. 11 are diagrams showing the data structure of the database stored in the server 30. Note that FIGS. 6, 7, 8, 9, 10, and 11 are examples and do not exclude data that is not described.

[0084] FIG. 6 is a diagram showing the data structure of the user database 2021. The user database 2021 is a database for managing information of users who use the electronic contract service. Each record in the user database 2021 of FIG. 6 includes an item "User ID", an item "Email address", an item "Name", an item "Company name", an item "Department", and an item "Position".

[0085] The item "User ID" indicates a unique ID for a user that is required when managing users of the electronic contract service in the electronic contract service. There are various forms of user IDs. For example, combinations of character strings, combinations of numbers and character strings, or email addresses, etc. can be mentioned. Generally, it is important for the user ID to be unique and it is designed not to be duplicated. For example, in the electronic contract service, when issuing an account for a user of the electronic contract service, the terminal of the user who uses the electronic contract service receives an input of email address registration from the user of the electronic contract service. In response to receiving the input of email address registration, the server 20 issues a user ID.

[0086] The item "Email address" is the email address of the user who uses the electronic contract service. The email address refers to the address necessary for sending and receiving emails.

[0087] The item "Name" is an item representing the name information of the user who uses the electronic contract service.

[0088] The item "Company Name" represents the name of the company to which the user using the electronic contract service belongs. The company name is one of the pieces of information for identifying the user, and when multiple users belong to the same company, grouping and statistical processing can be performed based on the company name.

[0089] The item "Department" represents the information of the department to which the user using the electronic contract service belongs within the company. The item representing the department information is one of the pieces of information for identifying the user and also includes information related to the user's job content, etc. The item "Department" is, for example, the Development Department, Information Security Department, Accounting Department, Legal Affairs Department, Intellectual Property Department, etc.

[0090] The item "Position" represents the role and duties of the user within the company to which the user using the electronic contract service belongs. The position is one of the pieces of information for identifying the user and also includes information related to the user's skills and job content, etc. The item "Position" is, for example, the department head, section chief, representative director, etc.

[0091] Figure 7 is a diagram showing the data structure of the document data database 2022. The document data database 2022 is a database for managing information on document data. Each record in the document data database 2022 in Figure 7 includes the item "Document Data ID", the item "Title", the item "Link", the item "Contract Conclusion Date", the item "Contract Start Date", and the item "Contract End Date".

[0092] The item "Document Data ID" indicates a unique ID for the document data, which is required when managing document data in the electronic contract service. For example, as the identification information of the document data, when Server 20 accepts the upload of the document data as the subject of the electronic contract, it includes unique information issued in association with the said document data. The unique information issued in association with the said document data is, for example, the identification information issued to the said document data, the link information for each terminal device to access the said document data, etc. The document data is, for example, a contract or the like. A contract is typically a file created by software for document creation and whose content cannot be modified. A contract is, for example, a PDF file or the like. The advantage of the document data ID is that it enables easy search, reference, and management of documents. For example, even when there are a large number of contracts, the necessary document data can be quickly identified using the document data ID. Also, the document data ID is used for version management, permission management, etc. of document data.

[0093] The item "Title" indicates the title name of the document data. The title name is a concise name representing each document data. Examples of the title of document data may indicate, for example, the type of contract. The title name of document data is, for example, "Confidentiality Agreement.pdf", "Contract Regarding Architectural Design Drawings.pdf", etc.

[0094] The item "Link" indicates a link to a cloud or the like that stores the data of the document data. By following the link, the server 20 can refer to information such as the file of the document data.

[0095] The item "Contract Conclusion Date" indicates the date on which the document data was concluded.

[0096] The item "Contract Start Date" indicates the date on which the contract of the document data started.

[0097] The item "Contract End Date" indicates the date on which the contract of the document data ended.

[0098] Figure 8 is a diagram showing the data structure of the document management database 2023. The document management database 2023 is a database for managing information related to the parties of document data. Each record in the document management database 2023 in Figure 8 includes the item "Document Management ID", the item "Document Data ID", the item "Sender", the item "Recipient", and the item "Approver".

[0099] The item "Document Management ID" indicates the identification information issued by, for example, the server 20 for each contract concluded by electronic contract. Specifically, the item "Document Management ID" is an ID unique to the electronic contract, which is necessary when managing each contract concluded by electronic contract among users.

[0100] The item "Document Data ID" is as described above.

[0101] The item "Sender" is an item that indicates the information of the sender of the contract document in the electronic contract service. Note that there may be cases where there are multiple senders of the contract document instead of just one. For the item "Sender", for example, if the user ID exists in the user database 2021 for the sender, the information of the user ID of the sender may be recorded.

[0102] The item "Recipient" is an item that indicates the information of the recipient of the contract document in the electronic contract service. Note that there may be cases where there are multiple recipients of the contract document instead of just one. For the item "Recipient", for example, if the user ID exists in the user database 2021 for the recipient, the information of the user ID of the recipient may be recorded.

[0103] The item "Approver" indicates the information of the approver in the contract document. Note that there may be multiple approvers instead of just one. For the item "Approver", for example, if the user ID exists in the user database 2021 for the approver, the information of the user ID of the approver may be recorded.

[0104] Figure 9 is a diagram showing the data structure of the user database 3021. The user database 3021 is a database for managing the information of users who use the contract document review service. Each record in the user database 3021 in Figure 9 includes the item "User ID", the item "Email address", the item "Name", the item "Company name", the item "Department", and the item "Position".

[0105] The item "User ID" indicates a unique ID for a user that is necessary when managing users of the contract review service in the contract review service. User IDs have various forms. For example, combinations of character strings, combinations of numbers and character strings, or email addresses, etc. can be mentioned. Generally, it is important for a user ID to be unique and it is designed not to duplicate. For example, in the contract review service, when issuing an account for a user of the contract review service, the terminal of the user who uses the contract review service receives an input of email address registration from the user of the contract review service. The server 30 issues a user ID in response to receiving the input of email address registration.

[0106] The item "Email address" is the email address of the user who uses the contract review service. The email address refers to the address necessary for sending and receiving emails.

[0107] The item "Name" is an item that represents the name information of the user who uses the contract review service.

[0108] The item "Company name" is an item that represents the name of the company to which the user who uses the contract review service belongs. The company name is one of the information for identifying the user, and when multiple users belong to the same company, grouping and statistical processing can be performed based on the company name.

[0109] The item "Department" is an item that represents the department information of the company to which the user who uses the contract review service belongs. The item representing the department information is one of the information for identifying the user and also includes information related to the user's job content, etc. The item "Department" is, for example, the Development Department, Information Security Department, Accounting Department, Legal Department, Intellectual Property Department, etc.

[0110] The item "Position" represents the role and duties in the company where the user who utilizes the contract review service belongs. The position is one of the pieces of information for identifying the user and also includes information regarding the user's skills and job content, etc. The item "Position" is, for example, department head, section chief, representative director, etc.

[0111] Figure 10 is a diagram showing the data structure of the argument database 3022. The argument database 3022 is a database for managing information regarding arguments related to the contract. Each record in the argument database 3022 of Figure 10 includes the item "Argument ID", the item "Document Data ID", the item "Risk Check ID", the item "Argument", the item "Explanation", the item "Corresponding Clause", the item "Action to be Taken", the item "Action Planned to be Taken by the Company", the item "Importance", and the item "Feedback".

[0112] The item "Argument ID" indicates a unique ID for an argument that is necessary when managing arguments related to the contract in the contract review service. For example, in the contract review service, the terminal of the user who utilizes the contract review service receives an input from the user of the contract review service to press a button for confirming (viewing) the contract and the arguments related to the contract. In response to receiving the input from the user of the contract review service to press a button for confirming (viewing) the contract and the arguments related to the contract, the server 30 issues an argument ID.

[0113] The item "Document Data ID" is as described above.

[0114] The item "Risk Check ID" indicates identification information issued, for example, by the server 30 regarding the result of the risk check for each contract. Specifically, the item "Risk Check ID" is a unique ID for the result of the risk check of the contract, which is necessary when managing the result of the risk check for each contract. For example, in a contract review service, the terminal of a user who uses the contract review service receives an input from the user of the contract review service to press a button for risk checking on the contract. In response to receiving the input from the user of the contract review service to press the button for risk checking, the server 30 issues an argument ID.

[0115] The item "Argument" is an item indicating the name of the argument regarding the contract. Specifically, the argument regarding the contract refers to, for example, the subject of discussion, important themes for opinion exchange, etc. in each contract. The item "Argument" is, for example, trademark usage rights, agreements at the time of price change, customer attribution after contract cancellation, etc. The operator of the contract review service may prepare several patterns in advance for the item "Argument". Also, for the item "Argument", the user of the contract review service may be able to input information about the argument arbitrarily. For example, the terminal of a user who uses the contract review service receives an input from the user of the contract review service for the name of the argument regarding the contract. In response to receiving the input of the name of the argument from the user of the contract review service, the server 30 updates the value of the item "Argument".

[0116] The item "Explanation" indicates information regarding the explanation of the argument. The item "Explanation" shows information about what the argument specifically is. The item "Explanation" is what makes the information regarding the item "Argument" clearer. The item "Explanation" is, for example, as follows. The following are examples and are not limited to these. When the item "Argument" is trademark usage rights, the item "Explanation" is, for example, something like "To what extent can the agent freely use the creative works presented in advertisements and exhibitions?" Also, when the item "Argument" is customer attribution after contract cancellation, the item "Explanation" is, for example, something like "After the cancellation of this contract, to which party, the vendor or the agent, does the customer ordered by the agent belong?" For the item "Explanation", the operator of the contract review service may prepare several patterns in advance regarding the content of the item "Explanation" in combination with the item "Points at Issue". The users of the contract review service may perform operations such as searching and specifying within the contract review service, and may view and use the information of the pre-prepared item "Explanation". Also, for the item "Explanation", the users of the contract review service may optionally input explanations. For example, the terminal of the user using the contract review service accepts input of comments on the explanation from the user of the contract review service for the item "Explanation" associated with the points at issue in the contract. The server 30 updates the value of the item "Explanation" in response to accepting the input of comments on the explanation from the user of the contract review service.

[0117] The item "Corresponding Clause" indicates the information of the clause in the contract corresponding to the point at issue. The item "Corresponding Clause" is, for example, Article 1, Article 2, Article 3, etc. There may be two or more clauses instead of just one for the item "Corresponding Clause". In the case where there is no clause in the contract corresponding to the point at issue, the item "Corresponding Clause" may be set as "None".

[0118] The item "Actions to be Taken" indicates information on what general actions should be taken regarding the point at issue. The item "Actions to be Taken" refers to principles and methods that can be widely and generally applied without depending on specific situations, specific industries, etc. However, different approaches may be required depending on the specific situation. For the item "Actions to be Taken", the users of the contract review service may optionally input a selection of importance. For example, the terminal of the user using the contract review service accepts input of comments from the user of the contract review service for the item "Actions to be Taken" associated with the points at issue in the contract. The server 30 updates the value of the item "Actions to be Taken" in response to accepting the input of comments from the user of the contract review service. In addition, for the item "Actions to be Taken", the server 30 may obtain data on actions to be taken in response to an argument by using an API or the like based on referenceable data of an external service (e.g., a service related to the legal check of a contract, a book related to the practical handling of a contract, etc.). The server 30 may store the obtained data as the value of the item "Actions to be Taken" in the argument database 3022. In addition, for the item "Actions to be Taken", based on the data accumulated in the argument database 3022 of the server 30, data on actions to be taken in response to an argument may be obtained from past data by using a technology such as machine learning. The server 30 may store the obtained data as the value of the item "Actions to be Taken" in the argument database 3022. When the item "Argument" is the right to use a trademark, the item "Actions to be Taken" refers to general guidelines, procedures, etc. that would normally be applied in a general business case. The item "Actions to be Taken" is merely general guidelines, procedures, etc., and also implies the meaning that it is necessary to respond flexibly according to specific situations.

[0119] The item "Actions Planned to be Performed by Oneself" indicates information on actions planned to be performed by the parties to the contract regarding the argument. Although the item "Actions Planned to be Performed by Oneself" is described as "oneself" here, in reality, it can be an individual, a team, or any party to the contract, not necessarily the company itself. Compared with the approach of what actions should generally be taken for the above-mentioned item "Actions to be Taken", the item "Actions Planned to be Performed by Oneself" is information on what actions should be taken by the parties to the contract under specific circumstances. For example, the terminal of a user using the contract review service accepts input of comments from the user of the contract review service for the item "Actions Planned to be Performed by Oneself" associated with the argument of the contract. The server 30 updates the value of the item "Actions Planned to be Performed by Oneself" in response to accepting the input of comments from the user of the contract review service. Note that there may be multiple types of "Actions to be Performed by the Company" instead of just one. The "Actions to be Performed by the Company" item is, for example, as follows. The following are examples and are not limited to these. For example, when the "Argument" item is related to the price, there may be multiple types of ranked actions in the "Actions to be Performed by the Company" item, such as "Pine: 100,000 yen or more, Bamboo: 300,000 yen or more, Plum: 500,000 yen or more". Also, for example, when the "Argument" item is the trademark usage right, there may be multiple types of actions in the "Actions to be Performed by the Company" item, such as "Proposal 1: Modify the clause text as 〇〇, Proposal 2: Delete the corresponding clause, Proposal 3: Sign a separate contract for this part".

[0120] The "Importance" item indicates the importance of the argument. The importance of the argument may be indicated by a three-level evaluation such as high, medium, and low, for example. For example, when the "Importance" item is high, it indicates that the importance of the argument is high. The "Importance" item may be automatically determined by the server 30 based on the following criteria for the importance of the argument, or the user of the contract review service may be able to arbitrarily select the importance. For example, the terminal of the user using the contract review service accepts an input of any one of the three-level evaluations of high, medium, and low from the user of the contract review service for the "Importance" item associated with the argument in the contract. The server 30 updates the value of the "Importance" item in response to receiving an input of any one of the three-level evaluations of high, medium, and low from the user of the contract review service. The criteria for the importance of the argument are, for example, as follows. The following are examples and are not limited to these. · An argument that mentions conditions unfavorable to the company side (for example, implementing a significant price discount, leaving a risk of incurring losses to the company, etc.) is determined to have a high importance · The argument that the risk of leakage of confidential information is extremely heightened is determined to be of high importance · The argument that mentions minor corrections such as typos and omissions is determined to be of low importance

[0121] The item "Feedback" is an item for recording what kind of input has been received from users who use the contract review service regarding the argument, etc. The item "Feedback" pertains to the operation of input regarding at least any one of approval, rejection, and comment. For example, the terminal of a user who uses the contract review service receives a comment from the user of the contract review service regarding the item "Actions to be taken by the company itself" associated with the argument of the contract. In response to receiving the comment from the user of the contract review service, the server 30 updates the value of the item "Feedback". The item "Feedback" is, for example, as follows. The following are examples and are not limited to these. · Regarding the argument, pertaining to the input of a comment received from the first user · Regarding the item "Actions to be taken by the company itself" associated with the argument, pertaining to the input of a comment received from the first user · Regarding the item "Actions to be taken by the company itself" associated with the argument, pertaining to the input of approval of Proposal 1 received from the first user · Regarding the item "Actions to be taken by the company itself" associated with the argument, pertaining to the input of rejection of Proposal 2 received from the first user

[0122] Figure 11 is a diagram showing the data structure of the risk check database 3023. The risk check database 3023 is a database for managing information related to the risk check of the contract. Each record of the risk check database 3023 in Figure 11 includes the item "Risk Check ID", the item "Document Data ID", the item "Clause", the item "Check Result", and the item "Priority".

[0123] The item "Risk Check ID" is as described above.

[0124] The item "Document Data ID" is as described above. The item "Document Data ID" in the risk check database 3023 indicates the information of the document data ID of the contract document to be reviewed.

[0125] The item "Clause" indicates the information of the clauses in the contract document. The item "Clause" is, for example, Article 1, Article 2, Article 3, etc.

[0126] The item "Check Result" shows the check result of the risk check for the clauses of the contract document. The item "Check Result" indicates information such as the evaluation result regarding the contract risk for each clause of the contract document. The item "Check Result" is calculated, for example, by the risk check module 3033 of the server 30.

[0127] The item "Priority" is the determination of the evaluation value regarding the priority of the risk check by quantifying the evaluation result for each clause of the contract document. The item "Priority" is calculated, for example, by the risk check module 3033 of the server 30, etc. The risk check module 3033 determines the evaluation value regarding the priority in a three-level evaluation of low, medium, and high by quantifying the evaluation result for each clause.

[0128] <Operation of the First Embodiment> Next, the operations of each device constituting the system 1 will be described.

[0129] FIG. 12 is a diagram showing the flow of processing regarding the evaluation result of the contract document.

[0130] As a premise, it is assumed that the server 30 stores the contract document data and the information regarding the evaluation result for each clause of the contract document.

[0131] In step S12031, the server 30 presents the results of evaluating each clause of the contract in an order regardless of the order of each clause of the contract. The order regardless of the order of each clause of the contract means an order that is not the order of each clause of the contract (the first clause, the second clause, the third clause,... from the top). The order regardless of the order of each clause of the contract is, for example, an order in which the items with the value of "priority" in the "priority" item of the risk check database 3023 are placed at the top and the items with the value of "low" in the "priority" item are placed at the bottom, in descending order with respect to the "priority" item. Also, the order regardless of the order of each clause of the contract is, for example, an order in which the items with the value of "importance" in the "importance" item of the risk check database 3023 are placed at the top and the items with the value of "low" in the "importance" item are placed at the bottom, in descending order with respect to the "importance" item. Note that the presentation methods may include tables, figures, texts, images, etc. The results of evaluating each clause of the contract are stored in the argument database 3022, the risk check database 3023, etc. The results of evaluating each clause of the contract are, for example, the information in the "check result" item of the risk check database 3023.

[0132] In step S12011, the first device 10 receives an operation of inputting feedback on the contract. The input of feedback on the contract is, for example, an operation of inputting regarding at least one of approval, rejection, and comment for a certain part of the contract.

[0133] In step S12032, the server 30 receives information on feedback on the contract.

[0134] In step S12033, the server 30 stores the information on feedback on the contract in the argument database 3022. The server 30 stores the information on feedback on the contract in the "feedback" item of the argument database 3022.

[0135] In step S12034, the server 30 presents feedback information regarding the contract. The target for presenting the feedback information regarding the contract is, for example, the second device 70 or the like.

[0136] FIG. 13 is a diagram showing the flow of processing related to actions in the contract.

[0137] In step S13071, the second device 70 receives an input operation regarding an action from the second user with respect to the contract. Here, the action indicates how the parties to the contract should respond regarding the points of the contract. Note that there may be not just one, but multiple types of inputs received for the action regarding the contract.

[0138] In step S13031, the server 30 receives information regarding an action.

[0139] In step S13032, the server 30 stores the information regarding the action in the argument database 3022. The server 30 stores the information regarding the action received in step S13031 in the item "Actions to be Performed by the Company" in the argument database 3022.

[0140] In step S13033, the server 30 presents the information regarding the action in association with the points of the contract. The server 30 may present, for example, the points of the contract, explanations of the points, information on the clauses corresponding to the points, actions to be taken regarding the points, actions the company plans to take regarding the points, etc. in tabular form. Each item corresponds to the following respectively. · Points of the contract: The item "Points" in the argument database 3022 · Explanation of the points: The item "Explanation" in the argument database 3022 · Information on the clauses corresponding to the points: The item "Corresponding Clauses" in the argument database 3022 · Actions to be taken regarding the points: The item "Actions to be Taken" in the argument database 3022 · Actions planned to be taken by the company regarding the issue: Item "Actions planned to be taken by the company" in the issue database 3022

[0141] In step S13011, the first device 10 receives an operation for inputting feedback on the contract. The input of feedback on the contract is, for example, an input operation regarding at least one of approval, rejection, and comment for a certain part of the contract. The first device 10 may receive, for example, an input operation such as selecting (approving) one action from among a plurality of types of actions planned to be taken by the company corresponding to the issue from the first user. In addition, when the action planned to be taken by the company corresponding to the issue relates to the modification of the contract, the server 30 may be configured to reflect it in the contract at any time in response to receiving an operation of pressing a button related to the action. For example, when the action planned to be taken by the company corresponding to the issue relates to the correction of minor typos and omissions, the server 30 may be configured to reflect the correction of typos and omissions in the contract at any time in response to receiving an operation of approving the action.

[0142] In step S13034, the server 30 receives feedback information on the contract.

[0143] In step S13035, the server 30 stores the feedback information on the contract in the issue database 3022. Each record in the issue database 3022 includes an item "issue ID", an item "document data ID", an item "risk check ID", an item "issue", an item "explanation", an item "corresponding clause", an item "action to be taken", an item "action planned to be taken by the company", an item "importance", and an item "feedback". The server 30 stores the feedback information on the contract in the item "feedback" of the issue database 3022.

[0144] In step S13036, the server 30 presents feedback information regarding the contract. The target for presenting the feedback information regarding the contract is, for example, the second device 70 or the like.

[0145] By doing as shown in FIG. 13, the first user can know information regarding actions in association with the points of the contract, and the labor for checking the contents of the contract is reduced.

[0146] FIG. 14 is a diagram showing the flow of processing regarding the presentation of points in the contract.

[0147] Step S13033 is as described above.

[0148] In step S14011, the first device 10 receives an input operation regarding condition specification for information regarding actions associated with the points of the contract. The first device 10 receives, for example, from the first user, an input operation for conditionally specifying only those without corresponding clauses regarding the presence or absence of corresponding clauses for the points. When there is no corresponding clause for a point, an element corresponding to the point is missing, so the possibility of a problem occurring with the point increases. That is, by doing as described above, the first user can grasp information only about those without corresponding clauses for points, which are highly likely to cause problems.

[0149] In step S14032, the server 30 receives information regarding condition specification.

[0150] In step S14033, the server 30, in response to the information regarding condition specification, presents information regarding actions associated with the points of the contract to the first device 10 in a state based on the condition. In step S14032, for example, when the server 30 receives from the first device 10 an input operation for conditionally specifying only those without corresponding clauses regarding the presence or absence of corresponding clauses for points, the server 30 extracts only those without corresponding clauses and presents them to the first device 10.

[0151] By doing so as shown in FIG. 14, it becomes possible to present the content of the contract in a form that is easier for the first user to view. This leads to a reduction in the effort for the first user to confirm the content of the contract.

[0152] <Screen Example> FIG. 15 is a diagram showing information regarding the evaluation result of the contract on the screen.

[0153] As described in step S12031, the server 30 presents the results of evaluating each clause of the contract in an order regardless of the order of each clause of the contract. FIG. 15 is an example of a screen example for presenting the results of evaluating each clause of the contract in an order regardless of the order of each clause of the contract on the first device 10.

[0154] Specifically, the first device 10 presents the following information on the dialog screen 1500. · Area 1501 is an area regarding the login name in the contract review service. · Area 1502 is an area showing the argument regarding the contract, the explanation of the argument, and the information of the clause corresponding to the argument of the contract. Each item corresponds to the following respectively. · Argument of the contract: Item "Argument" in the argument database 3022 · Explanation of the argument: Item "Explanation" in the argument database 3022 · Information of the clause corresponding to the argument: Item "Corresponding Clause" in the argument database 3022 Note that the area 1502 may be presented in a table format or the like so as to be visually easy for the first user to understand. · Area 1503 is an area showing information regarding the content of the contract. The information regarding the content of the contract is, for example, the information of the main text of the contract. · Area 1504 is an area that shows the risk check results of the contract. The area that shows the risk check results of the contract may show information such as what the risk check results were for each clause. The risk check results of the contract are presented on the first device 10 by referring to information such as the risk check database 3023. Also, area 1504 may appropriately change the information presented on the first device 10 based on the information of the item "priority" in the risk check database 3023 in the risk check results of the contract. For example, area 1504 may extract and present only the information regarding the clause corresponding to a high value of the item "priority" and the item "check result" of the risk check database 3023 for that clause based on the information of the item "priority".

[0155] Also, as described in FIG. 15, the first device 10 may present both an object that presents the arguments regarding the contract (e.g., area 1502) and an object that presents the results of evaluating each clause of the contract (e.g., area 1504). The object is used in the GUI and UI and is, for example, a window, frame, tab, box, panel, etc.

[0156] By presenting as shown in FIG. 15, there is an effect that it becomes even easier to grasp for the first user who needs to grasp the outline of the content of the contract and the arguments of the contract. This leads to a reduction in the effort for the first user to confirm the content of the contract.

[0157] FIG. 16 is a diagram showing on the screen the information regarding the order of the arguments of the contract.

[0158] As described in step S12031, the server 30 presents the results of evaluating each clause of the contract in an order regardless of the order of each clause of the contract. FIG. 16 is an example of a screen example presenting the results of evaluating each clause of the contract in an order regardless of the order of each clause of the contract on the first device 10.

[0159] Specifically, the first device 10 presents the following information on the dialog screen 1600. · Area 1501 is as described above. · Area 1502 is as described above. · Area 1503 is as described above. · Area 1504 is as described above. · Area 1601 is an area for specifying the order of the arguments. Area 1601 may receive a specification such as setting the order of the arguments in descending order of importance, for example. The server 30 refers to the value of the item "importance" in the argument database 3022 regarding the importance of the arguments. In response to receiving an operation related to specifying the order of the arguments from the first user in area 1601, the server 30 changes the display of area 1502. For example, the server 30 presents the display order of area 1502 from top to bottom in descending order of importance. By arranging in order of importance, the importance of each argument becomes clear, and the first user can focus on important arguments. This also enables the first user to concentrate on important aspects such as time and concentration when reviewing the contract.

[0160] FIG. 17 is a diagram showing information on the arguments and actions of the contract on the screen.

[0161] As described in step S13033, the server 30 presents information on actions in association with the arguments of the contract. FIG. 17 is an example of a screen example for presenting the arguments of the contract on the first device 10.

[0162] Specifically, the first device 10 presents the following information on the dialog screen 1700. · Area 1501 is as described above. · Area 1503 is as described above. · Area 1504 is as described above. · Region 1701 is a region that shows the arguments related to the contract, the explanations of the arguments, the information of the clauses corresponding to the arguments of the contract, the information of the actions to be taken, and the information of the actions that the company plans to implement. Each item corresponds to the following respectively. · Arguments of the contract: Item "Arguments" in the argument database 3022 · Explanation of the argument: Item "Explanation" in the argument database 3022 · Information of the clauses corresponding to the argument: Item "Corresponding Clauses" in the argument database 3022 · Actions to be taken for the argument: Item "Actions to be Taken" in the argument database 3022 · Actions that the company plans to implement for the argument: Item "Actions that the Company Plans to Implement" in the argument database 3022 Region 1701 may present these information in a table format or the like so as to be visually understandable to the first user. Note that in region 1701, as described in step S13011, the first device 10 may receive an operation for inputting feedback on the contract. The operation for inputting feedback on the contract is, for example, as follows. The following are examples and are not limited to these. · Receive input of comments from the first user regarding the arguments in region 1701 · Receive input of comments on proposal 1 from the first user regarding the item "Actions that the Company Plans to Implement" in region 1701 · Receive input of an approval-related operation from the first user regarding proposal 2 regarding the item "Actions that the Company Plans to Implement" in region 1701 · Receive input of a rejection-related operation from the first user regarding proposal 3 regarding the item "Actions that the Company Plans to Implement" in region 1701

[0163] As shown in FIG. 17, for the first user who is in the position of checking the contract, it has the effect of making it even easier to provide feedback on the contract. This leads to a reduction in the effort required for the first user to check the content of the contract.

[0164] FIG. 18 is a diagram showing information regarding the evaluation result of the contract on the screen.

[0165] As described in step S13033, the server 30 presents information regarding actions in association with the issues of the contract. Also, as described in FIG. 14, the server 30 may present information regarding actions associated with the issues of the contract in a state based on the said conditions in response to the information regarding condition specification. FIG. 18 is an example of a screen example presented in a state where the first device 10 performs condition specification on the issues of the contract.

[0166] Specifically, the first device 10 presents the following respective information on the dialog screen 1800. · Region 1501 is as described above. · Region 1503 is as described above. · Region 1504 is as described above. · Region 1701 is as described above. · Region 1801 is a region where condition specification can be performed on region 1701. By operating region 1801, for example, as the presence or absence of the clause corresponding to the issue of the contract, it is possible to present the result in a state where only those without the clause corresponding to the issue are extracted.

[0167] As shown in FIG. 18, presenting in a state based on the conditions has the effect of making it even easier for the first user who needs to grasp the outline etc. of the content and issues of the contract to grasp. This leads to a reduction in the effort required for the first user to check the content of the contract.

[0168] <Modification Example> (1) Utilization of the history of the contract The information stored in the argument database 3022 may be utilized for information transmission about the contract, the background of contract changes, the history of contract changes, version management, etc. The targets for utilizing this information include the parties to the contract (including inside and outside the company), internal users who want to share information with non - parties to the contract, users who want to inherit the details of the contract, etc.

[0169] (2) Screen mode selection The contract review service may be able to select the screen mode according to the attributes of the users who use the contract review service. For example, in FIG. 17, if the attribute of the user who uses the contract review service is a legal department employee, the first device 10 may display areas 1503 and 1504 and deliberately not display area 1701. Also, for example, in FIG. 17, if the attribute of the user who uses the contract review service is a user such as a management layer who does not necessarily engage in legal work full - time, the first device 10 may display areas 1503, 1504, and 1701 on one screen. By doing so, according to the attributes of the users who use the contract review service, each user can confirm the contract in a form that is easy to see and easy to use. This leads to a reduction in the effort for the users who use the contract review service to confirm the content of the contract.

[0170] As described above, some embodiments of the present disclosure have been explained. However, these embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are to be included in the scope of the invention and the gist thereof, as well as in the invention described in the claims and the equivalent scope thereof.

[0171] <Supplementary Note> What is described below is the supplementary note of the matters described in each of the above - mentioned embodiments. (Supplementary Note 1) A program for operating a computer, wherein the storage unit of the computer stores contract data and the results of evaluating each clause of the contract, and the program causes the processor of the computer to present to a first user the results of evaluating each clause of the contract in an order independent of the order of the clauses of the contract (step S12031).

[0172] (Appendix 2) In the presenting step (S12031), presenting in an order independent of the order of the clauses of the contract, presenting in the order of the importance of the arguments related to the contract (1600), the program described in (Appendix 1).

[0173] (Appendix 3) In the presenting step (S12031), presenting in an order independent of the order of the clauses of the contract, presenting the arguments related to the contract and the clauses of the contract in association with each other (1502), the program described in (Appendix 1).

[0174] (Appendix 4) In the presenting step (S12031), presenting in an order independent of the order of the clauses of the contract, presenting the presence or absence of the clauses of the contract associated with the arguments related to the contract (1502), the program described in (Appendix 3).

[0175] (Appendix 5) In the presenting step, presenting in an order independent of the order of the clauses of the contract, presenting only those clauses of the contract that are associated with the arguments related to the contract and have no such clauses with respect to the presence or absence of the clauses of the contract (1800), the program described in (Appendix 4).

[0176] (Appendix 6) The program further causes the processor to execute, in the presenting step (S12031), a step of presenting together an object presenting an argument related to the contract and an object presenting the results of evaluating each clause of the contract (1500), the program described in (Appendix 1).

[0177] (Appendix 7) In the storage unit of the computer, the arguments related to the contract and the actions that the parties to the contract should take with respect to the arguments related to the contract are stored in association with each other. The program causes the processor to further present, to the first user, the arguments related to the contract, the terms of the contract, and the actions that the parties to the contract should take, in association with each other (step 1701). The program described in (Appendix 1).

[0178] (Appendix 8) In the step (1701) of presenting, to the first user, the arguments related to the contract, the terms of the contract, and the actions that the parties to the contract should take, in association with each other, a plurality of types of actions that the parties to the contract should take are presented. The program described in (Appendix 7).

[0179] (Appendix 9) In the step (1701) of presenting, to the first user, the arguments related to the contract, the terms of the contract, and the actions that the parties to the contract should take, in association with each other, the program causes the processor to further receive, from the first user, an input operation regarding at least one of approval, rejection, and comment for the actions that the parties to the contract should take (step S13011). The program described in (Appendix 7).

[0180] (Appendix 10) A method for operating a computer, wherein in the storage unit of the computer, contract data and the results of evaluating each term of the contract are stored. The method includes a step (S12031) in which the processor of the computer presents the results of evaluating each term of the contract to the first user in an order independent of the order of the terms of the contract. The method.

[0181] (Appendix 11) An information processing apparatus including a control unit, wherein a storage unit stores contract document data and the results of evaluating each clause of the contract document, and the control unit presents to a first user the results of evaluating each clause of the contract document in an order independent of the order of the clauses of the contract document (step S12031).

Explanation of Signs

[0182] 1: System, 10: First device, 12: Communication IF, 13: Input device, 14: Output device, 15: Memory, 16: Storage unit, 19: Processor, 20: Server of electronic contract service, 22: Communication IF, 23: Input / output IF, 25: Memory, 26: Storage, 29: Processor, 30: Server of contract review service, 32: Communication IF, 33: Input / output IF, 35: Memory, 36: Storage, 39: Processor, 40: Device of user who is contract sender, 50: Server of contract management service, 60: Device of user who is contract receiver, 70: Second device, 80: Network, 111: Antenna, 121: First wireless communication unit, 130: Operation reception unit, 132: Display, 140: Audio processing unit, 141: Microphone, 142: Speaker, 191: Input operation reception unit, 192: Transmission / reception unit, 193: Data processing unit, 194: Notification control unit, 201: Communication unit, 202: Storage unit, 203: Control unit, 301: Communication unit, 302: Storage unit, 303: Control unit, 2021: Database of user data, 2022: Database of document data, 2023: Database of document management, 2031: Reception control module, 2032: Transmission control module, 3021: Database of user data, 3022: Database of argument, 3023: Database of risk check, 3031: Reception control module, 3032: Transmission control module, 3033: Risk check module

Claims

1. A program for operating a computer, wherein the storage unit of the computer stores contract data and the results of evaluating each clause of the contract, and the program causes the processor of the computer to present to a first user the results of evaluating each clause of the contract in an order independent of the order of the clauses of the contract. A program.

2. In the presenting step, presenting in an order independent of the order of the clauses of the contract, The program according to claim 1, wherein the program is presented in the order of importance of the arguments related to the contract.

3. In the presenting step, presenting in an order independent of the order of the clauses of the contract, The program according to claim 1, wherein the argument related to the contract and the clause of the contract are presented in association with each other.

4. In the presenting step, presenting in an order independent of the order of the clauses of the contract, The program according to claim 3, wherein the presence or absence of a clause of the contract associated with the argument related to the contract is presented.

5. In the presenting step, presenting in an order independent of the order of the clauses of the contract, The program according to claim 4, wherein only those clauses of the contract that are associated with the argument related to the contract and have no such clauses are presented with respect to the presence or absence of the clauses of the contract.

6. The program further causes the processor to In the presenting step, presenting both an object presenting the argument related to the contract and an object presenting the results of evaluating each clause of the contract. The program according to claim 1.

7. The storage unit of the computer stores in association with each other the argument related to the contract and the actions to be taken by the parties to the contract with respect to the argument related to the contract, and the program further causes the processor to present to the first user the argument related to the contract, the clause of the contract, and the actions to be taken by the parties to the contract in association with each other. The program according to claim 1.

8. In the step of presenting, in association with each other, the issues regarding the contract, the terms of the contract, and the actions to be taken by the parties to the contract, to the first user The program according to claim 7, wherein a plurality of types of actions to be taken by the parties to the contract are presented.

9. In the step of presenting, in association with each other, the issues regarding the contract, the terms of the contract, and the actions to be taken by the parties to the contract, to the first user The program further causes the processor to Regarding the actions to be taken by the parties to the contract The program according to claim 7, which executes a step of receiving, from the first user, an input operation regarding at least any one of approval, rejection, and comment.

10. A method for operating a computer, comprising: The storage unit of the computer stores contract data and the results of evaluating each term of the contract. The method includes the processor of the computer Executing a step of presenting, to a first user, the results of evaluating each term of the contract in an order independent of the order of the terms of the contract.

11. An information processing apparatus including a control unit, comprising: The storage unit stores contract data and the results of evaluating each term of the contract. The control unit Executes a step of presenting, to a first user, the results of evaluating each term of the contract in an order independent of the order of the terms of the contract.

Images