Program, method, and information processing apparatus

Abstract

To provide a technique for improving the efficiency of on-boarding for review task of contract terms, for mid-carrier human resources, or the like.SOLUTION: A storage unit stores document data, and a history of review content of a user who reviewed the content of the document data. A program causes a processor of a computer to execute the steps of: acquiring document data to be reviewed; specifying reviewed document data related to the to-be-reviewed document data, out of reviewed document data stored in the storage unit; and presenting the content of a review made on the specified reviewed document data.SELECTED DRAWING: Figure 12

Description

[Technical Field]

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

[0002] In conducting business activities, various contracts are concluded and the concluded contracts are managed. Electronic contract services are also used to approve document data between the parties, and the approved document data is managed on the service. For example, there are witness and party-based electronic signature methods.

[0003] Prior to the conclusion of a contract, the terms of the contract are reviewed by the legal department, etc. Patent Document 1 describes a document creation system that aims to "support the creation of documents when risk is taken into consideration," and includes "a selection means for selecting the type of document to be created, a creation means for creating a document according to the selected document type, a risk diagnosis means for diagnosing the risk of the created document, and a display means for displaying the created document in association with the diagnosed risk."

[0004] According to the technology of Patent Document 1, this has the effect of "enabling document creators to easily create documents that take risk into consideration." [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-138746 Summary of the Invention [Problem to be solved by the invention]

[0006] In business activities, operations are carried out by hiring personnel and ensuring that the hired personnel become accustomed to the work.

[0007] When legal department personnel review the terms and conditions set out in contracts, etc., there are books available that explain how to draft contracts, and although it is possible to generally review the pros and cons, it is also important to consider the circumstances of the company when conducting the review. For this reason, it is necessary to onboard personnel to review the contract by sharing knowledge of the company's circumstances.

[0008] Therefore, there is a need for a technology that can further improve the efficiency of onboarding mid-career employees and the like for the task of reviewing contract terms. [Means for solving the problem]

[0009] According to one embodiment of the present disclosure, there is provided a program for operating a computer having a processor, wherein a memory unit stores document data as well as a history of review content by users who have reviewed the contents of the document data, and the program causes the processor of the computer to execute the steps of acquiring the document data to be reviewed, identifying reviewed document data related to the document data to be reviewed from the reviewed document data stored in the memory unit, and presenting the review content made for the identified reviewed document data to the user. [Effects of the Invention]

[0010] According to the present disclosure, it is possible to further improve the efficiency of onboarding mid-career employees, etc., for the task of reviewing contract terms. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing the configuration of the system 1. [Figure 2] FIG. 2 is a diagram showing the configuration of the server 20. As shown in FIG. [Figure 3] FIG. 3 is a diagram showing the configuration of the terminal 10. As shown in FIG. [Figure 4] FIG. 4 is a diagram showing the data structure of the user database 211. As shown in FIG. [Figure 5] FIG. 5 is a diagram showing the data structure of the fastening management database 212. As shown in FIG. [Figure 6] FIG. 6 is a diagram showing the data structure of the document management database 213. As shown in FIG. [Figure 7] FIG. 7 is a diagram showing the data structure of the review history database 215. As shown in FIG. [Figure 8] FIG. 8 is a diagram showing the data structure of the user evaluation database 216. As shown in FIG. [Figure 9] FIG. 9 is a diagram showing the flow of processing for evaluating a user who has become a reviewer and calculating a score. [Figure 10] FIG. 10 is a diagram showing the flow of processing for acquiring document data to be reviewed, identifying document data including review contents previously reviewed by a reviewer, and presenting the document data to the user. [Figure 11] FIG. 11 shows the process flow for acquiring document data to be reviewed, accepting the designation of a user who has previously acted as a reviewer, identifying document data containing the review content of that user, and presenting the document data to the user. [Figure 12] FIG. 12 is a diagram showing an example of a screen that accepts upload of document data and displays document data including review contents of users who have reviewed in the past. [Figure 13] FIG. 13 shows an example of a screen that accepts uploading of document data and specification of a reviewer user who has previously reviewed a document, and displays document data including review content of the specified reviewer user. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. The names and functions of the components are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0013] <Outline of embodiment> <1.1 Overall system configuration> FIG. 1 is a diagram showing the configuration of the system 1.

[0014] 1 includes a contract conclusion and document management service server 20, a user terminal 10, a document review service server 93, a large-scale language model service server 95, a personnel management service server 96, and a user terminal 10A. These devices are connected for communication via a network 80.

[0015] In the illustrated example, terminals such as terminal 10 and terminal 10A are shown as terminals used by users of the contract conclusion and document management service provided by server 20, and each user operates their own terminal.

[0016] In this embodiment, each device (terminal device, server, etc.) can also be considered as an information processing device. That is, a collection of devices can be considered as one "information processing device," and system 1 can be formed as a collection of multiple devices. The way in which multiple functions required to realize system 1 according to this embodiment are allocated to one or multiple pieces of hardware can be determined appropriately in consideration of the processing capacity of each piece of hardware and / or the specifications required for system 1.

