JP2024031109A - Contract template management program, information processing device, information processing system, information processing method - Google Patents

Abstract

The present invention provides a contract template management program, an information processing device, a system, and a method for legal personnel to obtain suitable contract templates. A contract template management program for storing an electronic contract template in a computer including a processor and a storage unit, the processor includes a contract reception step of receiving a contract template related to a contract from a first user; A contract template storage process including a contract storage step that stores the contract template received in the contract reception step, and a contract template storage process that includes a contract storage step that stores the contract template received in the contract reception step, and a predetermined contract template among the contract templates stored in the contract storage step from a second user different from the first user. A contract template proposal process including a contract selection step of accepting a request to be selected and a contract output step of outputting a predetermined contract template to the second user in response to the request received in the contract selection step is executed. [Selection diagram] Figure 16

Description

The present disclosure relates to a contract template management program, an information processing device, an information processing system, and an information processing method.

With the development and spread of computer technology, documents that were previously paper-based are being digitized. For example, it is being considered that documents such as contracts that require the signatures and seals of the parties involved will be managed using electronic data.
Patent Document 1 discloses a document processing program and an information processing device that present the contract status of an organization based on the contents of a contract.

Japanese Patent Application Publication No. 2020-190905

In electronic contract procedures between multiple users, a contract document may be created from a template such as a model. When legal personnel prepare contract documents, they generally refer to templates provided in books, etc. However, there is a problem in that it is difficult for legal personnel and the like to obtain suitable contract forms, making it difficult to efficiently create contract documents.
Therefore, the present disclosure has been made to solve the above problems, and its purpose is to provide a technique for legal personnel and the like to obtain suitable contract forms.

A contract template management program for storing an electronic contract template in a computer including a processor and a storage unit, the processor comprising: a contract reception step for receiving a contract template related to a contract from a first user; and a contract reception step. a contract storage step of storing a contract template received in the contract storage step; and a contract selection step of receiving a request from a second user different from the first user to select a predetermined contract template from among the contract templates stored in the contract storage step. and a contract output step of outputting a predetermined contract template to a second user in response to a request received in the contract selection step.

According to the present disclosure, a user can efficiently obtain a template of a contract document.

1 is a block diagram showing the functional configuration of system 1. FIG. 1 is a block diagram showing the functional configuration of a server 10. FIG. 2 is a block diagram showing the functional configuration of a first user terminal 20. FIG. 3 is a block diagram showing the functional configuration of a second user terminal 30. FIG. 3 is a diagram showing a data structure of a user table 1012. FIG. 3 is a diagram showing the data structure of a group table 1013. FIG. 3 is a diagram showing the data structure of a document table 1014. FIG. 3 is a diagram showing a data structure of a confirmation table 1015. FIG. 3 is a diagram showing the data structure of an input item table 1016. FIG. 3 is a diagram showing the data structure of a contract group table 1017. FIG. 3 is a diagram showing a data structure of a template table 1018. FIG. 3 is a flowchart showing the operation of contract creation processing. 3 is a flowchart showing the operation of contract confirmation processing. 3 is a flowchart showing the operation of contract template storage processing. It is a flowchart showing the operation of score calculation processing. 3 is a flowchart showing the operation of contract template proposal processing. This is an example screen showing the operation of contract creation processing. This is an example of a screen showing a confirmation request message notified to the second user terminal 30. This is an example screen showing the operation of contract confirmation processing. It is an example of a screen showing a conclusion completion message notified to the first user terminal 20. This is an example screen showing the operation of contract template proposal processing. 2 is a block diagram showing the basic hardware configuration of a computer 90. FIG.

Embodiments of the present disclosure will be described below with reference to the drawings. In all the figures explaining the embodiments, common components are given the same reference numerals and repeated explanations will be omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all of the components shown in the embodiments are essential components of the present disclosure. Furthermore, each figure is a schematic diagram and is not necessarily strictly illustrated.

<Configuration of system 1>
A system 1 in the present disclosure is an information processing system for realizing a contract information service that stores and manages electronic contract forms (contract templates) used when creating contract documents.
In the system 1 according to the present disclosure, a user can freely upload a contract template, and the user can obtain contract templates uploaded by other users by downloading them. In other words, the system 1 according to the present disclosure is a system that can provide a platform service that allows a plurality of users to share a contract template.
Further, the user can use a contract template uploaded by another user as it is or edit it to create a contract document, and use the contract template to conclude a contract with other parties to the contract. That is, the system 1 according to the present disclosure includes a service that provides a service for creating a contract document and a service for concluding an electronic contract with another user.
The system 1 includes information processing devices such as a server 10, a first user terminal 20, and a second user terminal 30, which are connected via a network N.
FIG. 1 is a block diagram showing the functional configuration of the system 1. As shown in FIG.
FIG. 2 is a block diagram showing the functional configuration of the server 10.
FIG. 3 is a block diagram showing the functional configuration of the first user terminal 20.
FIG. 4 is a block diagram showing the functional configuration of the second user terminal 30.

Each information processing device is composed of a computer including an arithmetic unit and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. Regarding each of the server 10, the first user terminal 20, and the second user terminal 30, explanations that overlap with the basic hardware configuration of the computer and the basic functional configuration of the computer, which will be described later, will be omitted.

<Configuration of server 10>
The server 10 is an information processing device that provides electronic contract services between multiple users. The server 10 is an information processing device that provides a service for storing and managing electronic contract forms (contract templates) used when creating contract documents.
The server 10 includes a storage section 101 and a control section 104.

<Configuration of storage unit 101 of server 10>
The storage unit 101 of the server 10 includes an application program 1011, a user table 1012, a group table 1013, a document table 1014, a confirmation table 1015, an input item table 1016, a contract group table 1017, and a template table 1018.

The application program 1011 is a program for causing the control unit 104 of the server 10 to function as each functional unit.

The user table 1012 is a table that stores and manages information about member users (hereinafter referred to as users) who use the service. When a user registers to use a service, the user's information is stored in a new record in the user table 1012.
This allows the user to use the service according to the present disclosure. Note that in the present disclosure, users who use services do not necessarily need to be registered in the user table 1012.
The user table 1012 is a table having user ID as a primary key and columns of user ID, user name, email address, group ID, and approval authority.
FIG. 5 is a diagram showing the data structure of the user table 1012.

The user ID is an item that stores user identification information for identifying a user. The user identification information is an item in which a unique value is set for each user.
The user name is an item that stores the user's name. The user name may be any character string such as a nickname instead of a full name.
The email address is an item that stores the user's email address.
Group ID is an item that stores group identification information of a group to which a user belongs. Groups are defined by a group table 1013, which will be described later, and a user may belong to multiple groups.
The approval authority is an item that stores authority information regarding the user's approval conclusion. For a user who has the authority to approve the conclusion of a contract (authorization authority), information such as True that has the authority to approve the conclusion of the contract is stored. On the other hand, for a user who does not have the authority to approve the conclusion of a contract, information such as False, blank, or a null value that does not have the authority to approve the conclusion of the contract is stored.
A configuration may also be adopted in which approval authority can be set according to contract information. For example, a configuration may be adopted in which user A has approval authority for specific contract information A but does not have approval authority for specific contract information B.
It may also be configured such that approval authority can be set according to the type of contract information (contract information type) such as a non-disclosure agreement, joint research contract, or contract. For example, a configuration may be adopted in which user A has the authority to approve non-disclosure agreements, but not authority to approve contract contracts.
In addition, a configuration may be adopted in which authority information of multiple levels (levels, ranks) is stored depending on the department, government office, etc. to which the user belongs. For example, information such as C for temporary employees, B for general employees, A for managers, and S for executives is stored in the approval authority field, and depending on the contract type information, contract amount, etc., (For example, a configuration may be adopted in which only a user who has approval authority such as A or above for a non-disclosure agreement) can approve the conclusion of a contract.

The group table 1013 is a table that stores and manages information regarding groups to which users belong (group information). The group can be defined as any group to which the user belongs, such as a corporation, company, circle, organization, or department within a company.
The group table 1013 is a table having columns of group ID, group name, and administrator ID, with group ID as the primary key.
FIG. 6 is a diagram showing the data structure of the group table 1013.

Group ID is an item that stores group identification information for identifying a group. Group identification information is an item in which a unique value is set for each group.
Group name is an item that stores the name of the group. Any character string can be set for the group name.
The administrator ID is an item that stores user identification information of a user who has administrator authority in a group. A user with administrator authority can arbitrarily define and set a user who has a predetermined position or authority in a group such as an organization.

The document table 1014 is a table for storing and managing information regarding an electronic contract (contract information) exchanged between a creator and a recipient.
The document table 1014 is a table having document ID as a primary key and columns of document ID, document data, creator ID, and template ID.
FIG. 7 is a diagram showing the data structure of the document table 1014.

The document ID is an item that stores document identification information for identifying contract information. The document identification information is an item in which a unique value is set for each contract information.
The document data is an item that stores contract information (binary or text data) of a contract document related to conclusion of a contract. Specifically, the document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).
This item stores the creator ID and user identification information for identifying the user who is the creator of the contract information.
The template ID is an item that stores contract template identification information for identifying a contract model (contract template) that is the basis of a contract document to be created when a contract document is created.

