Program, method, and information processing apparatus

Abstract

To reduce the effort required for negotiating a contract.SOLUTION: A program for a computer causes a processor of the computer to execute the steps of: receiving an input of negotiation conditions from a first user who requests negotiation; presenting the negotiation conditions to a second user who is a proxy negotiator; and presenting information on the second user to the first user.SELECTED DRAWING: Figure 23

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 the content 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 may be made viewable between the parties to the contract while the conclusion process is being advanced. For example, when concluding a contract using an email address as the information identifying the parties to the contract, 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 advance the conclusion process by, for example, approving the contract document.

[0004] Japanese Patent Application Laid-Open No. 2021-152757 (Patent Document 1) stores information on the contract conditions of each past case in a storage device, calculates and displays the degree of agreement based on the contract conditions specified by the user in the contract and the contract conditions of each past case stored in the storage device (the required level specified by the user for each condition item that affects the negotiation), and every time the required level of any condition item is changed by the user, all past cases in which the required levels of all condition items currently specified by the user are equal to or higher are extracted from among the past cases in which information on the contract conditions is stored in the storage device, and the degree of agreement is calculated and displayed based on the extraction result.

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 a contract negotiation support device that can reduce the cost and labor required for contract negotiation. However, there is still room for improvement in reducing the labor required for contract negotiation even with the technology of Patent Document 1.

Means for Solving the Problems

[0007] One embodiment shown in the present disclosure is a program for operating a computer, the program causing a processor of the computer to execute steps of receiving an input of negotiation conditions from a first user who wishes to negotiate, presenting the negotiation conditions to a second user who acts on behalf of the negotiation, and presenting information on the second user to the first user.

Effects of the Invention

[0008] According to the present disclosure, it is possible to reduce the labor required for contract negotiation.

Brief Description of 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

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Mode for Carrying Out the Invention

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

[0011] <Outline of the First Embodiment> In the present embodiment, a user who uses the system 1 may operate a PC (Personal Computer) or the like and use functions related to negotiation of a contract or the like using a negotiation service or the like.

[0012] Functions related to negotiation of a contract or the like in the negotiation service include, for example, the following. The following are examples and are not limited thereto. · Function to request agency of negotiation · Function to apply for agency of negotiation · Function to match with regard to agency of negotiation · Function to display the result of evaluating negotiation conditions · Function to evaluate the result of negotiation · Function to display the scored result for the user who conducted agency of negotiation

[0013] Note that the use cases of the negotiation service are, for example, as follows. The following are examples and are not limited thereto. · Conditional negotiation accompanying the contract of a sports player, etc. (e.g., contract start, contract renewal) · Dispute over compensation (e.g., traffic accident, medical accident, labor problem, etc.) · When a small-scale enterprise wants to outsource contract negotiation when there is no or insufficient legal department (e.g., adjustment of negotiation conditions in a contract, check of a new contract, etc.) · When a small-scale enterprise wants to outsource contract negotiation when there is no or insufficient counsel (e.g., adjustment of contract language, negotiation against unfavorable conditions, etc.) · Negotiation regarding contracts and agreement documents between enterprises (e.g., price negotiation, change of contract conditions, etc.)

[0014] The document data such as contracts used in the negotiation service are, for example, of 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 · Service outsourcing contract · Transfer security agreement · M&A contract · Business transfer contract · Joint venture contract · Software development contract · Contracts related to intellectual property (license contracts, etc.) · Copyright assignment contract · Trademark license contract · License contract · Franchise contract · Board of directors meeting minutes · Contract regarding product manufacturing · Contract regarding architectural design drawings · Construction contract · Insurance contract · Consulting contract · Agency contract

[0015] Document data such as contracts may contain information such as the following. The following are examples and are not limited to these. · Subject of the contract and purpose of the contract The contract has a part describing the subject 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 conditions, etc. are included in its content. · Conditions of the contract and provisions of the contract The contract describes 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 warranties of the seller, etc. are included in its content. · Information such as signature and date The contract may contain information such as signature and date. These information are important for judging the validity and timing of the contract.

[0016] Also, in this embodiment, the user who uses the system 1 may operate a PC (Personal Computer) or the like and manage document data such as contracts using an electronic contract service or the like.

[0017] An electronic contract service is a service for managing contract documents. Specifically, it manages document data such as contract documents held by the parties, along with information such as who operated it and at what timing. 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 document. Thus, in addition to the basic functions related to contract document management, the electronic contract service also supports information sharing regarding contract documents among the parties.

[0018] In this embodiment, an electronic contract refers to electronically exchanging electronic data obtained by digitizing a contract document over the Internet, with the contracting parties expressing their consent, and attaching 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 whose content cannot be modified. 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. In an electronic contract, there is one or more approvers for approving the contract document. 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.

[0019] Also, in this embodiment, the user using 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.

[0020] A contract document review service is a service for evaluating a contract document. For example, a user of the contract document review service designates a contract document to be evaluated and conducts an evaluation of the contract document. The contract document review service may calculate, for example, the evaluation of negotiation conditions for each clause of the contract document. Note that the contract document review service may cooperate with a negotiation service and an electronic contract service to exchange various data.

[0021] <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 the present 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 negotiation service, a second device 70, and a server 90 for a contract review service. The system 1 has the first device 10, the server 20 for the electronic contract service, the server 30 for the negotiation service, the second device 70, and the server 90 for the contract review service connected to each other communicably via a network 80.

[0022] The example of FIG. 1 shows the 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 the present embodiment, the first user mainly refers to a user who inputs the content of negotiation conditions and requests a negotiation in the negotiation service among the system 1. The first device 10 is realized by, for example, a PC, a smartphone, or the like. The first device 10 provides an environment for operating the system 1 according to a program to the first user by executing the program.

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