[0017] The terminal 10 is a device operated by a user. The terminal 10 is realized, for example, as follows. · Handheld devices such as smartphones and tablets Desktop PCs (Personal Computers), laptop PCs Wearable devices worn by users (wristwatches, glasses, etc.) The terminal 10 includes a communication IF (Interface) 12 , an input device 13 , an output device 14 , a memory 15 , a storage 16 , and a processor 19 .

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

[0019] The input device 13 is a device for receiving input operations from a user (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.).

[0020] The output device 14 is a device (such as a display or speaker) for presenting information to the user.

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

[0022] The storage 16 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

[0023] The processor 19 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

[0024] Server 20 is a device that provides a service for electronically concluding contracts and a service for managing document data concluded through electronic contracts. In system 1, the contract conclusion service provided by server 20 and the document data management service may be provided by different devices or different businesses. For example, server 20 may provide a document management service and, in addition to data on electronically signed contracts, optically read paper contracts with stamps to extract information such as the contract period and whether the contract is automatically renewed, and manage this information together with the scanned data of the contract as management information. This allows users to be notified when the contract period expires.

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

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

[0027] The input / output IF 23 functions as an interface with an input device for receiving input operations from the user and an output device for presenting information to the user.

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

[0029] The storage 26 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

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

[0031] The document review service server 93 is a service that supports document data reviews by accepting document data such as contracts and term sheets that specify contract terms and providing users with information such as whether each clause is favorable or unfavorable to the company, whether there are any missing clauses, and the importance of review items. The document review service server 93 provides a service that supports the above review using a rule base or a trained model. For example, a rule base may be used to review document data by previously associating specific wording or expressions with favorable or unfavorable conditions and explanations. Furthermore, the above review service can be provided by using data obtained by experts reviewing contracts, term sheets, etc. as training data to generate a trained model that responds with review results in response to input document data. The document review service server 93 can also summarize the contents of contracts and generate review comments using a large-scale language model and provide the results to users.

[0032] The large-scale language model service server 95 is a server that executes language processing tasks using a language model constructed by a learning process including artificial intelligence (AI). An LLM (Large Language Model) is a server that has previously learned a large amount of large-scale data (text data, etc.), for example, web content on the Internet, or a large amount of data stored in a specified database, and can execute various language processing tasks by giving the model a task.

[0033] The large-scale language model service server 95 accepts prompt inputs such as text, images, and voice, and generates and responds to the prompts. Examples of LLMs include GPT-3 and GPT-4 developed by OpenAI, and BERT developed by Google.

[0034] The personnel management service server 96 provides services to support recruitment, labor, and other operations for users such as the personnel department of an organization that conducts business activities. The personnel management service server 96, for example, manages a list of employees, and updates the employee list each time an employee joins or leaves the company. The personnel management service server 96 stores information for managing human resources, such as employee salaries and employee evaluations.

[0035] <1.2 Functional configuration of server 20> 2 is a diagram showing the configuration of the server 20. As shown in FIG. 2, the server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0036] The communication unit 201 performs processing for the server 20 to communicate with external devices.

[0037] The storage unit 202 stores various databases such as a user database 211, a contract management database 212, a document management database 213, a review history database 215, and a user evaluation database 216.

[0038] The user database 211 is a database for managing users.

[0039] The user database 211 contains information such as the user's name, employee number, etc., for using the services provided by the server 20. Details will be described later.

[0040] The contract conclusion management database 212 is a database that manages the contract conclusion process carried out by the electronic contract service provided by the server 20. Details will be described later.

[0041] The document management database 213 is a database for managing document data, and includes information for managing document data concluded through the electronic contract service provided by the server 20. Details will be described later.

[0042] The review history database 215 is a database that manages the history of reviews of document data such as contracts, etc. Details will be described later.

[0043] The user evaluation database 216 is a database that manages evaluation values ​​of users who have written reviews, as will be described in detail later.

[0044] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. By operating in accordance with the program, the control unit 203 performs functions shown as a reception control module 2041, a transmission control module 2042, a user management module 2043, a conclusion processing module 2044, a document management module 2045, a review processing module 2046, and a user evaluation module 2047.

[0045] The reception control module 2041 controls the process by which the server 20 receives signals from external devices in accordance with a communication protocol.

[0046] The transmission control module 2042 controls the process in which the server 20 transmits signals to external devices in accordance with a communication protocol.

[0047] The user management module 2043 is a module for managing information about each user who uses the system 1. Specifically, the user management module 2043 accepts registration of information about each user and updates the user database 211.

[0048] The conclusion processing module 2044 controls the process of the parties approving document data as a process for concluding a contract by electronic contract. Specifically, the conclusion processing module 2044 notifies each user who approves the document data, and updates the conclusion management database 212 in response to the operation of approving the document data.