The confirmation table 1015 is a table that stores and manages information (confirmer information) including the email address of a user who is a confirmer of contract information.
The confirmation table 1015 is a table having columns of document ID, confirmation order, confirmer email address, confirmation flag, language data, access code, and date and time.
FIG. 8 is a diagram showing the data structure of the confirmation table 1015.

The document ID is an item that stores document identification information of the contract information to be confirmed by the confirmer.
The confirmation order is an item that stores information regarding the confirmation order when the contract information is confirmed by the confirmer. The contract information stored by the creator is circulated to the confirmers in the order of confirmation and confirmation is performed.
The confirmer email address is an item that stores the email address of the person who confirmed the contract information. The confirmer's email address does not need to be registered as a user in advance to use the service according to the present disclosure. In other words, the confirmer email address does not need to be included in the user table 1012.
The confirmation flag is an item that stores confirmation identification information for identifying whether or not the confirmer has completed the contract information confirmation procedure. When the confirmation person completes confirmation of the contract information, information indicating that confirmation has been completed, such as a value of True, is stored in the confirmation flag field.
The language data is an item that stores information regarding the confirming person's language (language information).
The access code is an item that stores the access code set for the confirmer.
The date and time is an item that stores the date and time when the contract information confirmation procedure was performed by the confirmer. Specifically, the date and time when the confirmation identification information was stored in the confirmation flag item is stored.

The input item table 1016 is a table that stores and manages information regarding input items (input item information) associated with electronic contract information.
The input item table 1016 is a table having columns of input item ID, document ID, inputter ID, input data, input rule, and date and time.
FIG. 9 is a diagram showing the data structure of the input item table 1016.

The input item ID is an item that stores input item identification information for identifying the input item.
The document ID is an item that stores document identification information of electronic contract information with which an input item is associated.
The input person ID is an item that stores the user identification information or email address of the input person who inputs the input data for the input item. Specifically, the input user ID stores a creator ID, an email address of a user specified by the creator ID, a confirmer email address, and the like.
The input data is an item that stores input data input into an input item by an inputter.
The input rule is an item that stores input rule information regarding input rules for input items. Input rules include data types such as date, datetime, text, and integer, as well as the number of characters for strings, regular expressions for strings, and other input items. Input rule information regarding input rules can be stored.
The date and time is an item that stores the date and time when the input data was input into the input item by the inputter.

The contract group table 1017 is a table for storing and managing information regarding contract groups (contract group information). Contract information can be stored and managed in association with one or more cabinets (classification information) for managing contract information. Depending on the information processing service, a cabinet may be called a group, tag, label, etc.
The contract group table 1017 is a table having columns of document ID and cabinet ID.
FIG. 10 is a diagram showing the data structure of the contract group table 1017.

The document ID is an item that stores document identification information for identifying contract information.
The cabinet ID stores cabinet identification information for identifying the cabinet. The cabinet ID is classification information for managing and classifying contract information.

The template table 1018 is a table for storing and managing contract templates of contract documents and information regarding contract templates (contract template information).
The template table 1018 is a table having template ID as a primary key and columns of template ID, user ID, template data, contract type, score, and publication availability.
FIG. 11 is a diagram showing the data structure of the template table 1018.

The template ID is an item that stores contract template identification information for identifying a contract template. The contract template identification information is an item in which a unique value is set for each contract template information.
The user ID is an item that stores user identification information for identifying the user who has stored the contract template information.
Template data is an item that stores contract template documents related to contract documents. Specifically, the template data includes data in any data format such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).
The contract type is an item that stores information regarding the contract type of the contract template (contract type information). The contract type stores contract type information that specifies any type of contract, such as a non-disclosure agreement, a business outsourcing contract, a rental contract, or a joint development contract.
The score is an item that stores an evaluation index (score information) indicating an evaluation value for each contract template information. The score is an evaluation index value indicating the quality of contract template information.
The disclosure permission is an item that stores whether the contract template information can be made public. A value of True is stored in contract template information that can be referenced by other users in a contract template proposal process to be described later, and a value of False is stored in contract template information that cannot be referenced by other users.

<Configuration of control unit 104 of server 10>
The control unit 104 of the server 10 includes a user registration control unit 1041, a contract creation unit 1042, a contract confirmation unit 1043, a template processing unit 1044, and a score calculation unit 1045. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

The user registration control unit 1041 performs a process of storing information of users who wish to use the service according to the present disclosure in the user table 1012.
Information stored in the user table 1012 is transmitted to the server 10 by a user opening a web page operated by a service provider from any information processing terminal, inputting information into a predetermined input form, and transmitting the information to the server 10 . The user registration control unit 1041 stores the received information in a new record of the user table 1012, and the user registration is completed. This allows the users stored in the user table 1012 to use the service.
Prior to the registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a predetermined examination to restrict whether or not the user can use the service.
The user ID may be any character string or number that can identify the user, and may be any character string or number desired by the user, or may be automatically set by the user registration control unit 1041. .

The contract creation unit 1042 executes contract creation processing. Details will be described later.

The contract confirmation unit 1043 executes a contract confirmation process. Details will be described later.

The template processing unit 1044 executes contract cancellation processing. Details will be described later.

<Configuration of first user terminal 20>
The first user terminal 20 is an information processing device operated by a user who uses the service. The first user terminal 20 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile terminal such as a smartphone or a tablet. Further, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The first user terminal 20 includes a storage section 201, a control section 204, an input device 206, and an output device 208.

<Configuration of storage unit 201 of first user terminal 20>
The storage unit 201 of the first user terminal 20 includes a first user ID 2011 and an application program 2012.

The first user ID 2011 is the user's account ID. The user transmits the first user ID 2011 from the first user terminal 20 to the server 10. The server 10 identifies the user based on the first user ID 2011 and provides the user with the service according to the present disclosure. Note that the first user ID 2011 includes information such as a session ID temporarily given by the server 10 to identify the user using the first user terminal 20.

The application program 2012 may be stored in advance in the storage unit 201, or may be downloaded from a web server operated by a service provider via a communication IF.
Application programs 2012 include applications such as web browser applications.
Application program 2012 includes an interpreted programming language such as JavaScript® that is executed on a web browser application stored on first user terminal 20 .

<Configuration of control unit 204 of first user terminal 20>
The control unit 204 of the first user terminal 20 includes an input control unit 2041 and an output control unit 2042. The control unit 204 realizes each functional unit by executing the application program 2012 stored in the storage unit 201.

<Configuration of input device 206 of first user terminal 20>
The input device 206 of the first user terminal 20 includes a camera 2061, a microphone 2062, a position information sensor 2063, a motion sensor 2064, and a touch device 2065.

<Configuration of output device 208 of first user terminal 20>
The output device 208 of the first user terminal 20 includes a display 2081 and a speaker 2082.

<Configuration of second user terminal 30>
The second user terminal 30 is an information processing device operated by a user who uses the service. The second user terminal 30 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile terminal such as a smartphone or a tablet. Further, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The second user terminal 30 includes a storage section 301, a control section 304, an input device 306, and an output device 308.

<Configuration of storage unit 301 of second user terminal 30>
The storage unit 301 of the second user terminal 30 includes a second user ID 3011 and an application program 3012.

The second user ID 3011 is the user's account ID. The user transmits the second user ID 3011 from the second user terminal 30 to the server 10. The server 10 identifies the user based on the second user ID 3011 and provides the service according to the present disclosure to the user. Note that the second user ID 3011 includes information such as a session ID temporarily given by the server 10 to identify the user using the second user terminal 30.

The application program 3012 may be stored in advance in the storage unit 301, or may be downloaded from a web server operated by a service provider via a communication IF.
Application programs 3012 include applications such as web browser applications.
Application program 3012 includes an interpreted programming language such as JavaScript® that is executed on a web browser application stored on second user terminal 30.

<Configuration of control unit 304 of second user terminal 30>
The control unit 304 of the second user terminal 30 includes an input control unit 3041 and an output control unit 3042. The control unit 304 realizes each functional unit by executing the application program 3012 stored in the storage unit 301.

<Configuration of input device 306 of second user terminal 30>
The input device 306 of the second user terminal 30 includes a camera 3061, a microphone 3062, a position information sensor 3063, a motion sensor 3064, and a keyboard 3065.

<Configuration of output device 308 of second user terminal 30>
The output device 308 of the second user terminal 30 includes a display 3081 and a speaker 3082.

<Operation of system 1>
Each process of the system 1 will be explained below.
FIG. 12 is a flowchart showing the operation of the contract creation process.
FIG. 13 is a flowchart showing the operation of the contract confirmation process.
FIG. 14 is a flowchart showing the operation of contract template storage processing.
FIG. 15 is a flowchart showing the operation of the score calculation process.
FIG. 16 is a flowchart showing the operation of the contract template proposal process.
FIG. 17 is an example of a screen showing the operation of the contract creation process.
FIG. 18 is an example of a screen showing a confirmation request message notified to the second user terminal 30.
FIG. 19 is an example screen showing the operation of the contract confirmation process.
FIG. 20 is an example of a screen showing a conclusion completion message notified to the first user terminal 20.
FIG. 21 is an example of a screen showing the operation of the contract template proposal process.

