1
Guest clicks the signing link
When a booking is confirmed, the host sends the contract link. The link is unique per signer — we capture the click timestamp, IP address, and user-agent the moment they open it.
How signing works.
Every rental agreement on bookyour.place is signed electronically, time-stamped, IP-logged, and preserved as a legal record. Here's exactly what happens behind the scenes — and why a guest dispute doesn't become your word against theirs.
The signing flow, step by step.
2
Legal name capture
Before signing, the guest enters (or confirms) their legal name. We freeze the name + the source of the name (self-attested or ID-verified) so the signed contract always matches a real identity.
3
E-SIGN / UETA consent
The guest reads and accepts the Electronic Signature Disclosure. We record the disclosure version, their consent timestamp, and their IP. Read the disclosure
4
Signature fields completed
Guest signs in-browser or on their phone (typed or drawn). Every field signed is independently time-stamped and tied to the verified legal-name identity.
5
Host countersigns — contract preserved
Once both parties sign, the final PDF is generated with an execution watermark (contract ID + timestamp) on every page. Both sides receive a copy. The audit trail is preserved immutably on the platform.
What we capture on every signature.
Timestamp
Server-side UTC timestamp on every consent, every field signed, every signing event.
IP address + user-agent
Captured at consent and at each signature. Confirms the signing device and session.
Per-signer unique link
Signing links are unique per signer and delivered only to their email address — only someone with access to that inbox can open the link.
Legal name + source
Legal name frozen at signing time, with a recorded source (self-attested or ID-verified).
ESIGN/UETA consent record
Disclosure version + consent timestamp + IP stored — what the signer agreed to, when, from where.
Contract ID anchor
Every page of the signed PDF carries a watermark footer with the unique contract UUID + execution timestamp. The audit anchor.
What the audit trail looks like.
Example data. Every signed contract on the platform produces a chronological event log like this — visible on the in-app audit-trail screen.
| Event | Signer | Timestamp (UTC) | IP |
|---|---|---|---|
| Invitation opened | Guest — Jane R. | 2026-06-14 15:02:17 | 72.14.x.x |
| Legal name confirmed | Guest — Jane R. | 2026-06-14 15:03:41 | 72.14.x.x |
| ESIGN consent recorded (v1) | Guest — Jane R. | 2026-06-14 15:04:09 | 72.14.x.x |
| Signature 1/2 completed | Guest — Jane R. | 2026-06-14 15:05:23 | 72.14.x.x |
| Host countersignature | Host — Mike D. | 2026-06-14 17:11:05 | 68.84.x.x |
| Contract executed — PDF generated | — | 2026-06-14 17:11:06 | — |
Both parties can download the final PDF with the audit anchor (contract UUID + execution timestamp) watermarked on every page.
Common questions.
How do I know my guest actually signed?
The audit trail shows you exactly when they consented to ESIGN, when each field was signed, and the IP + device they used. The PDF they receive and the PDF you receive are the same file, anchored by the same contract UUID in the watermark footer. A guest can't claim "I didn't sign" when there's a time-stamped consent record tied to their email's unique signing link.
What if there's a dispute later?
You have a fully-executed PDF with both signatures, both legal names, the disclosure version consented to, and a watermark anchor (contract UUID + execution timestamp) on every page. The full event log — per-signature timestamps, IPs, consent records — is visible on the in-app audit-trail screen for every signed contract in your account. External guests (off-platform signers without accounts) keep the signed PDF with watermark anchor; they can also reach out to us to retrieve their signing record if needed. We don't arbitrate disputes ourselves — the agreement is between you and your guest — but we give you the documentation you'd need to defend it.
Is this legally binding?
Yes. Contracts signed through our flow meet the ESIGN Act (15 U.S.C. § 7001) and state UETA requirements: (1) the signer consented to electronic signing, (2) the system can accurately reproduce the signed record, (3) we retain the audit trail. We're not legal advisors — if your specific situation needs it, consult a lawyer — but the mechanics meet the bar.
How is this different from DocuSign?
Same legal standing; different product shape. DocuSign is a general-purpose e-sign tool you configure for every document. Ours is vacation-rental-specific: the guest's legal name and booking dates flow into a rental-agreement template automatically, the contract is attached to the booking record, and the signing link ties to the guest's platform identity. It's the difference between a Swiss Army knife and a purpose-built tool.
Can the guest reject the contract?
Yes. Signing is consent — they can decline the ESIGN disclosure, refuse to complete signature fields, or abandon the flow entirely. If they do, no contract is executed and the booking stays in pending state. You'd see "declined" in the audit log rather than a signed PDF.
Ready to send your first contract?
Founding hosts get 1–3 years free. List your property, upload a template, send it to your next guest.