What to Save After an Agreement Is Signed

Keep the agreement and the evidence around it

Once an agreement is complete, save the final signed file, its completion evidence and enough context to identify the transaction. Keep them together in a location the responsible team can access after a staff member changes role or leaves.

The PDF records the terms and signatures. The completion record helps explain the signing process. Neither replaces the other, and a screenshot of a signature is a poor substitute for the original files.

What belongs in the record?

Download the completed record from Sign.Plus

In Documents, find the request under Completed. Download the signed document, then use its menu to download the certificate. The official instructions distinguish downloading the signed document from retrieving its completion certificate.

A General settings option can merge a certificate with the signed document. Check the export you actually received instead of assuming the certificate is always attached or always separate.

Open the files before archiving them. Confirm the parties, document version and page count. A request waiting for one more person is not ready to file as the completed agreement. If the status does not match expectations, first check which signing action remains outstanding.

Preserve the original before making working copies

Store the downloaded original unchanged. Use a separately named copy for internal comments or a redacted version for wider circulation. Printing and scanning or exporting through another application can produce a different file with different evidence.

When the terms change, retain the earlier agreement alongside the amendment or replacement. Follow a clear correction and re-signing process rather than overwriting the record that the parties originally signed.

For a property manager in Arizona, a useful folder contains the completed lease, its completion certificate and the later signed amendment. Naming the amendment clearly is more helpful than replacing the lease file with a document called “final-final.pdf”.

Choose retention for the record, not the software status

Start with the document's business purpose and applicable legal or regulatory requirements. A tax record, an employment agreement and a lease may need different schedules. Account storage, backups and a legal retention obligation are separate questions.

For covered US transactions, ESIGN's record-retention provisions address faithful retention, required access and later reproduction when a record must be kept. They do not give every signed agreement one universal retention period.

Record who may access the files, when the period starts and who can authorize disposal. If a dispute, investigation or other preservation requirement arises, involve the responsible legal or records team before deleting anything.

Make the archive usable without the sender

• Test retrieval: can an authorized colleague find and open both files?
• Keep the association: use a consistent transaction reference for the agreement and certificate.
• Limit access: completed agreements can contain personal and commercial information.
• Plan continuity: document who maintains access when an account owner or employee changes.

For an Enterprise archive, documented customer-owned storage options include an API-built archive and a custom S3-compatible delivery arrangement. Confirm setup and coverage for your account. Choosing an archive destination still leaves your organization responsible for its access and retention policy.