In the present disclosure, contract creation processing and contract confirmation processing in the server 10 will be described below.

<Contract creation process>
The contract creation process is a process in which the creator creates electronic contract information and sends it to the confirmer.

FIG. 15 is an example of a screen showing the operation of the contract creation process. A screen 50 for creating contract information displayed on the display 2081 of the first user terminal 20 includes a status 510 indicating the current creation status of contract information, and buttons 521, 522, 523 for specifying input items. , a contract information display area 530, document data 531, input items 532, 533, 534, and a send button 540 are displayed.

<Summary of contract creation process>
In the contract creation process, the creator creates electronic contract information, sets a confirmer to be the recipient of the electronic contract information, sets input items for the electronic contract information, sets input rules for the input items, and then the creator This is a series of processes in which input data for input items is received from , and electronic contract information is sent to the set confirmer.

<Details of contract creation process>
In step S101, the contract creation unit 1042 of the server 10 receives contract information from a creator to be the subject of a contract conclusion with a confirmer.
Specifically, the first user operates the input device 206 of the first user terminal 20 and creates contract information including document data (contract document) regarding the contract. The contract information can include document data in any data format such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).

In step S101, the contract creation unit 1042 of the server 10 executes a contract-related step in which the contract template stored in the contract storage step is stored in association with a contract document created based on the contract template.
In the present disclosure, the first user can create a contract document by using and editing template data stored in the template table 1018 of the server 10 through contract template proposal processing, etc., which will be described later. Specifically, the contract creation unit 1042 of the server 10 acquires a plurality of contract template information such as the template ID and template data stored in the template table 1018 and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 presents the acquired plurality of contract template information to the first user. By operating the input device 206 of the first user terminal 20, the first user selects predetermined contract template information that serves as a template for creating a contract document from the plurality of contract template information presented. Specifically, the first user presses and selects the contract document creation button D131A displayed on the display 2081 of the first user terminal 20 by operating the input device 206 of the first user terminal 20. The first user operates the input device 206 of the first user terminal 20 to edit template data included in the selected contract template information, thereby creating document data regarding the contract document. At this time, the document data is associated with the template IDD 101A included in the selected contract template information.

The first user operates the input device 206 of the first user terminal 20 and transmits the created document data, the first user ID 2011, and the template ID to the server 10. The contract creation unit 1042 of the server 10 receives the received first user ID 2011, document data, and template ID, and stores them in the creator ID, document data, and template ID fields of a new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores new contract information in the document table 1014.
Thereby, the contract document is stored in association with contract template identification information that identifies the contract template from which the contract document is created.

Document data 531 stored in document table 1014 is displayed on screen 50 for creating contract information.

In step S102, the first user operates the input device 206 of the first user terminal 20, etc. to select and specify a user who will be the confirmer (receiver) of the contract information. In the present disclosure, it is assumed that the first user selects and specifies the second user as the recipient.
The first user operates the input device 206 of the first user terminal 20 and inputs the e-mail address of the second user who will be the confirmer, and transmits the e-mail address to the server 10. The contract creation unit 1042 of the server 10 stores the received email address and the document ID of the contract information created and stored in step S101 in the confirmer email address and document ID fields of the confirmation table 1015, respectively, and stores the contract information and the document ID in the confirmation table 1015. It is stored in association with the second user's email address. Note that the first user may set the second user's language and access code, and store them in association with the second user's email address.
At this time, a value of 1 is stored in the confirmation order item of the confirmation table 1015. In step S102, the first user may be able to select and set a plurality of users to be confirmers. In this case, the value of the confirmation order item of the user who is the confirmer is incremented by one and stored in accordance with the selection order. This sets the order of circulation of confirmers in contract confirmation processing, which will be described later. Note that setting the circulation order is not essential.

In step S103, the first user operates the input device 206 of the first user terminal 20 and sets input items for the contract information.
Specifically, the first user operates the input device 206 of the first user terminal 20 and sets a plurality of input items for the contract information created and stored in step S101. Any input items can be set, such as a stamp field for stamping seal data, an input field for entering text data such as signature data, a check box field for selecting check items, and a date field for entering the date. .
The first user operates the input device 206 of the first user terminal 20 and transmits a request to add an input item to the server 10. Upon receiving the request, the contract creation unit 1042 of the server 10 stores the document ID of the contract information in the document ID of a new record in the input item table 1016. As a result, the newly added input item information is stored in association with the contract information. Note that the first user can store a plurality of pieces of input item information in association with the contract information.

In step S104, the first user sets input rules for each input item to be added. The first user specifies the input rule for each input item information set in step S103 by operating the input device 206 of the first user terminal 20, and transmits the input rule to the server 10. The contract creation unit 1042 of the server 10 stores the received input rule in the input rule field of each input item information record in the input item table 1016. This allows input rules to be set for each input item.

In step S105, the contract creation unit 1042 of the server 10 receives input data for a plurality of input items input by the first user.
Specifically, the first user inputs input data for each input item set in step S104 by operating the input device 206 of the first user terminal 20 or the like. For example, the first user may input input data of a number for managing contract information such as a reference number for a group to which the first user belongs to an input item set with a management number. The first user may input input data of the contract conclusion date of the contract information into the input item in which the contract conclusion date is set. When the first user completes inputting the input data to the input items, the first user transmits the input item ID and input data for each input item to the server 10.
The contract creation unit 1042 of the server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of the server 10 stores the received input data in the input data item of the input item information of the input item table 1016 specified by the received input item ID. As a result, the input data input by the first user is stored in the input item table 1016.

The contract creation unit 1042 of the server 10 receives an instruction from the first user to request the second user to conclude a contract based on the contract information.
Specifically, the first user operates the input device 206 of the first user terminal 20 and presses the send button 540 displayed on the screen 50 for creating contract information, thereby transmitting the contract information. Send the request to the server 10.

In step S106, the contract creation unit 1042 of the server 10 sends a message to the second user notifying that the first user has sent a request to confirm the contract information. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order item in the confirmation table 1015, and selects the user who is the first confirmer (first confirmation user) with the smallest value stored in the confirmation order item. Identify. In the present disclosure, the first confirmed user is, for example, the second user. The contract creation unit 1042 of the server 10 sends a message to the second user's e-mail address, using communication means such as e-mail, to notify that the first user has sent a request to confirm the contract information.
The message notified to the second user includes URL (Uniform Resource Locator) information including a document ID for specifying contract information. The URL may directly include the document ID, or may include information such as a character string obtained by arbitrarily encrypting the document ID, or other character strings that can identify the document ID by referring to a table (not shown). good. Further, the URL may include information for identifying the second user. For example, if the second user has not registered for the service according to the present disclosure, it is necessary to include information for identifying the second user in the URL.

When the first user sets an access code for the second user, the first user separately conveys the access code to the second user by means such as e-mail. As a result, even if a third party obtains the message to be notified to the second user, the third party cannot execute the contract confirmation process unless the third party obtains the access code.

FIG. 16 is an example of a screen showing a message notified to the second user terminal 30. The message screen 60 displayed on the display 3081 of the second user terminal 30 includes a message 61 and information of a URL 62 including a document ID for specifying contract information.

<Modified example>
When the first user selects and sets a plurality of confirmers in step S102, the first user may be configured to be able to independently set different input item information in step S103 for each of the plurality of confirmers. do not have. For example, when the first user sets two users, the second user and the ninth user, as confirmers, the input items for the contract start date and contract end date are set for the second user, and the contract is concluded. The input item for the day may be set for the ninth user. In this case, in the contract confirmation process described later, the second user can enter input data for the input fields of the contract start date and contract end date, but input data for the input field of the contract conclusion date. Can not do it. On the other hand, the ninth user cannot input data to the input items for the contract start date and contract end date, but can input input data for the input item for the contract conclusion date. A configuration may be adopted in which a plurality of confirmers can be selected and set in duplicate for one piece of input item information.

Input items 532, 533, and 534 are drawn as drawing objects on the screen 50 for creating contract information. In the input items 532 and 533, the user identification information "USER-B" of the user who has selected and set input of the input item as the assignment, and the item "Text" as the type of the input item are drawn. In the input item 534 regarding stamping, the user identification information "USER-C" of the user who has selected and set the stamping as the assignment, and "seal" as the input item type are drawn.

<Contract confirmation process>
The contract confirmation process is a process in which the confirmer confirms the contents of the electronic contract information received from the creator.

<Summary of contract confirmation process>
The contract confirmation process accepts access from the confirmer, presents the confirmer with a confirmation screen that displays contract information, receives input data for input items from the confirmer, and receives data related to confirming the contract information from the confirmer. This is a series of processes for accepting requests.

<Details of contract confirmation process>
In step S301, the second user who is the confirmer operates the input device 306 of the second user terminal 30 and selects the URL written in the received message, thereby using the browser application of the second user terminal 30. A web page specified by the URL can be opened. Thereby, the second user terminal 30 transmits a request to the server 10 to execute the contract confirmation process.

