Correction suggesting method, correction suggesting system, and correction suggesting program

Abstract

This correction suggesting method causes a processor to: associate and store, in a memory, pre-correction information, which is pre-correction content of an item in a first contract, and post-correction information, which is a post-correction item obtained by correcting the pre-correction item; and on the basis of the post-correction information, provide correction suggesting information regarding suggestion of correction for a target item in a second contract, which is different from the first contract.

Description

Correction suggestion method, correction suggestion system, and correction suggestion program

[0001] The present disclosure relates to a correction suggestion method, a correction suggestion system, and a correction suggestion program.

[0002] Conventionally, a technique for proposing document revisions based on a past revision history is known.

[0003] For example, in the device described in Patent Document 1, a detection means detects that a first item has been edited, a notification means notifies an operator to edit a second item corresponding to the detected first item that was the subject of editing, and a presentation means presents the edited information corresponding to the pre-edited information as an editing candidate if the pre-edited information stored in a storage means that stores pre-edited information and post-edited information is included in the information of the second item that was the subject of editing.

[0004] JP 2013-058168 A

[0005] However, the system described in Patent Document 1 merely displays editing suggestions for a second item in response to editing of a first item, and may not be suitable for proposing revisions to a contract.

[0006] Therefore, one aspect of the present invention aims to provide a revision proposal method, a revision proposal system, and a revision proposal program that are capable of making appropriate revision proposals in a contract.

[0007] In one aspect of the present invention, a method for suggesting revisions has a processor store in memory pre-revision information, which is the content of an item in a first contract before revision, and post-revision information, which is the item after revision of the pre-revision item, in association with each other, and provide revision proposal information regarding a proposal for revision of the target item in a second contract, which is different from the first contract, based on the post-revision information.

[0008] According to one aspect of the present invention, it is possible to provide a revision suggestion method, a revision suggestion system, and a revision suggestion program that are capable of making appropriate revision suggestions in a contract.

[0009] 1 is a diagram showing an overview of processing in the revision suggestion system 100, which is one embodiment of the present invention. FIG. 2 is a diagram showing the configuration of the revision suggestion system 100, which is one embodiment of the present invention. FIG. 3 is a diagram showing an example of contract information stored in the storage unit 110. FIG. 4 is a diagram showing an example of item information stored in the storage unit 110. FIG. 5 is a diagram showing an example of a revision process in the revision suggestion system 100. FIG. 6 is a diagram showing an example of correspondence information stored in the storage unit 110. FIG. 7 is a diagram showing an example of provision of revision suggestion information by the revision suggestion unit 170. FIG. 8 is a diagram showing an example of provision of revision suggestion information by the revision suggestion unit 170. FIG. 9 is a flowchart showing an example of processing in the revision suggestion system 100. FIG. 10 is a diagram showing a first modified example of the configuration of the revision suggestion system 100a, which is one embodiment of the present invention. FIG. 11 is a diagram showing an example of a screen for performing an operation to change the order of revisions to the first contract. FIG. 12 is a diagram showing an example of a screen for performing an operation to change the order of revisions to the first contract. FIG. 13 is a diagram showing an example of the hardware configuration of a computer 1100.

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described with reference to the drawings.

[0011] In this specification, the term "unit" does not simply mean a physical means, but also includes cases where the functions of the "unit" are realized by software. Furthermore, the functions of one "unit" or device may be realized by two or more physical means, devices, or software, and the functions of two or more "units" or devices may be realized by one physical means, device, or software.

[0012] FIG. 1 is a diagram showing an overview of the processing in a revision suggestion system 100 according to an embodiment of the present invention.

[0013] When a contract is concluded, the parties to the contract reach an agreement. When the parties to the contract reach an agreement, one or both of the parties may inspect and amend the contract. For example, in the case of a contract between companies, the legal department in charge of contract inspection will inspect the contents of the contract and amend it as necessary. Note that contract inspection is also sometimes called confirmation, examination, or review.

[0014] The amendment suggestion system 100 of this embodiment proposes amendments to a contract based on past cases.

[0015] The revision proposal system 100 of this embodiment is an information processing system realized by a revision proposal program, and is an information processing system that proposes revisions to the contents of target items in a second contract that is different from the first contract, based on a correspondence that associates the contents of the items in the first contract before and after the revision.

[0016] First, the user uploads the first contract before and after the revision to the revision proposal system 100. The revision proposal system 100 divides each of the first contract before and after the revision by item (for example, by clause), and stores in memory correspondence information that associates the contents of the items of the first contract before and after the revision (S101).

[0017] Next, the user uploads a second contract different from the first contract (i.e., a contract that is the target of the revision proposal process by the revision proposal system 100, for example, a contract that the user wishes to inspect) to the revision proposal system 100. The revision proposal system 100 divides the second contract into items, and extracts correspondence information based on target information that indicates the target items in the second contract that are the target of the revision proposal (S102).

[0018] The revision proposal system 100 then provides the user terminal with revision proposal information regarding the proposed revision of the target clause in the second contract based on the extracted correspondence information (e.g., post-revision information indicating the content after the revision) (S103). The user refers to the revision proposal information and, as necessary, revises the content of the target item in the second contract.

[0019] The contract to be processed by the revision suggestion system 100 is a document on an electronic medium (electronic document). That is, the contract is, for example, an electronic document created using predetermined electronic document creation software, or an electronic document obtained by digitizing a paper contract using predetermined image analysis technology (for example, OCR (Optical Character Recognition) technology). Furthermore, the contract to be processed by the revision suggestion system 100 is, for example, a document that includes clauses and generates predetermined legal effects, and includes applications, memoranda, etc.

[0020] Furthermore, contracts that are processed by the revision proposal system 100 include not only contracts that both parties have agreed upon, but also contracts that are currently being confirmed by both parties (i.e., contract drafts), contracts that have been exchanged between the parties but have not been agreed upon, or contract templates that have been created for reference when entering into a contract with another party. In the description of this embodiment, unless otherwise specified, "contract" includes not only contracts that both parties have agreed upon, but also contracts that are currently being confirmed by both parties (i.e., contract drafts), contracts that have been exchanged between the parties but have not been agreed upon, or contract templates that have been created for reference when entering into a contract with another party.

[0021] Furthermore, the revision suggestion system 100 does not need to perform the processes described below (for example, item division process, process of associating content before and after revision, and revision suggestion process) for all contracts to be processed. In other words, the revision suggestion system 100 may perform part of the processes described below for some contracts.

[0022] 2 is a diagram showing the configuration of a revision suggestion system 100 according to one embodiment of the present invention. The revision suggestion system 100 is, for example, an information processing system that is communicably connected to a user terminal 200 via a network such as the Internet. Details of the revision suggestion system 100 will be described later.

