What you will learn
- What belongs in a deliverables portal, and what stays internal
- How revision history prevents draft-versus-final confusion
- How access control works for clients, lawyers, and lenders
- How delivery, download, and acknowledgement are recorded
- The retention and security questions to settle before launch
What the project is
Delivering survey work by email creates a familiar mess: large attachments bounce, drafts circulate as finals, and nobody can prove which version the client received. A portal fixes the delivery end of the job. Each job gets a delivery page with its final documents, a revision history, and a record of who downloaded what and when.
The portal is client-facing, but it is driven by the office workflow. When a plat is signed and a report is finalised, the office publishes them to the portal, the client is notified, and the delivery is logged. Drafts stay in the job system and never reach the portal until they are approved for release.
Core features
Job delivery pages are the core: one page per job, listing final documents with version, date, and a download link. Revision history shows every published version, with superseded versions marked clearly but still available, because lawyers and lenders often need to see what changed. Access control lets the firm share a job with the client, their lawyer, and their lender separately, with each party seeing only their jobs.
- Job delivery pages with final plats, reports, and supporting files
- Revision history with superseded versions marked but retained
- Separate access for client, lawyer, lender, and other parties
- Download log recording who accessed what and when
- Expiry and access controls for sensitive documents
- Notifications when new deliverables are published
How it is built
Build the publishing step first, because the portal is only as reliable as the office process that feeds it. If publishing is a manual chore, it will be skipped under pressure, and clients will fall back to email. A publish action inside the job workflow, with a final check, is the practical design.
- Define the deliverable set per job type: plat, report, and supporting files.
- Build job delivery pages with revision history and access control.
- Add the publish step inside the job workflow, with an approval check.
- Add notifications, download logging, and expiry controls.
- Test with real clients, including lawyers and lenders, before firm-wide rollout.
Technology considerations
Security needs proportionate thinking. Survey deliverables include property details and legal descriptions, so access should be per job and per party, with links that expire and cannot be forwarded into open access. At the same time, the portal must stay simple for clients who use it once: a emailed secure link with no account setup is often the right balance, with accounts for repeat parties.
File handling matters at scale. Plats and reports are usually modest files, but supporting imagery and scan data can be large, so the portal should handle large files with resumable uploads and clear size guidance, rather than failing silently.
Challenges to plan for
The main challenge is draft leakage: a draft plat that reaches a client can be relied on, quoted, or filed before it is final. The publishing gate must be a real approval, not a checkbox that anyone can tick, and the portal should watermark or label any document that is not final, if such documents are ever shared at all.
- Drafts reaching clients before sign-off, and being treated as final
- Forwarded links giving unintended parties access to sensitive documents
- Clients who miss notifications and keep asking the office for files by email
- Old deliverables that stay accessible after a job closes, without a retention rule
Who it is for, and its limits
This portal fits survey firms delivering plats and reports to clients, lawyers, lenders, and developers on a regular basis, especially firms where email delivery already causes version confusion. Small firms with a few jobs a month may manage with secure file links and a clear naming convention instead.
A portal does not make a plat final; only the surveyor's sign-off does. The portal's job is to deliver the signed version clearly and to keep the history straight. Costs and timelines vary with access and integration scope, so confirm with a quote before budgeting.
Frequently asked questions
How is a portal better than emailing plats?
Email attachments get lost, forwarded, and confused with drafts. A portal gives each job one delivery page with final documents, a revision history, and a download log, so everyone works from the same version.
Can lawyers and lenders access the same job?
Yes, with separate access. The firm grants each party access to their jobs only, and the download log records who accessed what.
What stops a draft from being delivered by mistake?
A publishing gate inside the job workflow. Documents reach the portal only after approval for release, and drafts stay in the internal job system.
What happens to old deliverables?
They remain available under the firm's retention rules, with superseded versions marked as such, so the history of what was delivered stays traceable.
Do clients need an account?
Not necessarily. A secure link works for one-off clients, while accounts suit repeat parties like lawyers and developers. The firm can offer both.