If the access code item is stored in the second user's record in the confirmation table 1015, the second user is requested to input the access code, and the entered access code and the second user's record in the confirmation table 1015 are By comparing the access code stored in the user's record, it is possible to perform authentication processing for the second user.
Specifically, the server 10 transmits an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 of the second user terminal 30, inputs the access code, and transmits it to the server 10. The contract confirmation unit 1043 of the server 10 determines whether the received access code matches the access code stored in the record of the second user in the confirmation table 1015, and if they match, executes contract confirmation processing. continue. On the other hand, if they do not match, the contract confirmation process is canceled. Note that the authentication process using the access code may be omitted.

The contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID included in the received request, and acquires contract information. The contract confirmation unit 1043 of the server 10 searches the document ID item in the confirmation table 1015 based on the document ID included in the received request, and obtains confirmer information. The contract confirmation unit 1043 of the server 10 searches the document ID item in the input item table 1016 based on the document ID included in the received request, and obtains input item information associated with the contract information.

In step S302, the contract confirmation unit 1043 of the server 10 identifies the second user and acquires the second user's approval authority information. The second user may be identified based on the second user ID 3011 included in the request received from the second user terminal 30, or may be identified based on the identification information for identifying the second user included in the URL. good. If the second user has not registered for the service according to the present disclosure, it is necessary to identify the second user from the URL. For example, the URL may include the second user's email address, user ID, etc. as information for identifying the second user.

The contract confirmation unit 1043 of the server 10 searches the user ID item in the user table 1012 based on the user identification information of the specified second user, and acquires the second user's approval authority item. Note that in this disclosure, the second user's approval authority is stored in the user table 1012, but the second user's approval authority may be stored for each group to which the second user belongs, or may be stored for each group to which the second user belongs. It does not matter if it is stored for each information or for each contract information type. The contract confirmation unit 1043 of the server 10 acquires the second user's approval authority information for the target contract information.
Further, if the second user has not registered as a user in the service according to the present disclosure, the process may be executed by regarding the second user as a user who does not have approval authority.

In step S303, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, confirmer information (information identifying the second user), input item information, and confirmer approval authority information. 2 to the user terminal 30.

Specifically, the display 3081 of the second user terminal 30 presents the second user with a confirmation screen that accepts an operation to approve the contract information. The second user confirms and approves the contract information displayed on the display 3081 of the second user terminal 30.
Note that the confirmation screen presented to the second user is based on the language information stored in the language data item of the second user's record in the confirmation table 1015, and is displayed in the language specified for the confirmer by the second user. It is also possible to have a configuration in which the information is presented to the user.

FIG. 17 is an example of a confirmation screen showing the operation of the contract confirmation process. A confirmation screen 70 for approving contract information displayed on the display 3081 of the second user terminal 30 includes a status 710 indicating the current creation status of contract information, a contract information display area 730, document data 731, and input items. 732, 733, 734, 735, 736, and an agree button 740 are displayed.

Specifically, if the second user's approval authority information obtained in step S302 includes information that has the authority to approve the conclusion of the contract, the contract confirmation unit 1043 of the server 10 determines whether the second user has accepted the agreement. It is determined that the user is capable of approving the conclusion of the contract based on the contract information, a confirmation screen is presented to the second user, and the process proceeds to step S304.

On the other hand, if the second user is a user who cannot approve the conclusion of the contract based on the received contract information, the contract confirmation process ends.

In step S304, the contract confirmation unit 1043 of the server 10 receives input for one or more input items of contract information.
Specifically, the second user operates the input device 306 of the second user terminal 30 and inputs input data into input items 732, 733, 734, and 735 set in the contract information. Note that in the present disclosure, since input by the second user is not assigned to the input item 736, it is visually discernably displayed that the second user cannot input input data.

In step S305, the contract confirmation unit 1043 of the server 10 receives an instruction from the second user to agree to and approve the conclusion of the contract based on the contract information received from the first user.
The second user confirms the contract information and input data displayed on the display 3081 of the second user terminal 30, and when agreeing or consenting to the contents, operates the input device 306 of the second user terminal 30, etc. By pressing the consent button 740 displayed on the confirmation screen 70 for confirming the contract information, a request including the document ID, information identifying the second user, and input data for each input item input in step S305 is sent. The process of transmitting to the server 10 is executed. The information identifying the second user may be the second user ID 3011.
The contract confirmation unit 1043 of the server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Specifically, the contract confirmation unit 1043 of the server 10 searches the confirmation table 1015 based on the received document ID and information specifying the second user, and stores a value of True in the confirmation flag field of the record. For example, if the information specifying the second user is an email address, the document ID and confirmer email address items in the confirmation table 1015 are searched, and a value of True is stored in the confirmation flag item of the record. If the information that identifies the second user is user identification information, the document ID and confirmation information in the confirmation table 1015 are determined based on the email address of the second user identified by searching the user ID item in the user table 1012. The user's email address field is searched, and a value of True is stored in the confirmation flag field of the record.
The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1016 specified by the input item ID associated with the input data. Thereby, in step S305, the input data input by the second user is stored as input item information in the input item table 1016.

The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been executed by all confirmers having approval authority. Specifically, if a value of True is stored in the confirmation flag of the record of the confirmer who has approval authority in the confirmation table 1015, the contract confirmation unit 1043 of the server 10 performs the contract check by all confirmers who have approval authority. It is determined that the contract confirmation process has been executed. That is, the determination is made while ignoring the value of the confirmation flag of the record of a confirmer who does not have approval authority.
When the contract confirmation process is executed by all the confirmers having approval authority, the contract confirmation unit 1043 of the server 10 sends a message to the first user notifying that the contract confirmation process is completed. Note that, similarly, the contract confirmation unit 1043 of the server 10 may send a message to the second user notifying that the contract confirmation process has been completed.

Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the first user's e-mail address, using communication means such as e-mail, to notify that the second user has completed confirmation of the contract information. That is, the first user is notified that the second user has approved the conclusion of the contract. This allows the first user to know that the contract has been concluded with the second user.
The message to be notified to the first user may include information on a URL that is an endpoint that includes a document ID for specifying contract information.

FIG. 18 is an example of a screen showing a message notified to the first user terminal 20. The message screen 80 displayed on the display 2081 of the first user terminal 20 includes a message 81 and information of a URL 82 including a document ID for specifying contract information.

Similarly, the contract confirmation unit 1043 of the server 10 sends a message notifying that the second user has completed confirmation of the contract information, including a mention to the first user, using a chat service (not shown) or the like. You may do so. That is, the first user is notified via the chat service that the second user has approved the conclusion of the contract. This allows the first user to know that the contract has been concluded with the second user.
The message to be notified to the first user may include information on a URL that is an endpoint that includes a document ID for specifying contract information.

The first user can use the browser application of the first user terminal 20 to open the web page specified by the URL included in the received message. The first user terminal 20 refers to the contract information and transmits a request for inquiry to the server 10. The contract confirmation unit 1043 of the server 10 refers to the contract information, generates a web page for inquiry, and sends it to the first user terminal 20. The first user can obtain the document data included in the contract information by downloading or the like from the web page screen displayed on the display 2081 of the first user terminal 20.

If multiple users are set as confirmers, the contract confirmation unit 1043 of the server 10 informs the user other than the last user who executed the contract confirmation process that the contract confirmation process has been completed. You may also send a message to notify you. Thereby, the user corresponding to the confirmer can also receive a notification that execution of the contract confirmation process has been completed by all confirmers.
Further, the contract confirmation unit 1043 of the server 10 may send a message notifying that the contract confirmation process has been completed to a user who has authority equivalent to an administrator in a group to which a plurality of confirmers belong.
Note that the message may be sent via email, chat service, or the like.
Thereby, the administrator of the group to which the user who is the confirmer belongs can receive notification that execution of the contract confirmation process has been completed.

Specifically, the contract confirmation unit 1043 of the server 10 acquires the group ID item by searching the user ID or email address item in the user table 1012 based on the user ID or email address. The contract confirmation unit 1043 of the server 10 searches the group ID item of the group table 1013 based on the acquired group ID item, acquires the administrator ID item, and, based on the administrator ID, identifies the person who corresponds to the administrator. An authorized user is identified by searching the user ID in the user table 1012, and a message is sent to notify that the contract confirmation process has been completed.

<Electronic signature processing>
Step S305 may include electronic signature processing. In response to the instruction to approve the contract conclusion received from the second user in step S305, the contract confirmation unit 1043 of the server 10 indicates, in the contract information received from the first user, that the contract conclusion of the contract information is approved. Add and store an electronic signature.
Specifically, the contract confirmation unit 1043 of the server 10 adds and stores an electronic signature to the contract information based on the received request. The contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID and acquires contract information.
The contract confirmation unit 1043 of the server 10 adds an electronic signature to the acquired contract information and stores it in the document data item of the document table 1014. Note that the contract confirmation unit 1043 of the server 10 may update (overwrite) items of document data with the contract information to which the electronic signature has been added, or may store the contract information before the electronic signature has been added in a separate storage device (not shown). I don't mind if you do.
The contract confirmation unit 1043 of the server 10 includes the document ID, the first user's email address, the second user's email address, approval date and time, confirmation date and time, authentication method of approval date and time, authentication method of confirmation date and time, and input items in the electronic signature. Any information such as the value of input data for each user, consent (approval) of the first user and second user, and a time stamp may be included.
As a result, the contract confirmation unit 1043 of the server 10 stores the contract information with an electronic signature indicating that the second user has approved the conclusion of the contract information. It is possible to prevent impersonation or falsification of contract information by a third party.

