Program, method, and information processor

Abstract

To satisfy a need for a technology that enables necessary procedures for concluding a contract to be carried out more smoothly.SOLUTION: In a storage unit, information is stored that defines, in multiple stages, task items a user needs to perform when a contract is concluded between parties. The program causes a processor of a computer to execute the steps of: presenting, to a user, task items included in a first stage among task items for concluding a contract, and receiving input indicating whether or not the user has executed each of the task items; detecting that, with respect to at least one of the task items included in the first stage, the user has progressed to an extent sufficient to proceed to a second stage following the first stage; and a step of setting a state in which input is accepted indicating whether or not the user has executed task items included in the second stage, in accordance with the detection result in the detecting step.SELECTED DRAWING: Figure 11

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] Patent Document 1 addresses the issue of "ensuring the conclusion and cancellation of a contract and storing electronic contracts," and describes a technology that "includes a contract application client that sends contract application information to a contract acceptance server via a communications network and receives contract information from the contract acceptance server, a contract acceptance server that receives application information from the client via the communications network, generates contract information from the contract application information, and sends the contract information to the client, and a contract storage server that obtains communication messages between the client and the contract acceptance server, attaches electronic signatures to the communication messages, and stores the communication messages and the electronic signatures."

[0004] According to the technology of Patent Document 1, this has the effect of "ensuring the conclusion and cancellation of a contract, allowing the storage of the contract, and also making it possible to detect any misconduct by the contract recipient in the conclusion of an electronic contract." [Prior art documents] [Patent documents]

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

[0006] Concluding a contract between parties means that a transaction is taking place, and therefore various procedures are required.

[0007] On the other hand, when concluding a contract, the person in charge may not be able to fully grasp the overall picture of the work and may forget to carry out necessary procedures, which could result in the contract being concluded without sufficient prior confirmation.

