When the last signature lands, the executed document comes back to Pipeline on its own. Here is where it goes and what rides along with it.
Introduction
The part of e-signing that used to eat the most time was the end of it — downloading the executed file from one system and uploading it into another, hoping you named it the same way you named the last one.
Pipeline eSign closes that loop for you. When the final signature is in, the signed document comes back into Pipeline by itself. There's nothing to download and nothing to re-upload.
Where it lands depends on where the request started. That's the one thing worth knowing up front, because it decides whether the document is already pointed at a transaction or waiting for you to decide.
How It Works
One signed file, two return paths, and a certification riding along with it.
If You Started From a Transaction
The signed document returns to Unassigned, already pre-assigned to the transaction it came from. It's connected and ready — you still assign it to finish putting it on the transaction with the right name and permission category.
If You Started From Reference or the eSign Page
The signed document stays with your sent requests, tracked entirely outside the transaction workflow. Nothing lands in Unassigned until you copy it there, so you keep full control over when — and whether — it ever joins a transaction.
What Rides Along
Pipeline appends a Certification of Authenticity and an Event Log to the end of the signed document. The event log records the signing events, which is what an audit or a compliance review asks for.
Everyone Gets a Copy
Pipeline emails a final copy to you and to every recipient on the request, so your signers have their own record without asking you for it.
One Packet Comes Back as One Document
Send five documents in one request and five documents come back as one file, in the order you sent them. That's the packet as it was signed. Break it apart afterwards if you want them filed separately.
Split a Very Long Document First
You can still download a signed file long enough to run past Pipeline's preview and break-apart tools, but you can't preview or split it in place. For contracts that long, split them outside Pipeline before you send.
Copy a Signed Doc to Unassigned
Move a completed signed document out of your requests list and into Unassigned, where you can put it on a transaction.
Who Can Do This: Anyone whose company is subscribed to Pipeline eSign can copy their own completed documents. Admins can also copy completed documents from requests across the company, within what they have permission to see.
To copy a signed doc to Unassigned:
- Click [eSign] from the top menu to view your sent requests.
- Find the completed request.
- Click the gear next to it, then select [Copy to Unassigned].
The signed document appears in Unassigned, ready to assign. Requests that started from a transaction are already there — you only need this for the ones sent from Reference or the eSign page.
What to Do With the Doc Once It's Back
From here the signed document is an ordinary Pipeline document, and the rest of what you'd do with it is documented where documents live.
Unassigned Docs List
Unassigned is the holding queue every emailed doc passes through on its way to a transaction — open it to see what arrived, who added it, and what it came in with.
Doc Assignment
A doc has landed in Unassigned and now it needs a home. Assigning is the step that puts it on the right transaction, with the right name and the right permission category.
See Doc Assignment
Doc Break Apart
One scanned stack, many documents. Break a doc apart to split it into separate docs, pull out the pages you need, and name each one as you go.
See Doc Break Apart
Signed Docs Return FAQ
The executed document returns to Pipeline on its own, with a certification and event log attached. Answers to the common questions about where it lands, what's in it, and what to do next.