Program, communication terminal, and upload method

Abstract

This invention provides a program, communication terminal, and upload method that enable a server to easily perform checks on information related to legal documents without requiring complex operations. [Solution] The program causes the computer to perform the following steps: receive a first email with a first file representing a legal document attached; display a first icon representing the first file and the body of the first email on the mailer; and upload first email information, which represents at least one of the first file and the body of the first email, to the server while the user is not responding to any operations on the first icon. On the server, the first email information is checked as it is uploaded.

Description

Technical Field

[0001] The present invention relates to a program, a communication terminal, and an upload method.

Background Art

[0002] Japanese Unexamined Patent Application Publication No. 2020-184251 (Patent Document 1) discloses a legal text evaluation system. In this legal text evaluation system, a legal text is evaluated based on predetermined evaluation rules.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the legal text evaluation system disclosed in Patent Document 1 above, a document file including a legal text is transmitted from a user terminal to a server terminal, and the legal text is evaluated at the server terminal. In this legal text evaluation system, the upload of the document file to the server terminal is performed, for example, by dragging and dropping the document file into a predetermined area on a web page. Thus, a complicated operation is required for uploading the document file to the server terminal.

[0005] The present invention has been made to solve such problems, and an object thereof is to provide a program, a communication terminal, and an upload method that can easily cause a server to check information related to a legal document without performing a complicated operation.

Means for Solving the Problems

[0006] A program according to a certain aspect of the present invention causes a computer to perform the following steps: receive a first email with a first file representing a legal document attached; display a first icon representing the first file and the body of the first email on a mailer; and upload first email information, which represents at least one of the first file and the body of the first email, to a server while the user is not responding to any operations on the first icon. On the server, the first email information is checked as it is uploaded.

[0007] When this program is executed by a computer, the first email information is uploaded to the server while no user interaction with the first icon is being received, and the server then checks the first email information. Therefore, this program allows the server to easily check the first email information without requiring any complicated operations.

[0008] The above program may cause the computer to perform a further step of receiving instructions from the user to upload the first email information, and the upload of the first email information may be performed in response to the acceptance of such instructions.

[0009] When this program is executed by a computer, it receives instructions from the user to upload the first email information, uploads the first email information to the server, and checks the first email information on the server. Therefore, with this program, the server can easily perform the check of the first email information with just a few simple operations.

[0010] The above program may cause the computer to perform the following steps: receive a second email with a second file attached that does not represent a legal document; display a second icon representing the second file and the body of the second email on the mailer; and upload second email information, which represents at least one of the second file and the body of the second email, to the server while the user is not responding to any operations on the second icon. The server does not need to perform any checks on the second email information even after it has been uploaded.

[0011] In the above program, the first email information may indicate at least the first file, and the program may cause the computer to perform a step of updating the version information of the first file, and the version information may indicate how many times the first file has been received from the other party, and if the version information indicates the first time, the server may check the full text of the legal document as the first file is uploaded.

[0012] When this program is executed by a computer, if the version information of the first uploaded file indicates the initial version, the entire legal document is checked as the first file is uploaded. Therefore, this program allows for checking legal documents appropriately and comprehensively at each phase leading up to the conclusion of a contract.

[0013] In the above program, if the version information indicates the second or subsequent version, the server may check for changes in the legal document since the previous version as the first file is uploaded.

[0014] When this program is run by a computer, if the version information of the first uploaded file indicates a second or subsequent upload, the program checks for changes in the legal document since the last upload, in accordance with the upload of the first file. Therefore, this program allows for checking the legal document appropriately and comprehensively at each phase leading up to the conclusion of a contract.

[0015] The above program may also cause the computer to perform a further step of notifying the user when the upload of the first email information is complete.

[0016] When this program is executed by the computer, the user is notified when the upload of the first email information is complete. Therefore, this program allows the user to be aware that the upload of the first email information is complete.

[0017] In the above program, the first email information may indicate at least the first file, the program may cause the computer to perform a step of updating the status information of the first file, the legal document check may be performed by multiple entities in a predetermined order, the status information may indicate how far the check in the predetermined order has been completed, and the program may cause the computer to perform a step of notifying the recipient according to the status information.

[0018] When this program is executed by a computer, the status information of a legal document is updated as the checks are performed sequentially by multiple entities, and notifications are sent to the appropriate recipients according to the status information. Therefore, this program allows each entity that checks a legal document to be aware that it is their turn to check it.

[0019] The above program may further cause the computer to perform a step that displays an area for editing the content of the notification to be sent to the recipient, based on the status information.

