Insights · east-estate.com
Collecting documents from clients securely, beyond email
In short: The secure way to collect client documents is a dedicated upload route, either a client portal with individual logins or a secure upload link tied to a specific request, served over HTTPS, with access limited to the staff who need it and a set retention period. Email works, but files get forwarded, duplicated and lost in personal inboxes.
Secure document collection means receiving files from clients through a channel where you control who can see them, where they are stored and how long they are kept. For property and service businesses this covers identity documents, references, contracts, certificates, photos of damage and signed forms. Most firms still rely on email, and for low-risk files that may be acceptable. For anything personal or financial, there are better options.
Why email attachments are a weak default
Email was not designed as a document store. The problems are practical rather than theoretical:
- Copies multiply. One attachment ends up in the sender's sent folder, the recipient's inbox, every forward and every reply-all.
- Files go missing. When the person who received it is on leave or leaves the firm, the document sits in their mailbox.
- Mistakes are permanent. A file sent to the wrong address cannot be recalled in any reliable way.
- There is no tidy deletion. Removing a document at the end of its retention period means finding every copy.
- Clients send what they have, not what you need. Without a structured request, you receive blurry photos, wrong pages or the same file three times.
The alternatives compared
| Method | How it works | Best for | Watch out for |
|---|---|---|---|
| Client attaches files to a message | Low-risk, occasional documents | Copies, misdirected mail, no clear retention | |
| Secure upload link | A link tied to one request where the client uploads files | One-off requests from many clients | Links forwarded to others; set expiry dates |
| Upload form on your site | A form with file fields that routes to the right team | Standard requests such as job photos | Size limits and where files land afterwards |
| Client portal | Each client logs in to a private area to upload and download | Ongoing relationships with regular exchanges | Needs onboarding; clients must manage a password |
What makes a collection route secure
Whatever tool you choose, check it against these points:
- Encrypted in transit. Uploads should happen over HTTPS, so files cannot be read as they travel.
- Restricted access. Only the staff who need a client's documents should see them. Shared team logins defeat this.
- Individual accounts. In a portal, each client and each employee has their own login, so you know who did what.
- Clear storage location. You should know where files end up and who administers that system.
- Retention rules. Decide how long each type of document is kept and delete it afterwards.
- Revocable access. You can disable an account or remove a document when a relationship ends.
If you collect personal data and are subject to the GDPR or a similar law, two principles apply directly: collect only the data you need for the purpose (data minimisation) and protect it with appropriate technical and organisational measures (security of processing, Article 32).
Designing the request so clients get it right first time
Security is half the job. The other half is getting the right documents without three rounds of follow-up. A good request:
- Lists each document by name, with a one-line explanation of what is acceptable, for example "proof of address dated within the last three months".
- States accepted formats and whether photos from a phone are fine.
- Shows which items are already received and which are outstanding.
- Gives a deadline and a contact for questions.
- Explains briefly why each document is needed, which reduces hesitation.
Pair this with an automated chaser that lists only the missing items. Our guide to reminders and follow-ups covers how often to send them.
A practical rollout
- List the documents you collect regularly and rate each as low, medium or high sensitivity.
- Move high-sensitivity items, such as identity and financial documents, off email first.
- Write a standard request for each common job type.
- Choose the route: upload links for one-off clients, a portal for ongoing ones.
- Tell clients clearly that you no longer want sensitive documents by email, and why.
- Set retention periods and a monthly reminder to delete what has expired.
Trade-offs
A portal asks clients to create a login, which some will resist for a single transaction. Upload links are easier but can be forwarded, so set expiry dates. No tool protects you from a client who photographs a document and also emails it "just in case"; clear instructions matter as much as technology. And you remain responsible for deciding what to collect and how long to keep it.
How we help
Digital Office Premium includes secure client and employee portals with individual accounts and document sharing, plus OCR and PDF processing for scanned files. Structured request and chaser flows can be added as automations, quoted in writing.
Questions and answers
Is a password-protected PDF sent by email secure enough?
It is better than an unprotected attachment, but the password is often sent in the same thread or a second email, and copies still multiply. For sensitive documents a dedicated upload route is the stronger option.
Should clients upload documents during booking?
Usually not. Keep the booking form short and send a separate document request afterwards, through a secure link or portal, listing exactly what is needed.
How long should we keep client documents?
Only as long as you need them for the purpose and any legal or regulatory requirement in your country. Set a retention period per document type and delete files once it has passed.