<Contract template storage processing>
The contract template storage process is a process in which the user uploads the contract template that he/she owns to the contract information service according to the present disclosure.

<Summary of contract template storage processing>
The contract template storage process is a series of processes in which a selection of a contract template to be uploaded is accepted from the user, a selection of a contract type is accepted from the user, and the contract template is uploaded to the server 10 and stored.
In this disclosure, contract template storage processing by the first user terminal 20 will be described as an example. Note that the contract template storage process may be executed from the second user terminal 30 or any other user terminal.

<Details of contract template storage processing>
Details of the contract template storage process will be explained below.

In step S501, the template processing unit 1044 of the server 10 executes a contract acceptance step of accepting a plurality of contract templates related to a contract from a plurality of users.
Specifically, the first user starts a browser application stored in the storage unit 201 of the first user terminal 20, inputs a URL for executing contract template storage processing on the server 10, and opens an upload screen. The control unit 204 of the first user terminal 20 transmits a request including the first user ID 2011 for executing contract template storage processing to the server 10.
The template processing unit 1044 of the server 10 receives the first user ID 2011 included in the received request. The template processing unit 1044 of the server 10 generates an upload screen and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the upload screen on the display 2081 of the first user terminal 20.

By operating the input device 206 of the first user terminal 20, the first user presses an upload button etc. displayed on the upload screen to upload the data to the server 10 and store it in the storage unit 201 of the first user terminal 20. Select the contract template document that was created.
A contract template document is information regarding a contract document defined in any data format such as PDF, Word, or XML.

In step S502, the first user inputs the contract type of the contract template document selected in step S501 into the contract type input field displayed on the upload screen by operating the input device 206 of the first user terminal 20. do.
Specifically, the first user enters contract type information that specifies the type of any contract, such as a non-disclosure agreement, outsourcing contract, rental contract, joint development contract, etc., into the contract type input field displayed on the upload screen. do. Note that input of contract type information may be omitted in the contract template storage process.

The control unit 204 of the first user terminal 20 transmits the contract template document selected in step S501, the contract type information input in step S502, and the first user ID 2011 to the server 10.

In step S503, the template processing unit 1044 of the server 10 executes a contract storage step of storing the plurality of contract templates received in the contract reception step.
Specifically, the template processing unit 1044 of the server 10 stores the contract template document, contract type information, and first user ID 2011 in the template data, contract type, and user ID fields of a new record in the template table 1018, respectively. .
In the template table 1018, the newly assigned template ID is stored in association with the template document uploaded by the first user and the contract type information input by the first user.

<Score calculation process>
The score calculation process is a process of calculating a score that is an evaluation index value regarding the quality of the contract template stored in the server 10 by the contract template storage process.

<Overview of score calculation process>
The score calculation process identifies the contract template to be processed, acquires contract information using the contract template, totals the number of times the contract template is used, acquires and evaluates negotiation information related to the contract information, and collects contract information using the contract template. This is a series of processing that acquires and evaluates the contract attributes of the contract template, and calculates a score that is an evaluation index value regarding the quality of the contract template.

<Details of score calculation process>
The details of the score calculation process will be explained below.
The template processing unit 1044 of the server 10 periodically executes score calculation processing. Note that the score calculation process may be configured to be executed at the timing when the contract template storage process is executed by the user. In addition, the score calculation process may be executed at any timing.

In step S701, the score calculation unit 1045 of the server 10 acquires and specifies contract template information from the template table 1018. Note that the score calculation unit 1045 of the server 10 may be configured to acquire and specify contract template information searched based on predetermined search conditions from the template table 1018.
In this disclosure, for the sake of simplicity, score calculation processing for one predetermined contract template information (contract template information specified by the score calculation unit 1045 of the server 10) will be described; is executed for each.

In step S702, the score calculation unit 1045 of the server 10 obtains contract information created using the contract template information identified in step S701 and associated with the contract template information.
Specifically, the score calculation unit 1045 of the server 10 searches the template ID item of the document table 1014 based on the template ID included in the contract template information specified in step S701, and searches the document ID, document data, and creator ID. Get a record of contract information including. Thereby, the score calculation unit 1045 of the server 10 acquires a plurality of pieces of contract information created based on the contract template information.

In step S703, the score calculation unit 1045 of the server 10 totals the number of contract documents created using the contract template information specified in step S701. That is, the score calculation unit 1045 of the server 10 totals the number of uses of the contract template information specified in step S701.
The score calculation unit 1045 of the server 10 totals the number of records of contract information acquired in step S702.
Note that the score calculation unit 1045 of the server 10 excludes contract information that has not been concluded between the contracting parties from among the contract information stored in the document table 1014, and calculates the contract through contract creation processing and contract confirmation processing. Information on contracts concluded between parties may be aggregated.
Thereby, the evaluation index value of the contract template information can be calculated based on the contract information that actually led to the conclusion of the contract. In other words, the quality of contract template information can be evaluated based on usage conditions that are more in line with actual conditions.

In step S704, the score calculation unit 1045 of the server 10 acquires negotiation information related to negotiations up to the conclusion of the contract document, which was stored in association with the contract template in the contract-related step.
Specifically, it is assumed that negotiation information regarding the content of negotiations when a creator and a confirmer conclude a contract related to contract information in contract creation processing and contract confirmation processing is stored in the storage unit 101 of the server 10. Specifically, the contents of the negotiation include clauses included in the contract document, additions and amendments to the clause, communication information such as text information exchanged between the creator and the confirmer via a message service (not shown), and the contract document. Contains any information exchanged between the creator and the confirmer during contract negotiations up to the conclusion of the contract, such as comments on the contract.
The score calculation unit 1045 of the server 10 acquires negotiation information regarding the content of negotiation when concluding a contract, which is stored in the storage unit 101 of the server 10 and is associated with the contract information acquired in step S702.

In step S705, the score calculation unit 1045 of the server 10 acquires contract attribute information regarding the contract attributes of the contract document stored in association with the contract template in the contract-related step. More specifically, the score calculation unit 1045 of the server 10 acquires party attribute information that is attribute information regarding the contract party of the contract document stored in association with the contract template in the contract-related step.
Specifically, the score calculation unit 1045 of the server 10 acquires the creator ID and confirmer ID associated with the contract information acquired in step S702. The score calculation unit 1045 of the server 10 calculates the name of the contracting party (company name, organization name), company attributes such as first-section listed companies, second-section listed companies, financial status, etc., associated with the contract information acquired in step S702. Acquire attribute information (party attribute information) regarding the parties to the contract, including the parties to the contract.
In addition, the score calculation unit 1045 of the server 10 acquires contract attribute information including at least one of the following: whether or not a legal person has reviewed the contract information acquired in step S702, and a rating evaluation by the user.
For example, if the user who creates or confirms contract information is a lawyer or other legal person, contract information that has been reviewed by the legal person will not contain information indicating that the review has been performed. It is stored in association with contract information, and in other cases, information indicating that a review has been performed is not stored.
For example, the rating evaluation by the user is a 10-level evaluation from 1 to 10, the higher the number, the higher the quality, and the lower the number, the lower the quality.The subjective evaluation by the user is stored in association with the contract information.

In step S706, the score calculation unit 1045 of the server 10 executes an evaluation calculation step of calculating an evaluation index value regarding the quality of the contract template stored in the contract storage step.
The evaluation calculation step is a step of calculating an evaluation index value of the contract template based on the contract document stored in association with the contract template in the contract-related step.
Specifically, the score calculation unit 1045 of the server 10 calculates the number of contract documents created using the contract template information calculated in step S703, contract attribute information regarding the contract attributes of the contract documents stored in association with the contract template, The evaluation index value of the contract template is calculated based on party attribute information, which is attribute information regarding the contract parties of the contract document stored in association with the contract template, and negotiation information regarding negotiations leading up to the conclusion of the contract document, stored in association with the contract template. calculate.

The evaluation calculation step executes a step of calculating an evaluation index value of the contract template based on the number of contract documents stored in association with the contract template in the contract-related step.
Specifically, the score calculation unit 1045 of the server 10 uses the number of contract documents created using the calculated contract template information as the evaluation index value of the contract template information. In addition, the evaluation index value of the contract template information may be any evaluation index value that increases as the number of contract documents created using the calculated contract template information increases.