[0020] When this program is run by a computer, an area is displayed where the content of the notification to be sent to the recipients is edited according to the status information. Therefore, this program makes it easy to edit what to communicate to the next recipient.

[0021] A communication terminal according to another aspect of the present invention comprises a receiving unit, a display unit, and a transmitting unit. The receiving unit receives an email with an attached file representing a legal document. The display unit displays an icon representing the file and the body of the email on the mailer. The transmitting unit uploads email information, which represents at least one of the file and the body of the email, to a server when no user interaction with the icon has been received. The server checks the email information as it is uploaded.

[0022] In this communication terminal, the first email information is uploaded to the server before any user interaction with the first icon is received, and the server then checks the first email information. Therefore, this communication terminal allows the server to easily check the first email information without requiring any complicated operations.

[0023] An upload method according to another aspect of the present invention includes the steps of: receiving an email with an attached file representing a legal document; displaying an icon representing the file and the body of the email on the mailer; and uploading email information representing at least one of the file and the body of the email to a server while the user is not responding to any operations on the icon. The server checks the email information as it is uploaded.

[0024] In this upload method, the first mail information is uploaded to the server while an operation on the first icon has not been received from the user, and the server checks the first mail information. Therefore, according to this upload method, it is possible to easily cause the server to check the first mail information without performing complicated operations.

Advantages of the Invention

[0025] According to the present invention, it is possible to provide a program, a communication terminal, and an upload method that can easily cause a server to check information related to legal documents without performing complicated operations.

Brief Description of the Drawings

[0026] [Figure 1] It is a diagram schematically showing the configuration of a legal document checking system. [Figure 2] It is a block diagram schematically showing the hardware configuration of a legal document checking server. [Figure 3] It is a diagram schematically showing a part of an example of a viewpoint DB. [Figure 4] It is a diagram schematically showing a part of an example of a contract document DB. [Figure 5] It is a diagram schematically showing a part of an example of a check root DB. [Figure 6] It is a block diagram schematically showing the hardware configuration of a user terminal.

[0040] [Figure 7] It is a flowchart showing the procedure from a check request for a contract document to automatic check completion. [Figure 8] It is a diagram schematically showing a first example of a screen displayed when a mailer is activated. [Figure 9] It is a diagram schematically showing a second example of a screen displayed when a mailer is activated. [Figure 10] It is a flowchart showing the procedure from automatic check completion of a contract document to review completion. [Figure 11]This diagram schematically shows an example of a screen that displays a list of contract files that a specific user should review. [Figure 12] This flowchart shows the steps to be taken if there are subsequent reviewers after the contract has been reviewed. [Figure 13] This flowchart shows the procedure to follow if there is no next checker after the contract has been reviewed. [Modes for carrying out the invention]

[0027] Hereinafter, an embodiment relating to one aspect of the present invention (hereinafter also referred to as "this embodiment") will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and their descriptions will not be repeated. Furthermore, each drawing is schematically depicted with parts omitted or exaggerated as appropriate for ease of understanding.

[0028] [1. Overview] Figure 1 is a schematic diagram showing the configuration of a legal document checking system 10 according to this embodiment. As shown in Figure 1, the legal document checking system 10 includes a legal document checking server 100 and a plurality of user terminals 200. The legal document checking server 100 is implemented, for example, by a general-purpose computer. Each user terminal 200 is implemented, for example, by a PC (Personal Computer), tablet, or smartphone. In the legal document checking system 10, the legal document checking server 100 and the plurality of user terminals 200 communicate with each other via the Internet N1.

[0029] The legal document checking system 10 is configured to check legal documents from various perspectives. Legal documents include, for example, contracts, rules, and notices. A contract is a document that has contractual effect. Examples of contracts include confidentiality agreements, sales contracts, and real estate lease agreements. Rules are documents that show the rules that a person must follow when taking a certain action. An example of rules is employment regulations. A notice is a document used to notify a recipient of some matter. An example of a notice is a policy declaration document such as a privacy policy declaration. The following describes an example where the legal document to be checked is a contract.

[0030] In the legal document checking server 100, for example, the points to be checked are pre-registered for each type of contract to be checked. The points to be checked refer to the content to be checked in the contract, for example. For example, one example of a point regarding a non-disclosure agreement is whether "information that has become publicly known without fault of the recipient constitutes an exception to the confidentiality rule."

