Overview
There are three related actions:
Action | Use it when | Relationship recorded |
Duplicate contract | You want an independent contract prefilled from an existing one | None |
Amend contract | A customer with an ongoing contract needs an additional key | The new contract is shown as an amendment of the original |
Link contract | Both contracts already exist and should be shown together | A plain link or a directional amendment |
The form and information copied depend on the source contract type. Always review the prefilled values before saving.
Before you begin
For duplication and amendment:
You need permission to add contracts.
You must be able to view the source contract.
For amendment:
The source must be an ongoing handover contract.
A mechanical handover is amendable after the key has been fetched.
An ongoing iLOQ handover can be amendable while it is shown as waiting for the customer.
Return contracts cannot be amended.
For linking and unlinking:
You need permission to edit contracts.
Both existing contracts must be within your access.
How to amend an ongoing contract
Use amendment when a customer needs an additional key and the new contract should retain a visible relationship to the original.
Open the ongoing contract, or find it in the contract list.
Select Amend contract.
Review the copied contract context, such as contacts, free text, attachments, access schedule, and relevant iLOQ handover details. The amendment uses the original contract’s end date.
Add the new key or keys. Specific keys, key quantity, and access rights are not copied into an amendment.
Adjust any values that have changed.
Save the contract.
The new contract shows the source under Original contract. The source shows the new contract under Amendments.
How to duplicate a contract
Use duplication when you want a new independent contract that starts from existing information.
Open the source contract, or find it in the contract list.
Select Duplicate contract.
Review the prefilled form.
Select or confirm the keys required by that form.
Adjust any other values and save.
Key handling varies by flow:
A normal mechanical handover duplicate starts without selected keys; select the keys for the new contract.
An iLOQ handover duplicate can copy key quantity and access-right context, but the system assigns keys for the new contract rather than copying key IDs.
A return/receive duplicate can preselect the keys relevant to that return flow.
A duplicate has no link to the source. Attachments are copied as independent files; editing or removing a file on one contract does not change the other.
How to link existing contracts
Open one of the contracts.
Select Link contract.
Enter the other contract’s ID in Target contract ID.
Choose the Link type:
Link creates a general, non-directional connection.
Amendment makes the contract you are currently viewing an amendment of the target.
Confirm the link.
For an amendment link, start from the amendment and select the original as the target. Starting from the original reverses the relationship.
How to unlink contracts
Open either linked contract.
Find the related contract and select the unlink action.
Confirm Unlink contract?.
The relationship disappears from both contract views. The event history retains a record of the change.
What appears on related contracts
Linked contracts shows general links without direction.
Original contract appears on an amendment and points to its source.
Amendments appears on an original and lists its amendments.
Related entries are clickable. A contract outside your access may be represented only by a count. A deleted target is shown as a deleted-contract entry so the surviving contract retains the relationship record.
Important behavior and limitations
Duplicate and amend use the normal contract-creation rules. Prefilled agreements and access schedules may change when selected keys place the new contract in another organization unit.
Completed verification or signature data is never copied. A required verification type may be preselected, but the new contract requires its own verification.
Amendment copies contract context but not the original keys. Add the new key explicitly.
Duplication creates independent customer and attachment data. Later changes or anonymization on one contract do not automatically affect the other.
A contract cannot link to itself or to a contract outside the user’s access.
Troubleshooting
Amend contract is missing or disabled
Check that the source is an ongoing handover contract and that you have permission to add contracts. Return contracts and ended contracts cannot be amended. A mechanical handover that is still waiting for pickup is not yet amendable.
The amendment relationship is reversed
Unlink the contracts, open the amendment, and create the link again with the original as the target and Amendment as the type.
The duplicate opened without keys
This is expected for a normal mechanical handover duplicate. The feature copies contract context, but you select the keys for the new contract. Other contract flows handle keys differently, so review the form before saving.
Link contract was rejected
Check the target contract ID, confirm both contracts are within your access, confirm the target is not the current contract, and verify that the pair is not already linked.
A prefilled agreement or schedule disappeared
Selecting keys can change the organization unit used for the new contract. LivionKey Register recalculates unit-specific agreements and access-schedule availability so unsupported source settings are not carried into the new unit.
Frequently asked questions
Is a duplicate linked to its source?
No. A duplicate is independent. Use Amend contract when the new contract should appear under the original’s amendments, or use Link contract afterward.
Are attachments shared between the two contracts?
No. Copied attachments are independent files.
Can I amend a return contract?
No. Amendment represents an additional handover from an ongoing contract, while a return contract records keys coming back.
Need help?
Contact Livion Support at [email protected]. Include the organization, source and new contract IDs, the action used, approximate timestamp and timezone, and the visible error message. Do not send signatures, identity-verification data, or credentials.