[0024] 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.

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

[0026] The input device 13 is a device for receiving an input operation from the first user. Devices for receiving an input operation are, for example, pointing devices such as a touch panel, a touch pad, a mouse, and a keyboard.

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

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

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

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

[0031] The example of 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.

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

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

[0034] The input / output IF 23 functions as an input device for receiving input operations from users using the electronic contract service and an interface with an output device for presenting information to the users.

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

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

[0037] 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.

[0038] The server 20 is a device for managing information of users who use the electronic contract service, information of document data, etc.

[0039] The server 20 appropriately transmits data necessary for using the electronic contract service to the first device 10, thereby visualizing the situation of the electronic contract service in the first device 10. Further, the server 20 communicates with the first device 10 and transmits images, files, text data, etc. to the first device 10 according to the operations of each user. Similarly, the server 20 appropriately transmits data necessary for using the electronic contract service to the second device 70, thereby visualizing the situation of the electronic contract service in the second device 70. Further, the server 20 communicates with the second device 70 and transmits images, files, text data, etc. to the second device 70 according to the operations of each user.

[0040] The example of FIG. 1 shows the server 30 of the negotiation service. Hereinafter, the server 30 of the negotiation service may be abbreviated and also shown as the server 30.

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

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

[0043] The input / output IF 33 functions as an interface between an input device for receiving input operations from users who utilize the negotiation service and an output device for presenting information to the users.

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

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

[0046] 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.

[0047] The server 30 is a device for managing information of users who utilize the negotiation service.

[0048] The server 30 appropriately transmits data necessary for utilizing the negotiation service to the first device 10 to visualize the situation of the negotiation service in the first device 10. Further, the server 30 communicates with the first device 10 and transmits images, files, text data, etc. to the first device 10 according to the operations of users who utilize the negotiation service. Similarly, the server 30 appropriately transmits data necessary for utilizing the negotiation service to the second device 70 to visualize the situation of the negotiation service in the second device 70. Further, the server 30 communicates with the second device 70 and transmits images, files, text data, etc. to the second device 70 according to the operations of users who utilize the negotiation service.

[0049] 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 on the applicant side who uses the negotiation service to make a request for negotiation within the system 1. The second user is, for example, a lawyer, an expert familiar with a specific contract, a negotiation person, etc. The second device 70 is realized by, for example, a PC, a smartphone, etc. The second device 70 provides an environment for operating the system 1 according to a program to the second user by executing the program.

[0050] 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.

[0051] The example in FIG. 1 shows a server 90 for a contract review service. Hereinafter, the server 90 for the contract review service may be abbreviated as the server 90. Although not shown in FIG. 1, it is assumed that the server 90 includes a communication IF, an input / output IF, a memory, a storage, and a processor.

[0052] <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.

[0053] 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 gives the received signal to the first wireless communication unit 121.

[0054] The first wireless communication unit 121 performs modulation / demodulation 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., performs modulation / demodulation and frequency conversion of the wireless signals transmitted and received by the first device 10, and supplies the received signals to the processor 19.

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

[0056] The operation reception unit 130 has a mechanism for receiving the 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 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 on a touch panel or the like to receive the input operation.

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

[0058] 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).

[0059] The voice processing unit 140 performs modulation and demodulation of voice signals. The voice processing unit 140 modulates the signal provided from the microphone 141 and provides the modulated signal to the processor 19. Also, the voice processing unit 140 provides the voice signal to the speaker 142.

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

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

[0062] When the processor 19 operates according to a program, it exhibits functions as an input operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, and a notification control unit 194. The input operation reception unit 191 performs a process of receiving an input operation of a first user on an 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 a process 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 a process of performing calculations on the data received by the first device 10 according to a program and outputting the calculation result to a memory or the like. The notification control unit 194 performs processes such as displaying a display image on the display 132, outputting voice to the speaker 142, and generating vibration in a vibrator or the like as processes for presenting information to the user.

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

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

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

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

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

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

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

[0070] The reception control module 2031 controls processing for the server 20 to receive a signal from an external device according to a communication protocol.

[0071] The transmission control module 2032 controls processing for the server 20 to transmit a signal to an external device according to a communication protocol.

[0072] <1.4 Functional Configuration of Server 30 for Negotiation Service> FIG. 4 is a diagram showing the functional configuration of server 30 for the negotiation service. As shown in FIG. 4, server 30 functions as a communication unit 301, a storage unit 302, and a control unit 303.

[0073] The communication unit 301 performs processes for server 30 to communicate with external devices.

[0074] The storage unit 302 stores various databases such as a user database 3021, a skill database 3022, a project database 3023, a matching database 3024, and a scoring database 3025.

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

[0076] The skill database 3022 is a database for managing information related to the skills of users who use the negotiation service. Details will be described later.

[0077] The project database 3023 is a database for managing information related to projects in the negotiation service. Details will be described later.

[0078] The matching database 3024 is a database for managing information related to matching in the negotiation service. Details will be described later.

[0079] The scoring database 3025 is a database for managing information related to scoring in the negotiation service. Details will be described later.

[0080] The control unit 303 is realized by the processor 39 reading the program stored in the storage unit 302 and executing the instructions included in the program. By operating according to the program, the control unit 303 exhibits the functions shown as the reception control module 3031 and the transmission control module 3032.

[0081] The reception control module 3031 controls the process by which the server 30 receives signals from an external device according to a communication protocol.

[0082] The transmission control module 3032 controls the process by which the server 30 transmits signals to an external device according to a communication protocol.