[0023] The user terminal 200 is, for example, a computer used by a user of the correction suggestion system 100, such as a smartphone, a tablet terminal, or a personal computer.

[0024] For example, the user accesses the revision proposal system 100 through the user terminal 200 and uploads the first contract before and after revision to the revision proposal system 100. Furthermore, the user uploads the second contract to the revision proposal system 100 through the user terminal 200. Then, the user is provided with revision proposal information for the target items in the second contract through the user terminal 200.

[0025] Although only one user terminal 200 is shown in FIG. 2, the number of user terminals 200 is not limited to this.

[0026] Next, details of the revision proposal system 100 will be described. The revision proposal system 100 of this embodiment includes a storage unit 110, a contract acquisition unit 120, an item division unit 130, a correspondence setting unit 140, a correspondence extraction unit 150, a revision proposal information generation unit 160, and a revision proposal unit 170. Each unit shown in Fig. 2 can be realized, for example, by using a storage area or by a processor executing a program stored in the storage area.

[0027] The storage unit 110 of this embodiment stores information processed in the revision suggestion system 100. The storage unit 110 can store, for example, contract information, item information, and correspondence information, which will be described later. The storage unit 110 may be, for example, a memory.

[0028] The contract acquisition unit 120 of this embodiment, for example, acquires contract information related to the contracts (first contract and second contract) and stores it in the storage unit 110. The contract acquisition unit 120 can acquire contract information for the first contract before amendment, the first contract after amendment, and the second contract.

[0029] Here, the contract information is information relating to the contract, and includes, for example, status information, position information, contract type information, and contract content information.

[0030] The status information is information indicating the status of the contract, for example, information indicating the revision status of the contract. The status information may be, for example, "Partner's Draft" indicating that the contract is a draft (e.g., a first draft) by the contracting party, "Partner's Revision" indicating that the contract has been revised by the contracting party, "Reviewed" indicating that the contract has been confirmed by the company (the business to which the user belongs), or "Concluded" indicating that the contracting parties have reached an agreement.

[0031] The position information in this embodiment is information indicating the position of the contract, for example, information indicating the position of the company (the business to which the user belongs). The position information may be, for example, "outsourcing party" indicating the outsourcing party in a business outsourcing contract, or "disclosing party" indicating the disclosing party of confidential information in a confidentiality agreement.

[0032] The contract type information in this embodiment is information indicating the type of contract, and may be, for example, a "service outsourcing contract" or a "non-disclosure agreement."

[0033] The contract content information in this embodiment is information (for example, character data) that indicates the content of the contract.

[0034] The contract acquisition unit 120 may acquire the contract information from, for example, the user terminal 200. That is, the user may provide (upload) a contract to the revision proposal system 100 via the user terminal 200, and the contract acquisition unit 120 may acquire the contract information of the uploaded contract.

[0035] At this time, the contract acquisition unit 120 may acquire contract information from the user, for example, through operation of the user terminal 200. In this case, when receiving an upload of a contract from the user terminal 200, the contract acquisition unit 120 may acquire the contract information by accepting input (for example, input from a keyboard or selection of an item preset by the system) of at least some of the contract information (for example, status information, position information, contract type information) from the user.

[0036] Furthermore, the contract acquisition unit 120 may acquire contract information from, for example, another information processing system. In this case, for example, the user may provide contract information to the other information processing system via the user terminal 200, and the contract acquisition unit 120 may acquire the contract information provided from the other information processing system. Examples of other information processing systems include a contract management system, a document management system, and cloud storage.

[0037] Furthermore, the contract acquisition unit 120 may analyze the content information of the contract and acquire at least a portion of the contract information (for example, status information, position information, contract type information).

[0038] 3 is a diagram showing an example of contract information stored in the storage unit 110. The contract information stored in the storage unit 110 includes, for example, a contract ID, a sequence ID, status information, position information, contract type information, and contract content information.

[0039] The contract ID in this embodiment is information that identifies a contract processed by the revision proposal system 100. The contract ID is identification information that is assigned so that the contract before and after revision of the same contract can be identified. In other words, the contract ID is information that uniquely identifies the contract (i.e., the electronic document) acquired by the contract acquisition unit 120.

[0040] The sequence ID in this embodiment is information that identifies the contract indicated by the contract processed in the revision proposal system 100. In other words, the sequence ID is a unit for managing, for example, a series of contracts that have been drafted, revised, and agreed upon (i.e., multiple contracts, such as a draft contract, a contract under revision, and an agreed upon contract, aimed at concluding the contract).

[0041] More specifically, the same sequence ID may be associated with multiple contracts with different contract IDs. In other words, if the same contract has both pre- and post-revision contracts, the pre- and post-revision contracts will have different contract IDs but the same sequence ID. This allows the revision suggestion system 100 to recognize the corresponding pre- and post-revision contracts (i.e., which contract was revised to result in which contract).

[0042] The contract acquisition unit 120 of this embodiment may generate a sequence ID, for example, in response to a user's operation of the user terminal 200. Specifically, when a user uploads the first contract before revision, for example, the first contract before revision may be uploaded to an area for managing the first contract (for example, a virtual folder managed on the revision suggestion system 100), and a specific sequence ID (for example, a sequence ID corresponding to the virtual folder or a sequence ID identical to the sequence ID of the first contract before revision) may be generated.

[0043] Furthermore, when uploading a first contract after revision by a user, the contract acquisition unit 120 may generate a sequence ID for the uploaded first contract as the sequence ID for the revised first contract (or generate multiple sequence ID candidates and present them to the user terminal 200) based on the similarity between the content of the revised first contract and the content of the first contract already uploaded to the revision proposal system 100. This allows the user to easily perform the process of generating a sequence ID when uploading the revised first contract.

[0044] Here, the contract acquisition unit 120 may evaluate the similarity between the revised first contract and the first contract that has already been uploaded to the revision proposal system 100, for example, based on the contracting parties in the first contract, the creation dates of the first contract before and after the revision, and contract information (e.g., status information, position information, contract type information, contract content information) for each of the first contract before and after the revision.

[0045] The item dividing unit 130 of this embodiment divides the contents of the contract into items included in the contract based on the contract information, and stores item information relating to the items in the storage unit 110.

[0046] Here, the items may correspond to clauses included in the contract, for example. That is, the item dividing unit 130 can divide the contents of the contract into, for example, "articles" or "paragraphs."

[0047] For example, the item dividing unit 130 can analyze the contents of a contract and divide the contents of the contract into items based on the positions of characters corresponding to the items (for example, the characters "article" or "paragraph"). Note that the item dividing unit 130 does not have to divide all contracts into items, and it does not have to divide all items of a contract into items. In other words, the item dividing unit 130 may perform item division processing on only a portion of a contract, or only a part of a contract.

