Amendment processes with Conga typically rely on a new record type for the agreement object called amendment, and a parent-child type relationship between this record type and the record type for which the amendment is being created. A quick action or flow button can be added to the parent record type to generate an amendment record.

Most Legal processes will not regenerate the contract in its entirety, but will only add the clause which is being amended. If the legal team wishes to always start from a standard version of the clause being amended, they can rely on the Select Clauses list button on the managed clause related list where they can select a few clauses to generate on the amendment. If they want to start from the custom language saved in the parent record's managed clause related list, the best route is to regenerate the entire contract and add a task to the record using Conga Orchestrate to notify legal team members to eliminate all language except for the clause(s) being amended.

Keep in mind that any amendment process should preserve the original agreement record as best as possible. This means that it is best to duplicate relevant fields and clauses at the amendment record level so that modifications can be tracked separately from the original agreement. This creates a highly reportable contract family where legal is able to see the terms originally agreed to as they relate to later modifications.