Merging Contract Versions
Abstract
Proposed revisions to a contract can be selectively merged with provisions included in a base version of a contract to generate a merged contract. To determine whether a particular provision in the merged contract should be selected from the base contract or the proposed revision to the contract, a check can be made to determine if an event affecting a provision in the base contract has occurred. If such an event has occurred, the contract provision from the base contract can be chosen for the merged contract. Otherwise, a provision from the proposed revision to the contract can be used in the merged contract. A graphical user interface (GUI) can be used to present various contract versions.
Claims
exact text as granted — not AI-modified1 . A method comprising:
obtaining a base version of a contract including a first contract provision and a proposed revision to the contract including a second contract provision; determining whether an event affecting the first contract provision has occurred and generating an indication thereof, if the indication indicates that the event has occurred, selecting the first contract provision as a merged contract provision; if the indication indicates that the event has not occurred, selecting the second contract provision as the merged contract provision; and generating a merged contract including the merged contract provision.
2 . The method of claim 1 , further comprising:
determining if the base version of the contract includes a third contract provision; determining if the proposed revision to the contract includes a fourth contract provision; selecting the third contract provision as the merged contract provision if the proposed revision does not include the fourth contract provision; and selecting the fourth contract provision as the merged contract provision if the base version of the contract does not include the third contract provision.
3 . The method of claim 1 , further comprising:
determining if a portion of a current original charge, included in the base version of the contract, has been billed; selecting the current original charge for inclusion in the merged contract if at least a portion of the current original charge has been billed; and selecting a current revised charge from the proposed revision for inclusion in the merged contract if the at least a portion of the current original charge has not been billed.
4 . The method of claim 1 , further comprising:
determining if a portion of a current original billing plan, included in the base version of the contract, has been billed; selecting the current original billing plan for inclusion in the merged contract if at least a portion of the current original billing plan has been billed; and selecting a current revised billing plan from the proposed revision for inclusion in the merged contract if the at least a portion of the current original billing plan has not been billed.
5 . The method of claim 1 , further comprising:
determining if a portion of a current original spotline, included in the base version of the contract, has aired; selecting the current original spotline for inclusion in the merged contract if at least a portion of the current original spotline has aired; and selecting a current revised spotline from the proposed revision for inclusion in the merged contract if the at least a portion of the current original spotline has not aired.
6 . The method of claim 1 , further comprising:
determining whether the base version of the contract has been at least partially performed; and setting at least one general field of the merged contract based on the results of the determining whether the base version of the contract has been at least partially performed.
7 . The method of claim 1 , further comprising:
storing a contract history that includes the base version of the contract, the proposed revision to the contract, and the merged contract.
8 . A system comprising:
a memory configured to store a program of computer readable instructions; a processor operably coupled to the memory and configured to execute the program of instructions stored in the memory, the program of instructions comprising:
at least one instruction to obtain a base version of a contract including a first contract provision and a proposed revision to the contract including a second contract provision;
at least one instruction to determine whether an event affecting the first contract provision has occurred and generate an indication thereof,
at least one instruction to select the first contract provision as a merged contract provision if the indication indicates that the event has occurred;
at least one instruction to select the second contract provision as the merged contract provision if the indication indicates that the event has not occurred; and
at least one instruction to generate a merged contract including the merged contract provision.
9 . The system of claim 8 , wherein the program of instructions further comprises:
at least one instruction to determine if the base version of the contract includes a third contract provision; at least one instruction to determine if the proposed revision includes a fourth contract provision; at least one instruction to select the third contract provision as the merged contract provision if the proposed revision does not include the fourth contract provision; and at least one instruction to select the fourth contract provision as the merged contract provision if the base version of the contract does not include the third contract provision.
10 . The system of claim 8 , wherein the program of instructions further comprises:
at least one instruction to determine if a portion of a current original charge, included in the base version of the contract, has been billed; at least one instruction to select the current original charge for inclusion in the merged contract if at least a portion of the current original charge has been billed; and at least one instruction to select a current revised charge from the proposed revision for inclusion in the merged contract if the at least a portion of the current original charge has not been billed.
11 . The system of claim 8 , wherein the program of instructions further comprises:
at least one instruction to determine if a portion of a current original billing plan, included in the base version of the contract, has been billed; at least one instruction to select the current original billing plan for inclusion in the merged contract if at least a portion of the current original billing plan has been billed; and at least one instruction to select a current revised billing plan from the proposed revision for inclusion in the merged contract if the at least a portion of the current original billing plan has not been billed.
12 . The system of claim 8 , wherein the program of instructions further comprises:
at least one instruction to determine if a portion of a current original spotline, included in the base version of the contract, has aired; at least one instruction to select the current original spotline for inclusion in the merged contract if at least a portion of the current original spotline has aired; and at least one instruction to select a current revised spotline from the proposed revision for inclusion in the merged contract if the at least a portion of the current original spotline has not aired.
13 . The system of claim 8 , wherein the program of instructions further comprises:
at least one instruction to determine whether the base version of the contract has been at least partially performed; and at least one instruction to set at least one general field of the merged contract based on the results of the at least one instruction to determine whether the base version of the contract has been at least partially performed.
14 . The system of claim 8 , further comprising:
at least one instruction to store a contract history that includes the base version of the contract, the proposed revision to the contract, and the merged contract.
15 . A graphical user interface (GUI) comprising:
a first area displaying information associated with a base contract; a second area displaying information associated with a proposed contract; and a third area displaying information associated with a merged contract, including information selected from at least one of the base contract and the proposed contract.
16 . The GUI of claim 15 , further comprising a field in the third area capable of accepting user input related to a provision included in the merged contract.
17 . The GUI of claim 15 , further comprising a field in at least one of the first area, the second area, and the third area indicating a contract status.
18 . The GUI of claim 15 , wherein the third area displays at least one provision selected from the base contract, and at least one provision selected from the proposed contract.
19 . The GUI of claim 15 , further comprising at least one event status indicator.
20 . The GUI of claim 15 , further comprising a plurality of user selectable tabs in each of the first area, the second area, and the third area, the user selectable tabs controlling which contract provisions are displayed in each respective area.Join the waitlist — get patent alerts
Track US2011015956A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.