In step S706, the evaluation calculation step calculates the evaluation index value of the contract template based on the party attribute that is attribute information regarding the contract party of the contract document stored in association with the contract template in the contract related step.
Specifically, the score calculation unit 1045 of the server 10 determines, regarding the party attributes for each piece of contract information acquired in step S705, if the name of the company that is a party to the contract is included in the predetermined company name, the score calculation unit 1045 determines that the contract information A predetermined point is added to the evaluation index value for each time. A configuration may be adopted in which different points are added for each company name. For example, if the contract information of company A is worth 3 points and the contract information of company B is worth 5 points, each point may be added to the evaluation index value.
For example, the score calculation unit 1045 of the server 10 may add the evaluation value of the company in the contract information created based on the contract template information to the evaluation index value for each contract template information. For example, if the evaluation value of company A is 3 points and the evaluation value of company B is 5 points, a configuration may be adopted in which each point is added to the evaluation index value.
In addition, an evaluation value depending on the company's corporate attributes, such as 5 points if the company is listed on the first section and 3 points if the company is listed on the second section, can be added to the evaluation index value. good.

In step S706, the evaluation calculation step is performed in accordance with the degree of deviation between the contract document stored in association with the contract template in the contract-related step and the contract template, such that the larger the degree of deviation, the smaller the evaluation index value. , performing the step of calculating the evaluation index value.
Specifically, the score calculation unit 1045 of the server 10 calculates the degree of deviation between the contract template document and the contract document included in the plurality of contract information acquired in step S702. Specifically, the degree of divergence can be calculated as the reciprocal of the degree of similarity using any known algorithm for calculating the degree of similarity between text information, such as TF-IDF or cosine similarity. Note that in calculating the degree of deviation, any syntactic analysis technique may be applied to the text information. For example, the degree of deviation between text information may be calculated by considering (excluding) notation fluctuations such as dependencies.
The score calculation unit 1045 of the server 10 calculates the degree of deviation from the contract template document for each piece of contract information acquired in step S702. The evaluation index value of the contract template document is calculated by calculating the value that is the sum of the reciprocals of the degrees of deviation for each of the calculated plurality of contract information. For example, the larger the accumulated deviation degree, the lower the quality of the contract template can be determined, so the evaluation index value is calculated so that the evaluation index value becomes smaller. Similarly, the degree of similarity between the contract document and the contract template document is calculated, and the higher the accumulated degree of similarity, the higher the quality of the contract template. Therefore, the evaluation index value is calculated so that the evaluation index value becomes larger. You may do so.

In step S706, the evaluation calculation step is a step of calculating an evaluation index value for the contract document stored in association with the contract template in the contract-related step such that the evaluation index value becomes smaller as the number of corrections from the contract template increases. Execute.
Specifically, the score calculation unit 1045 of the server 10 totals the number of corrections from the contract template document for each piece of contract information acquired in step S702. The evaluation index value of the contract template document is calculated by calculating the reciprocal of the sum of the number of corrections for each of the collected plurality of contract information. For example, it can be determined that the higher the number of cumulative corrections, the lower the quality of the contract template, so the evaluation index value is calculated so that the evaluation index value becomes smaller.

In other words, the evaluation index value is calculated so that the contract template in which the contract document is created has a greater degree of modification from the contract template (larger deviation, more revisions), the smaller the evaluation index value.
In addition, when calculating the evaluation index value considering both the magnitude of the deviation degree and the number of correction points, the evaluation index value calculated based on the magnitude of the deviation degree and the number of correction points A weighted sum with the calculated evaluation index value may be calculated as the evaluation index value of the contract template. In this case, the weight of the evaluation index value calculated based on the magnitude of the degree of deviation may be set to be greater than the weight of the evaluation index value calculated based on the number of correction points.
This is because when calculating the degree of modification from the contract template, the degree of deviation is considered to have a higher degree of influence than the number of modified parts.

In step S706, the evaluation calculation step calculates the evaluation index value of the contract template based on the negotiation information related to the negotiation up to the conclusion of the contract document, which was stored in association with the contract template in the contract-related step.
Specifically, the score calculation unit 1045 of the server 10 calculates the evaluation index value based on the negotiation information for each of the plurality of contract information acquired in step S704.
For example, based on the negotiation content of the negotiation information, the more additions and amendments to the clauses and clauses included in the contract document, the lower the quality of the contract template can be determined. calculate. The larger the amount of communication information such as text information exchanged between the creator and the confirmer via a message service, etc., the lower the evaluation index value will be because it can be judged that the contract template is of low quality and took time to negotiate the contract. Calculate the evaluation index value so that In addition, the evaluation index value of the contract template is calculated by evaluating the quality of the contract template based on any information exchanged between the creator and the confirmer during the contract negotiations leading up to the conclusion of the contract, such as comments on the contract document. You may do so.

In step S706, the evaluation calculation step performs the evaluation calculation step, regarding the contract document stored in association with the contract template in the contract-related step, which has been proposed as a contract document draft by one contract party to the other contract party, but has not been proposed to the conclusion of the contract. If there is no evaluation index value, execute the step of calculating the evaluation index value so that the evaluation index value of the contract template becomes smaller.
Specifically, the score calculation unit 1045 of the server 10 calculates the evaluation index value of contract information that did not lead to contract conclusion due to rejection by the confirmer, based on the negotiation information for each of the plurality of contract information acquired in step S704. , the evaluation index value of the contract template is calculated lower than that of contract information that was not rejected by the confirmer and led to the conclusion of the contract.
For example, regarding the plural pieces of contract information acquired in step S702, contract information that was rejected by the confirmer and did not lead to the conclusion of a contract is 0 points, and contract information that was not rejected by the confirmer and was not rejected and did not lead to the conclusion of the contract is 5 points. Then, the evaluation index value of the contract template is calculated by adding up the points of each piece of contract information for a plurality of pieces of contract information.

In step S706, the evaluation calculation step calculates the evaluation index value of the contract template based on the contract attributes of the contract document stored in association with the contract template in the contract-related step.
Specifically, the score calculation unit 1045 of the server 10 stores information indicating that the contract attributes for each of the plurality of contract information acquired in step S705 have been reviewed by a legal person in association with the contract information. The evaluation index value of the contract template is calculated to be higher than the evaluation index value of contract information in which information indicating that a review by a legal person has not been stored is stored.
For example, for the plural pieces of contract information acquired in step S705, information indicating that a review by a legal person has been performed will give 5 points to the contract information stored in association with the contract information. The evaluation index value of the contract template is calculated by adding up the points of each piece of contract information for a plurality of pieces of contract information, with the contract information for which no information indicating that the contract is stored as 0 points.

In step S706, the evaluation calculation step evaluates the contract template based on indicators such as the popularity of the contract template such as the number of downloads from other users, rating evaluation, and word-of-mouth evaluation of the contract template stored in the contract storage step. A step of calculating an index value may be performed.

In addition, the evaluation index value may be calculated by applying the contract attributes, party attributes, negotiation information, etc. explained above to any rule-based model, machine learning model, artificial intelligence model, deep learning model, etc. good. The evaluation index value may be calculated by combining two or more arbitrary pieces of information included in contract attributes, party attributes, negotiation information, and the like.

Note that in calculating the evaluation index value, the evaluation index value may be calculated by combining at least one evaluation index value among the plurality of evaluation index values. Specifically, a value obtained by integrating evaluation index values calculated by a plurality of methods may be calculated as the evaluation index value.

In step S706, the score calculation unit 1045 of the server 10 executes an evaluation storage step in which the evaluation index value calculated in the evaluation calculation step is stored in association with the contract template.
Specifically, the score calculation unit 1045 of the server 10 adds steps S702 to S706 to the score item of the record specified by searching the template ID of the template table 1018 based on the template ID of the contract template specified in step S701. The evaluation index value calculated in is stored. As a result, the evaluation index value is stored in association with the contract template.

<Contract template proposal processing>
The contract template proposal process is a process of proposing a contract template stored in the contract information service according to the present disclosure to the user.
In this disclosure, contract template proposal processing by the second user terminal 30 will be described as an example. Note that the contract template proposal process may be executed from the first user terminal 20 or any other user terminal.

<Summary of contract template proposal processing>
The contract template proposal process accepts the selection of the contract type from the user, searches for contract templates based on the contract type, displays a list of contract templates to the user according to the score of each contract template, and selects the contract templates that are listed. This is a series of processes for accepting selection instructions for. The user can download the selected contract template or create a contract document based on the selected contract template.

<Details of contract template proposal processing>
Details of the contract template proposal process will be explained below.

In step S901, the template processing unit 1044 of the server 10 executes a type reception step of receiving contract type information regarding the contract type of the contract template from the user.
Specifically, the second user starts the browser application stored in the storage unit 301 of the second user terminal 30, enters the URL for executing the contract template proposal process of the server 10, and opens the template selection screen. . The control unit 304 of the second user terminal 30 transmits a request including the second user ID 3011 for executing contract template storage processing to the server 10.
The template processing unit 1044 of the server 10 receives the second user ID 3011 included in the received request. The template processing unit 1044 of the server 10 generates a template selection screen and transmits it to the second user terminal 30. The control unit 304 of the second user terminal 30 displays a template selection screen on the display 3081 of the second user terminal 30.