[0083] <1.5 Functional Configuration of the Server 90 of the Contract Review Service> FIG. 5 is a diagram showing the functional configuration of the server 90 of the contract review service. As shown in FIG. 5, the server 90 exhibits the functions as a communication unit 901, a storage unit 902, and a control unit 903.

[0084] The communication unit 901 performs processes for the server 90 to communicate with an external device.

[0085] The storage unit 902 stores various databases such as the database 9021 of review results.

[0086] The database 9021 of review results is a database for managing information on the review results of the contract in the contract review service. Details will be described later.

[0087] The control unit 903 is realized by the processor of the contract review service reading the program stored in the storage unit 902 and executing the instructions included in the program. By operating according to the program, the control unit 903 exhibits the functions shown as the reception control module 9031, the transmission control module 9032, and the contract evaluation module 9033.

[0088] The reception control module 9031 controls the process in which the server 90 receives signals from an external device according to a communication protocol.

[0089] The transmission control module 9032 controls the process in which the server 90 transmits signals to an external device according to a communication protocol.

[0090] The contract evaluation module 9033 is a module in which the server 90 reviews and evaluates negotiation conditions and the like for each clause of a contract with respect to the contract. The contract evaluation module 9033 may, for example, quantify the results of evaluation for each clause and determine an evaluation value in a five - level evaluation from 1 to 5. Further, the contract evaluation module 9033 may calculate information such as comments and amendments using technologies such as machine learning from data accumulated in the past with respect to the results of evaluation for each clause. The server 90 stores the results of evaluation for each clause evaluated by the contract evaluation module 9033 in the review result database 9021. Each record in the review result database 9021 includes, for example, an item "review result ID", an item "document data ID", an item "clause", an item "evaluation value", and an item "evaluation comment". Details for each item will be described later. Note that if there already exist functions related to various evaluations of a contract in the contract review service, those functions may be used.

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

[0092] First, the contract sender uploads a 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 attaches the electronic signature of the contract sender to the contract committed to be sent by the contract sender.

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

[0094] The contract recipient performs an operation (such as clicking or tapping) to specify the information for accessing the contract received on the device 60 of the user of the contract recipient, and can view the content of the contract on the server 50 of the contract management service online and conclude the agreement. The device 60 of the user of the contract recipient presents a screen for receiving an operation indicating agreement with the contract to the user of the device 60 of the contract recipient and receives an operation for agreement from the contract recipient. If there are defects in the contract content at this point, the server 50 of the contract management service may receive an operation from the contract recipient indicating non - agreement with the contract.

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

[0096] This embodiment realizes such a cloud-based electronic contract service.

[0097] <2 Data Structure> FIG. 7, FIG. 8, and FIG. 9 are diagrams showing the data structure of the database stored in server 20. FIG. 10, FIG. 11, FIG. 12, FIG. 13, and FIG. 14 are diagrams showing the data structure of the database stored in server 30. FIG. 15 is a diagram showing the data structure of the database stored in server 90. Note that FIG. 7, FIG. 8, FIG. 9, FIG. 10, FIG. 11, FIG. 12, FIG. 13, FIG. 14, and FIG. 15 are examples, and do not exclude data not described.

[0098] FIG. 7 is a diagram showing the data structure of the document data database 2021. The document data database 2021 is a database for managing document data information. Each record in the document data database 2021 of FIG. 7 includes an item "document data ID", an item "title", an item "link", an item "contract conclusion date", an item "contract start date", and an item "contract end date".

[0099] 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 identification information for the document data, when server 20 accepts the upload of document data as an object of an electronic contract, it includes unique information issued in association with the document data. The unique information issued in association with the document data is, for example, identification information issued to the document data, link information for each terminal device to access the document data, etc. The document data is, for example, a contract document or the like. The contract document is typically a file created by software for document creation and whose content cannot be modified. The contract document 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. In addition, the document data ID is also used for version management, permission management, etc. of document data.

[0100] 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 names of document data are, for example, "Confidentiality Agreement.pdf", "Contract Regarding Architectural Design Drawings.pdf", etc.

[0101] The item "Link" indicates a link to a cloud or the like that stores the data of the document data. When the server 20 follows the link, it is possible to refer to information such as the file of the document data.

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

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

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

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

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

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

[0108] 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 2023 for the sender, the information of the user ID of the sender may be recorded.

[0109] 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 2023 for the recipient, the information of the user ID of the recipient may be recorded.

[0110] 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 2023 for the approver, the information of the user ID of the approver may be recorded.

[0111] Figure 9 is a diagram showing the data structure of the user database 2023. The user database 2023 is a database for managing the information of users who use the electronic contract service. Each record in the user database 2023 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".

[0112] The item "User ID" indicates a unique ID for a user that is necessary when managing users of the electronic contract service in the electronic contract service. User IDs come in various forms. For example, combinations of character strings, combinations of numbers and character strings, or email addresses, etc. Generally, it is important for the user ID to be unique and it is designed to avoid duplication. For example, in the electronic contract service, when issuing an account for a user of the electronic contract service, the terminal of the user using 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.

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

[0114] The item "Name" is an item representing the name information of the user.

[0115] The item "Company Name" is an item representing the name of the company to which the user 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.

[0116] The item "Department" is an item representing the department information of the company to which the user belongs. The item representing the department information is one of the pieces of information for identifying the user and also includes information regarding the user's job content, etc. The item "Department" is, for example, the Development Department, Information Security Department, Accounting Department, Intellectual Property Department, etc.

[0117] The item "Position" represents the role and duties of the user in the company to which the user 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.

[0118] Figure 10 is a diagram showing the data structure of the user database 3021. The user database 3021 is a database for managing information of users who use the negotiation service. Each record in the user database 3021 of Figure 10 includes the item "User ID", the item "Email address", the item "Name", the item "Profile image", and the item "Company name".

