The invite bounced.
A hard bounce is flagged against that signer. Correct the address in place and OfferFlow rotates their link and sends again — the fields, the other signers and the document all stay as they were.
How it works
Five steps on your side.A browser and one link on theirs.
Nobody installs anything and nobody creates an account to sign. What follows is what actually happens between the PDF leaving your machine and the completed document becoming available in OfferFlow.
30-day free trial · No card required
Your side
The five steps you take
Steps one to three happen in the editor. Step four is a button. Step five runs until the last person signs.
Upload the PDF you already send
Your own file, laid out the way your business already lays it out. Nothing is rebuilt in a form designer and no template is required to send the first one.
Drop the fields where signatures belong
Signature, initials, date, text, checkbox and printed name. Drag one onto the page, resize it, mark it optional if it is, and copy a field down every page of a long agreement in one action.
Name the signers and assign each field to one of them
Up to eight people on a document, typed in or picked from saved contacts. A field belongs to exactly one signer, and a signer is only ever shown the fields addressed to them.
Send each signer their own link
Send every signer a separate link at the same time. The send itself is one transaction: either every signer's link is issued or the document stays exactly as it was.
Watch the inbox instead of your sent folder
Anything still waiting on a signature collects in one list that names who is holding it. Nudge them, fix a bad address, or void the document from there.
Their side
What the person signing actually gets
One email, one link, and a page that will not let them finish the job halfway.
An email with a link, not an attachment
The link is unique to that person. It opens the document in whatever browser they already have — desktop or phone, no app and no account.
The disclosure before the document
They acknowledge signing electronically before they reach the pages. That acknowledgement is recorded when successfully captured, with its own timestamp.
Only their own fields, in order
Fields addressed to other people are not loaded for them. On a phone they are walked to the next field still needing an answer rather than left to find each one by scrolling.
A signature they type or draw
Typed in one of three handwriting styles, or drawn with a finger or a mouse. There is nothing to print, scan or photograph.
No way to send back a half-finished document
The server rechecks every required field before it accepts a submission. A page four that nobody initialled is rejected, not filed.
At the last signature
What runs after the final signer clicks Complete
The signed PDF and certificate are built before completion; OfferFlow then sends completion emails and keeps the artifacts available in the dashboard.
The signatures are stamped into the PDF
Each signature, initial, date, typed value and checkbox mark is drawn into the page itself. The result is one flat PDF, not an original plus a layer.
That final PDF is fingerprinted
A SHA-256 hash is taken of the stamped file and stored on the document, in a database column that only accepts 64 hex characters.
The Certificate of Completion is built and stored
Every recorded event is collected into a separate PDF and uploaded before completion is committed. If the certificate cannot be produced, the whole completion is rolled back.
Completion emails and dashboard access
OfferFlow sends completion emails with download access after the final signature. The signed PDF and certificate remain available from the dashboard afterwards.
A document cannot be completed without its certificate
The certificate is generated and uploaded before the completed state is committed, not after it. When that step fails the document returns to its previous state and stays sendable — so a completed OfferFlow document always has a record behind it.
When it stalls
The four ways a send goes sideways, and what you do
None of these needs the document rebuilt. Each one has a control in the dashboard.
Nobody has opened it.
The inbox shows who has not signed. Send a reminder to the outstanding signers without disturbing the ones who are already done.
Their link has expired.
Signing links do not sit live forever. When one lapses, resending from the dashboard issues a fresh link to that signer.
The document itself is wrong.
Void it. The document stops accepting signatures, and the void is recorded as an event rather than deleting what already happened.
Every capability named on this page is listed in one place on the features page, and the documents four kinds of team actually send are on the use-case pages.
See what it costs