[0049] The document management module 2045 controls the process of managing document data by referring to the document management database 213. Specifically, the document management module 2045 notifies the user whether to renew the contract when the contract period expires, based on the information about the contract period set in the document data, and updates the document management database 213 in response to the user's operation (such as renewal).

[0050] The review processing module 2046 causes the document review service server 93 or the like to review the contract conditions set forth in the document data, and updates the review history database 215 according to the review results. The review processing module 2046 accepts user comments and the like on the document data to be reviewed in accordance with user operations, and updates the review history database 215.

[0051] The user rating module 2047 refers to the review history database 215, identifies the rating value used to rate each user who reviews based on the history of reviews made by the user, and updates the user rating database 216.

[0052] <1.3 Configuration of Terminal 10> FIG. 3 is a diagram showing the configuration of the terminal 10. As shown in FIG.

[0053] As shown in FIG. 3, the terminal 10 includes multiple antennas (antenna 111, antenna 112), communication units (first communication unit 120, second communication unit 121) corresponding to the respective antennas, an input device 130 (including a touch-sensitive device 131), a display 132, an audio processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, a camera 160, a motion sensor 170, a memory unit 180, and a control unit 190. The terminal 10 also has functions and configurations (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.) that are not specifically shown in FIG. 3. As shown in FIG. 3, the blocks included in the terminal 10 are electrically connected by a bus or the like.

[0054] The antenna 111 emits a signal emitted by the terminal 10 as a radio wave. The antenna 111 also receives a radio wave from space and provides the received signal to the first communication unit 120.

[0055] The antenna 112 emits a signal emitted by the terminal 10 as a radio wave. The antenna 112 also receives a radio wave from space and provides the received signal to the second communication unit 121.

[0056] The first communication unit 120 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 111 so that the terminal 10 can communicate with other wireless devices. The second communication unit 121 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 112 so that the terminal 10 can communicate with other wireless devices. The first communication unit 120 and the second communication unit 121 are communication modules including a tuner, a received signal strength indicator (RSSI) calculation circuit, a cyclic redundancy check (CRC) calculation circuit, a high-frequency circuit, and the like. The first communication unit 120 and the second communication unit 121 perform modulation / demodulation, frequency conversion, and the like for wireless signals transmitted and received by the terminal 10, and provide the received signals to the control unit 190.

[0057] Input device 130 has a mechanism for accepting input operations by a user. Specifically, input device 130 is configured as a touch screen and includes touch-sensitive device 131. Touch-sensitive device 131 accepts input operations by a user of terminal 10. Touch-sensitive device 131 detects the user's touch position on the touch panel, for example, by using a capacitive touch panel. Touch-sensitive device 131 outputs a signal indicating the user's touch position detected by the touch panel to control unit 190 as an input operation.

[0058] The display 132 displays data such as images, videos, and text under the control of the control unit 190. The display 132 is realized by, for example, an LCD, an organic EL display, or the like.

[0059] The audio processing unit 140 modulates and demodulates audio signals. The audio processing unit 140 modulates a signal provided from the microphone 141 and provides the modulated signal to the control unit 190. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is realized, for example, by a processor for audio processing. The microphone 141 accepts audio input and provides an audio signal corresponding to the audio input to the audio processing unit 140. The speaker 142 converts the audio signal provided from the audio processing unit 140 into audio and outputs the audio to the outside of the terminal 10.

[0060] The location information sensor 150 is a sensor that detects the location of the terminal 10, and is, for example, a GPS (Global Positioning System) module. The GPS module is a receiving device used in a satellite positioning system. The satellite positioning system receives signals from at least three or four satellites, and detects the current location of the terminal 10 equipped with the GPS module based on the received signals.

[0061] The camera 160 is a device that receives light with a light receiving element and outputs the received light as a captured image. The camera 160 is, for example, a depth camera that can detect the distance from the camera 160 to a subject being photographed.

[0062] The motion sensor 170 includes an acceleration sensor, an angular velocity sensor, etc., and detects the movement of the terminal 10 .

[0063] The storage unit 180 is configured with, for example, a flash memory, and stores data and programs used by the terminal 10. The various types of information stored in the storage unit 180 will be described later.

[0064] The control unit 190 controls the operation of the terminal 10 by reading a program stored in the storage unit 180 and executing instructions included in the program. The control unit 190 is, for example, an application processor. By operating in accordance with the program, the control unit 190 fulfills the functions of an operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, a notification control unit 194, and a storage control unit 195.

[0065] Operation acceptance unit 191 performs processing to accept a user's input operation to an input device such as touch-sensitive device 131. Operation acceptance unit 191 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation, based on information about the coordinates where the user has touched touch-sensitive device 131 with a finger or the like.

[0066] The transmitting / receiving unit 192 performs processing for the terminal 10 to transmit and receive data to and from an external device such as the server 20 in accordance with a communication protocol.

[0067] The data processing unit 193 performs calculations on data that the terminal 10 has received as input in accordance with a program, and outputs the calculation results to a memory or the like.

