The reservation that took six days
A sale agreed on a Friday afternoon. The buyer is on a work trip in Germany. The seller is local, but the property is jointly owned with a spouse abroad until the following week. The reservation agreement needs four signatures.
Monday goes to finding an email address for the spouse. Tuesday the buyer signs from a hotel. Wednesday the seller signs in the office. Thursday the spouse signs. By Thursday afternoon the second interested party has put an offer on something else.
Nobody was slow. The deal lost four days to the mechanics of collecting four names on one page.
A sale is a chain, not a document
The estate agency document workflow is not one signature event. It is a sequence running for weeks. The seller appears at the start, the buyer in the middle, lenders and a notary late and briefly. The agency is the only party present at every link, which is why the chain becomes the agency's problem even when the documents are not its own.
What makes it hard is not volume. It is that the signer set changes at every step.
| Step | Who typically signs | What stalls it |
|---|---|---|
| Listing and mandate | Seller, and every co-owner | Co-owners in different countries; an inherited property with four heirs |
| Identity and AML checks | Each party individually | Documents arriving as phone photos, at different times |
| Offer or reservation | Buyer, and their spouse where the marital regime requires it | A short deadline colliding with people who are travelling |
| Promissory contract | Both sides in full, sometimes a lender | The largest signer set, and the first time everyone must align at once |
| Deposit and payment paperwork | Buyer, sometimes the agency as depositary | Waiting on the contract above before it can start |
| Deed | Notarial act, outside any e-signature workflow | Scheduling, and whatever earlier is still unresolved |
The deed is a notarial act in the major European markets and sits outside electronic signing entirely. Everything before it does not, and that is where the weeks go.
Marital regimes and co-owners are the real bottleneck
Under a community-of-property marital regime, both spouses sign. That is not an edge case in Europe, it is the default regime in several markets, and the two people are frequently not in the same place. The paper version of this problem is a courier, or a wait.
Inherited property is worse. Four siblings who inherited a flat, living in Lisbon, London, Zurich and Luxembourg, all needing to appear on the mandate. On paper that means finding a date that works for four calendars.
What helps is sending one document to four people wherever they are, each identity verified at the level the document calls for, and seeing who is still outstanding without phoning any of them.
Order is a separate decision. Sequential signing enforces each person's turn server side, so nobody signs ahead of their position even with a valid link. Parallel sends to everyone at once, and for co-owners who are peers it finishes in days rather than weeks. The choice is set when the envelope is created, and the reasoning behind it is about approval structure rather than technology.
Signature level is a per-signer decision
Form requirements for property documents are national and they vary. What a mandate requires in one country is not what it requires in the next, and that question belongs to a lawyer in that jurisdiction, not to a signing platform.
What matters operationally is that the level is set per signer when the envelope is created, and different levels can coexist in one envelope. Where one party needs a qualified signature and another does not, that is one envelope, not two processes to reconcile afterwards.
The legal floor across the EU is Article 25(1) of the eIDAS Regulation (EU) No 910/2014: "An electronic signature shall not be denied legal effect and admissibility as evidence in legal proceedings solely on the grounds that it is in an electronic form or that it does not meet the requirements for qualified electronic signatures."
Working out how that maps onto your own document set, across the countries you operate in, is worth doing once and properly.
Running this across an agency?
Tell us how your transactions flow today and we will show you where signing fits.
No spam. We use your email only to reply and to send relevant updates on this topic. Provided by WallID Smart Sign, specialists in signing and documenting transactions across Europe.
The same three documents, two hundred times a month
An agency does not sign two hundred different documents. It signs three documents two hundred times, with different names in them.
That is what templates are for: a document prepared once with fields positioned where they belong, signature, text, date, checkbox, name, datetime, and signer roles that are either fixed or placeholders filled in at the moment of use. A mandate template with a "Seller" role and a "Co-owner" role. A reservation template with "Buyer" and "Agency". Without this, someone drags signature boxes onto a PDF every time and gets it wrong occasionally.
Reservation agreements are the clearest case. A holding deposit, commonly 5,000 to 15,000 EUR in the Iberian market, takes the property off the market for a window commonly 7 to 15 days while due diligence runs. Losing two days of that window to paperwork costs the buyer a real fraction of what they paid for.
Why this has to live in the CRM
The agent lives in the CRM. That is the whole constraint.
If closing a document means leaving the CRM, opening another platform, uploading a PDF and re-typing four email addresses that already sit in the property record, adoption dies. It dies quietly, as agents go back to email attachments, and then nobody knows what state anything is in.
The European real estate CRM landscape is regional rather than dominated by a single global product. Inmovilla works with more than 3,500 real estate entities and professionals, largely in Spain. Casafari operates a CRM in the Iberian market. Propertybase serves other markets again. Those names are market context, not our integrations, partners or supported connectors.
So nobody is going to build a native connector for the CRM your network happens to run. The integration has to be small enough that your own developer can build it. It comes down to three things.
Create the envelope from the record. One call, POST /api/signing-sessions/start, authenticated with an x-api-key header. The property record already holds the parties, so the CRM sends them and nobody re-types an email address.
Receive the events back. Webhooks report signer.signed, envelope.completed, and signer.failed, a technical failure of the signature process needing an operator to help that person through it again. A ping comes from the dashboard test button. Deliveries are signed with HMAC-SHA256 and retried on failure. The CRM updates the deal from the event, so paperwork state stays visible where the deal is managed.
File the signed document. Applications are named delivery destinations for the completed file: an email address, a webhook, or an FTP location, with credentials stored encrypted. This is what lands a signed mandate in a document management system.
The endpoint, payload shapes and webhook verification are covered in wiring electronic signatures into your CRM.
When the client is sitting in front of you
Not everything happens remotely. A buyer comes into the office to sign the reservation. Someone drops in with AML paperwork.
SignOnSite is an in-person mode where a signer at a counter is routed to a station tablet and has no email address recorded at all. It fits the walk-in half of an agency's day and produces the same audit record as a remote signature. The detail is in in-person signing at a counter or tablet.
Where the buyer is abroad for the whole transaction, see buying property abroad and signing remotely.
What the file has to prove afterwards
Property transactions get questioned, sometimes years later, by someone who was not in the room.
Per signer, the audit trail records notifiedAt, firstViewedAt, lastViewedAt, linkAccessCount, signedAt, IP address, user agent, and SHA-256 hashes of the original and the signed document. A signed PDF can be looked up by its hash to find its envelope, which answers "someone has sent us this file, is it the one we issued".
Frequently asked questions
Can a reservation agreement be signed electronically? Generally yes, subject to national law on form requirements for that document. The level required varies by country. What is consistent across the EU is Article 25(1) of eIDAS: an electronic signature cannot be denied legal effect solely for being electronic.
How do we get both spouses to sign when they are in different countries? Send one envelope to both, each with their own link and their own identity verification. Neither has to travel, and neither waits for the other unless you deliberately set the signing to be sequential.
Can our real estate CRM send documents for signature automatically? Yes, through the API. Your CRM creates the envelope from the property record with one call authenticated by an API key, then receives webhook events as each party signs. Agents never open a second platform.
Can the deed be signed electronically? No. The deed is a notarial act in the major European markets and sits outside an e-signature workflow. Everything before it, mandates, reservations, promissory contracts and AML paperwork, does not sit outside it.
How do we handle a property with several co-owners? Add each co-owner as a separate signer on the same envelope, each with their own link and audit record. Parallel signing lets them all sign whenever they can, which is usually what you want when the co-owners are peers.