[0048] When the contract acquisition unit 120 acquires contract information for the first contract before amendment, the item division unit 130 can divide the first contract before amendment into items and generate pre-amendment information indicating the pre-amendment content of each item as item information.

[0049] Furthermore, when the contract acquisition unit 120 acquires contract information for the revised first contract, the item division unit 130 can divide the revised first contract into items and generate revised information indicating the revised content of each item as item information.

[0050] In addition, when the contract acquisition unit 120 acquires the contract information of the second contract, the item division unit 130 can divide the second contract into items and generate target information indicating the target items in the second contract that are the subject of the proposed revisions as item information.

[0051] 4 is a diagram showing an example of item information stored in the storage unit 110. The item information stored in the storage unit 110 includes, for example, an item ID, a contract ID, and item content information.

[0052] The item ID in this embodiment is information that identifies the item information processed in the revision suggestion system 100. The item content information in this embodiment is information that indicates the content corresponding to the item, for example, information that indicates the content of each clause.

[0053] In addition, whether the item information stored in the memory unit 110 is pre-correction information, post-correction information, or target information may be determined, for example, based on the contract ID included in the item information (specifically, for example, based on the status information corresponding to the contract ID).

[0054] The correspondence setting unit 140 of this embodiment generates correspondence information that associates the pre-correction information with the post-correction information, and stores the information in the storage unit 110 .

[0055] The correspondence information in this embodiment is information that associates the content before and after amendment for each item in the first contract, and specifically, is information that indicates the correspondence between the information before and after amendment for the same item in multiple contracts in the same sequence.

[0056] In this embodiment, multiple contracts in the same sequence are, for example, multiple contracts with the same sequence ID.

[0057] When the items of multiple contracts in the same sequence are the same, for example, the pre-amendment information and the post-amendment information are items that correspond to each other.

[0058] Note that the items corresponding to the pre-amendment information and the items corresponding to the amended information may both have the same item ID (in other words, for example, the article number, or the article and paragraph number). Specifically, if the pre-amendment information and the amended information both correspond to "Article 1" in the first contract, the amendment suggestion system 100 may determine that the pre-amendment information and the amended information are the same items in multiple contracts in the same sequence.

[0059] Furthermore, an item corresponding to the pre-revision information and an item corresponding to the post-revision information may have different item IDs. In this case, the revision suggestion system 100 may determine, for example, based on the contents indicated by the pre-revision information and the post-revision information, that the pre-revision information and the post-revision information are identical to each other in multiple contracts of the same sequence.

[0060] Specifically, if the contents indicated by the pre-amendment information and the post-amendment information both relate to the scope of the contracting parties' responsibilities, they correspond to the same item whether their item IDs are the same or different. On the other hand, if the contents indicated by the pre-amendment information indicate the expiration date of the contract and the contents indicated by the post-amendment information indicate the scope of the contracting parties' responsibilities, they do not correspond to the same item whether their article numbers are the same or different.

[0061] The item ID may also be linked to an issue that appears in the contract or type of contract. For example, the item ID may be linked to information indicating whether the contract is automatically renewed, or to an issue such as governing law or jurisdiction. For example, if the type of contract is a confidentiality agreement, the item ID may be assigned in association with an issue that appears depending on the type of contract (for example, if the type of contract is a confidentiality agreement, an issue such as the scope of confidential information or disposal of confidential information).

[0062] The revision suggestion system 100 may determine that the items of multiple contracts in the same sequence, whose pre-revision information and post-revision information are identical, are identical based on both the matching status of item IDs and the matching status of content. In this case, the revision suggestion system 100 may place more importance on either the matching status of item IDs or the matching status of content based on a predetermined priority. Furthermore, when determining that the items of multiple contracts in the same sequence are identical, the revision suggestion system 100 may determine that the items of multiple contracts in the same sequence are identical if one item matches more closely than other items, even if the matching status of item IDs or content do not match completely.

[0063] Furthermore, the order of the item division processing by the item division unit 130 for the first contract and the processing by the correspondence setting unit 140 does not matter. In other words, the correspondence setting unit 140 may set the correspondence between the first contract before and after the revision based on the contract information, and then the item division unit 130 may perform item division processing to generate correspondence information between the information before revision and the information after revision for each item, or after the item division processing by the item division unit 130, the correspondence setting unit 140 may perform processing to generate correspondence information for each item.

[0064] 5A is a diagram showing an example of the revision process of the revision suggestion system 100 of this embodiment. Item information 501 is item information at the time of drafting. Item information 502 is item information after the first revision (first revision) of item information 501. Item information 503 is item information after the second revision (second revision) of item information 502 has been finalized. The sequence ID is the same for both pieces of item information.

[0065] Fig. 5B is a diagram showing an example of correspondence information stored in the storage unit 110. The example of correspondence information shown in Fig. 5B corresponds to the example of the correction process shown in Fig. 5A. The correspondence information stored in the storage unit 110 includes, for example, pre-correction information and post-correction information. The correspondence information may include, for example, corresponding item IDs as the pre-correction information and the post-correction information.

[0066] When the correction shown in Fig. 5A is made, the correspondence relationship information stored in the storage unit 110 becomes, for example, as the example shown in Fig. 5B. That is, the correspondence relationship information holds, for example, item information 501 and 502 as pre-correction information, and holds item information 503 as post-correction information so as to correspond to item information 501 and 502.

[0067] The correspondence information may hold item information 502 (in this case, "C0002-2-1") instead of item information 503 (in this case, "C0003-2-1") as post-correction information (in this case, "C0001-2-1") corresponding to item information 501 of the pre-correction information, or may hold both item information 502 and item information 503. This allows the correction suggestion system 100 to have correspondence information for each correction process.

[0068] The correspondence extraction unit 150 of this embodiment extracts at least one piece of correspondence information from the pre-correction information and post-correction information for each item in the first contract, based on the target information in the second contract.

[0069] Furthermore, the correspondence extraction unit 150 can extract at least one piece of correspondence information based on the degree of association between the pre-correction information and the target information. Specifically, the correspondence extraction unit 150 can extract correspondence information corresponding to the pre-correction information having an item that is highly related to the target item indicated by the target information (especially, for example, the post-correction information associated with the pre-correction information).

[0070] Here, the degree of relevance is, for example, the degree of relevance between the content indicated by the pre-revision information and the content indicated by the target information. Specifically, the degree of relevance may be based on at least one of the content of the pre-revision information and the target information, the position or contract type in the first contract corresponding to the pre-revision information and the second contract corresponding to the revised information, and the issues included in the pre-revision information and the target provision information.

