Skip to content
Property and leasing teams

Mandates, leases and renewals — signed on a phone, without an app.

Send the document as a link rather than an attachment. It opens in the browser your counterparty already has, walks them field by field to the end, and will not let them finish with a required field still empty.

30-day free trial · No card required

What you send

The documents a property file collects

Standard, repeated paperwork — the kind where the record matters as much as the signature.

Mandate or listing agreement

Signature, date and printed name for each owner. Each owner gets a separate link and sees only the fields assigned to them.

Lease agreement

Initials wherever your template calls for them, signatures at the end. Nothing can be submitted with a required field empty.

Renewal and addendum

The short document sent against an existing lease, built from a saved template and addressed from saved contacts.

Tenant application and consent forms

Text, date and checkbox fields the applicant types in the browser, so nothing arrives handwritten and unreadable.

Condition report sign-off

Sent at check-in and again at check-out, each one producing its own dated record.

Offer and acceptance

Only where your jurisdiction and your firm accept a standard electronic signature for that instrument. Check the requirement before you send.

Before OfferFlow

Why the attachment version leaves gaps in the file

The problem is rarely the signature itself. It is what the file can show afterwards.

A counterparty on a phone cannot sign a PDF attachment without an app.

The signing link opens in the browser they already have. Signatures are typed, or drawn with a finger.

Pages come back initialed in some places and not others.

Required fields have to be complete before the signer can finish, so partial returns do not happen.

Nobody can say exactly when the tenant received it.

Sending, opening, viewing, consent and signing events are recorded with timestamps when successfully captured.

The record sits in the mailbox of whoever was handling it that week.

The signed PDF and the Certificate of Completion stay attached to the document in the dashboard.

In OfferFlow

How a lease gets signed

A one-page addendum and a forty-page lease go out the same way.

01

Place the fields on your own lease template

Signature, initials, date, printed name, text and checkbox fields, each assigned to a named party. A party only sees their own.

02

Send each party their own link

Everyone receives a separate signing link at the same time, and the inbox shows which parties are still outstanding.

03

Track it, and fix it when the address is wrong

Signing links expire rather than sitting in an inbox forever. When one does, resend it — and if an invite hard-bounces, that signer is flagged so you can fix the address and send it again without starting the document over.

Proof and evidence

What the completed file holds

Evidence, not assurance. What a completed document can show, stated exactly and no wider.

  1. A Certificate of Completion for the file, listing recorded events with timestamps, actor context and request information where captured.

  2. A SHA-256 fingerprint of the final PDF, recorded at completion, so a later copy can be checked against it.

  3. Audit events that cannot be edited or deleted once written, by anyone, including the account owner.

  4. Both PDFs stay downloadable from the dashboard for as long as the document is there.

What OfferFlow does not do

OfferFlow produces standard electronic signatures only. It does not verify identity documents, witness a signature, notarize anything, or issue qualified or PKI-backed signatures, and it makes no claim about whether a given instrument is validly executed in your jurisdiction. Deeds, and any document your law requires to be witnessed or notarized, are outside what it can do. Check the requirement for each document type before you send it.

View trust details
Other use cases

The same workflow, different paperwork

Three more audiences sending a short list of documents that each need a record afterwards.

See all four use cases

Consultants

Keep proposals, scopes of work, MSAs, and renewals moving without turning contract signing into a side project.

Consultants use case

Agencies

Send retainers, campaign scopes, approvals, and change requests as one link per person, instead of a thread with three attached versions.

Agencies use case

Service businesses

Handle onboarding packs, work authorizations, service agreements, and approval forms without a printer or a scanner in the loop.

Service businesses use case
Free for 30 days

Send the next mandate as a link.