[0031] In the legal document checking system 10, the contract to be checked is uploaded (sent) from the user terminal 200 to the legal document checking server 100. Once the contract to be checked is uploaded to the legal document checking server 100, the legal document checking server 100 checks the contract from pre-registered perspectives. The check results are sent from the legal document checking server 100 to the user terminal 200 and displayed on the user terminal 200. This allows the user to check the results of the contract check.

[0032] Before a contract is finalized, draft contracts are exchanged between the contracting parties. Through this exchange of draft contracts, revisions are made to the draft contract until the final contract is completed. For example, email is used for exchanging draft contracts. For instance, an electronic file containing the draft contract (hereinafter also referred to as the "contract file") is attached to an email, and the exchange of draft contracts takes place through the sending and receiving of such emails.

[0033] A user of the legal document checking system 10, for example, when receiving an email with a contract file attached from the other party to a contract, uploads the received contract file to the legal document checking server 100. One example of the procedure for uploading a contract file is to drag and drop the contract file into the area for uploading electronic files to the legal document checking server 100 (hereinafter also referred to as the "upload area"). However, this procedure requires multiple operations, such as displaying the upload area and dragging and dropping the contract file into the upload area, and this procedure is not necessarily easy. As will be described in detail later, the legal document checking system 10 according to this embodiment is equipped with a procedure that allows the legal document checking server 100 to easily check information related to legal documents without requiring complicated operations. The configuration and operation of the legal document checking system 10 will be described in detail below.

[0034] [2. Structure] <2-1. Configuration of the Legal Document Checking Server> Figure 2 is a schematic block diagram showing the hardware configuration of the legal document checking server 100. As shown in Figure 2, the legal document checking server 100 includes a control unit 110, a communication interface 130, and a storage unit 120. Each component is electrically connected via a bus.

[0035] The control unit 110 includes a CPU (Central Processing Unit) 112, RAM (Random Access Memory) 114, and ROM (Read Only Memory) 116, and is configured to control each component according to information processing. The communication interface 130 is configured to communicate with the user terminal 200 (Figure 1) via the Internet N1. The communication interface 130 is composed of, for example, a wired LAN (Local Area Network) module or a wireless LAN module.

[0036] The storage unit 120 is composed of an auxiliary storage device such as a hard disk drive or a solid-state drive. The storage unit 120 stores, for example, a control program 121, a perspective database 122, a contract database 123, and a check root database 124. The various functions of the legal document check server 100 are realized when the control program 121 is executed by the CPU 112.

[0037] Figure 3 is a schematic diagram illustrating a part of an example of the perspective database 122. As shown in Figure 3, in the perspective database 122, "perspectives" and "evaluation comments" are managed in correspondence with each other. Each of the multiple "perspectives" is associated with an "evaluation comment." The "evaluation comment" is a message displayed on the user terminal 200 when a problem is detected as a result of the check performed at the "perspective." The check of the contract at each perspective is performed by the control program 121 being executed by the CPU 112.

[0038] Figure 4 is a schematic diagram illustrating a part of an example of the contract DB123. As shown in Figure 4, the contract DB123 manages multiple data groups UD1. Each of the multiple data groups UD1 manages information about the user associated with that data group UD1 (hereinafter also referred to as "user information") and multiple data groups CD1.

[0039] User information includes, for example, the username, user ID (identifier), and company ID. The username is, for example, the user's full name. The user ID is an identifier used to identify users registered with the legal document checking system 10 (hereinafter also referred to as the "legal document checking service"). The company ID is an identifier used to identify companies registered with the legal document checking service. The username included in data group UD1 is the full name of the user associated with data group UD1. The user ID included in data group UD1 is the user ID of the user associated with data group UD1. The company ID included in data group UD1 is the company ID of the company to which the user associated with data group UD1 belongs.

[0040] Each of the multiple data group CD1 manages information about contract files uploaded to the legal document check server 100 by the user associated with the data group UD1 which contains each data group CD1. Each data group CD1 manages information about one or more contract files exchanged in relation to a specific contract. The information managed in each data group CD1 includes, for example, information indicating whether the contract file is a received version or a sent version, version information of the contract file, file name information of the contract file, information indicating the user's position in the contract indicated by the contract file, information indicating the type of contract indicated by the contract file, information indicating the date and time the contract file was registered in the contract DB 123, status information of the contract file, and information indicating the storage location of the contract file.

[0041] Information indicating whether a contract file is a received version or a sent version indicates whether the contract file is a received version received from the other party to the contract, or a sent version sent from this party to the other party. Version information of the contract file indicates how many times the contract file has been received from the other party, or how many times the contract file has been sent from this party to the other party. Information indicating the user's role in the contract file indicates, for example, whether the user is the recipient or sender of information if the contract file represents a non-disclosure agreement.

