When to use packets and document merging

1. Only one contract will be created in the SpotDraft repository.
2. This feature is available only from the SpotDraft app. It cannot be used from related integrations such as Salesforce, Hubspot, etc.

Group related contracts together for a seamless review experience using SpotDraft Contract Packets. This powerful feature allows you to manage multiple contracts as a single unit, improving visibility and streamlining internal approval processes. Read more.

1. Each uploaded document will be created as individual contracts in the SpotDraft repository. They can have their own lifecycle.
2. This does not merge the uploaded documents.
3. This view is available only to the creator party.
4. This feature is available only from the SpotDraft app. It cannot be used from related integrations such as Salesforce, Hubspot, etc.

In many instances, contracts sent out for signatures need to include supporting documents, which, although not subject to negotiation, must be attached for reference. These supporting documents, such as annexures, remain unchanged throughout the negotiation process. While the main contract undergoes redlining and review, the annexures are separately referred to but ultimately need to be included in the final contract for ease of reference. Read more.

1. This is usually used to upload supporting or reference documents. It is NOT possible to use this feature to merge one contract into another.
2. This feature is available only from the SpotDraft app. It cannot be used from related integrations such as Salesforce, Hubspot, etc.

Append one or more contracts to another contract template document and send them as one single document to the counterparty for review or signature. You can add an already existing contract or create a new contract using the new contract workflow, to be appended to the parent contract. Read more.

1. The related contract can be merged into the parent template in any pre-defined location. The creator of the contract can't decide the position where the related contract will be merged.
2. The related/child contract being merged into the parent template will continue to exist independently in the repository.