[0071] The relevance based on the content of the pre-revision information and the target information is, for example, the relevance between the content of the item indicated by the pre-revision information and the target information (e.g., the content of the article). That is, for example, if the content indicated by the pre-revision information and the content indicated by the target information are evaluated to be similar based on a predetermined natural language processing, the relevance may be evaluated as high. This allows the revision suggestion system 100 to extract pre-revision information having content similar to the target information, and to perform the revision suggestion process without the user having to modify the content of the target information.

[0072] The relevance based on the position or contract type in the first contract corresponding to the pre-amendment information and the second contract corresponding to the amended information may be evaluated highly, for example, when the positions or contract types of the first contract and the second contract are the same. This allows the amendment proposal system 100 to extract pre-amendment information of the first contract with a similar position or contract type to the second contract, and to perform amendment proposal processing.

[0073] The issues contained in the Pre-Revised Information and the Subject Information are, for example, matters that should be noted in the content of the Pre-Revised Information and the Subject Information. In other words, the issues relate to matters that the company should particularly confirm, such as the definitions of terms used in contracts with other companies or the scope of the content.

[0074] The relevance based on the issue may be highly evaluated when the issue included in the pre-revision information and the target information is the same or similar. This allows the revision suggestion system 100 to extract pre-revision information that includes an issue that is the same or similar to an issue of the target information, and to make a revision suggestion.

[0075] Here, the points of contention may be set in advance by the administrator of the revision suggestion system 100 in correspondence with predetermined content. Alternatively, the points of contention may be set at parts that are frequently revised by users based on the correspondence relationship information.

[0076] The revision suggestion system 100 can extract points of contention by analyzing the contents of the contract based on predetermined natural language processing.

[0077] The relevance may also be a relevance based on comment information indicating the content of comments included in the electronic file of the contract (first contract or second contract).