[0042] Furthermore, for example, regarding contract review, it is conceivable that the business unit's representative would review the contract first, followed by the legal department's representative, and finally the legal department's manager would review it. As will be described in more detail later, the legal document review system 10 allows for setting the order (review route) of contract reviews. The status information of the contract file indicates how far along the set review order the review of the contract file has been completed. The information indicating the storage location of the contract file indicates the storage location of the contract file in the storage unit 120. In the storage unit 120, for example, the received version of the contract file, each revised version of the contract file, and the sent version of the contract file are stored.

[0043] Figure 5 is a schematic diagram illustrating a part of an example of the check route DB 124. Referring to Figure 5, the check route DB 124 manages the order in which contracts are checked for each company. In the check route DB 124, "Company ID," "Company Name," and "Check Order" are associated. Each order in the check order is associated with a user ID. The check route DB 124 is updated when a user with the necessary authority changes the settings for the check order. As will be described in more detail later, in the legal document checking system 10, each user is notified of a request to check the contract according to the check order.

[0044] <2-2. User Terminal Configuration> Figure 6 is a schematic block diagram showing the hardware configuration of the user terminal 200. As shown in Figure 6, the user terminal 200 includes a control unit 210, a communication interface 230, an operation unit 240, a display 250, and a storage unit 220. In the user terminal 200, each component is electrically connected via a bus.

[0045] The control unit 210 includes a CPU, RAM, ROM, etc., and is configured to control each component according to information processing. The communication interface 230 is configured to communicate with the legal document checking server 100 via the internet N1. The communication interface 230 is composed of, for example, a wired LAN module or a wireless LAN module.

[0046] The control unit 240 is configured to receive input from the user. The control unit 240 consists of, for example, some or all of a touch panel, keyboard, mouse, and microphone. The display 250 is configured to display images. The display 250 consists of, for example, a liquid crystal monitor or an organic EL (Electro-Luminescence) monitor.

[0047] The storage unit 220 is, for example, an auxiliary storage device such as a hard disk drive or a solid-state drive. The storage unit 220 stores, for example, a control program 222. Various functions in the user terminal 200 are realized when the control program 222 is executed by the CPU of the control unit 210.

[0048] [3. Operation] <3-1. Actions taken from requesting a contract review to the completion of the automated review> Figure 7 is a flowchart showing the procedure from the request to check a contract to the completion of the automatic check. The process shown in the flowchart on the left side of Figure 7 is executed by the control unit 210 of the user terminal 200 after the attached files, such as the contract file, are received via email. The process shown in the flowchart on the right side of Figure 7 is repeatedly executed at predetermined intervals by the control unit 110 of the legal document check server 100.

[0049] Referring to the flowchart on the left side of Figure 7, the control unit 210 of the user terminal 200 determines whether or not it has received an instruction from the user to upload an attached file (step S100). The instruction to upload an attached file is received, for example, via the operation unit 240 of the user terminal 200.

[0050] Figure 8 schematically shows a first example of the screen displayed when the mailer is launched. Referring to Figure 8, screen IM1 is displayed on the display 250 of the user terminal 200. In screen IM1, the body of the received email is displayed in area TR1 located in the lower left, and the basic information of the received email (email title, sender address, recipient address, etc.) and icon IC1 are displayed in the upper left. Icon IC1 indicates an attachment attached to the received email. In this example, the attachment is a contract file, and this is the first time the contract file has been received from the other party to the contract. The number of times the contract file has been received from the other party to the contract can be determined, for example, from the number of attachments previously received in the same email thread in the mailer (for example, attachments with similar file names).

[0051] On screen IM1, area TR2 on the right displays button B2, which implements a function added to the mailer. Area TR2 is displayed on display 250 when, for example, button B1, which instructs the activation of the add-in, is pressed. Button B2 accepts the instruction to upload the attachment to the legal document check server 100 as the initial version. In other words, for example, button B2 accepts the instruction to upload the aforementioned attachment.

[0052] Figure 9 schematically shows a second example of the screen displayed when the mail client is launched. Referring to Figure 9, screen IM2 is displayed on the display 250 of the user terminal 200. In screen IM2, the body of the received email is displayed in area TR1 located in the lower left, and the basic information of the received email and icon IC1 are displayed in the upper left. Icon IC1 indicates an attachment attached to the received email. In this example, the attachment is a contract file, and this is the second or subsequent time that the contract file has been received from the other party to the contract.