[0068] The notification control unit 194 performs processing for displaying a display image on the display 132, processing for outputting sound from the speaker 142, and processing for generating vibrations.

[0069] The storage control unit 195 controls the storage of data in the storage unit 180 .

[0070] A description will be given of various types of information stored in storage unit 180. In one aspect, storage unit 180 stores various types of information such as user information 181, review result information 182, and user evaluation information 183.

[0071] The user information 181 is information about a user who uses the services of the server 20. The user information 181 includes, for example, information such as the employee number and name of the user.

[0072] The review result information 182 is information indicating the results of reviewing the document data.

[0073] The user evaluation information 183 is information on the score that evaluates the user who wrote the review.

[0074] <2 Data Structure> 4 is a diagram showing the data structure of the user database 211. The user database 211 includes the following items: "User ID," "Business Operator ID," "Name," "Email Address," "Department," "Position," "Date of Employment," "Date of Resignation," and "Qualifications."

[0075] The item "user ID" is information that identifies each user.

[0076] The item "business operator ID" is information that identifies each business operator.

[0077] The item "Name" is information about the user's name.

[0078] The item "email address" is information that serves as the user's contact information.

[0079] The item "department" is information about the user's department.

[0080] Specifically, the item "department" may include the following as information about the department to which the user belongs: - Business departments, sales departments, etc. that do not primarily handle legal affairs Departments that primarily handle legal affairs, such as the legal department and intellectual property department The item "position" is information about the position of the user.

[0081] The item "Date of joining" is information about the date on which a user joined an organization.

[0082] The item "Retirement Date" is information about the date on which the user retired from the organization.

[0083] The item "Qualifications held" is information about qualifications held by the user.

[0084] Specifically, the item "Qualifications held" includes the following information as qualifications held by the user: Qualifications that are expected to give the knowledge to review contracts, such as a lawyer Qualifications that are expected to show knowledge of business activities, such as small and medium-sized enterprise management consultants Qualifications that are expected to have the necessary knowledge in accounting, tax, etc., such as certified public accountants and tax accountants 5 is a diagram showing the data structure of the agreement management database 212. The agreement management database 212 includes an item "agreement ID," an item "sender ID," an item "recipient ID," an item "data to be agreed upon," an item "first email address," an item "second email address," an item "sent date and time," an item "user signature date and time," an item "agreement completion date and time," and an item "status."

[0085] The item "contract ID" is information that identifies each contract conclusion procedure.

[0086] Specifically, the item "Conclusion ID" includes identification information issued by the server 20 when a new registration of a process for concluding an electronic contract by specifying an approver is accepted for document data to be approved by the parties.

[0087] The item "sender ID" is information for identifying the party who will be the sender when the party approves document data.

[0088] Specifically, the item "sender ID" may be associated with information about the business (business ID) or information about the user (user ID) managed in the user database 211.

[0089] The item "recipient ID" is information for identifying the party who will be the recipient when the party approves document data.

[0090] Specifically, the item "Receiver ID" is information that identifies the party designated by the sender's user as the receiver, and like the sender ID, may be associated with information about the business (business ID) or the user (user ID) managed in the user database 211.

[0091] The item "data to be concluded" is document data to be approved by the parties.

[0092] Specifically, the item "data to be concluded" indicates data (files such as PDF) of transaction documents such as contracts, applications, and estimates.

[0093] The item "primary email address" is an email address that serves as a contact point for the user who will be the sender in the process of concluding a contract by approving document data.

[0094] Specifically, the item "first email address" is the email address of the user who performs the operation to send document data as the sender.

[0095] The item "secondary email address" is an email address that serves as the contact address of the user who approves as a recipient in the process of concluding a contract by approving document data.

[0096] Specifically, the item "second email address" is the email address of the user who will approve the document data as the recipient. Note that there may be multiple users who approve the document data among the parties, and if the user who sends the document data specifies the email addresses of multiple users who will approve the document data, the specified email addresses are also managed in the agreement management database 212.

[0097] The item "transmission date and time" is information on the date and time when an operation to transmit document data was accepted from a user who will be the sender in order to request approval of the document data from each user.

[0098] The item "user signature date and time" is information on the date and time when the user performed an operation to approve the document data.

[0099] Specifically, the item "User Signature Date and Time" includes information on the timing when a user who has been requested to approve document data checks the document data, performs an operation to approve, and then digitally signs the document data by having the operation accepted by the server 20. The server 20 digitally signs the document data each time a user performs an operation to approve, and stores the timing information in the agreement management database 212.

[0100] The item "conclusion completion date and time" is information about the date and time when the conclusion of the contract was completed.

[0101] Specifically, when a contract is concluded using the electronic contract service provided by server 20, the item "Date and time of conclusion completion" stores the date and time information in the conclusion management database 212, assuming that the conclusion of the contract is completed when all users designated to approve the document data perform the approval operation.

[0102] The item "status" is information indicating the stage at which the contract conclusion work is currently underway.

