Releasing a Survey Report Through a Client Portal: Common Mistakes With Payment and Access
Short answer: The main mistakes are releasing the report before the payment position is settled, emailing a permanent link that anyone can forward, letting several versions circulate, ignoring who else is entitled to read the report, and keeping reports available forever without a plan. A client portal fixes these only if its rules are decided first: what unlocks a report, who may open it, which version is current and how long access lasts. The sections below go through each mistake and the fix.
This is general guidance on systems. Your terms of engagement, professional body rules and local law decide who may rely on a report and when you may withhold it, so check those with your own adviser.
Mistake 1: The gate is a feeling, not a rule
Many firms say "reports are released on payment" but implement it by someone remembering to send the PDF. Sometimes it is sent early to a friendly client; sometimes it is held up when payment arrived days ago.
Fix. Write the rule in the engagement terms and mirror it in the system. A typical set of states is:
- Draft (internal only).
- Reviewed and approved by the signing surveyor.
- Awaiting release (payment or other condition outstanding).
- Released to client.
- Superseded or withdrawn.
Only a person with the signing role may move a report to approved. The system moves it to released when the condition is met, or when a named person overrides it and records a reason. An override log is more useful than a rule with no exceptions, because exceptions always occur.
Mistake 2: Treating "paid" as one thing
A card payment, a bank transfer that has not cleared, a part payment and an invoice on account are not the same. A portal that unlocks the report on "payment initiated" can release a report for a payment that later fails.
Fix. Decide in advance which payment states unlock which reports. For example: card payments release on confirmed success, bank transfers release when matched to the invoice, and corporate clients on account terms release on approval of the account. Where payment is handled by a processor, use its confirmed event rather than the customer's return to your site. Say in the engagement letter which payment states count.
Mistake 3: The permanent link in an email
A report attached or linked in an email is easily forwarded to a lender, a seller's agent or a neighbour. That is sometimes acceptable and sometimes not.
Fix. Deliver through a portal sign-in or a link that expires, and say what each means. Where sign-in is used, require proper authentication; the MDN overview of HTTP authentication covers the underlying mechanisms, though a typical portal uses an account system rather than raw server prompts. When serving files, set caching headers so that sensitive documents are not stored by shared devices or proxies unnecessarily; the Cache-Control reference explains the "no-store" and "private" directives.
If you choose expiring links, send a fresh link on request and record each request. A client who lost the file a year later should not have to start a new job.
Mistake 4: Several versions in circulation
A common scenario (illustrative): a report is sent, the client notices a wrong lot number, a corrected version is issued, and then the lender holds the first one. Nobody can say which is right.
Fix.
- Give every report a reference and a version number visible on every page.
- Keep the earlier version in the portal but label it "Superseded by version 2, issued on a date" in a clear banner, and make the current version the default download.
- Record why the version changed in a short note that you can show if asked.
- Never overwrite a released file with a corrected one under the same name.
Mistake 5: Forgetting the other readers
Reports are often read by people who are not the client: a lender, a solicitor or conveyancer, a body corporate, a co-owner. If the portal only has one login per job, the client will share their password, which is worse than a formal arrangement.
Fix. Offer named additional recipients, added by the client or by you with the client's consent. Give each a role (view only, view and download) and keep a record of who opened what. State in the report and portal who may rely on it. That statement belongs in your terms and professional rules, not in the portal's code.
Mistake 6: A report with no expiry plan
Keeping reports forever sounds safe but creates risk and cost. Deleting them early is risky too, because you may need them for a dispute or insurance purposes.
Fix. Decide your retention period according to your professional body and insurer's requirements, put it in your privacy notice and implement it as a setting. Client access can end sooner than your own retention. For example, the client may have 12 months of download access while you hold the file longer in an archive. Tell clients that they should keep their own copy.
Mistake 7: Poor error handling at the moment of release
Release day is when clients are most impatient. Mistakes here are visible: a message saying "report not found", a link that opens a blank page, a notification sent before the file is ready.
Fix. Test the full path with a dummy job before launch:
- Approve a sample report, trigger release and confirm the email arrives with a working link.
- Open the link on a phone and in an email app's built-in browser, which behaves differently from a full browser.
- Check what a client sees when the report is not yet released. A calm "Your report is being finalised and will be available once your invoice is settled" avoids anxiety.
- Try an expired link and a wrong login to confirm the error message is helpful and discloses nothing about other jobs.
Mistake 8: Releasing before the right person has signed off
Automation can accidentally release a report as soon as the invoice is paid, even if the surveyor has not approved it. That might mean releasing a draft.
Fix. Make approval a prerequisite, not an alternative. The release condition should be "approved AND payment condition met", and the system should not offer a release button on a draft. Show staff a clear status on the job screen so they never have to guess.
A one-page release checklist
- [ ] Report approved by the signing surveyor.
- [ ] Reference and version number on every page.
- [ ] Payment state matches the rule in the engagement terms.
- [ ] Recipients listed, roles assigned.
- [ ] Download link or sign-in tested on a phone.
- [ ] Notification text reviewed.
- [ ] Retention date set.
- [ ] Any override recorded with a reason.
FAQ
Can we email the report as well as using the portal?
You can, but it defeats the purpose of access control and version labelling. If clients insist, send a link to the portal and not the file itself.
Should the client be able to download or only view?
Allow download for the client, because they will need to give copies to others. Restrict only where your terms and professional rules require it.
What if the client disputes the fee after release?
That is a contract matter. Keep the override and release logs so you can show exactly what was released and when, and seek advice from your professional body or legal adviser.
How long should a link stay valid?
Choose a period that matches the way clients work, often seven to thirty days, with an easy way to request a new link.
If you are setting up report delivery for your practice, describe your current process to us and we will propose a portal flow with these controls built in.