[0119] The item "User ID" indicates a unique ID for a user of the negotiation service that is required when managing users of the negotiation service in the negotiation 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 negotiation service, when issuing an account for a user of the negotiation service, the terminal of the user who uses the negotiation service receives an input of email address registration from the user of the negotiation service. The server 30 issues a user ID in response to receiving the input of email address registration.

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

[0121] The item "Name" is an item representing the name information of the user who uses the negotiation service.

[0122] The item "Profile Image" represents information about the profile image of a user who uses the negotiation service. The profile image is an image for visually identifying a user who uses the negotiation service.

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

[0124] Figure 11 is a diagram showing the data structure of the skill database 3022. The skill database 3022 is a database for managing information related to the skills of a user who uses the negotiation service. Each record in the skill database 3022 in Figure 11 includes the item "Skill ID", the item "User ID", the item "Category", the item "Skill Details", and the item "Qualification".

[0125] The item "Skill ID" indicates a unique ID for the skills of a second user that is required when managing information related to the skills of the second user in the negotiation service.

[0126] The item "User ID" is as described in Figure 10.

[0127] The item "Category" indicates information about the fields that the second user can handle when acting as an agent in negotiations. The item "Category" includes, for example, the following. The following are examples and are not limited to these. · Borrowing, debt restructuring · Traffic accident · Divorce, gender issues · Inheritance · Labor issues · Debt collection · Medical problems · Fraud victimization, consumer victimization · International, foreigner issues · Internet issues · Crime, criminal issues · Real estate, construction · Tax litigation · Corporate legal issues · Contracts of sports players

[0128] The item "Skill Details" indicates information on the details of the skill. The item "Skill Details" includes, for example, the following information. The following are examples and are not limited to these. · Activities in the field of expertise: Information on the activities in the field that the second user specializes in · Achievements: Specific details about the past achievements of the second user · Years of experience: The number of years of experience that the second user has been involved in the skill · Skill set: Information on the skill set that the second user possesses · Scope of provided services: Information on the scope of skills and services that can be provided · Languages that can be handled: Information on the languages (e.g., Japanese, English, etc.) that the second user can handle

[0129] The item "Qualifications" indicates information on the qualifications held by the second user. The item "Qualifications" may also contain descriptions related to qualifications for contract negotiation. The item "Qualifications" indicates information such as the presence or absence of a lawyer qualification, a patent attorney qualification, a certified public accountant qualification, and qualifications related to specific languages.

[0130] Figure 12 is a diagram showing the data structure of the project database 3023. A project, in this embodiment, refers to a series of operations temporarily carried out to achieve the purpose related to the negotiation requested by the first user. The project database 3023 is a database for managing information related to projects in the negotiation service. Each record in the database 3023 of the project in FIG. 12 includes an item "Project ID", an item "Creator", an item "Title", an item "Content", an item "Category", an item "Attached File", an item "Evaluation Result of Negotiation Conditions", an item "Budget", an item "Due Date", an item "Status", and an item "Evaluation of the Project".

[0131] The item "Project ID" indicates a unique ID for the project required when managing information related to the project in the negotiation service.

[0132] The item "Creator" indicates information about the creator of the project. Specifically, the item "Creator" stores information on the "User ID" of the user who created the project.

[0133] The item "Title" indicates information about the title of the project.

[0134] The item "Content" indicates information about the content of the project.

[0135] The item "Category" is as described above. Here, the item "Category" indicates information about the category associated with the project.

[0136] The item "Attached File" indicates information about the attached files in the project. The attached files are, for example, contract documents, materials with supplementary information regarding the negotiation, etc. Note that attached files such as contract documents may be managed by the server 20 in cooperation with the server 20 when proceeding with requests in the negotiation service.

[0137] The item "Evaluation Result of Negotiation Conditions" indicates information on the evaluation result of the negotiation conditions. Specifically, the item "Evaluation Result of Negotiation Conditions" includes the following information. The following are examples and are not limited to these. · Which part of the contract is disadvantageous · Information regarding the basis of the evaluation The item "Evaluation Results of Negotiation Conditions" may store the information received from the server 90.

[0138] The item "Budget" indicates information regarding the budget of the project.

[0139] The item "Deadline" indicates information regarding the deadline of the project.

[0140] The item "Status" indicates information regarding the status of the project. Specifically, the item "Status" is as follows. The following are examples and are not limited to these. · In progress: Indicates that the work of the project is in progress and not yet completed. · Completed: Indicates that the work of the project has been completed. · Not started: Indicates that the work of the project has not yet been undertaken. · Interrupted: Indicates that the project has been interrupted.

[0141] The item "Project Evaluation" indicates information regarding the evaluation of the project from the first user to the second user for the project. The item "Project Evaluation" is recorded, for example, in a five - level evaluation from 1 to 5 that quantifies the evaluation of the project. The five - level evaluation may specifically include the following information. The following are examples and are not limited to these. · 1 represents an evaluation indicating very low satisfaction. · 2 represents an evaluation indicating low satisfaction. · 3 represents an evaluation indicating medium satisfaction. · 4 represents an evaluation indicating high satisfaction. · 5 represents an evaluation indicating very high satisfaction.

[0142] Figure 13 is a diagram showing the data structure of the matching database 3024. The matching database 3024 is a database for managing information regarding matching in the negotiation service. Each record in the matching database 3024 of FIG. 13 includes an item "matching ID", an item "applied user", an item "project ID", and an item "status".

[0143] The item "matching ID" indicates a unique ID for the matching that is required when managing information related to the matching in the negotiation service.

[0144] The item "applied user" indicates information about the user who applied for the matching. Specifically, the item "applied user" stores the information of the item "user ID" of the user who applied for the matching.