[0103] Specifically, the item "status" may include the following as the stage of the contract conclusion process: Before sending: Indicates that the document data has been registered on the server 20 by the sender, but has not yet been sent to the recipient. - In Progress: Indicates that the document data has been sent and approval by each user has not yet been completed. Completed: Indicates that the contract has been concluded Rejected, returned: Indicates that the contract was not completed due to reasons such as the user not approving the document data, or a timeout occurring after a certain period of time had passed without approval being completed. 6 is a diagram showing the data structure of the document management database 213. The document management database 213 includes an item "document management ID," an item "contract ID," an item "document title," an item "contract start date," an item "contract expiration date," and an item "automatic renewal status."

[0104] The item "document management ID" is information for identifying each document data being managed.

[0105] The item "contract ID" is information that identifies each contract conclusion procedure that the parties have performed to approve the document data.

[0106] Specifically, the item "contract ID" may be associated with information (contract ID) that identifies each contract conclusion, which is managed in the contract management database 212.

[0107] The item "document title" is information about the title of the document data being managed.

[0108] Specifically, the item "document title" may be a word used as a type or name of a contract, such as a confidentiality agreement, a sales contract, or a license agreement.

[0109] The item "contract start date" is information indicated as the start date of the contract in the document data.

[0110] Specifically, the value of the item "contract start date" may be set as follows. When the contract is concluded, the server 20 reads the start date of the contract from the contract data. - Information entered by the user as the contract start date The same applies to the following items "Contract Expiration Date" and "Automatic Renewal Enabled."

[0111] The item "contract expiration date" is information indicated as the contract expiration date in the document data.

[0112] The item "automatic renewal" is information indicating whether the contract period is automatically extended (automatic renewal) when the contract period expires in the document data without the parties having to re-enter the contract.

[0113] 7 is a diagram showing the data structure of the review history database 215. The review history database 215 includes an item "review ID," an item "document data," an item "document management ID," an item "review date and time," an item "review user," an item "review content," and an item "review requester's evaluation."

[0114] The item "review ID" is information that identifies each review performed on document data. The item "Document Data" is information about the document data to be reviewed. The item "document management ID" is information for identifying each document data being managed.

[0115] Specifically, the item "document management ID" may be associated with information (document management ID) that identifies each piece of document data, which is managed in the document management database 213.

[0116] The item "review date and time" is information about the date and time when the review was performed.

[0117] The item "reviewer user" is information about the user who reviewed the item.

[0118] The item "review content" is information indicating the results of the review.

[0119] Specifically, the item "review content" may include the following as review results: - Review results by the document review service server 93 (advantages and disadvantages of the conditions, importance, proposed revisions, etc.) Comments and suggested corrections entered by users (including information about users who enter review comments) The item "rating of review requester" is information indicating the rating of the user who requested the review on the review content of the reviewer.

[0120] Specifically, the item "review requester's evaluation" includes the result of the user who requested the review evaluating the reviewer based on the operation performed on the review result, and the following are possible. The user who requested the review can set a score for the review result. The number of reactions, such as "likes," added to posts sent via messaging tools to contact users for reviews 8 is a diagram showing the data structure of the user evaluation database 216. The user evaluation database 216 includes an item "user ID," an item "number of document data items," an item "amount of review data," an item "evaluation of review requester," an item "aggregation period," an item "overall evaluation," and an item "review performance document data."

[0121] The item "user ID" is information that identifies each user.

[0122] Specifically, the item "user ID" may be associated with user information (user ID) managed in the user database 211.

[0123] The item "number of document data items" is information on the number of items reviewed by the user during the collection period.

[0124] Specifically, the item "number of document data items" includes information on the number of items totaled by the server 20 by referring to the review history database 215 and identifying records that users have reviewed during the totaling period.

[0125] The item "review data volume" is information on the volume of data to which a user added a comment when writing a review during the collection period.

[0126] Specifically, the item "review data volume" includes the result of the server 20 aggregating the data volume of comments added to reviews by referring to the review history database 215 and identifying records for which users have performed reviews during the aggregation period.

[0127] The item "review requester's evaluation" is information on the evaluation of the user requesting the review with respect to the user who is writing the review.

[0128] Specifically, the item "Review requester's evaluation" includes the result of the server 20 identifying the evaluation of the user who requested the review by referring to the review history database 215 and identifying records in which users have performed reviews during the aggregation period, and evaluating the reviewer based on the identified results.

[0129] The item "aggregation period" is information that specifies the period during which the review was made when evaluating the user who made the review.

[0130] The item "overall rating" is information resulting from identifying the overall score of the user who wrote the review by weighting the values ​​of each item managed in the user rating database 216, for example.

[0131] The item "reviewed document data" is information indicating the type of contract that the user has reviewed.

[0132] Specifically, the item "Review History Document Data" includes the results of the server 20 identifying the types of contracts that have been reviewed by referring to the review history database 215 and identifying records that have been reviewed by users.

[0133] <3 operations> FIG. 9 is a diagram showing the flow of processing for evaluating a user who has become a reviewer and calculating a score.

