This is a secondary, enquiry-led route for document-chasing workflows outside our main accountancy work. We do not publish a package or tariff for these sectors. Start with the document-chasing overview; a fit call confirms whether a bounded operational workflow is practical.
A case-document chase built around a broker-approved checklist.
Where a broker has already defined the documents to request for a specific case, a bounded workflow may help prepare reminders and organise replies. The broker remains responsible for lender requirements, client communication and every regulated decision.
Human-approved messagesCase list supplied by the brokerNo mortgage advice
A document list is an input, not a decision.
The workflow can only act on the case, client, request and permitted contact details supplied through an agreed source.
A potential use case is the administrative chase for an item that a broker has already marked as outstanding. Approved reminders could be prepared from that source and the response associated with the case.
The workflow would not decide which lender evidence is required, confirm that a case is complete, assess authenticity or interpret the contents of financial documents.
One case-document cycle, kept narrow
- Read the broker-approved outstanding-item list and the permitted client contact route.
- Prepare the approved reminder for the specific document named by the broker.
- Wait for human approval before a client-facing message is sent at launch.
- Associate the reply with the correct case and file an attachment where technically feasible.
- Route questions, discrepancies, sensitive information and any advice-related reply to the case owner.
What remains with authorised people
Mortgage judgement
Suitability, affordability, lender criteria, product selection, disclosure and recommendations are never handled by the workflow.
Document assessment
Identity checks, fraud concerns, document validity and whether evidence satisfies a lender stay with the broker's authorised process.
Systems and permissions
Access to case systems, inboxes and folders is reviewed during scoping. No named platform or direct connection is assumed.
The written scope must cover data processing, suppliers, retention, client contact permissions, approval rules, escalation, pause controls and the operating record before any access is granted.
Use one anonymised case to test fit.
- Show how the broker marks an item as outstanding.
- Bring the reminder templates the firm already permits.
- Identify where documents arrive and who assesses them.
- Mark every reply type that must stop and escalate.
If the workflow would require interpreting lender rules or client circumstances, it is not the bounded admin loop described here.
Bring one broker-approved document chase.
We will assess whether the administrative request can be separated safely from the regulated work.