[0053] In screen IM2, buttons B2 and B3, which implement the functions added to the mailer, are displayed in area TR2 on the right. Button B2 accepts the instruction to upload the attachment to the legal document check server 100 as the initial version, while button B3 accepts the instruction to upload the attachment to the legal document check server 100 as the second or subsequent version. In other words, for example, buttons B2 and B3 accept the aforementioned attachment upload instructions.

[0054] Referring again to the flowchart on the left side of Figure 7, if it is determined that the instruction to upload an attachment has not been received (NO in step S100), the control unit 210 waits until it receives the instruction to upload an attachment. On the other hand, if it is determined that the instruction to upload an attachment has been received (YES in step S100), the control unit 210 controls the communication interface 230 to upload the attachment of the received email displayed in the mailer (step S110). When uploading an attachment, for example, the user ID and the version information of the attachment are also sent to the legal document check server 100. In addition, after the instruction to upload an attachment, the user may be asked to input information about the attachment (information indicating whether the contract file is a received version or a sent version, information indicating the user's position in the contract shown in the contract file, and information indicating the type of contract shown in the contract file), and the input information may be sent to the legal document check server 100.

[0055] The control unit 210 determines whether it has received a notification from the legal document check server 100 indicating that the upload of the attached file has been completed (hereinafter also referred to as the "upload completion notification") (step S120). If it is determined that the upload completion notification has not been received (NO in step S120), the control unit 210 waits until it receives the upload completion notification. On the other hand, if it is determined that the upload completion notification has been received (YES in step S120), the control unit 210 controls the display 250 to display a message indicating that the upload has been completed (step S130).

[0056] Referring to the flowchart on the right side of Figure 7, the control unit 110 of the legal document checking server 100 determines whether or not it has received an attachment from the user terminal 200 (step S200). If it is determined that the attachment has not been received (NO in step S200), the control unit 110 waits until the attachment is received.

[0057] On the other hand, if it is determined that an attachment has been received (YES in step S200), the control unit 110 controls the storage unit 120 so that information about the received attachment is added to the contract DB 123 (step S210). Some items included in the data group CD1 may be inferred, for example, by the control unit 110 analyzing the attachment. Once the update of the contract DB 123 is complete, the control unit 110 controls the communication I / F 130 to send an upload completion notification to the user terminal 200 (step S220).

[0058] The control unit 110 determines whether the attached file is a contract file by analyzing the attached file (step S230). If it is determined that the attached file is not a contract file (NO in step S230), the process shown in this flowchart ends without any further checks on the attached file.

[0059] On the other hand, if the attached file is determined to be a contract file (YES in step S230), the control unit 110 determines whether the contract file is the initial receipt version (step S240). If the contract file is determined to be the initial receipt version (YES in step S240), the control unit 110 refers to the viewpoint DB 122 and performs a full check of the contract (step S250). Various known methods can be applied as specific methods for checking the contract.

[0060] On the other hand, if the contract file is determined to be a second or subsequent receipt version (NO in step S240), the control unit 110 refers to the viewpoint DB 122 and performs a check for differences from the previous version (step S260). Once the check of the contract file is complete, the control unit 110 controls the storage unit 120 so that the check results are reflected in the contract DB 123 (step S270).

[0061] Thus, in the legal document checking system 10, the contract file is uploaded to the legal document checking server 100 while no user operation is being accepted for icon IC1, and the legal document checking server 100 checks the contract file. Therefore, with the legal document checking system 10, the legal document checking server 100 can easily check the contract file without requiring complicated operations.

[0062] Furthermore, in the legal document checking system 10, if the version information of the uploaded contract file indicates the first upload, the entire contract is checked as the contract file is uploaded. On the other hand, if the version information of the uploaded contract file indicates the second or subsequent upload, the system checks the changes in the contract since the previous upload as the contract file is uploaded. Therefore, the legal document checking system 10 allows for checking the contract to an appropriate extent at each phase leading up to the conclusion of the contract.

[0063] <3-2. Operation from completion of automatic contract check to completion of review> Figure 10 is a flowchart showing the procedure from the completion of the automated contract check to the completion of the review. The processes shown in the flowchart on the left side of Figure 10 are executed by the control unit 210 of the user terminal 200 after the automated contract check is completed. The processes shown in the flowchart on the right side of Figure 10 are repeatedly executed at predetermined intervals by the control unit 110 of the legal document check server 100.

[0064] Referring to the flowchart on the left side of Figure 10, the control unit 210 of the user terminal 200 determines whether or not it has received an instruction to display the contract check results (hereinafter also referred to as the "check result display instruction") (step S300). The check result display instruction is received, for example, via the operation unit 240 of the user terminal 200.

[0065] Figure 11 is a schematic diagram illustrating an example of a screen that displays a list of contract files that a specific user should review. Referring to Figure 11, screen IM3 is displayed on the display 250 of the user terminal 200. On screen IM3, list CH1 is displayed, which shows a list of contract files that the user who owns the user terminal 200 should review. If the user is the first checker in the check route, a list of contract files uploaded by the user is displayed in list CH1. On the other hand, if the user is the second or subsequent checker in the check route, a list of contract files uploaded by the first checker is displayed in list CH1. In list CH1, a button B4 is associated with each contract. Button B4 accepts a command to display the check result of the associated contract. Note that if the user is the second or subsequent checker in the check route, button B4 may be displayed after the check by the previous checker is completed.

[0066] Referring again to the flowchart on the left side of Figure 10, if it is determined that the instruction to display the check results has not been received (NO in step S300), the control unit 210 waits until the instruction to display the check results is received. On the other hand, if it is determined that the instruction to display the check results has been received (YES in step S300), the control unit 210 controls the communication I / F 230 to send a signal requesting the transmission of the check results (hereinafter also referred to as the "check result request signal") to the legal document check server 100 (step S310).

[0067] The control unit 210 determines whether or not it has received a check result from the legal document check server 100 (step S320). If it is determined that no check result has been received (NO in step S320), the control unit 210 waits until it receives the check result. On the other hand, if it is determined that a check result has been received (YES in step S320), the control unit 210 controls the display 250 to display the received check result (step S330).

[0068] On the screen displaying the check results, for example, the system accepts requests for modification (editing) of the contract file. The user can, for example, modify the contract file based on the check results. The control unit 210 determines whether the user has completed modifying the contract file (step S340). If it is determined that the user has not completed modifying the contract file (NO in step S340), the control unit 210 waits until the user has completed modifying the contract file. On the other hand, if it is determined that the user has completed modifying the contract file (YES in step S340), the control unit 210 controls the communication interface 230 to send the modified contract file to the legal document check server 100 (step S350).

[0069] Referring to the flowchart on the right side of Figure 10, the control unit 110 of the legal document checking server 100 determines whether or not it has received a check result request signal from the user terminal 200 (step S400). If it is determined that no check result request signal has been received (NO in step S400), the control unit 110 waits until it receives a check result request signal.

[0070] On the other hand, if it is determined that a check result request signal has been received (YES in step S400), the control unit 110 controls the communication interface 130 to send the latest check result to the user terminal 200 (step S410). Here, if there is a checker before the user who owns the user terminal 200 in the check route, the latest check result will be the contract file modified by the previous checker (user).

[0071] The control unit 110 determines whether or not it has received the revised contract file from the user terminal 200 (step S420). If it is determined that the revised contract file has not been received (NO in step S420), the control unit 110 waits until it receives the revised contract file. On the other hand, if it is determined that the revised contract file has been received (YES in step S420), the control unit 110 controls the storage unit 120 so that information about the revised contract file is reflected in the contract DB 123 (step S430). In step S430, for example, the status information in the contract DB 123 is updated.

[0072] Figure 12 is a flowchart showing the procedure to be performed when there is a next checker after the contract has been reviewed. The process shown in the flowchart on the left side of Figure 12 is repeatedly executed at predetermined intervals by the control unit 210 of the user terminal 200. The process shown in the flowchart on the right side of Figure 12 is executed by the control unit 110 of the legal document check server 100 when the next checker is specified in the check root DB 124 after the revised contract file has been received.

[0073] Referring to the flowchart on the left side of Figure 12, the control unit 210 of the user terminal 200 determines whether or not it has received information about the next checker (for example, information about their position and name) from the legal document check server 100 (step S500). If it is determined that information about the next checker has not been received (NO in step S500), the control unit 210 waits until it receives information about the next checker.

[0074] On the other hand, if it is determined that information about the next checker has been received (YES in step S500), the control unit 210 controls the display 250 to display an area that accepts editing of a message directed to the next checker (hereinafter also referred to as the "message editing area") (step S510). The user, for example, writes points for which they wish to have a more detailed check in the message editing area.

[0075] The control unit 210 determines whether or not message editing in the message editing area is complete (step S520). If it is determined that message editing is not complete (NO in step S520), the control unit 210 waits until message editing is complete. On the other hand, if it is determined that message editing is complete (YES in step S520), the control unit 210 controls the communication interface 230 to send the edited message to the legal document check server 100 (step S530).

[0076] Referring to the flowchart on the right side of Figure 12, the control unit 110 of the legal document check server 100 controls the communication interface 130 to send information about the next checker to the user terminal 200 if the next checker is specified in the check route DB 124 after the revised contract file has been received from the user terminal 200 (step S600). The control unit 110 determines whether or not it has received a message from the user terminal 200 (step S610). If it is determined that no message has been received (NO in step S610), the control unit 110 waits until it receives a message.

[0077] On the other hand, if it is determined that a message has been received (YES in step S610), the control unit 110 controls the communication interface 130 to send a notification and message indicating that it is the next checker's turn to check to the user terminal 200 (step S620). The next checker, after confirming the notification and message displayed on the display 250, for example, checks the latest check result (for example, the revised contract file) through the process shown in the flowchart of Figure 10.

[0078] Figure 13 is a flowchart showing the procedure to be performed when there is no next checker after the contract has been reviewed. The process shown in the flowchart on the left side of Figure 13 is repeatedly executed at predetermined intervals by the control unit 210 of the user terminal 200. The process shown in the flowchart on the right side of Figure 13 is executed by the control unit 110 of the legal document check server 100 when the revised contract file has been received and no next checker has been specified in the check root DB 124.

[0079] Referring to the flowchart on the left side of Figure 13, the control unit 210 of the user terminal 200 determines whether or not it has received the contract file for delivery from the legal document check server 100 (step S700). If it is determined that the contract file for delivery has not been received (NO in step S700), the control unit 210 waits until it receives the contract file for delivery.

[0080] On the other hand, if it is determined that the sent version of the contract file has been received (YES in step S700), the control unit 210 creates a draft reply email to the other party to the contract and controls the display 250 to display the created draft reply email on the mailer (step S710). In the draft reply email, for example, the recipient's email address is automatically entered, as well as a standard phrase used when sending the sent version of the contract. The sent version of the contract file is also attached to the reply email.

[0081] The control unit 210 determines whether or not it has received an instruction from the user to send a reply email (step S720). If it is determined that it has not received an instruction from the user to send a reply email (NO in step S720), the control unit 210 waits until it receives an instruction from the user to send a reply email. On the other hand, if it is determined that it has received an instruction from the user to send a reply email (YES in step S720), the control unit 210 controls the communication interface 230 to send the reply email (step S730).

[0082] Referring to the flowchart on the right side of Figure 13, the control unit 110 of the legal document check server 100 generates a version of the contract file for delivery based on the latest check results if the next checker is not specified in the check route DB 124 after the revised contract file has been received from the user terminal 200 (step S800). The control unit 110 controls the communication I / F 130 to send the version of the contract file for delivery to the user terminal 200 (step S810).

[0083] Thus, in the legal document checking system 10, as the contract is checked sequentially by multiple checkers (users), the status information is updated, and notifications are sent to the appropriate recipients according to the status information. Therefore, the legal document checking system 10 allows each checker of the contract to be aware that it is their turn to check the contract.

[0084] Furthermore, in the legal document checking system 10, a message editing area for editing the notification content to the checker according to the status information is displayed on the display 250. Therefore, with the legal document checking system 10, the user can easily edit the content to be communicated to the next checker.

[0085] [4. Features] As described above, in the legal document checking system 10 according to this embodiment, the contract file is uploaded to the legal document checking server 100 while no operation on icon IC1 has been received from the user, and the legal document checking server 100 checks the contract file. Therefore, with the legal document checking system 10, the legal document checking server 100 can be easily made to check the contract file without requiring complicated operations.

[0086] [5. Other Embodiments] The concept of the above embodiments is not limited to those described above. Examples of other embodiments to which the concept of the above embodiments can be applied will be described below.

[0087] <5-1> In the above embodiment, an email attachment was uploaded to the legal document checking server 100, and if the attachment was a contract file, the contract file was checked. However, the data uploaded to the legal document checking server 100 is not limited to attachments. For example, data representing the email body may be uploaded to the legal document checking server 100, and the content of the email body may be checked by the legal document checking server 100. Alternatively, email data with a contract file attached may be uploaded to the legal document checking server 100, and both the email body and the contract file may be checked by the legal document checking server 100.

[0088] <5-2> Furthermore, in the above embodiment, the attached file was uploaded from the user terminal 200 to the legal document checking server 100 in response to an instruction from the user to upload the attached file. However, an upload instruction is not necessarily required to upload an attached file. For example, the attached file may be automatically uploaded from the user terminal 200 to the legal document checking server 100 in response to receiving an email with an attached file from the other party to a contract. In this case, for example, the user terminal 200 may determine whether the attached file is a contract file based on the content of the email body or the content of the attached file, and only if the attached file is a contract file may the attached file be automatically uploaded from the user terminal 200 to the legal document checking server 100.

[0089] Embodiments of the present invention have been described illustratively above. That is, a detailed description and accompanying drawings have been disclosed for illustrative purposes. Therefore, some of the components described in the detailed description and accompanying drawings may not be essential for solving the problem. Consequently, the mere fact that these non-essential components are described in the detailed description and accompanying drawings does not mean that they should be immediately assumed to be essential.

[0090] Furthermore, the above embodiments are merely illustrative in every respect of the present invention. The above embodiments can be improved or modified in various ways within the scope of the present invention. For example, at least a part of the configuration of one embodiment may be combined with at least a part of the configuration of any other embodiment. In other words, in carrying out the present invention, specific configurations can be appropriately adopted depending on the embodiment. [Explanation of Symbols]

[0091] 10 Legal document checking system, 100 Legal document checking server, 110,210 Control unit, 112 CPU, 114 RAM, 116 ROM, 120,220 Storage unit, 121,222 Control program, 122 Perspective DB, 123 Contract DB, 124 Check route DB, 130,230 Communication I / F, 200 User terminal, 240 Operation unit, 250 Display, B1-B4 Buttons, CD1,UD1 Data group, CH1 List, IC1 Icon, IM1,IM2,IM3 Screen, N1 Internet, TR1,TR2 Area.

Claims

1. The first step is to receive the first email with the first file containing the legal document attached, The steps include displaying a first icon representing the first file and the body of the first email on the mail client, The computer is instructed to perform the following steps: upload to a server the first file and the first email information, which indicates at least one of the first file and the body of the first email, while no user interaction has been received with the first icon; The server has a program that checks the first email information as it is uploaded.

2. The computer is further instructed to perform the step of receiving an instruction from the user to upload the first email information, The program according to claim 1, wherein the upload of the first email information is performed in response to the acceptance of the instruction.

3. The steps include receiving a second email with a second file attached that does not represent a legal document, The steps include displaying a second icon representing the second file and the body of the second email on the mail client, The computer is further instructed to perform the step of uploading to the server the second email information, which shows at least one of the second file and the body of the second email, while no operation on the second icon has been accepted by the user. The program according to claim 1 or claim 2, wherein the server does not perform a check on the second email information even if the second email information is uploaded.

4. The first email information indicates at least the first file, The computer is further instructed to perform the step of updating the version information of the first file, The aforementioned version information indicates how many times the first file has been received from the other party. The program according to claim 1 or 2, wherein, if the version information indicates the first time, the server checks the entire text of the legal document in response to the upload of the first file.

5. The program according to claim 4, wherein if the version information indicates a second or subsequent version, the server checks for changes in the legal document since the previous version as the first file is uploaded.

6. The program according to claim 1 or claim 2, further causing the computer to perform a step of notifying the user when the upload of the first email information is completed.

7. The first email information indicates at least the first file, The computer is further instructed to perform the step of updating the status information of the first file, The aforementioned legal documents are checked by multiple entities in a predetermined order. The status information indicates how far along the predetermined order of checks has been completed. The program according to claim 1 or claim 2, further comprising the step of causing the computer to perform the step of notifying a recipient according to the status information.

8. The program according to claim 7, further comprising the step of causing the computer to perform the step of displaying an area for editing the content of a notification to a recipient according to the status information.

9. A receiving unit that receives emails with attached files containing legal documents, A display unit that displays an icon representing the aforementioned file and the body of the aforementioned email on the mailer, The system includes a sending unit that uploads email information, which includes at least one of the file and the body of the email, to a server when no user interaction with the aforementioned icon has been received. The server has a communication terminal that checks the email information as it is uploaded.

10. The steps include receiving an email with a file containing legal documents attached, The steps include displaying an icon representing the aforementioned file and the body of the aforementioned email on the mail client, The process includes the step of uploading to a server email information that shows at least one of the file and the body of the email, while the user has not yet responded to the aforementioned icon, An upload method in which, on the server, the email information is checked as it is uploaded.

Images