[0145] The item "project ID" is as described above.

[0146] The item "status" indicates the status information of the matching. Specifically, the item "status" is as follows. The following are examples and are not limited to these. · Matched: Indicates the state where the matching was successful. · Not Matched: Indicates the state where the matching did not succeed. · Under Consideration: Indicates the state where one user has applied and the applied user is still under consideration.

[0147] FIG. 14 is a diagram showing the data structure of the scoring database 3025. The scoring database 3025 is a database for managing information related to scoring in the negotiation service. Each record in the scoring database 3025 of FIG. 14 includes an item "scoring ID", an item "user ID", an item "evaluation result", and an item "category".

[0148] The item "scoring ID" indicates a unique ID for the scoring that is required when managing information related to the scoring in the negotiation service.

[0149] The item "User ID" is as described above. Here, the item "User ID" indicates the person to be scored.

[0150] The item "Evaluation Result" indicates information on the evaluation result of the scoring. The item "Project Evaluation" records information obtained by quantifying, for example, an evaluation regarding the agency of negotiations for the target user.

[0151] The item "Category" indicates information on the category in the scoring. The item "Category" is as described with reference to FIG. 11. If, as a result of the scoring, a certain second user ranked fifth in the traffic accident category, the item "Category" in the scoring database 3025 stores "traffic accident", and the item "Evaluation Result" in the scoring database 3025 stores "fifth place".

[0152] FIG. 15 is a diagram showing the data structure of the review result database 9021. The review result database 9021 is a database for managing information regarding the review results of the contract documents. Each record in the review result database 9021 of FIG. 15 includes an item "Review Result ID", an item "Document Data ID", an item "Clause", an item "Evaluation Value", and an item "Evaluation Comment".

[0153] The item "Review Result ID" indicates identification information issued, for example, by the server 90 for each review result of the contract document. Specifically, the item "Evaluation Result ID" is a unique ID for the review result of the contract document, which is necessary when managing the review results of each contract document.

[0154] The item "Document Data ID" is as described above. The item "Document Data ID" in the review result database 9021 indicates information on the document data ID of the contract document to be reviewed.

[0155] The item "Clause" indicates the clause information in the contract. The item "Clause" is, for example, Article 1, Article 2, Article 3, etc.

[0156] The item "Evaluation Value" indicates the evaluation value regarding the negotiation conditions for the clauses of the contract. The item "Evaluation Value" is, for example, the evaluation value regarding the contract risk for each clause of the contract, etc. The item "Evaluation Value" is calculated, for example, by the contract evaluation module 9033 of the server 90. The item "Evaluation Value" is recorded, for example, in a five - level evaluation from 1 to 5, which quantifies the evaluation of the negotiation conditions for the clauses of the contract. The five - level evaluation of the item "Evaluation Value" may specifically include the following information. The following is an example and is not limited to these. · 1 indicates a value where the risk of the contract, etc. is very low. · 2 indicates a value where the risk of the contract, etc. is low. · 3 indicates a value where the risk of the contract, etc. shows a medium level of satisfaction. · 4 indicates a value where the risk of the contract, etc. is high. · 5 indicates a value where the risk of the contract, etc. is very high.

[0157] The item "Evaluation Comment" indicates the evaluation comment regarding the clauses of the contract. The item "Evaluation Comment" indicates the evaluation comments regarding the clauses of the contract, such as the good points about the clauses of the contract and the points unfavorable to the company in the clauses of the contract.

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

[0159] FIG. 16 is a diagram showing the flow of processing related to the input of negotiation conditions.

[0160] In step S16011, the first device 10 receives an operation of inputting negotiation conditions from the first user. The input of negotiation conditions specifically includes the following information. The following are examples and are not limited thereto. · Project title · Project content · Project attachment files (e.g., contract documents before negotiation, etc.) · Project budget · Project deadline · Project category · Information on which negotiation conditions are causing trouble · Information on how to modify which negotiation conditions · Content to be won in negotiation conditions (e.g., want to have company superiority in the description of contract terms, want to delete contract terms, etc.)

[0161] In step S16031, the server 30 receives an operation for inputting negotiation conditions.

[0162] In step S16032, the server 30 stores the information on the negotiation conditions received in step S16031 in the project database 3023. Each record in the project database 3023 includes an item "Project ID", an item "Creator", an item "Title", an item "Content", an item "Category", an item "Attachment File", an item "Evaluation Result of Negotiation Conditions", an item "Budget", an item "Deadline", an item "Status", and an item "Evaluation of Project". For example, the server 30 stores the content of the project title in the item "Title".

[0163] In step S16033, the server 30 refers to the project database 3023 and sends the information on the negotiation conditions to the server 90. Specifically, the server 30 sends the information of each item in the project database 3023 regarding the information on the negotiation conditions. For example, the server 30 sends the information of the attached contract as the information of the item "Attachment File" in the project database 3023 regarding the information on the negotiation conditions.

[0164] In step S16034, the server 30 receives the evaluation result of the negotiation conditions from the server 90. The details from step S16033 to step S16034 will be described later with reference to FIG. 19.

[0165] In step S16035, the server 30 stores the evaluation result of the negotiation conditions in the project database 3023. Each record in the project database 3023 includes items "project ID", "creator", "title", "content", "category", "attached file", "evaluation result of negotiation conditions", "budget", "due date", "status", and "evaluation of the project". For example, the server 30 stores the evaluation result of the negotiation conditions in the item "evaluation result of negotiation conditions" of the project database 3023.