[0134] In step S921, the server 20 refers to the review history of each user in the review history database 215, evaluates each user as a reviewer, and updates the user evaluation database 216.

[0135] In step S911, the terminal 10 accepts an operation to access a service.

[0136] In step S923, the server 20 refers to the user evaluation database 216 and presents the score of each user.

[0137] In step S913, the terminal 10 displays the score of each user.

[0138] The terminal 10 accepts a designation as to whether or not to provide the score of each user to an external system.

[0139] In step S925, the server 20 provides information on the time series transition of each user's score to an external system (for example, the server 96 of a personnel management service), which can be used for personnel evaluations and the like.

[0140] FIG. 10 is a diagram showing the flow of processing for acquiring document data to be reviewed, identifying document data including review contents previously reviewed by a reviewer, and presenting the document data to the user.

[0141] In step S1021, the server 20 presents the user with a screen for uploading document data to be reviewed.

[0142] In step S1011, the terminal 10 accepts an operation to designate document data to be reviewed.

[0143] In step S1023, the server 20 acquires the document data to be reviewed.

[0144] In step S1025, the server 20 identifies reviewed document data related to the document data to be reviewed from the reviewed document data stored in the review history database 215.

[0145] The server 20 evaluates the user of the reviewer who wrote the review based on the history of the review content stored in the review history database 215.

[0146] The server 20 evaluates the reviewer user who wrote the review based on at least one of the following: the number of document data items for which the reviewer user has registered review content, the amount of data entered as review content by the reviewer user, the length of time the reviewer user has been employed, the qualifications held by the reviewer user, and the job title of the reviewer user. The server 20 assigns weights to these pieces of information to determine the score used to evaluate the user.

[0147] The server 20 associates information about users who have reviewed with the review contents of the users and stores them as history in the review history database 215. To identify reviewed document data, the server 20 determines the attributes of the document data to be reviewed, and identifies a user according to the determined attributes from among users who have reviewed document data whose review contents are stored as history in the review history database 215 (identifying the user who reviewed the identified contract). The server 20 identifies reviewed document data that has review contents of the identified user.

[0148] In step S1027, the server 20 presents the review content made on the identified reviewed document data to the user.

[0149] The server 20 presents the reviewer's user evaluation results together with the review content.

[0150] The server 20 presents reviewed document data including review contents of reviewer users who have received relatively high ratings, according to the evaluation results of the reviewer users.

[0151] In step S1013, the terminal 10 displays the review content made on the reviewed document data.

[0152] In step S1015, the terminal 10 accepts an operation to set the reviewer user of the reviewed document data as the creator of the document data, the person in charge of review, the approver who approves the document data after review, or the like.

[0153] In step S1029, the server 20 executes processing according to the role designated in step S1015.

[0154] FIG. 11 shows the process flow for acquiring document data to be reviewed, accepting the designation of a user who has previously acted as a reviewer, identifying document data containing the review content of that user, and presenting the document data to the user.

[0155] In step S1121, the server 20 presents the user with a screen for specifying a user who has previously left a review.

[0156] In step S1111, the terminal 10 accepts an operation to specify a user who has previously performed a review, and an operation to specify document data to be reviewed.

[0157] In step S1123, the server 20 acquires the document data to be reviewed and acquires the user's designation of the reviewer.

[0158] In step S1125, the server 20 identifies, from the reviewed document data accumulated in the review history database 215, reviewed document data in which the review content of the user of the designated reviewer is stored.

[0159] In this way, the server 20 presents document data that has been reviewed in the past by a user designated by the user. The server 20 may also identify document data that has been reviewed in the past by a user in the same department as the user, or document data that has been reviewed by an experienced user (with a certain number of years of employment).

[0160] The server 20 evaluates the user of the reviewer who wrote the review based on the history of the review content stored in the review history database 215.

[0161] Specifically, the server 20 evaluates the reviewer user who wrote the review based on at least one of the number of document data items for which the reviewer user has registered review content, the amount of data entered by the reviewer user as review content, the length of time the reviewer user has been employed, the qualifications held by the reviewer user, and the reviewer user's job title.

[0162] The server 20 stores information about the user who performed the review in association with the review content of that user in the review history database 215, and identifies the reviewed document data by determining the attributes of the document data to be reviewed (for example, the title of the document data, such as a confidentiality agreement, design document, application form, etc.), and identifies users according to the determined attributes from among the users who reviewed the document data whose review content is stored as history in the review history database 215 (identifying users who reviewed contracts with the determined attributes).

[0163] The server 20 identifies reviewed document data that includes review content from the identified user.

[0164] In step S1127, the server 20 preferentially presents to the user the reviewed document data identified as including the review content of the reviewer user.

[0165] The server 20 presents the reviewer's evaluation results to the user.

[0166] The server 20 presents reviewed document data including review contents of reviewer users with relatively high ratings according to the evaluation results of the reviewer users.