FIG. 21 is an example of a screen showing the operation of the contract template proposal process. The template selection screen D10 displayed on the display 3081 of the second user terminal 30 includes a contract type input field D151, a contract template information list display field D11, and template IDs 101A, D101B, D101C, and D101D for each of the contract template information listed. , score D111A, D111B, D111C, D111D, contract type D121A, D121B, D121C, D121D, contract document creation button D131A, D131B, D131C, D131D, icon indicating that a contract document was created using contract template information D101A Contains D141A.

By operating the input device 306 of the second user terminal 30, the second user selects and inputs the contract type of the contract template to be searched into the contract type input field D151 displayed on the template selection screen.
Specifically, the second user selects contract type information that specifies any type of contract, such as a nondisclosure agreement, outsourcing contract, rental contract, or joint development agreement, and inputs the contract type displayed on the template selection screen. Enter it in column D151.
The control unit 304 of the second user terminal 30 transmits the contract type information selected by the second user to the server 10.

In step S902, the template processing unit 1044 of the server 10 searches the contract type item of the template table 1018 based on the contract type information received from the second user terminal 30, and searches for a plurality of contract type items including template ID, template data, and score. Get a record of contract template information.
Note that the template processing unit 1044 of the server 10 excludes, from among the contract template information, contract template information in which information indicating that the contract template information can be disclosed to the second user is not stored in the disclosure permissions. The contract template information may be acquired in which information indicating whether the contract template information can be disclosed to the second user is stored. As a result, in any contract template storage process, by setting an appropriate disclosure range for disclosure permission, it is possible to prevent contract template information from being proposed to a party to whom disclosure is not desired.

In step S903, the template processing unit 1044 of the server 10 transmits the plurality of contract template information acquired in step S902 to the second user terminal 30. The control unit 304 of the second user terminal 30 displays a list of the received plurality of contract template information in the list display field D11 of the display 3081 of the second user terminal 30, arranging them in descending order of scores (evaluation index values).
Furthermore, it is conceivable to display template information with a high score at the top of the list, or to display template information on the first page when displaying a plurality of template information by carousel or page turning.

In step S903, the control unit 304 of the second user terminal 30 sends the plurality of contract templates stored in the contract storage step to the user in different ways depending on the contract documents stored in association in the contract related step. Execute the presentation step to present.
Specifically, the control unit 304 of the second user terminal 30 controls the contract template information used when creating the actual contract document for the plurality of contract template information displayed on the display 3081 of the second user terminal 30. , is presented to the user in a manner different from other contract template information.
Specifically, when transmitting contract template information to the second user terminal 30, the template processing unit 1044 of the server 10 searches the document table 1014 based on the template ID and determines the existence of a contract document associated with the template ID. Check whether it is present. For example, if one or more records of contract information are found based on the template ID, it is determined that a contract document created using the contract template information exists. On the other hand, if one or more records of contract information are not found based on the template ID, it is determined that there is no contract document created using the contract template information. The template processing unit 1044 of the server 10 associates the template information with information for identifying whether a contract document exists or not, and transmits the template information to the second user terminal 30.
The control unit 304 of the second user terminal 30 selects a contract template that is associated with information indicating that a contract document created using the contract template information exists among the plurality of received template information. The information is displayed in association with the icon D141A, etc., or the font, font, etc. are changed. As a result, when the second user checks multiple pieces of template information, the second user can identify the contract template information as not being associated with information indicating the existence of a contract document created using the contract template information. can be confirmed.
This allows the second user to confirm at a glance the contract template information actually used in creating the contract document.

In step S904, the template processing unit 1044 of the server 10 accepts a request from a user different from the plurality of users to select a predetermined contract template from among the plurality of contract templates stored in the contract storage step. Execute the steps.
Specifically, the second user selects desired template information from the plurality of template information displayed on the display 3081 of the second user terminal 30 by operating the input device 306 of the second user terminal 30. The second user can select template information uploaded by a user other than the second user, for example, the first user, in the contract template storage process. The control unit 304 of the second user terminal 30 transmits the template ID of the selected template information to the server 10. The server 10 accepts the template ID received from the second user terminal 30.

The template processing unit 1044 of the server 10 executes a contract output step of outputting a predetermined contract template to another user in response to the request received in the contract selection step.
Specifically, the template processing unit 1044 of the server 10 searches the template ID item in the template table 1018 based on the received template ID, and acquires template data. The template processing unit 1044 of the server 10 transmits the acquired template data to the second user terminal 30 and outputs it to the second user. That is, the contract template stored by the first user through the contract template storage process is output to the second user, who is different from the first user.

<Basic hardware configuration of the computer>
FIG. 22 is a block diagram showing the basic hardware configuration of the computer 90. The computer 90 includes at least a processor 901, a main storage device 902, an auxiliary storage device 903, and a communication IF 991 (interface). These are electrically connected to each other by a communication bus 921.

The processor 901 is hardware for executing an instruction set written in a program. The processor 901 includes an arithmetic unit, registers, peripheral circuits, and the like.

The main storage device 902 is for temporarily storing programs, data processed by the programs, and the like. For example, it is a volatile memory such as DRAM (Dynamic Random Access Memory).

The auxiliary storage device 903 is a storage device for storing data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, semiconductor memory, and the like.

The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using a wired or wireless communication standard.
The network is composed of various mobile communication systems constructed using the Internet, LAN, wireless base stations, and the like. For example, the network includes 3G, 4G, 5G mobile communication systems, LTE (Long Term Evolution), a wireless network (for example, Wi-Fi (registered trademark)) that can be connected to the Internet through a predetermined access point, and the like. When connecting wirelessly, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), and the like. In the case of a wired connection, the network also includes a network that is directly connected using a USB (Universal Serial Bus) cable or the like.

Note that the computer 90 can be virtually realized by distributing all or part of each hardware configuration to a plurality of computers 90 and interconnecting them via a network. In this way, the concept of the computer 90 includes not only the computer 90 housed in a single housing or case, but also a virtualized computer system.

<Basic functional configuration of computer 90>
The functional configuration of the computer realized by the basic hardware configuration of the computer 90 (FIG. 22) will be described. The computer includes at least functional units of a control section, a storage section, and a communication section.

Note that the functional units included in the computer 90 can also be implemented by distributing all or part of each functional unit to a plurality of computers 90 interconnected via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

The control unit is realized by the processor 901 reading various programs stored in the auxiliary storage device 903, loading them into the main storage device 902, and executing processing according to the programs. The control unit can implement a functional unit that performs various information processing depending on the type of program. Thereby, the computer is realized as an information processing device that performs information processing.

The storage unit is realized by a main storage device 902 and an auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Further, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 according to the program. Further, the control unit can cause the processor 901 to execute processing for adding, updating, and deleting data stored in the storage unit according to various programs.

A database refers to a relational database, which is used to manage a data set called a master, which is a tabular table whose structure is defined by rows and columns, in relation to each other. In a database, a table is called a table or a master, a table column is called a column, and a table row is called a record. In a relational database, you can set and associate relationships between tables and masters.
Normally, each table and each master is set with a column that serves as a primary key to uniquely identify a record, but it is not essential to set a primary key on a column. The control unit can cause the processor 901 to add, delete, or update records to a specific table or master stored in the storage unit according to various programs.

Note that the database and master in the present disclosure may include any data structure (list, dictionary, associative array, object, etc.) in which information is structurally defined. Data structures include data that can be considered as a data structure by combining data with functions, classes, methods, etc. written in any programming language.

The communication unit is realized by a communication IF 991. The communication unit realizes a function of communicating with other computers 90 via a network. The communication unit can receive information transmitted from other computers 90 and input it to the control unit. The control unit can cause the processor 901 to execute information processing on the received information according to various programs. Further, the communication unit can transmit information output from the control unit to another computer 90.

<Additional notes>
The matters described in each of the above embodiments are additionally described below.

(Additional note 1)
A contract template management program for storing an electronic contract template in a computer including a processor and a storage unit, the processor comprising: a contract reception step (S501) in which the processor receives a contract template related to a contract from a first user; A contract storage step (S503) that stores the contract template received in the contract reception step; and a request from a second user different from the first user to select a predetermined contract template from among the contract templates stored in the contract storage step. a contract template management program that executes a contract selection step (S904) that accepts a request, and a contract output step (S904) that outputs a predetermined contract template to a second user in response to a request received in the contract selection step; .
As a result, a user who is a user of the service related to this disclosure can upload a contract template that is a template of a contract document, and other users can select and download a desired contract template from the uploaded contract templates. It can be obtained by doing. Other users can edit the obtained contract template and efficiently create contract documents.

(Additional note 2)
The contract template management program according to appendix 1, wherein the processor executes a contract-related step (S101) in which the contract template stored in the contract storage step is stored in association with a contract document created based on the contract template.
Thereby, the contract template uploaded by the user is stored in association with the contract document created when the contract is actually concluded. It is possible to store and manage what kind of contract document a contract template is used in.