[0166] In step S16036, the server 30 refers to the information in the project database 3023 and presents the negotiation conditions and the evaluation result of the negotiation conditions. The target for presenting the negotiation conditions and the evaluation result of the negotiation conditions may be the first device 10 or the second device 70. Doing so is valuable in itself for the first user because it is difficult to determine which parts of the contract are disadvantageous terms, and thus it becomes possible to know the disadvantageous terms and disadvantageous negotiation conditions. Also, doing so enables the second user to quickly grasp the points that need to be particularly confirmed in the contract by knowing which parts are disadvantageous terms.

[0167] FIG. 17 is a diagram showing the flow of processing related to the presentation of negotiation conditions.

[0168] Step S16036 is as described above.

[0169] In step S17071, the second device 70 receives an input operation for applying to a project related to the negotiation conditions.

[0170] In step S17031, the server 30 receives an input operation for applying to a project.

[0171] In step S17032, the server 30 stores it in the matching database 3024. Each record in the matching database 3024 includes an item "matching ID", an item "applied user", an item "project ID", and an item "status". For example, the server 30 stores the information of the "user ID" item of the user who performed the input operation for applying to the project in step S17031 in the item "applied user" of the matching database 3024.

[0172] FIG. 18 is a diagram showing the flow of processing related to matching.

[0173] Step S17032 is as described above.

[0174] In step S18031, the server 30 refers to information such as the user database 3021, the skill database 3022, and the scoring database 3025 of the user, and presents information about the second user who applied for the matching to the first user.

[0175] In step S18011, the first device 10 receives an input operation regarding the acceptance of the matching. The first device 10 receives, for example, an operation indicating acceptance of the matching for the application for the matching.

[0176] In step S18032, the server 30 receives an input operation regarding the acceptance of the matching.

[0177] In step S18033, the server 30 stores it in the matching database 3024. For example, when the server 30 receives an operation indicating acceptance of the matching from the first device 10, it stores "matched" in the "status" item of the matching database 3024.

[0178] In step S18034, the server 30 refers to the information in the matching database 3024 and presents the matching result. Note that the matching result may be presented to either the user who applied for the matching or the user who approved the matching.

[0179] FIG. 19 is a diagram showing the flow of processing related to the evaluation of negotiation conditions.

[0180] Step S16033 is as described above.

[0181] In step S19091, the server 90 receives the information related to the negotiation conditions transmitted from the server 30 in step S16033.

[0182] In step S19092, the server 90 evaluates the negotiation conditions. In step S13093, the server 90, for example, performs an evaluation of the negotiation conditions for each clause of the contract for the attached file (e.g., contract). When the server 90 performs an evaluation for each clause of the contract, it uses a contract evaluation module 9033 or the like. Note that even without specifying the contract, the server 90 may automatically perform an evaluation for each clause of the contract using an API or the like with respect to the information stored in the server 30 and using the contract information of the attached file stored in the server 30.

[0183] In step S19093, the server 90 stores the evaluation result of the negotiation conditions in the review result database 9021. Each record in the review result database 9021 includes an item "review result ID", an item "document data ID", an item "clause", an item "evaluation value", and an item "evaluation comment". The server 90 stores, for example, for the result of evaluating the first clause of the contract that is the negotiation condition, the first clause in the item "clause" and the evaluation result in the item "evaluation value".

[0184] In step S19094, the server 90 refers to the information in the review result database 9021 and transmits the evaluation result of the negotiation conditions to the server 30.

[0185] Step S16034 is as described above.

[0186] Figure 20 is a diagram showing the flow of processing related to the evaluation by the second user.

[0187] In step S20031, the server 30 refers to information such as the skill database 3022 and the project database 3023, and evaluates the proxy negotiation for the second user. What is described below is an example of how to determine the evaluation related to the proxy negotiation of the second user in the negotiation service. As an evaluation related to the proxy negotiation of the second user, the server 30 may, for example, refer to information such as the project database 3023 and calculate the number of cases that the second user has handled in the negotiation service in the past. The server 30 may highly evaluate the second user with a large number of cases handled in the past. In addition, as an evaluation related to the proxy negotiation of the second user, the server 30 may, for example, refer to information such as the project database 3023 and calculate the number of cases that the second user has handled in the negotiation service in the past by category. In addition, the server 30 may, for example, parameterize each item such as the skill database 3022 and the project database 3023, then score each parameterized item, and perform an evaluation related to the proxy negotiation of the second user. Note that the server 30 may, for example, weight specific items so as to emphasize the item "project evaluation" in the project database 3023, score, and perform an evaluation. Also, the server 30 may, for example, weight the item "qualification" in the skill database 3022 so that having a lawyer qualification leads to a high evaluation, score, and perform an evaluation. In addition, the server 30 may further perform a comprehensive evaluation regarding the proxy negotiation for the second user by multiplying the results of the above-mentioned count aggregation, scoring, and evaluation. By implementing as described above, the server 30 refers to information such as the skill database 3022 and the project database 3023, and performs an evaluation regarding the proxy negotiation for the second user.

[0188] In step S20032, the server 30 stores the evaluation information calculated in step S20031 in the scoring database 3025. Each record in the scoring database 3025 includes, for example, an item "scoring ID", an item "user ID", an item "evaluation result", and an item "category". For example, when a certain second user ranks 5th in the traffic accident category, the server 30 stores "traffic accident" in the "category" item of the scoring database 3025 and "5th place" in the "evaluation result" item of the scoring database 3025.

[0189] In step S20033, the server 30 refers to the information in the scoring database 3025 and presents an evaluation regarding the proxy negotiation for the second user. The evaluation regarding the proxy negotiation for the second user presents, for example, the following information. The following is an example and is not limited thereto. · The ranking of the second user in the overall negotiation service ranking · The ranking of the second user in each category ranking · The number of cases the second user has handled in the negotiation service in the past (it may also be the number of cases for each category) · Regarding the projects the second user has handled in the negotiation service in the past, the average value of the evaluations from the first user