[0078] Here, the comment is, for example, an annotation written by a user (for example, a person in charge of a contracting party (i.e., one's own company) using the revision proposal system 100) describing the intention or concerns of the revision content when inspecting the contract. Note that the comment may also be an annotation written by a person in charge of the other contracting party (i.e., another company).

[0079] The comment information in this embodiment is information indicating the content of the comment, and is included in the electronic file of the contract uploaded by the user. The revision suggestion system (particularly, for example, the contract acquisition unit 120) can acquire the comment information as contract information when the user uploads the contract.

[0080] The relevance based on the comment information may be evaluated highly, for example, when the content of the comments in the pre-editing information and the target information is identical or similar. This allows the edit suggestion system 100 to extract pre-editing information with identical or similar comments and to suggest edits without the user having to edit the content of the target information.

[0081] The items to be prioritized in calculating the relevance between the pre-revision information and the target information may be set by an administrator or a user of the revision suggestion system 100. That is, for example, if a user sets the calculation of the relevance to prioritize position over content in a contract, the correspondence extraction unit 150 may not extract correspondence information of pre-revision information in which the position in the pre-revision information is not the same as the position in the target information, even if the content in the pre-revision information is similar to the content in the target information. This allows the revision suggestion system 100 to extract pre-revision information that is more suitable for the user's revision.

[0082] In this way, the correspondence extraction unit 150 can extract correspondence information suitable for proposing amendments to the target items in the second contract.

[0083] More specifically, the correspondence extraction unit 150 can extract correspondence information corresponding to pre-revision information related to the target item (i.e., pre-revision information having content similar to that of the target item, for example). In this case, since the content indicated by the target information and the content indicated by the pre-revision information are similar, there is a possibility that the content of the revision in the first contract corresponding to the pre-revision information will also be appropriate for the second contract corresponding to the target information. Therefore, the correspondence extraction unit 150 can extract correspondence information suitable for proposing revisions to the target item in the second contract.

[0084] The amendment proposal information generation unit 160 of this embodiment generates amendment proposal information regarding proposed amendments to the target clause in the second contract based on the post-amendment information, and stores the information in the storage unit 110. More specifically, the amendment proposal information generation unit 160 can generate amendment proposal information regarding proposed amendments to the target clause in the second contract based on the post-amendment information included in at least one piece of extracted correspondence information.

[0085] Here, the correction suggestion information is information for suggesting to the user how to correct the target item.

[0086] The correction suggestion information may include, for example, post-correction information included in at least one of the extracted correspondence information, which allows the user to understand the content of past corrections and correct the target item.

[0087] Furthermore, the proposed revision information may further include, in addition to the revised information, comment information added by the user when revising the clause before revision (i.e., comment information included in the electronic file of the first contract before revision). This allows the user to understand comments made in the past revision process and make revisions to the target items.

[0088] Furthermore, the proposed revision information may include, in addition to the revised information, at least one of position information and contract type information indicating the position and contract type in the first contract. This allows the user to understand the position or contract type in the first contract that corresponds to the proposed revision information and to revise the target item.

[0089] Furthermore, the revision proposal information may further include, in addition to the revised information, information (e.g., status information) regarding whether the revision has been adopted. Here, whether the revision has been adopted may be determined, for example, based on the status information of the contract corresponding to the revised information. That is, if the contract is “concluded,” or if the status information of another contract having the same sequence ID as the contract is “concluded,” and the content of the item corresponding to the revised information has not been revised, it may be determined that the revision has been adopted. The revision proposal information may include the “concluded” status information in addition to the revised information. This allows the user to understand whether the revised content indicated by the revision proposal information is content that has been agreed upon and whether the revision is likely to be adopted in the current contract being inspected. Note that, if it is unclear whether the revision has been adopted, the revision proposal information may or may not include information indicating whether the revision has been adopted.

[0090] The revision suggestion information does not necessarily have to be prepared by the user, but may be prepared or set by a third party. For example, it may be prepared in advance by a vendor that provides the revision suggestion system so that it can be used by users. This reduces the effort required to set up the revision suggestion information.

[0091] Furthermore, the vendors can revise the revision proposal information as needed to adapt to legal changes, etc. This allows users to receive appropriate revision proposals at the appropriate time.

[0092] In addition, if it is necessary to change the proposed revision information due to legal amendments, changes in standards, etc., the system may have a function for collectively amending the proposed revisions for multiple documents containing similar issues, allowing users to receive appropriate proposed revisions.

[0093] The amendment proposing unit 170 of this embodiment provides amendment proposal information to the user terminal 200. That is, the amendment proposing unit 170 provides amendment proposal information regarding a proposal to amend the target clause in the second contract to the user terminal 200 of the user, based on at least one piece of extracted correspondence information.

[0094] Furthermore, the correction suggestion unit 170 can display the results of a series of correction processes corresponding to the extracted correspondence information on the user terminal 200. Specifically, when multiple corrections (for example, a first correction and a second correction) are made to the first contract corresponding to the extracted correspondence information, the correction suggestion unit 170 can display the results of the first correction and the results of the second correction on the user terminal 200. This allows the user to correct the target item after understanding the detailed correction process.

[0095] Furthermore, the revision suggestion unit 170 can provide the user terminal 200 with a plurality of pieces of revision suggestion information based on a plurality of pieces of correspondence information. In this case, the plurality of pieces of revision suggestion information may be associated with information indicating a predetermined order. Note that the predetermined order may be, for example, the order of the date and time when the revision corresponding to the revised information was made (e.g., the order in which the date and time when the revision was made is closest), or the order of the status information of the first contract corresponding to the revised information (e.g., the order in which the status information of "concluded" is given priority).

[0096] Furthermore, when the revision suggestion unit 170 provides the user terminal 200 with multiple pieces of revision suggestion information based on multiple pieces of correspondence information, it can display similar pieces of revision suggestion information (for example, revision suggestion information whose content is similar to the post-revision information or the pre-revision information) together from among the multiple pieces of revision suggestion information.

[0097] Specifically, for example, the revision suggestion unit 170 can display, on the user terminal 200, one piece of revision suggestion information (e.g., revision suggestion information generated based on correspondence information corresponding to the latest post-revision information) from among multiple pieces of revision suggestion information that are similar to each other, and a button for displaying other pieces of revision suggestion information that are similar to the one piece of revision suggestion information. At this time, the revision suggestion unit 170 can also display revision suggestion information that is dissimilar to the multiple pieces of revision suggestion information that are similar to each other. This allows the user to simplify the display of similar revision suggestion information and be provided with more revision suggestion information.

[0098] At this time, the revision suggestion unit 170 may change the display order depending on the number of similar revision suggestion information. That is, the more similar the revision suggestion information is, the more the revision suggestion unit 170 may display it at the top of the screen of the user terminal 200. This allows the revision suggestion system 100 to preferentially provide frequently used example sentences to the user.

[0099] 6 is a diagram showing an example of provision of suggested revision information by the revision suggestion unit 170. The screen shown in FIG. 6 shows an example of a display screen of the user terminal 200 to which suggested revision information has been provided by the revision suggestion unit 170.

[0100] 6 includes an area 610 that displays the second contract, and areas 620 and 630 that display suggested revision information for each item (for example, article). Area 620 further includes an area 621 that displays post-revision information, an area 622 that shows buttons for displaying comment information, an area 623 that displays status information corresponding to the post-revision information, an area 624 that displays contract type information and position information corresponding to the post-revision information, an area 625 that displays the name of the person in charge and the date that the revised first contract was uploaded, and an area 626 that shows a button for viewing the revised first contract. Note that area 630 includes areas that correspond to the areas included in area 620.

[0101] The content of the revised information is displayed as suggested revision information in area 621. That is, in the example screen shown in Fig. 6, the revised information of the correspondence information extracted based on the content of the target item (here, Article 1 of the second contract) is displayed. The user can refer to the revised information displayed in area 621 and make revisions to the target item.

[0102] The user can also refer to the content displayed in areas 623, 624, and 625 to correct the target item.

[0103] That is, for example, if the status information displayed in area 623 is "reviewed," the user can recognize the proposed revision information displayed in area 620 as information based on the first contract that has been reviewed by the user's company.

[0104] Also, for example, if the contract type information and position information displayed in area 624 are the same as those of the second contract, the user can recognize the proposed revision information displayed in area 620 as information based on the first contract, which has the same contract type or position as the second contract.

[0105] Furthermore, for example, if the information indicating the person in charge and the date displayed in area 625 indicates a reliable person in charge or indicates a date close to the present, the user can recognize the proposed revision information displayed in area 620 as more appropriate. In other words, the user can determine whether the revisions to the first contract were made by a reliable person in charge or whether the revisions to the first contract were made on a date close to the present, and then decide whether to make revisions to the second contract based on the proposed revision information.

[0106] Furthermore, when area 622 is selected, the screen switches to the screen shown in FIG. 7, which will be described later, which displays comment information included in the first contract after correction in the extracted correspondence information.

[0107] The user can then refer to the comment information and make corrections to the target items. That is, the user can understand the intention of the corrections to the first contract, which are included in the comment information, and decide whether to make corrections to the second contract based on the correction proposal information.

[0108] Furthermore, when area 626 is selected, the first contract after correction based on the extracted correspondence information is displayed. The user can refer to the first contract after correction and correct the target items. In other words, the user can, for example, understand the other items in the first contract after correction and decide whether to correct the second contract based on the suggested correction information.

[0109] The amended first contract to be displayed may be displayed on the user terminal 200 in a window separate from the window displaying the screen shown in FIG.

[0110] Fig. 7 is a diagram showing an example of the provision of revision suggestion information by the revision suggestion unit 170. The example screen shown in Fig. 7 corresponds to Fig. 6, but shows an example of the screen when area 622 in Fig. 6 is selected and comment information is displayed.

[0111] The screen shown in FIG. 7 includes an area 627 showing a button for hiding the comment information in the revised first contract, and an area 628 for displaying the comment information in the revised first contract.

[0112] When area 627 is selected, the screen switches to the screen shown in FIG. 6, in which comment information is not displayed.

[0113] The user can make corrections to the target items by referring to the comment information displayed in area 628. That is, the user can understand, for example, the intention of the corrections to the first contract, which is included in the comment information, and decide whether or not to make corrections to the second contract based on the correction proposal information.

[0114] The revision suggestion unit 170 may also display an area on the user terminal 200 that accepts a user's rating, such as a favorite, or a flag related to a suggestion. That is, for example, if the user finds the proposed revision suggestion information appropriate, the user can register the proposed revision suggestion information in their favorites. When providing the revision suggestion information to the user terminal 200, the revision suggestion unit 170 may also provide information (e.g., a star mark) indicating whether the proposed revision suggestion information has been registered in their favorites. The revision suggestion system 100 may also provide the user with a list of the revision suggestion information registered in their favorites. The revision suggestion unit 170 may also preferentially provide the user terminal 200 with the revision suggestion information registered in their favorites. This allows the revision suggestion system 100 to make revision suggestions that are more suitable for the user. The rating and flag information may be available only to the individual user who performed the rating or flag registration operation, or may be available to other users, such as users in an organization to which the user who performed the registration operation belongs. This allows information about revision suggestions to be shared within an organization, thereby providing more appropriate revision suggestion information.

[0115] In this way, the revision suggestion system 100 according to one embodiment of the present invention performs a revision suggestion process for each item (e.g., clause or issue). This allows the user to easily revise the second contract by replacing the proposed revision items. Specifically, the user can revise the second contract, for example, by simply replacing the proposed revision items, without having to perform revision processes that require word replacement (e.g., grammatical revision processes such as modification of dependency).

[0116] This is because an item (e.g., a clause or an issue) corresponds not to a word or character unit but to a certain range of character strings (e.g., a paragraph, a sentence, or a clause) that indicates a certain meaning, and the revision suggestion information generation unit 160 generates the revision suggestion information based on the revised information divided into items.

[0117] The correction suggestion system 100 according to an embodiment of the present invention may use words as items, that is, the correction suggestion system 100 may perform the correction suggestion process for each word.

[0118] FIG. 8 is a flowchart showing an example of processing in the correction suggestion system 100.

[0119] First, the contract acquisition unit 120 acquires contract information relating to the first contract before and after the revision, and the item division unit 130 divides it by item to generate pre-revision information and post-revision information (S801). Next, the correspondence setting unit 140 sets the correspondence between the pre-revision information and post-revision information for each item (S802).

[0120] The contract acquisition unit 120 acquires contract information related to the second contract, and the item division unit 130 divides the second contract into items to generate target information (S803). Subsequently, the correspondence extraction unit 150 extracts at least one piece of correspondence information based on the target information (S804). Then, the revision proposal information generation unit 160 generates revision proposal information based on post-revision information included in the extracted at least one piece of correspondence information, and the revision proposal unit 170 provides the revision proposal information to the user terminal 200 (S805).

[0121] <Variation 1> Next, a first variation of the revision suggestion system 100 will be described. Fig. 9 is a diagram showing a first variation of the configuration of the revision suggestion system 100a, which is one embodiment of the present invention. Note that only the configuration that differs from the revision suggestion system 100 will be described below, and unless otherwise specified, it will be assumed that the configuration is the same as the revision suggestion system 100.

[0122] The revision suggestion system 100 a further includes an output unit 180 and a criterion generation unit 190 .

[0123] As described above, the revision suggestion unit 170 can accept registration of flags related to ratings and suggestions, such as favorites, from users (including users and organizations to which the users belong; the same applies hereinafter). In this case, the flag may be a flag related to a positive rating by the user, or a flag related to a negative rating. Examples of positive ratings include "favorite," "like," and adding a star mark. Furthermore, the star mark may be in a format that indicates the degree of rating according to the number of stars (e.g., 3 or 5).

[0124] Furthermore, the revision suggestion unit 170 can provide revision suggestion information to the user terminal 200 based on a flag registered by the user. Specifically, the revision suggestion unit 170 may provide revision suggestion information that has been registered with a positive user rating or highly rated (for example, revision suggestion information with a high average score on a 5-point scale) to the user terminal 200 preferentially by displaying it at the top, and may also display revision suggestion information that has been registered with a negative rating at the bottom or not display it at all. This allows the revision suggestion system 100a to make revision suggestions that are more suitable for the user.

[0125] Furthermore, when the revision suggestion unit 170 provides revision suggestion information to the user terminal 200 based on the flag registered by the user, the revision suggestion unit 170 may perform different processing, for example, for each attribute (e.g., position, contract type) of the contract that is the subject of the revision suggestion.

[0126] Specifically, for example, if the position in the contract corresponding to the revision proposal information in which a positive flag has been registered by the user differs from the position in the second contract that is the subject of the revision proposal, the revision proposal information may not be appropriate for the second contract. In this case, the revision proposal unit 170 may display the revision proposal information at a lower level or may not display it at all. This makes it possible to provide revision proposal information that is more appropriate for the contract being reviewed.

[0127] Furthermore, for example, if the contract type in the contract corresponding to the revision proposal information registered by the user with a positive flag differs from the contract type in the second contract that is the subject of the revision proposal, the revision proposal information may not be appropriate for the second contract. In this case, the revision proposal unit 170 may not display or provide the revision proposal information at a lower level. This makes it possible to provide revision proposal information that is more appropriate for the contract being reviewed.

[0128] The process of providing suggested revision information by the revision suggestion unit 170 can be customized by user settings. That is, for example, when the revision suggestion unit 170 changes the display order depending on the number of suggested revision information when providing the suggested revision information, if the user sets the process not to be performed, the revision suggestion unit 170 may provide suggested revision information to the user terminal 200 without performing the process.

[0129] Furthermore, when providing the proposed revision information, the revision suggesting unit 170 can display the differences between the content of the second contract and the content of the revised information in a manner that allows the user to easily recognize them. For example, the differences and non-differences can be displayed in different ways.

[0130] A specific explanation will be given using Figure 6. In the screen shown in Figure 6, the second contract is displayed in area 610, and the revised information is displayed in area 621. In this case, the revision suggesting unit 170 can, for example, highlight in area 621 characters or character strings that are not written in area 610. This allows the user to easily recognize the differences between the second contract to be reviewed and the proposed revision information, making it easier to review the second contract.

[0131] Furthermore, when displaying a plurality of pieces of proposed revision information, the revision suggestion unit 170 may highlight the differences for the proposed revision information selected by the user, and may not highlight the differences for the proposed revision information not selected by the user. Specifically, for example, when the pointer of the mouse operated by the user is over area 620, the differences between the revised information displayed in area 621 and the second contract displayed in area 610 may be highlighted, and when the pointer of the mouse operated by the user is over area 630, the differences between the revised information displayed in area 630 and the second contract displayed in area 610 may be highlighted.

[0132] The method of highlighting the differences by the correction suggestion unit 170 may be, for example, to display the highlighted characters or strings in a different color, to display the background of the characters or strings in a specific color (highlighting), to surround the characters or strings with a specific shape (e.g., a rectangle), or any other method that allows the user to easily distinguish between the characters or strings that are highlighted and the characters or strings that are not highlighted.

[0133] The user may set whether or not to display the highlighting of the differences by the correction suggestion unit 170. This allows the user to switch the setting for highlighting on or off depending on the situation he or she desires.

[0134] The revision suggestion system 100a may further include an output unit 180 that outputs the revision suggestion information to an external system (e.g., the user terminal 200). In this case, the output unit 180 of the revision suggestion system 100a may output the revision suggestion information for which a flag has been registered by the user to the external system (e.g., the user terminal 200).

[0135] Furthermore, the output unit 180 of the revision suggestion system 100a may output information indicating the correspondence between the flag registered by the user and the revision suggestion information in which the flag is registered. This allows the user to consider the review criteria of the user (particularly the user's department or company) based on the revision suggestion information accumulated in the revision suggestion system 100a, while referring to the status of use and evaluation of the revision suggestion information.

[0136] The revision suggestion system 100a may further include a criteria generation unit 190 that generates criteria information that serves as a criterion for a user's review of the contract based on the revision suggestion information. In this case, the criteria generation unit 190 of the revision suggestion system 100a may generate the criteria information based on the revision suggestion information for which a flag has been registered by the user. This allows the user to obtain criteria for a contract review based on the revision suggestion information accumulated in the revision suggestion system 100a.

[0137] The criteria generation unit 190 can generate a contract template or update an existing contract template using items (e.g., clauses) including suggested revision information (especially revised information) with a positive flag registered as the criteria information. The criteria generation unit 190 can also generate, as the criteria information, user review criteria, a collection of use cases, a handbook, or a rulebook, for example.

[0138] The criteria generating unit 190 may also generate criteria information based on the number of pieces of revision suggestion information. That is, the criteria generating unit 190 may generate criteria information based on a group of pieces of revision suggestion information that have a certain number or more of similar pieces of revision suggestion information. In this way, when a certain number or more pieces of similar revision suggestion information have been accumulated, the accumulated pieces of similar revision suggestion information can be used as a criterion for user reviews, and more appropriate review criteria can be generated.

[0139] Furthermore, the criteria generator 190 may generate reference information based on suggested revision information that is selected from the suggested revision information based on a user operation (or further based on approval from an organization to which the user belongs). Specifically, the criteria generator 190, for example, displays on the user terminal 200 candidates for suggested revision information to be used in generating reference information and accepts a selection operation by the user. Then, the criteria generator 190 generates reference information based on the suggested revision information selected by the selection operation, for example. This allows the user to select suggested revision information suitable for generating reference information and obtain the reference information.

[0140] Furthermore, when displaying candidates for revision proposal information used to generate the reference information on the user terminal 200, the criterion generating unit 190 can also display information useful for selecting the revision proposal information. The information useful for selecting the revision proposal information may be, for example, information indicating a flag registered by the user, information indicating the number of times the revision proposal information has been used in contract reviews, or information indicating the number of similar revision proposal information. Specifically, the criterion generating unit 190, for example, associates the revision proposal information with information indicating the flag and displays it on the user terminal 200. The user can generate the reference information by, for example, selecting revision proposal information with a positive flag and not selecting revision proposal information with a negative flag. This allows the user to select the revision proposal information to be used as the reference information and obtain more appropriate reference information.

[0141] The criteria information generated by the criteria generating unit 190 may be stored in the storage unit 110 or provided to an external information processing system. The criteria information generated by the criteria generating unit 190 may be editable by a user or a system administrator of the revision suggestion system 100a.

[0142] <Second Modification> Next, a second modification of the correction suggestion system 100 will be described.

[0143] The revision suggestion system 100 may acquire the first contract and generate revision suggestion information, recognizing that revisions have been made in an order different from the order in which the revisions were actually made. In other words, the revision suggestion system 100 may mistakenly recognize and process the first contract before revision as the first contract after revision, or may mistakenly recognize and process the first contract after revision as the first contract before revision.

[0144] Such a case may occur, for example, when the revision proposal system 100 recognizes the order of revisions to the uploaded first contract based on the chronology of the dates and times acquired by the contract acquisition unit 120 (i.e., for example, when uploaded by a user). That is, if a user first uploads the revised first contract to the revision proposal system 100 and then uploads the unrevised first contract to the revision proposal system 100, the revised first contract uploaded first may be managed as the unrevised first contract in the revision proposal system 100, and the unrevised first contract uploaded later may be managed as the revised first contract.

[0145] In this case, since the pre-correction information does not indicate the information before correction for the item, and the post-correction information does not indicate the information after correction for the item, the correction suggestion information generation unit 160 may not be able to generate appropriate correction suggestion information.

[0146] Therefore, the contract acquisition unit 120 can acquire the first contract so as to match the order of the amendments that were actually made. The contract acquisition unit 120 acquires contract information including amendment order information that indicates the order of amendments to the first contract, for example, and stores it in the storage unit 110.

[0147] Specifically, the contract acquisition unit 120 can generate revision order information according to the order of the dates and times indicated by the file update dates and times of the first contract to be acquired, for example, and store this information in the storage unit 110. In other words, in this case, the contract acquisition unit 120 acquires the first contract assuming that the first contract was revised in the order of the dates and times indicated by the update dates and times. Then, the item division unit 130 generates item information with item IDs according to the order of the actual revisions based on the contract information including the revision order information.

[0148] This allows the revision proposal system 100 to manage the first contract before revision and the first contract after revision in the order in which the revisions were actually made, and also allows the revision proposal information generation unit 160 to generate appropriate revision proposal information.

[0149] Furthermore, the revision suggestion system 100 (for example, the contract acquisition unit 120) can update the contract information (particularly, for example, revision order information) stored in the storage unit 110 based on a user operation. This allows the user to change the order of revisions to the first contract after uploading the contract. In this case, the item division unit 130 may perform a process of dividing the contents of the contract into each item included in the contract based on the contract information updated in response to the user's rearrangement operation.

[0150] The user's replacement operation may be, for example, an operation of selecting and moving (e.g., a drag operation) an icon representing the first contract that is displayed on the display unit of the user terminal 200 according to the order of amendments.

[0151] In addition, the user may perform the replacement operation, for example, at or after uploading the first contract, at or after a sequence ID is assigned in response to uploading the first contract, at or after multiple first contracts are integrated into one sequence ID, or at or after multiple sequence IDs are integrated into one sequence ID.

[0152] Figures 10A and 10B are diagrams showing examples of screens for performing an operation to change the order of amendments to the first contract. Figures 10A and 10B are displayed, for example, on the display unit of the user terminal 200. The screen shown in Figure 10A shows an example of a screen that appears when the order of amendments to the first contract is incorrectly recognized and displayed. The screen shown in Figure 10B shows an example of a screen that appears after the order of amendments to the first contract has been changed.

[0153] 10A includes an area 1001 selected by the user when uploading the first contract, an area 1002 showing the order of amendments to the uploaded first contract, and areas 1003a, 1004a, and 1005a that display icons indicating the uploaded first contract. Areas 1003a, 1004a, and 1005a display, for example, information indicating the date and time the first contract was uploaded and information indicating the file name of the first contract.

[0154] The screen shown in Figure 10A indicates that the first contract corresponding to the icon displayed at the top of the display unit is a first contract that was obtained by amending the first contract corresponding to the icon displayed one level lower. The screen shown in Figure 10A indicates that the amendment proposal system 100 has mistakenly recognized that amendments were made in the order of the dates and times when the first contracts were uploaded, and that the second draft of the first contract was created by amending the third draft of the first contract. In this case, the user rearranges the order of amendments to the correct order.

[0155] Specifically, the user selects an icon indicating the first contract to be replaced (for example, the icon displayed in area 1004a) and drags it to the correct position (in this case, the top). In response to the replacement operation, the revision suggestion system 100 updates the contract information (in particular, for example, revision order information) stored in the storage unit 110.

[0156] As a result, as shown in the screen in FIG. 10B, an icon representing the third draft of the first contract is displayed in area 1003b, and an icon representing the second draft of the first contract is displayed in area 1004b.

[0157] Next, an example of a hardware configuration in which the correction suggestion system 100 is realized by a computer 1100 will be described with reference to Fig. 11. Fig. 11 is a diagram showing an example of the hardware configuration of the computer 1100.

[0158] As shown in FIG. 11, a computer 1100 includes, for example, a processor 1101, a memory 1102, a storage device 1103, an input I / F unit 1104, a data I / F unit 1105, a communication I / F unit 1106, and a display device 1107.

[0159] Computer 1100 may be, for example, a server computer, a personal computer (e.g., desktop, laptop, tablet, etc.), a media computing platform (e.g., cable, satellite set-top box, digital video recorder, etc.), a handheld computing device (e.g., PDA, email client, etc.), or any other type of computing or communications platform.

[0160] The processor 1101 is a control unit that controls various processes in the computer 1100 by executing programs stored in the memory 1102 .

[0161] The memory 1102 is a storage medium such as a RAM (Random Access Memory), etc. The memory 1102 temporarily stores the program code of the program executed by the processor 1101 and data required when the program is executed.

[0162] The storage device 1103 is a non-volatile storage medium such as a hard disk drive (HDD), flash memory, etc. The storage device 1103 stores an operating system and various programs for realizing the above-mentioned components.

[0163] The input I / F unit 1104 is a device for receiving input from a user. The input I / F unit 1104 is, for example, a keyboard, a mouse, a touch panel, various sensors, a wearable device, etc. The input I / F unit 1104 may be connected to the computer 1100 via an interface such as a USB (Universal Serial Bus).

[0164] The data I / F unit 1105 is a device for inputting data from outside the computer 1100. The data I / F unit 1105 is, for example, a drive device for reading data stored in various storage media. The data I / F unit 1105 may be provided outside the computer 1100. When the data I / F unit 1105 is provided outside the computer 1100, the data I / F unit 1105 is connected to the computer 1100 via an interface such as a USB.

[0165] The communication I / F unit 1106 is a device for performing data communication via a network such as the Internet, either wired or wirelessly, with devices external to the computer 1100. The communication I / F unit 1106 may be provided external to the computer 1100. When the communication I / F unit 1106 is provided external to the computer 1100, the communication I / F unit 1106 is connected to the computer 1100 via an interface such as a USB.

[0166] The display device 1107 is a device for displaying various types of information. The display device 1107 is, for example, a liquid crystal display, an organic EL (Electro-Luminescence) display, a display of a wearable device, or the like. The display device 1107 may be provided outside the computer 1100. When the display device 1107 is provided outside the computer 1100, the display device 1107 is connected to the computer 1100 via, for example, a display cable. Furthermore, when a touch panel is adopted as the input I / F unit 1104, the display device 1107 may be configured as an integral part of the input I / F unit 1104.

[0167] The above describes one embodiment of the present invention. The revision proposal system 100 uses a revision proposal method to associate pre-revision information with post-revision information and store them in memory, and can provide revision proposal information for the second contract based on the post-revision information. This allows the user to receive appropriate revision proposals for the contract.

[0168] Furthermore, the revision proposal system 100 can provide revision proposal information based on post-revision information associated with pre-revision information for an item in the first contract that is highly related to the target item in the second contract. This allows the user to receive a revision proposal based on the post-revision information related to the target item.

[0169] Furthermore, the revision suggestion system 100 can provide revision suggestion information including post-revision information to the user terminal 200. This allows the user to receive revision suggestions based on past revision results.

[0170] Furthermore, the revision suggestion system 100 can provide a plurality of pieces of revision suggestion information associated with information indicating a predetermined order, thereby enabling the revision suggestion system 100 to provide the plurality of pieces of revision suggestion information to the user terminal 200 in accordance with the predetermined order.

[0171] Furthermore, the revision proposal system 100 can provide the user terminal 200 with revision proposal information including comment information added by the user when revising the first contract. Furthermore, the revision proposal system 100 can provide the user terminal 200 with revision proposal information including at least one of the position and the contract type in the first contract. This allows the user to receive appropriate revision proposals for the contract based on contract information regarding the first contract that was revised in the past.

[0172] Furthermore, the revision suggestion system 100 can generate display data for displaying information indicating the target item and the revision suggestion information on the user terminal 200. This allows the user to refer to the revision suggestion information and make revisions to the target item.

[0173] Furthermore, the correction suggestion system 100 can generate display data for emphasizing and displaying the difference between the information indicating the target item and the correction suggestion information, thereby enabling the user to grasp the difference and more easily correct the target item.

[0174] Furthermore, the revision suggestion system 100 can swap the pre-revision information and post-revision information stored in association with each other in the memory, store them in association with each other, and provide revision suggestion information based on the swapped post-revision information, based on the user's operation via the user terminal 200. As a result, even if the revision suggestion system 100 acquires the first contract recognizing that the revisions were made in an order different from the order in which the revisions were actually made, it can swap the information to match the order in which the revisions were actually made, and as a result, it can provide appropriate revision suggestion information to the user terminal 200.

[0175] It should be noted that the present embodiment is provided to facilitate understanding of the present invention and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit thereof, and equivalents thereof are also included in the present invention.

[0176] The processes and procedures according to the present disclosure may be realized not only by the devices explicitly described in the embodiments, but also by software, hardware, or a combination thereof. Specifically, the processes and procedures described herein may be realized by implementing logic corresponding to the processes in a medium such as an integrated circuit, volatile memory, non-volatile memory, a magnetic disk, or optical storage. Furthermore, the processes and procedures described herein may be implemented as computer programs and executed by various computers, including terminal devices and server devices.

[0177] Processes and procedures described herein as being performed by a single device, software, component, and / or module may be performed by multiple devices, software, components, and / or modules. Various pieces of information described herein as being stored in a single memory or storage device may be stored in multiple memories included in a single device or in multiple memories distributed across multiple devices. Furthermore, the software and hardware described herein may be realized by integrating them into fewer components or by decomposing them into more components.

[0178] 100 Revision proposal system, 110 Memory unit, 120 Contract acquisition unit, 130 Item division unit, 140 Correspondence setting unit, 150 Correspondence extraction unit, 160 Revision proposal information generation unit, 170 Revision proposal unit, 180 Output unit, 190 Criteria generation unit, 200 User terminal, 1100 Computer, 1101 Processor, 1102 Memory, 1103 Storage device, 1104 Input I / F unit, 1105 Data I / F unit, 1106 Communication I / F unit, 1107 Display device

Claims

[Claim 1] The processor, The original information, which is the content of the items in the first contract before modification, and the revised information, which is the modified item after the modification of the original item, are stored in memory in association with each other. Based on the aforementioned revised information, we provide proposed revision information regarding proposed revisions to the subject items of the second contract, which differ from those of the first contract. How to suggest modifications.