Document Management with Approvals for Emailed and Posted PDFs
Legal services team
In short
How can a legal team file, approve and chase closing documents automatically?
When closing documents arrive as PDFs by email and by post, each one has to be found, checked, approved, completed, sent and chased by hand. A missed reply or an unsigned page stalls a closing. We built a SharePoint and Power Automate process that files each document, routes it to a paralegal, produces the outgoing PDF and keeps reminding until the reply arrives.
Results in numbers
- saved per document
- 15 min
- saved per 30 properties
- 20 hrs
At a glance
- PDFs from email and post filed in one structure
- Word template to PDF to email with no retyping
- Reminders stop when the other lawyer replies
The client
The solution serves a legal services team of four paralegals handling property transfer document sets, with an outside lawyer and a government legal department in the signing chain. It runs on Microsoft 365 and SharePoint.
What it was costing them
- Manual filing: PDFs from email and post are saved and named by hand into folders.
- Retyping: outgoing documents are completed by copying details into Word, then converted to PDF.
- Chasing: nobody is reminded when the other side's lawyer has not returned a signed document.
- Hidden status: whether a document is approved, sent, signed or billed is known only to whoever handled it.
What we built
We built a SharePoint site with a folder structure per property, a paralegal approval step and Power Automate flows for document generation, sending and reminders.
- One home for every document: a main folder with subfolders per property, filled from email and scanned post.
- Approval in one click: a paralegal picks up an item and approves with a yes or no checkbox that starts the flow.
- No retyping: a Word template is filled from SharePoint list data, including lookups from other lists, then converted to PDF.
- Consistent sending: the PDF goes by email to the other party's lawyer, and a copy is stored with the record.
- Reminders that stop on time: a received yes or no flag halts reminders once the document returns.
- A visible status trail: checkboxes for sent for final signature, then billing, then Completed.
- A choice of front end: a model-driven app with Power Apps dashboards, or SharePoint with a canvas form and Power BI dashboards.
- Licensing kept small: a service account holds the premium licences, not every user.
Results
- The solution is sized for small volumes, about 5 to 30 properties with a few documents each, and four paralegal approvers.
- Two licensing routes were compared: a model-driven app with Power Apps dashboards, and SharePoint with a canvas form and Power BI.
- Result: template population saves 15 minutes per outgoing document, about 20 hours across a full run of 30 properties with three documents each.
The risk most teams miss
At month three the risk is a premium dependency and one owner. Encodian or other premium connectors need a funded service account, and if one person owns the flows the process stops when they leave. The approval checkbox also needs a rule for who may approve what. The solution uses a service account, one folder convention and a clear status column, so nothing relies on memory. The external phase needs its own security review.
What we would add today
Improvements we would add on top of what is live.
- Use Azure Document Intelligence or AI Builder document processing to read incoming PDFs, classify the document type and fill the record, so intake needs no typing.
- Move to Dataverse with row level security by matter, so paralegals see only their files.
- Add an e-signature step with a signing connector for witnessed signatures, replacing posted pages where the parties allow it.
- Deploy the flows in a solution with connection references and a service principal, and add a Copilot Studio agent that lists documents waiting on the other lawyer.
Technology
SharePoint Online, Power Automate, Power Apps (model-driven or canvas), Word templates, Encodian (considered), Power BI, Microsoft 365.
Tell us how documents reach your team and who has to sign off, and we will tell you how to file, approve and send them without retyping.
Products and capabilities
- SharePoint
- Power Automate
- Power Apps
- document management
- approval workflow
- PDF generation
- Word templates
The service behind this work
Power Platform development
Related use cases
Operations and field workPower Automate Desktop Response to a Municipal RPA Market Consultation
A municipality that wants to buy robotic process automation must choose between tools and decide how to tender them, with little time. The municipality ran a request for information to learn what the market offers. We answered it for Power Automate Desktop.
Contractor Management App Rebuilt in Microsoft Power Apps
When the client acquired a US risk services business, one business-critical application could not simply move across. It ran on a third-party form tool that the client did not want to carry into its main Microsoft tenant, and the team that served contractors every day depended on it. We rebuilt it in Power Apps, with every function intact, inside the migration deadline.
- 2,000+
- items in the largest list
Dynamics 365 Field Service Security Roles and Project Closure
In Field Service, wrong access rights cost twice: dispatchers who cannot do their job, or users who can change records they should not. The client needed security roles that matched how its service team works, and a delivery that closed cleanly. We mapped three roles across 27 tables and worked the remaining tickets down to finish the project.
- 27
- tables secured by role
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.