[0008] Therefore, there is a need for a technology that can more smoothly carry out the necessary procedures when concluding a contract. [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, in which a memory unit stores information defining task items that a user needs to perform when concluding a contract between parties, divided into multiple stages. The program causes the processor of the computer to perform the following steps: for each task item for concluding the contract, presenting the task items included in the first stage to the user and accepting input as to whether the user has performed the task items; detecting that the user has progressed one or more task items included in the first stage to the extent that they can proceed to a second stage following the first stage; and, in response to the detection in the detecting step, putting the task items included in the second stage into a state where they can accept input as to whether the user has performed the task items. [Effects of the Invention]

[0010] According to the present disclosure, the necessary procedures for concluding a contract can be carried out more smoothly. [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 business operator management database 214. As shown in FIG. [Figure 8] FIG. 8 is a diagram showing the data structure of the approval request database 215. As shown in FIG. [Figure 9] FIG. 9 is a diagram showing the data structure of the task progress database 216. [Figure 10] FIG. 10 is a diagram showing the flow of processing for managing the progress of a task by presenting the process leading up to the conclusion of a contract as a plurality of steps to be completed by the user. [Figure 11] FIG. 11 is an example of a screen that displays the tasks up to the conclusion of a contract and supports the user in the contract conclusion process. [Figure 12] FIG. 12 is an example of a screen showing that a certain stage of the task leading up to the conclusion of a contract has been completed and the next stage has begun. [Figure 13] Figure 13 is an example of a screen that supports the improvement of contract-conclusion work. 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 business support (approval) service server 92, a document review service server 93, a business information provision service server 94, a large-scale language model service server 95, a personnel management service server 96, and a user terminal 10A. These devices are connected to each other 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 business support (approval request) service server 92 is a server that provides a service to support business operations such as applying for approval in an organization (such as a business company) that conducts business activities. The business support (approval request) service server 92 provides a service to a user that enables the user to design a workflow for obtaining budget approval among multiple users, for example.

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

[0033] The business information service server 94 is a service that collects information on organizations and groups such as business companies and provides information related to the credibility of these organizations. Information related to the credibility of organizations is accumulated by collecting publicly available information such as news articles and IR information, and also by the operator of the business information service independently collecting information through interviews, etc. Server 94 provides the following information related to the credibility of organizations. Whether the organization is (or may be) a party that falls under the conditions for contract termination, such as being an anti-social force. For example, there may be publicly available information, such as a database or news article, that indicates that the organization falls under the above conditions. The reputation of a business company or other organization, such as when consumers have a negative reaction and the information is spread in the news, on social media, etc. For example, information may be spread on social media with negative keywords and a certain number of impressions. Information about business performance, such as sales, revenue (profit amount, profit margin, etc.), and assessment results regarding business continuity (continued losses, possibility of bankruptcy, bond ratings, etc.). 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.

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

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

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

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

[0038] The storage unit 202 stores various databases such as a user database 211, a contract management database 212, a document management database 213, a business management database 214, an approval application database 215, and a task progress database 216.

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

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

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

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

[0043] The business management database 214 is a database for managing information on the credibility of business operators, such as whether or not a transaction with the business operator can be continued. Details will be described later.

[0044] The approval request database 215 is a database that manages approval requests for concluding contracts, etc. Details will be described later.

[0045] The task progress database 216 is a database that manages the progress of tasks of users related to the conclusion of a contract, as will be described in detail later.

[0046] 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 exhibits 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, an approval processing module 2046, and a task progress module 2047.

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

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

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

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

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

[0052] The approval request processing module 2046 receives an operation to apply for approval from a user and controls the process in which an approver approves the approval. Specifically, the approval request processing module 2046 notifies each user who approves the approval request, and updates the approval request database 215 in response to the operation to approve the approval.

[0053] The task progress module 2047 divides each task item up to the conclusion of the contract into multiple stages and manages the progress of the user's task at each stage. Specifically, the task progress module 2047 updates the task progress database 216 in accordance with the user's operation to complete the task at each stage.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0072] 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, schedule information 182, and the like.

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

[0074] The schedule information 182 is information about the user's schedule, and is information that associates calendar dates with plans. The terminal 10 can register schedules by using, for example, a cloud-based schedule sharing service. The server 20 can grasp whether each user has plans by cooperating with the schedule sharing service.

[0075] <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."

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

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

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

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

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

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

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

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

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

[0085] 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."

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

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

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

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

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

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

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

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

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

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

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

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

[0098] The item "transmission date and time" is information about 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.

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

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

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

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

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

[0104] 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."

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

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

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

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

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

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

[0111] 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."

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

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

[0114] 7 is a diagram showing the data structure of the business management database 214. The business management database 214 includes the following items: "Business ID," "Business Name," "Reputation," "Possibility of Bankruptcy," "Company Standards," and "Business Partner Registration."

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

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

[0117] The item "business name" is information about the name of the business.

[0118] The item "reputation" is information about the reputation of the business.

[0119] Specifically, the "reputation" item communicates with the business information service server 94 to store information on the history of negative reactions from consumers to a business and the spread of coverage in the news, on social media, etc., or the score that the business information service server 94 etc. has calculated based on this information to evaluate the business's reputation.

[0120] The item "Probability of bankruptcy" is information about the business performance of the company.

[0121] Specifically, the item "Possibility of Bankruptcy" stores information about business performance such as sales, revenue (profit amount, profit margin, etc.), and evaluation results regarding business continuity (continued losses, possibility of bankruptcy, bond rating, etc.) by communicating with the business information service server 94.

[0122] The item "Company Standards" is information indicating the user's standards for whether or not to do business with a business partner.

[0123] Specifically, the item "Company Standards" indicates the criteria for whether or not to do business with a company, based on reputation information, bankruptcy possibility information, etc. For example, some businesses may do business with a company without paying attention to its reputation score.

[0124] The item "Business Partner Registration" is information indicating whether or not the company is registered as a business partner within the company.

[0125] Specifically, the "Customer Registration" item may be used to determine whether the user meets the requirements for registration as a customer, check whether the customer is managed in a customer database, and store the results.

[0126] 8 is a diagram showing the data structure of the approval request database 215. The approval request database 215 includes an item "approval request ID," an item "applicant ID," an item "approver ID," an item "application date," an item "approval date," an item "application content," and an item "conclusion ID."

[0127] The item "approval request ID" is information that identifies each approval request.

[0128] The item "Applicant ID" is information that identifies the user who is the applicant for the approval request.

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

[0130] The item "Approver ID" is information that identifies the user who approves the approval request.

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

[0132] The item "application date" is information about the date and time when an operation to transmit the approval request data was accepted from the applicant user in order to request each user to approve the approval request data.

[0133] The item "approval date" is information about the date and time when the user performed an operation to approve the data of the approval request.

[0134] The item "application content" is information indicating the content of the approval request.

[0135] Specifically, the item "application content" includes the content of the approval request, such as: Conclusion of contracts Budget approval Expense claim The item "contract ID" is information that identifies each contract conclusion procedure.

[0136] Specifically, the item "conclusion ID" may be associated with information (conclusion ID) that identifies each contract conclusion procedure, which is managed in the conclusion management database 212. This associates the data of the approval request in the approval request database 215 with the data of the contract conclusion in the conclusion management database 212.

[0137] 9 is a diagram showing the data structure of the task progress database 216. The task progress database 216 includes an item "task ID," an item "user ID," an item "task registration date," an item "contract type," an item "first stage task," an item "first stage task completion date," an item "second stage task," an item "second stage task completion date," an item "status," and an item "task score."

[0138] The item "task ID" is information that identifies the entire process leading up to the conclusion of a contract as one task.

[0139] The item "user ID" is information for identifying a user.

[0140] The item "task registration date" indicates the date and time when a task indicating the entire process up to the conclusion of a contract was registered in the task progress database 216.

[0141] The item "contract type" is information about the type of contract that is the subject of the contract.

[0142] Specifically, the item "contract type" manages various types of contracts such as a confidentiality agreement, a sales contract, etc. as the type of contract.

[0143] The item "First stage task" is a task included in the first stage when the process leading up to the conclusion of a contract is divided into multiple stages.

[0144] Specifically, the "First Stage Task" item may include multiple task items. For example, if the first stage is set to "Request review from legal," the first stage may include task items such as requesting review from legal via a messaging tool or form, receiving the review results from legal, etc.

[0145] The item "first stage task completion date" is information indicating the timing when each of one or more task items included in the first stage was completed.

[0146] The item "Second stage tasks" is a task included in the second stage following the first stage when the process leading up to the conclusion of a contract is divided into multiple stages.

[0147] Specifically, if the item "Second stage task" is set as the second stage, "Request evaluation of possibility of registration with business partner" (for example, whether it falls under clauses for contract termination such as anti-social organization checks), it may include task items such as requesting the legal department to conduct anti-social organization checks on the parties to the contract.

[0148] In the illustrated example, tasks up to the second stage are shown, but multiple stages may be set, such as a third stage following the second stage, and a fourth stage following the third stage.

[0149] The item "second stage task completion date" is information indicating the timing when each of one or more task items included in the second stage was completed.

[0150] The item "status" is information for managing the progress of tasks that indicate the entire process up to the conclusion of a contract.

[0151] Specifically, the item "status" manages the following states: Before the task begins · What stage of the task are you in (how far have you completed the task items) Complete the entire task ·cancel The item "Work score" is a score that evaluates the work of the user in the process leading up to the conclusion of the contract.

[0152] Specifically, the item "activity score" may include a score evaluated as follows: The score may be determined by weighting each parameter. The result of tallying up the work time for each task for the contract conclusion track record managed in the contract conclusion management database 212 (the work time for each task is measured from the timing of task completion) · Each user's contact history in the workflow of approval requests and contract conclusion (number of comments on threads in messaging tools, etc., frequency of comments, etc., as well as the number of review comments added by users in contract reviews, the amount of comment data, etc.) <3 operations> FIG. 10 is a diagram showing the flow of processing for managing the progress of a task by presenting the process leading up to the conclusion of a contract as a plurality of steps to be completed by the user.

[0153] In step S1011, the terminal 10 accepts an operation from the user to newly register a task for managing the process up to the conclusion of a contract. In step S1021, the server 20 presents an operation screen that allows the user to confirm each task item that is defined by dividing the task items that the user needs to perform when concluding a contract between the parties into a plurality of stages.

[0154] Here, the multiple stages include a stage of requesting approval to obtain approval within the parties to conclude a contract between the parties.

[0155] The stage following the stage of requesting approval includes the stage of conclusion work in which a contract is concluded between the parties upon approval of the request for approval.

[0156] Prior to the stage of requesting approval, the process may include at least one of the following stages: a stage of requesting a reviewer to review each clause of the contract, or a stage of confirming whether the parties to the contract are specific parties specified in the termination clause of the contract.

[0157] The server 20 may store information on task items defined in multiple stages for each type of contract between the parties (the "contract type" item in the task progress database 216). The server 20 may present task items of the type to the user according to the type of contract and accept input from the user.

[0158] The server 20 stores the work time required by the user to perform the task item in the task progress database 216 (such as the item "Date of completion of first stage task" in the task progress database 216).

[0159] The server 20 may refer to the schedule information (schedule information 182) of the user in charge of each task item for concluding the contract, estimate the available work time of the user in charge of the task item based on the free time in the schedule, and estimate the expected work time to complete the conclusion of the contract based on the estimated available work time. For example, by referring to the schedule of the user who will review the contract, the time until completion of the task can be estimated based on the availability of the schedule (if the schedule is full, the time until completion of the task will be longer, and if the schedule is relatively free, the time until completion of the task will be shorter).

[0160] The server 20 sets a deadline for each task item for concluding a contract based on at least one of the actual timing for completing the task items or the actual working time for the task stored in the task progress database 216, presents the set deadline to the user, and presents to the user an estimated working time for completing each task item and concluding the contract.

[0161] In step S1013, the terminal 10 presents the task items included in a certain stage for each task item for concluding a contract to the user and accepts input as to whether or not the task item has been performed by the user. For example, if the task item of requesting a legal department for review has been performed, the URL of the post may be accepted as input.

[0162] In step S1023, the server 20 updates the task progress database 216 according to the user's input for the task item.

[0163] The server 20 sets a deadline for each task item for concluding a contract based on at least one of the actual timing for completing the task items or the actual working time stored in the task progress database 216, presents the set deadline to the user, and presents to the user an estimate of the working time required to complete each task item and conclude the contract.

[0164] The server 20 may refer to the schedule information (schedule information 182) of the user in charge of each task item for concluding the contract, estimate the available work time of the user in charge based on the available time in the schedule, and estimate the expected work time to complete the conclusion of the contract based on the estimated available work time.

[0165] In step S1025, when the server 20 detects that the user has progressed one or more task items included in a certain stage to the extent that they can proceed to the next stage (for example, the URL or user check operation has been performed for all required task items in a certain stage), the server 20 updates the status to a state where it accepts input as to whether the user has executed the task items in the next stage (item "status" in the task progress database 216), and presents an operation screen to the user.

[0166] For example, upon detecting that approval has been obtained among the parties at the stage of requesting approval (such as notification that the application for approval has been completed), the server 20 enters a state in which it is ready to accept input regarding task items included in the stage of the closing work.

[0167] The server 20 takes over parameters recorded by the user when the user performs the task item of the first stage, which are also used in the task item of the second stage, without user input, and sets them as parameters for the task item of the second stage. For example, the server 20 may set parameters of the parties to the contract at the stage of requesting a review, or of the specific parties at the stage of confirming whether the specific parties fall under the anti-social organization check, as parameters of the parties to the contract in the request for approval or parameters of the parties managed in the conclusion work, without user input.

[0168] The server 20 includes a stage of requesting approval for the parties to obtain approval within the parties to conclude a contract between them, and a stage of concluding a contract between the parties when the approval request is approved, as a stage following the stage of requesting approval. Prior to the stage of requesting approval, the server 20 may include at least one of a stage of requesting a reviewer to review each clause of the contract, or a stage of confirming whether the parties to the contract are specific parties specified in the termination clause of the contract.

[0169] In step S1015, the terminal 10 receives an input indicating whether the status has been updated and the user has executed the task item of the next stage.

[0170] In step S1027, when the server 20 receives input of what the user has done for all stages of task items, it identifies a score that evaluates the efficiency of the work to conclude the contract and updates the task progress database 216 (item "Work score" in the task progress database 216).

[0171] The server 20 stores the work time required by users to execute task items in the task progress database 216, and for each task item, obtains information regarding communication between users related to the task item (for example, the number of replies to the thread of the post related to the review request, the number of likes, the frequency of posts, etc.), and may determine a score that evaluates the efficiency of the work of concluding a contract based on the obtained information regarding communication between users and the work time required for the task item.

[0172] <4 Screen example> FIG. 11 is an example of a screen that displays the tasks up to the conclusion of a contract and supports the user in the contract conclusion process.

[0173] FIG. 12 is an example of a screen showing that a certain stage of the task leading up to the conclusion of a contract has been completed and the next stage has begun.

[0174] A screen 1200 is an operation screen that displays the entire contract conclusion task and manages the progress.

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

[0176] The task addition receiving unit 1220 is an operation member that manages all of the tasks for concluding a contract and receives the registration of a new task.

[0177] The task addition receiving unit 1220 corresponds to the processing of step S1011 and the like.

[0178] The entire task display area 1230 is an area for displaying the tasks for each stage when the task items that the user needs to perform when the parties enter into a contract are defined as being divided into multiple stages.

[0179] The first stage task display area 1231 is an area that displays task items included in the first stage among a plurality of stages.

[0180] As shown in the figure, the first stage task display area 1231 defines the stage "request review of contract" as the first stage.

[0181] The second stage task display area 1232 is an area that displays task items included in the second stage among a plurality of stages.

[0182] As shown in the figure, the second stage task display area 1232 defines the second stage as a stage of "confirming the possibility of doing business with a business partner that falls under the termination clause, for example," such as checking for anti-social elements.

[0183] The third stage task display area 1233 is an area for displaying task items included in the third stage among a plurality of stages.

[0184] As shown in the figure, the third stage task display area 1233 defines the stage of "submitting an approval request" as the third stage.

[0185] The fourth stage task display area 1234 is an area that displays task items included in the fourth stage among the multiple stages.

[0186] As shown in the figure, the fourth stage task display area 1234 defines the stage "conclude a contract" as the fourth stage. As shown in the figure, the stage in progress is displayed separately from the stage that is not in progress so that the user can distinguish which stage of each stage they are at. In the example shown in the figure, the first stage (first stage task display area 1231) is displayed separately from the other stages (the other stages are framed with a dotted line) so that the user can recognize that it is the first stage. In FIG. 12, the user has completed the first stage task, and the second stage task display area 1232 is displayed separately from the other stages so that the user can recognize that it is the second stage.

[0187] The first subtask 1241 is one of multiple task items included in the first stage.

[0188] As shown in the figure, the first subtask 1241 indicates that it is a task to request a review from the legal department in the first stage (contract review). The first subtask 1241 receives the URL of the post for which the legal department has been requested to review. This allows the server 20 to obtain the post for which the legal department has been requested to review from the URL.

[0189] The second subtask 1242 is one of multiple task items included in the first stage.

[0190] As shown in the figure, the second subtask 1242 indicates that it is a task to request a review from legal department in the first stage (contract review) and confirm the results. The second subtask 1242 receives the URL of the post for which the review results have been received from legal department.

[0191] The first stage completion estimate 1261 is an estimate of the work time required to complete a plurality of task items included in the first stage and proceed to the next stage.

[0192] The first stage completion target 1261 corresponds to the processing of step S1021 and the like.

[0193] The first subtask 1243 is one of multiple task items included in the second phase.

[0194] As shown in the figure, the first subtask 1243 receives the URL of a post that requests the legal department or the like to determine whether the post falls under the anti-social check or whether it is possible to do business with the company. Alternatively, it may receive an operation to check that a request has been made to the department to request confirmation.

[0195] The second subtask 1244 is one of multiple task items included in the second phase.

[0196] As shown in the figure, the second subtask 1244 may request a determination as to whether the company falls under the anti-social check or whether it is possible to do business with the company as a business partner, and may accept the result of the determination.

[0197] The second stage completion estimate 1262 is an estimate of the amount of work time required to complete a plurality of task items included in the second stage and proceed to the next stage.

[0198] The information acquisition receiving unit 1252 is an operating member that receives an operation to query the server 20 (business management database 214) or the business information providing server 94 to acquire information about the parties to the contract in order to execute the task in the second stage.

[0199] The first subtask 1245 is one of multiple task items included in the third phase.

[0200] As shown in the figure, the first subtask 1245 may check whether the workflow for the approval request has started or may accept input of a URL issued by the workflow for the approval request, etc. When the server 20 accepts the approval request, the server 20 may refer to the approval request database 215 and set that the task item has been completed.

[0201] The second subtask 1246 is one of multiple task items included in the third phase.

[0202] As shown in the figure, the second subtask 1246 may check whether the approver has completed approval in the approval request workflow, or may accept input such as a URL issued when approval is completed in the approval request workflow. When the approval request is accepted by the server 20, the server 20 may refer to the approval request database 215 and set that the task item has been completed.

[0203] The third stage completion estimate 1263 is an estimate of the working time required to complete a plurality of task items included in the third stage and proceed to the next stage.

[0204] The information acquisition reception unit 1253 is an operating component that, in the third stage, queries the server 20 (approval application database 215) or the server 92 of the business support system service to execute the task, and calls up an operation screen for applying for approval.

[0205] The first subtask 1247 is one of multiple task items included in the fourth phase.

[0206] As shown in the figure, the first subtask 1247 may check that the contract conclusion workflow has started, or may accept input such as a URL issued by starting the contract conclusion workflow, or, if contract conclusion has been started by server 20, may refer to the conclusion management database 212 and set that the task item has been performed by server 20.

[0207] The second subtask 1248 is one of multiple task items included in the fourth phase.

[0208] As shown in the figure, if contract conclusion is initiated by server 20, which checks that approval by the approver has been completed in the contract conclusion workflow, second subtask 1248 may refer to the conclusion management database 212 and set that the task item has been completed by server 20.

[0209] The fourth stage completion estimate 1264 is an estimate of the working time required to complete a plurality of task items included in the fourth stage and proceed to the next stage.

[0210] The fourth stage completion target 1264 corresponds to the processing of step S1021 and the like.

[0211] The information acquisition receiving unit 1254 is an operating member that receives an operation to make an inquiry to the server 20 (the conclusion management database 212) and start the conclusion of a contract in order to execute the task in the fourth stage.

[0212] Figure 13 is an example of a screen that supports the improvement of contract-conclusion work.

[0213] The work score display area 1235 is an area that displays the score evaluating the work at each stage after the tasks at all stages have been completed and the contract has been concluded, as well as suggestions for improvements to the work at each stage.

[0214] As shown, the task score display area 1235 displays the following: Total work time: The sum of work time for each stage (Task Progress Database 216) - Business improvement points: Task items that can be improved to shorten work time. In the example shown, the work time for the task in the third stage was longer than the average work time for each stage, which is displayed as a business improvement point. Score: The result of evaluating the work up to the completion of the contract (item "Work Score" in the Task Progress Database 216) The sharing operation receiving unit 1270 is an operation member that receives an operation to share the scores obtained by evaluating the work at each stage with another system.

[0215] In the illustrated example, the shared operation receiving unit 1270 can share the information with a server 96 of a personnel management service as another system, and use the information as a reference for personnel evaluation.

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

[0217] In the above embodiment, it has been described that each business provides a service using devices such as the business support system service server 92, the document review service server 93, the business information provision service server 94, the large-scale language model service server 95, and the human resources management service server 96. However, a single business may 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.

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

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

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

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

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

[0223] (Appendix 1) A program for operating a computer having a processor, wherein a memory unit stores information defining task items that a user needs to perform when concluding a contract between parties, the task items being divided into multiple stages, and the program causes the computer's processor to execute the following steps: for each task item for concluding the contract, presenting the task items included in the first stage to the user and accepting input as to whether the user has performed the task items; detecting that the user has progressed one or more task items included in the first stage to the extent that they can proceed to a second stage following the first stage; and, in response to the detection in the detection step, putting the computer into a state where it can accept input as to whether the user has performed the task items included in the second stage.

[0224] (Appendix 2) A program as described in Appendix 1, which includes, as a first stage, a stage of requesting a request for approval to enter into a contract between the parties, and as a second stage, a stage of conclusion work in which the contract is entered into between the parties upon approval of the request for approval, and in the step of entering into a state, enters into a state in which input for task items included in the stage of conclusion work is accepted in response to detecting that approval has been obtained between the parties at the stage of requesting the request for approval.

[0225] (Appendix 3) The program described in Appendix 2 includes at least one of the following steps prior to the first step of requesting approval: requesting a reviewer to review each clause of the contract; or confirming whether the parties to the contract are specified parties specified in the termination clause of the contract.

[0226] (Appendix 4) A program according to any one of appendices 1 to 3, wherein a memory unit stores information on task items defined in multiple stages for each type of contract between the parties, and in the receiving step, task items for that type are presented to the user according to the type of contract, and input is received from the user.

[0227] (Appendix 5) 5. A program according to any one of appendices 1 to 4, wherein in the step of setting the state, parameters recorded by the user when performing the task item of the first stage that are also used in the task item of the second stage are inherited and set as parameters in the task item of the second stage without any input from the user.

[0228] (Appendix 6) A program as described in Appendix 5, which includes, as a first stage, a stage of requesting a request for approval to enter into a contract between the parties, and as a second stage, a stage of concluding the contract between the parties when the request for approval is approved, and which includes, prior to the first stage of requesting the request for approval, at least one of a stage of requesting a reviewer to review each clause of the contract, or a stage of confirming whether the parties to the contract are specific parties specified in the termination clause of the contract, and in the step of setting the state, the parameters of the parties to the contract at the stage of requesting a review, or the specific parties at the stage of confirming whether they are specific parties, are set to at least one of the parameters of the parties to the contract in the request for approval in the first stage, or the parameters of the parties managed in the concluding work in the second stage, without user input.

[0229] (Appendix 7) A program as described in any of Appendices 1 to 6, wherein in the accepting step, the work time required by the user to execute the task items is stored in the memory unit, and the program further causes the processor to set a deadline for each task item for concluding the contract based on at least one of the timing or work time stored in the memory unit, present the set deadline to the user, and present to the user an estimated work time required to complete each task item and conclude the contract.

[0230] (Appendix 8) The program described in Appendix 7, in which, in the presenting step, the program refers to schedule information of the user in charge of each task item for concluding the contract, estimates the available work time of the user in charge based on the available work time in the schedule, and estimates the expected work time to complete the conclusion of the contract based on the estimated available work time.

[0231] (Appendix 9) A program described in any of Appendices 1 to 8, wherein in the receiving step, the working time required by the user to execute the task item is stored in a memory unit, and the program further causes the processor to acquire, for the task item, information regarding communication made between users related to the task item, and determine a score evaluating the efficiency of the work of concluding the contract based on the acquired information regarding communication made between users and the working time for the task item.

[0232] (Appendix 10) A method executed by a computer having a processor, in which a memory unit stores information defining task items that a user needs to perform when concluding a contract between parties, divided into multiple stages, and the method includes the following steps: for each task item for concluding the contract, presenting the task items included in the first stage to the user and accepting input as to whether the user has performed the task item; detecting that the user has progressed one or more task items included in the first stage to the extent that they can proceed to a second stage following the first stage; and, in response to the detection in the detection step, putting the task items included in the second stage into a state where input as to whether the user has performed the task items is accepted.

[0233] (Appendix 11) An information processing device, in which a memory unit stores information defining task items that a user needs to perform when concluding a contract between parties, divided into multiple stages, and a control unit of the information processing device executes the following steps: for each task item for concluding the contract, presenting the task items included in the first stage to the user and accepting input as to whether the user has performed the task items; detecting that the user has progressed one or more task items included in the first stage to the extent that they can proceed to a second stage following the first stage; and, in response to the detection in the detection step, putting the information processing device into a state where it can accept input as to whether the user has performed the task items included in the second stage.

Claims

1. A program for operating a computer having a processor, The storage unit stores information defining task items that a user needs to perform in order to conclude a contract between the parties, the task items being divided into multiple stages; The program causes the processor of the computer to: a step of presenting the task items included in the first stage to the user for each task item for concluding the contract and receiving input as to whether or not the user has performed the task item; detecting that a user has progressed one or more task items included in the first stage to a degree that allows the user to proceed to a second stage subsequent to the first stage; and a step of putting the task items included in the second stage into a state in which input as to whether or not the user has executed the task items is accepted in response to the detection in the detection step.

2. The first stage includes a request for approval to enter into a contract between the parties, The second stage includes a stage of concluding a contract between the parties when the request for approval is approved, The program of claim 1, wherein in the step of setting the state, the program sets the state to accept input for task items included in the conclusion work stage in response to detecting that approval has been obtained among the parties at the request stage of the request for approval.

3. Before the first stage, which is the request for approval, a step of requesting a reviewer to review each clause of the contract relating to the contract; or confirming whether the parties to the contract are specified parties in the contractual document specified in the termination clause; The program according to claim 2, comprising at least one of the steps of:

4. the storage unit stores information on the task items defined by dividing them into the plurality of stages for each type of contract between the parties; 2. The program according to claim 1, wherein in the receiving step, the task items of the type are presented to the user in accordance with the type of the contract document of the contract, and the input is received from the user.

5. 2. The program according to claim 1, wherein in the step of setting the state, parameters recorded by the user when the user performs the task item of the first stage, which are also used in the task item of the second stage, are inherited and set as parameters in the task item of the second stage without being input by the user.

6. The first stage includes a request for approval to enter into a contract between the parties, The second stage includes a stage of concluding a contract between the parties when the request for approval is approved, Before the first stage, which is the request for approval, a step of requesting a reviewer to review each clause of the contract relating to the contract; or confirming whether the parties to the contract are specified parties in the contractual document specified in the termination clause; and 6. The program of claim 5, wherein in the step of setting the state, the parameters of the parties to the contract at the stage of requesting the review or the specific parties at the stage of confirming whether they are the specific parties are set to at least one of the parameters of the parties to the contract in the request for approval at the first stage or the parameters of the parties to be managed in the conclusion work at the second stage, without relying on input from the user.

7. In the receiving step, the operation time required for the user to execute the task item is stored in the storage unit, The program further causes the processor to The program described in claim 1, which sets a deadline for each task item for concluding the contract based on at least one of the timing or the work time stored in the memory unit, presents the set deadline to the user, and presents to the user an estimated work time required to complete each task item and conclude the contract.

8. 8. The program according to claim 7, wherein in the presenting step, the program refers to schedule information of the user in charge of each task item for concluding the contract, estimates the available working time of the user in charge based on the available time in the schedule, and estimates the expected working time to complete the conclusion of the contract based on the estimated available working time.

9. In the receiving step, the operation time required for the user to execute the task item is stored in the storage unit, The program further causes the processor to The program of claim 1, further comprising: acquiring information regarding communication between users related to the task item; and determining a score that evaluates the efficiency of the work of concluding a contract based on the acquired information regarding communication between users and the work time for the task item.

10. 1. A computer-implemented method having a processor, comprising: The storage unit stores information defining task items that a user needs to perform in order to conclude a contract between the parties, the task items being divided into multiple stages; The method further comprises the processor: a step of presenting the task items included in the first stage to the user for each task item for concluding the contract and receiving input as to whether or not the user has performed the task item; detecting that a user has progressed one or more task items included in the first stage to a degree that allows the user to proceed to a second stage subsequent to the first stage; In response to the detection in the detecting step, the method executes a step of putting the task items included in the second stage into a state in which the user can input whether or not the task items have been executed by the user.

11. An information processing device, The storage unit stores information defining task items that a user needs to perform in order to conclude a contract between the parties, the task items being divided into multiple stages; a control unit of the information processing device, a step of presenting the task items included in the first stage to the user for each task item for concluding the contract and receiving input as to whether or not the user has performed the task item; detecting that a user has progressed one or more task items included in the first stage to a degree that allows the user to proceed to a second stage subsequent to the first stage; and in response to the detection in the detecting step, putting the task item included in the second stage into a state in which input as to whether or not the user has executed the task item is accepted.

Images