(Appendix 3)
The processor performs an evaluation calculation step (S706) in which the evaluation index value regarding the quality of the contract template stored in the contract storage step is calculated, and an evaluation storage step in which the evaluation index value calculated in the evaluation calculation step is stored in association with the contract template. (S706) and the contract template management program described in Supplementary Note 2.
Thereby, evaluation index values can be stored and managed in association with a plurality of contract templates uploaded by users. When a user obtains a contract template, by referring to the evaluation index value, a more suitable contract template can be efficiently obtained.

(Additional note 4)
The contract template management program according to appendix 3, wherein the evaluation calculation step (S706) is a step of calculating the evaluation index value of the contract template based on the contract document stored in association with the contract template in the contract-related step.
Thereby, the evaluation index value of the contract template can be calculated for the contract template by taking into consideration the information of the contract document created based on the contract template. When a user obtains a contract template, by referring to the evaluation index value, a more suitable contract template can be efficiently obtained.

(Appendix 5)
The evaluation calculation step (S706) is a step of calculating the evaluation index value of the contract template based on the party attribute, which is the attribute information regarding the contract party of the contract document stored in association with the contract template in the contract-related step. Contract template management program described.
Thereby, it is possible to calculate the evaluation index value of the contract template by taking into account the information of the parties in the contract document created based on the contract template. For example, it is conceivable to assign a high evaluation index value to a contract template used by a famous company when creating a contract document.
The user can efficiently obtain a more suitable contract template.

(Appendix 6)
In the evaluation calculation step (S706), the evaluation index value is calculated according to the degree of deviation between the contract document stored in association with the contract template in the contract-related step and the contract template, so that the larger the degree of deviation, the smaller the evaluation index value. The contract template management program according to appendix 4, which is a step of calculating an evaluation index value.
Thereby, when creating a contract document, it is possible to lower the evaluation index value of a contract template that has many changes from the contract template.
The user can efficiently obtain a more suitable contract template.

(Appendix 7)
The evaluation calculation step (S706) is a step of calculating an evaluation index value for the contract document stored in association with the contract template in the contract-related step such that the evaluation index value becomes smaller as the number of corrections from the contract template increases. There is a contract template management program described in Appendix 6.
As a result, when creating a contract document, if there are many corrections from the contract template, it is assumed that the quality of the contract template is lower than if there are few corrections, and the contract template is evaluated according to such quality. can do.
The user can efficiently obtain a more suitable contract template.

(Appendix 8)
The evaluation calculation step (S706) is a step of calculating the evaluation index value of the contract template based on the negotiation information related to the negotiation up to the conclusion of the contract document stored in association with the contract template in the contract-related step, as described in Appendix 4. Contract template management program.
As a result, contract templates for which it is difficult to form a consensus between the parties during the negotiation process of concluding a contract are assumed to be of lower quality than contract templates for which it is easier to form a consensus, and the Contract templates can be evaluated.
The user can efficiently obtain a more suitable contract template.

(Appendix 9)
In the evaluation calculation step (S706), the contract document stored in association with the contract template in the contract-related step is proposed by one contracting party to the other contracting party as a draft contract document, but the contract has not been concluded. If the evaluation index value of the contract template is smaller, the contract template management program according to supplementary note 8 is a step of calculating the evaluation index value so that the evaluation index value of the contract template becomes smaller.
As a result, it is assumed that contract templates that have not resulted in the conclusion of a contract are of lower quality than contract templates that have resulted in the conclusion of a contract, and the contract templates can be evaluated according to such quality.
The user can efficiently obtain a more suitable contract template.

(Appendix 10)
The contract template management program according to appendix 4, wherein the evaluation calculation step (S706) is a step of calculating the evaluation index value of the contract template based on the contract attributes of the contract document stored in association with the contract template in the contract-related step.
This allows the user to evaluate the contract template based on the evaluation index value that takes into account the contract attributes of the contract document created based on the contract template.
The user can efficiently obtain a more suitable contract template.

(Appendix 11)
The contract template management program according to appendix 10, wherein the contract attribute includes at least one of the following information: whether a contract document from which wording is extracted has been reviewed by a legal person, and a rating evaluation by a user.
This allows users to check and review contract documents that have been checked and reviewed by legal personnel such as lawyers, and other contract documents that have been given high evaluation index values by users. It can be evaluated as a contract template.
The user can efficiently obtain a more suitable contract template.

(Appendix 12)
Supplementary Note 2: The processor executes a presentation step (S903) in which the contract template stored in the contract storage step is presented to the user in a different manner depending on the contract document stored in association with the contract related step. Contract template management program described.
As a result, the user can check the uploaded contract templates in a manner that allows them to distinguish between contract templates used in actual contract conclusion and other contract templates. For example, the user can intuitively check the contract template associated with the contract document used in the actual conclusion of the contract.

(Appendix 13)
An information processing device comprising a processor and a storage unit, wherein the processor executes a contract template management program according to any one of Supplementary Notes 1 to 12.
As a result, a user who is a user of the service related to this disclosure can upload a contract template that is a template of a contract document, and other users can select and download a desired contract template from the uploaded contract templates. It can be obtained by doing.

(Appendix 14)
An information processing system including an information processing device including a processor and a storage unit, wherein the processor executes a contract template management program according to any one of Supplementary Notes 1 to 12.
As a result, a user who is a user of the service related to this disclosure can upload a contract template that is a template of a contract document, and other users can select and download a desired contract template from the uploaded contract templates. It can be obtained by doing.

(Appendix 15)
An information processing method executed by a computer including a processor and a storage unit, wherein the computer executes a contract template management program according to any one of appendices 1 to 12.
As a result, a user who is a user of the service related to this disclosure can upload a contract template that is a template of a contract document, and other users can select and download a desired contract template from the uploaded contract templates. It can be obtained by doing.

1 system, 10 server, 101 storage unit, 104 control unit, 106 input device, 108 output device, 20 first user terminal, 201 storage unit, 204 control unit, 206 input device, 208 output device, 30 second user terminal, 301 storage unit, 304 control unit, 306 input device, 308 output device

Claims (15)

A contract template management program for storing an electronic contract template in a computer including a processor and a storage unit, the program comprising:
The processor includes:
a contract reception step of receiving a contract template related to the contract from the first user;
a contract storage step for storing the contract template received in the contract reception step;
a contract selection step of accepting a request from a second user different from the first user to select a predetermined contract template from among the contract templates stored in the contract storage step;
a contract output step of outputting the predetermined contract template to the second user in response to the request received in the contract selection step;
A contract template management program that runs the. The processor includes:
a contract-related step of storing the contract template stored in the contract storage step in association with a contract document created based on the contract template;
execute,
The contract template management program according to claim 1. The processor includes:
an evaluation calculation step of calculating an evaluation index value regarding the quality of the contract template stored in the contract storage step;
an evaluation storage step of storing the evaluation index value calculated in the evaluation calculation step in association with the contract template;
execute,
The contract template management program according to claim 2. The evaluation calculation step is a step of calculating the evaluation index value of the contract template based on the contract document stored in association with the contract template in the contract-related step.
The contract template management program according to claim 3. The evaluation calculation step is a step of calculating the evaluation index value of the contract template based on a party attribute that is attribute information regarding the contract party of the contract document stored in association with the contract template in the contract-related step. ,
The contract template management program according to claim 4. In the evaluation calculation step, the evaluation index value decreases as the degree of deviation increases, depending on the degree of deviation between the contract document stored in association with the contract template in the contract-related step and the contract template. The step of calculating the evaluation index value as follows:
The contract template management program according to claim 4. The evaluation calculation step calculates the evaluation index value for the contract document stored in association with the contract template in the contract-related step such that the evaluation index value becomes smaller as the number of corrections from the contract template increases. This is the step of calculating
The contract template management program according to claim 6. The evaluation calculation step is a step of calculating the evaluation index value of the contract template based on negotiation information related to negotiations up to the conclusion of the contract document, which is stored in association with the contract template in the contract-related step.
The contract template management program according to claim 4. In the evaluation calculation step, the contract document stored in association with the contract template in the contract-related step is proposed as a draft contract document by one contract party to the other contract party, but the contract document is not concluded. If not, a step of calculating the evaluation index value so that the evaluation index value of the contract template is small;
The contract template management program according to claim 8. The evaluation calculation step is a step of calculating the evaluation index value of the contract template based on the contract attributes of the contract document stored in association with the contract template in the contract-related step.
The contract template management program according to claim 4. The contract attribute is defined in the contract document from which wording is extracted.
Whether there is a review by a legal person,
Rating evaluation by users,
at least one information of
including,
The contract template management program according to claim 10. The processor includes:
a presenting step of presenting the contract template stored in the contract storage step to the user in different manners depending on the contract document stored in association with the contract in the contract-related step;
3. The contract template management program according to claim 2, which executes the contract template management program. An information processing device comprising a processor and a storage unit,
The processor executes the contract template management program according to any one of claims 1 to 12.
Information processing device. An information processing system including an information processing device including a processor and a storage unit,
The processor executes the contract template management program according to any one of claims 1 to 12.
Information processing system. An information processing method executed by a computer including a processor and a storage unit,
The computer executes the contract template management program according to any one of claims 1 to 12.
Information processing method.