[0167] <4 Screen example> FIG. 12 is a diagram showing an example of a screen that accepts upload of document data and displays document data including review contents of users who have reviewed in the past.

[0168] A screen 1200 is an operation screen for reviewing document data.

[0169] The account display area 1210 is an area for displaying information about the account of a user who has logged in to a service provided by the server 20.

[0170] The reviewed document display area 1220 is an area that, when an upload of document data to be reviewed is accepted, identifies and displays document data that has been reviewed in the past.

[0171] The contract data 1221 is an area that displays details of the document data to be reviewed.

[0172] The upload receiving unit 1222 is an operation member that receives an operation from the user to acquire document data to be reviewed on the server 20 by uploading or the like.

[0173] The upload reception unit 1222 corresponds to the processing of step S1011 and the like.

[0174] The past reviewer display area 1233 is an area for displaying information about users who have reviewed related past document data.

[0175] Specifically, the past reviewer display area 1233 includes: Reviewed contracts, Are you currently employed or retired? The rating value of the user who reviews the item, Qualifications held, By displaying such information, it becomes easier to gauge the reviewer's experience and to determine whether the reviewer is currently employed and can be consulted within the company.

[0176] The reviewed document data information 1234 is an area that displays the review results of related past document data.

[0177] As shown in the figure, the reviewed document data information 1234 displays the parties to the contract, the reviewer, the reviewer's evaluation, an outline of the review by the reviewer, etc., making it easier for the user to determine whether the related reviewed document data is useful to the user. This corresponds to the processing of step S1027, etc.

[0178] The preview operation acceptance section 1235 is an operation member that accepts an operation to display details of related past document data.

[0179] The request operation receiving unit 1237 is an operation member that receives an operation to request the extracted reviewer to review the uploaded document data.

[0180] The request operation receiving unit 1237 corresponds to the processing of step S1029 and the like.

[0181] FIG. 13 shows an example of a screen that accepts uploading of document data and specification of a reviewer user who has previously reviewed a document, and displays document data including review content of the specified reviewer user.

[0182] The reviewer designation receiving section 1326 is an operation member that receives the designation of a user who has a track record of reviewing.

[0183] The reviewer designation receiving unit 1326 corresponds to the processing of step S1111 and the like.

[0184] The past reviewer display area 1333 is an area that displays information about a reviewer designated by the user.

[0185] The reviewed document data information 1334 is an area that displays the review results of document data that has been reviewed in the past by a reviewer designated by the user.

[0186] The preview operation receiving section 1335 is an operation member that receives an operation to display details of document data that has been reviewed in the past by a reviewer designated by the user.

[0187] <Modification> In addition to the aspects described in the above embodiment, the following may be adopted.

[0188] In the above embodiment, it has been described that each business provides a service using each device, such as the document review service server 93, the large-scale language model service server 95, and the human resources management service server 96. However, it is also possible for a single business to provide multiple services. For example, a single business may provide a contract conclusion service, a document management service, and a business support (approval application) service.

[0189] In the above embodiment, the review user is evaluated based on the review results of the contract. The user may be evaluated based on the review results of the contract, as well as the term sheet that defines the contract terms, or the review user may be evaluated based on the number of comments added to the document data, the number of posts in the review thread on the messaging tool, the number of characters, etc.

[0190] Although several embodiments of the present disclosure have been described above, these embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are intended to be included in the scope of the inventions and their equivalents as defined in the claims, as well as in the scope and spirit of the inventions.

[0191] The functions performed by the components described herein may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), a CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes programs stored in memory.

[0192] In this specification, a circuitry, unit, or means is hardware that is programmed to realize or performs the described functions, which may be any hardware disclosed herein or any hardware known to be programmed to realize or perform the described functions.

[0193] If the hardware is a processor considered to be a type of circuitry, the circuitry, means, or unit is a combination of the hardware and software used to configure the hardware and / or processor.

[0194] <Additional Notes> The matters explained in the above embodiment will be supplemented below.

[0195] (Appendix 1) A program for operating a computer having a processor, wherein a memory unit stores document data as well as a history of review content by users who have reviewed the contents of the document data, and the program causes the processor of the computer to execute the steps of acquiring the document data to be reviewed, identifying reviewed document data related to the document data to be reviewed from the reviewed document data stored in the memory unit, and presenting to the user the review content made for the identified reviewed document data.

[0196] (Appendix 2) A program as described in Appendix 1, in which a memory unit stores information about the user who wrote the review in association with the review content of the user as a history, and the program further causes the processor to execute a step of accepting an operation to designate the reviewer user who wrote the review, in the identification step, identifying reviewed document data in which the review content of the designated reviewer user is stored, and in the presenting step, presenting preferentially reviewed document data identified as including the review content of the reviewer user.

[0197] (Appendix 3) A program described in any of Appendices 1 to 2, wherein the program further causes the processor to execute a step of evaluating the user of the reviewer who wrote the review based on the history of review content stored in the memory unit, and in the presentation step, presents the evaluation results of the reviewer's user.