[0190] <Example screen> FIG. 21 is a diagram showing information regarding the input of negotiation conditions on the screen.

[0191] As described in step S16011, the first device 10 receives an operation for inputting negotiation conditions. FIG. 21 is an example of a screen for receiving an operation for inputting negotiation conditions on the first device 10.

[0192] Specifically, the first device 10 presents the following information on the dialog screen 2100. · Area 2101 is an area related to the login name in the negotiation service. · Area 2102 is an area for inputting information related to negotiation conditions. The area for inputting information related to negotiation conditions is, for example, for inputting the following information. The following is an example and is not limited to these. · Title · Content · Category · Budget · Delivery date · Attachment · Button 2103 is a button for determining the input of negotiation conditions in response to an input operation from the first user. For example, in response to an operation where the first user presses button 2103, the first device 10 transmits information related to the negotiation conditions to the server 30.

[0193] FIG. 22 is a diagram showing information related to the evaluation of negotiation conditions on the screen.

[0194] As described in step S16036, the server 30 presents the negotiation conditions and the evaluation results of the negotiation conditions. FIG. 22 is an example of a screen for presenting the negotiation conditions and the evaluation results of the negotiation conditions on the first device 10.

[0195] Specifically, the first device 10 presents the following information on the dialog screen 2200. · Area 2101 is as described above. · Area 2201 is an area for presenting contract information. The area for presenting contract information is, for example, the file name of the contract, the text of the contract, etc. · Area 2202 is an area for presenting the evaluation results of negotiation conditions. The evaluation results of the negotiation conditions present, for example, the evaluation information in each contract, etc. · Area 2203 is an area for showing information on the basis for evaluating negotiation conditions. · Area 2204 is an area for showing the clauses regarding the basis for evaluating the contract. For example, when Article 3 of the contract is a part related to a major basis in the evaluation of the contract, Area 2204 may present Article 3 of the contract in a manner that is easy for the first user to recognize (for example, in bold, underlined, highlighted, etc.). · Button 2205 is a button for determining the input of negotiation conditions in response to an input operation from the first user. For example, in response to the operation of the first user pressing Button 2205, the first device 10 receives an operation indicating that it will publicly request a negotiation service from the server 30.

[0196] By doing so, the first user can grasp what problems exist in the negotiation conditions and then publicly request a negotiation service.

[0197] Figure 23 is a diagram showing information related to the presentation of negotiation conditions on the screen.

[0198] As described in step S16036, the server 30 presents the negotiation conditions and the evaluation results of the negotiation conditions. Figure 23 is an example of a screen example for presenting the negotiation conditions and the evaluation results of the negotiation conditions on the second device 70.

[0199] Specifically, the second device 70 presents the following information on the dialog screen 2300. · Area 2101 is as described above. · Area 2201 is as described above. When presenting on the second device 70, Area 2201 may be in a state where some information is hidden based on regulations regarding information confidentiality, etc. · Area 2202 is as described above. · Area 2203 is as described above. · Area 2301 is an area for presenting the request content of the first user. · Button 2302 is a button for determining an input to apply for a request regarding negotiation conditions in response to an input operation from the second user. For example, in response to an operation where the second user presses button 2302, the second device 70 transmits information on the input to apply for a request regarding negotiation conditions to the server 30.

[0200] FIG. 24 is a diagram showing information regarding the second user on the screen.

[0201] As described in step S18031, the server 30 presents the information of the second user who has applied for matching to the first user. FIG. 24 is an example of a screen example for presenting the information of the second user who has applied for matching to the first user.

[0202] Specifically, the first device 10 presents the following information on the dialog screen 2400. · Area 2101 is as described above. · Area 2401 is an area for presenting the request content of the first user. · Area 2402 is an area for presenting the information of the second user who has applied for matching. The area for presenting the information of the second user who has applied for matching presents, for example, the following information. The following is an example and is not limited to these. · Name of the second user · Company name to which the second user belongs · Profile image of the second user · Category in which the second user specializes · Ranking of the overall ranking of the second user · Ranking of the ranking for each category of the second user · Number of cases the second user has handled in the past in the negotiation service (it may also be the number of cases for each category) · Area 2403 is an area that presents information on the ranking order for each category. For example, in response to an operation where the first user presses area 2403, a transition may be made to a screen such as FIG. 25 described later. · Button 2404 is a button that determines the input of negotiation conditions in response to an input operation from the first user. For example, in response to an operation where the first user presses button 2404, the first device 10 transmits information regarding the negotiation conditions to the server 30.

[0203] By doing so, for the first user, information on the second user who applied for matching becomes known, and it becomes easier to make a judgment to request negotiation.

[0204] FIG. 25 is a diagram showing information on the evaluation of the second user on the screen.

[0205] The negotiation service may present the result of evaluating the second user in a ranking format or the like. FIG. 25 is an example of a screen example presenting information on the evaluation of the second user.

[0206] Specifically, the first device 10 presents the following information on the dialog screen 2500. · Area 2101 is as described above. · Area 2501 is information regarding the target of the ranking. Specifically, the information regarding the target of the ranking is, for example, the ranking of the traffic dispute category or the like. · Area 2502 is an area that presents the result of evaluating the second user in the negotiation service. The area that presents the result of evaluating the second user presents, for example, the following information. The following is an example and is not limited thereto. · Name of the second user · Profile image of the second user · Evaluation value of the second user · Area for requesting the second user · Area 2503 is an area for requesting the second user. For example, in response to an operation where the first user presses area 2503, the first device 10 may send information such as a request to the second user to the server 30.