[0198] (Appendix 4) The program according to appendix 3, wherein in the presenting step, reviewed document data including review contents of reviewer users with relatively high ratings is presented according to the evaluation results of the reviewer users.

[0199] (Appendix 5) A program described in any of Appendices 3 to 4, wherein in the evaluating step, the reviewer user who wrote the review is evaluated based on at least one of the number of document data items for which the reviewer user has registered review content, the amount of data entered by the reviewer user as review content, the length of time the reviewer user has been employed, the qualifications held by the reviewer user, and the reviewer user's job title.

[0200] (Appendix 6) A program described in any of Appendices 3 to 5, wherein a memory unit stores information about the user who wrote the review in association with the review content of the user as a history, and in the identification step, identifying reviewed document data involves determining the attributes of the document data to be reviewed, identifying a user according to the determined attributes from among users who reviewed document data whose review content is stored as a history in the memory unit, and identifying reviewed document data that has review content from the identified user.

[0201] (Appendix 7) A program described in any of Appendices 1 to 6, wherein a memory unit stores a history of approval operations between users for reviewed document data, and the user who performed the approval operation for the reviewed document data identified in the identification step is set as at least one of the creator of the document data to be reviewed, the person in charge of reviewing the document data to be reviewed, and the approver who performs the approval operation after reviewing the document data to be reviewed.

[0202] (Appendix 8) A method for operating a computer having a processor, wherein a memory unit stores document data together with a history of review content by users who have reviewed the contents of the document data, and the method includes the steps of the computer processor acquiring the document data to be reviewed, identifying reviewed document data related to the document data to be reviewed from the reviewed document data stored in the memory unit, and presenting to the user the review content made for the identified reviewed document data.

[0203] (Appendix 9) An information processing device, wherein a memory unit stores, together with document data, a history of review content by users who have reviewed the contents of the document data, and a control unit of the information processing device executes the steps of: acquiring the document data to be reviewed; identifying reviewed document data related to the document data to be reviewed from the reviewed document data stored in the memory unit; and presenting to the user the review content made for the identified reviewed document data.

Claims

1. A program for operating a computer having a processor, the storage unit stores, together with the document data, a history of review contents of users who have reviewed the contents of the document data; The program causes the processor of the computer to: acquiring document data to be reviewed; Identifying reviewed document data related to the document data to be reviewed from the reviewed document data stored in the storage unit; and presenting to a user the review content made on the identified reviewed document data.

2. the storage unit stores information about the user who wrote the review and the review content of the user in association with each other as the history; The program further causes the processor to receiving an operation to designate a user of the reviewer who wrote the review; In the step of specifying, the reviewed document data in which review contents of the user of the designated reviewer are stored is specified; The program according to claim 1 , wherein the step of presenting the reviewed document data identified as including review content of the user of the reviewer is presented with priority.

3. The program further causes the processor to executing a step of evaluating a user of a reviewer who has written a review based on the history of the review content stored in the storage unit; The program according to claim 1 , wherein the step of presenting presents the evaluation results of the reviewers.

4. 4. The program according to claim 3, wherein the step of presenting presents the reviewed document data including review contents of the reviewer's users who have relatively high ratings according to the evaluation results of the reviewer's users.

5. In the step of evaluating, the user of the reviewer who wrote the review is evaluated, the number of the document data for which the reviewer user has registered review content; The amount of data entered by the reviewer user as review content; The period during which the reviewer user has been employed; the qualifications held by said reviewer user; the reviewer's user role; The program according to claim 3 , wherein the user is evaluated based on at least one of the following:

6. the storage unit stores information about the user who wrote the review and the review content of the user in association with each other as the history; In the step of identifying, the reviewed document data is identified by determining attributes of the document data to be reviewed; identifying a user according to the determined attribute from among users who have reviewed document data whose review contents are stored as a history in the storage unit; The program according to claim 3 , further comprising: identifying the reviewed document data having review content of the identified user.

7. The storage unit stores a history of operations for approving the reviewed document data between users, a user who has performed the operation of approving the reviewed document data identified in the identifying step; the creator of the document data to be reviewed; a person in charge of reviewing the document data to be reviewed; an approver who performs an operation to approve the document data to be reviewed after reviewing the document data; The program according to claim 1 , wherein the program is set as at least one of the above.

8. 1. A method of operating a computer having a processor, comprising: the storage unit stores, together with the document data, a history of review contents of users who have reviewed the contents of the document data; The method further comprises: acquiring document data to be reviewed; Identifying reviewed document data related to the document data to be reviewed from the reviewed document data stored in the storage unit; and presenting to a user the review content made on the identified reviewed document data.

9. An information processing device, the storage unit stores, together with the document data, a history of review contents of users who have reviewed the contents of the document data; a control unit of the information processing device, acquiring document data to be reviewed; Identifying reviewed document data related to the document data to be reviewed from the reviewed document data stored in the storage unit; and presenting to a user the review content made on the identified reviewed document data.

Images