[0207] By doing so, for the first user, the information of the second user becomes known, and it becomes easier to make a determination to request negotiation.

[0208] 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 and gist of the invention, and are also to be included in the invention described in the claims and the equivalent scope thereof.

[0209] <Supplementary Note> What is described below is the supplementary note of the matters described in each of the above embodiments. (Supplementary Note 1) A program for operating a computer, the program causing a processor of the computer to execute a step (S16011) of receiving an input of negotiation conditions from a first user who desires negotiation, a step (S16036) of presenting the negotiation conditions to a second user who acts on behalf of the negotiation, and a step (S18031) of presenting information of the second user to the first user.

[0210] (Supplementary Note 2) The program further causes the processor to execute a step (S16034) of obtaining an evaluation result of the negotiation conditions and a step (S16036) of presenting the obtained evaluation result of the negotiation conditions to the first user, the program according to (Supplementary Note 1).

[0211] (Supplementary Note 3) Display a screen for receiving a request operation to request a proxy negotiation for the first user, and on the screen, display the evaluation result of the negotiation conditions for the first user (2200). In response to receiving the request operation from the first user, present the negotiation conditions to the second user. The program described in (Appendix 2).

[0212] (Appendix 4) The program further causes the processor to execute a step of obtaining the evaluation result of the negotiation conditions (S16034). In the step of presenting the negotiation conditions, present the negotiation conditions and the evaluation result of the negotiation conditions. The program described in (Appendix 1).

[0213] (Appendix 5) In the step of presenting the information of the second user (S18031), present the past performance regarding the proxy negotiation of the second user (2400). The program described in (Appendix 1).

[0214] (Appendix 6) The program further causes the processor to execute a step of evaluating the proxy negotiation of the second user based on the past performance regarding the proxy negotiation of the second user (S20031). The evaluating step evaluates the proxy negotiation of the second user based on at least any one of the information on the number of proxy negotiations performed by the second user, the evaluation information from the first user regarding the proxy negotiations performed by the second user, and the skill information regarding the proxy negotiations of the second user. In the step of presenting the information of the second user (S18031), present the evaluation result of the second user. The program described in (Appendix 1).

[0215] (Appendix 7) A method for operating a computer, the method comprising: a step of receiving an input of negotiation conditions from a first user who desires a negotiation (S16011); a step of presenting the negotiation conditions to a second user who acts as a proxy for the negotiation (S16036); and a step of presenting the information of the second user to the first user (S18031).

[0216] (Appendix 8) An information processing apparatus including a control unit, wherein the control unit executes a step (S16011) of receiving an input of negotiation conditions from a first user who desires negotiation, a step (S16036) of presenting the negotiation conditions to a second user who substitutes for the negotiation, and a step (S18031) of presenting information of the second user to the first user.

Explanation of Signs

[0217] 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 negotiation service, 32: Communication IF, 33: Input / output IF, 35: Memory, 36: Storage, 39: Processor, 40: Device of the user who is the contract document sender, 50: Server of contract management service, 60: Device of the user who is the contract document receiver, 70: Second device, 80: Network, 90: Server of contract document review service, 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, 901: Communication unit, 902: Storage unit, 903: Control unit, 2021: Database of document data, 2022: Database of document management, 2023: Database of users, 2031: Reception control module, 2032: Transmission control module, 3021: Database of users, 3022: Database of skills, 3023: Database of projects, 3024: Database of matching, 3025: Database of scoring, 3031: Reception control module, 3032: Transmission control module, 9021: Database of review results, 9031: Reception control module, 9032: Transmission control module, 9033: Contract document evaluation module

Claims

1. A program for operating a computer, wherein the program causes a processor of the computer to receive an input of negotiation conditions from a first user who wishes to negotiate, present the negotiation conditions to a second user who acts on behalf of the negotiation, present information of the second user to the first user, and execute the steps, a program.

2. The program further causes the processor to obtain an evaluation result of the negotiation conditions, present the obtained evaluation result of the negotiation conditions to the first user, and execute the steps, the program according to claim 1.

3. display a screen for receiving a request operation for requesting the first user to act on behalf of the negotiation, display an evaluation result of the negotiation conditions to the first user on the screen, present the negotiation conditions to the second user in response to receiving the request operation from the first user, the program according to claim 2.

4. The program further causes the processor to execute a step of obtaining an evaluation result of the negotiation conditions, present the negotiation conditions and the evaluation result of the negotiation conditions in the step of presenting the negotiation conditions, the program according to claim 1.

5. In the step of presenting information of the second user, present a track record regarding acting on behalf of past negotiations of the second user, the program according to claim 1.

6. The program further causes the processor to execute a step of evaluating acting on behalf of the negotiation of the second user based on a track record regarding acting on behalf of past negotiations of the second user, the step of evaluating is information on the number of cases of acting on behalf of negotiations performed by the second user, information on an evaluation from the first user regarding acting on behalf of negotiations performed by the second user, information on skills regarding acting on behalf of negotiations in the second user, evaluate acting on behalf of the negotiation of the second user based on at least any one of the above, in the step of presenting information of the second user, present an evaluation result of the second user, the program according to claim 1.

7. A method for operating a computer, wherein the method causes a processor of the computer to receive an input of negotiation conditions from a first user who wishes to negotiate, Presenting the negotiation conditions to a second user who acts on behalf of the negotiation; Presenting information of the second user to the first user, a method for executing.

8. An information processing apparatus including a control unit, wherein the control unit Receiving an input of negotiation conditions from a first user who wishes to negotiate; Presenting the negotiation conditions to a second user who acts on behalf of the negotiation; Presenting information of the second user to the first user, an information processing apparatus for executing.

Images