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.
Sales-progression requests, organised around human judgement.
If a branch already runs a consistent progress-request cycle, we can explore a narrow workflow that prepares approved chasers, records replies against an internal status list and sends ambiguity back to the negotiator responsible for the sale.
Messages approved at launchStatus is never guessedPeople own the chain
Start with the branch's actual progress list.
The practical question is whether staff already know who may be contacted, what may be asked and how a reply should change the internal tracker.
A controlled workflow might support a recurring request for an administrative update from a buyer, seller, broker or conveyancer. It would use the branch's approved wording and the contact route agreed for that transaction.
It would not decide that a milestone has been reached from an ambiguous email, promise a completion date or present an unverified status to a client. Those calls stay with the branch team.
How a narrow progress-request loop could run
- Select the live transactions, approved contacts and next permitted request from the branch's source tracker.
- Draft the progress note using language approved for that audience.
- Wait for a staff member to approve the external message at launch.
- Associate a clear reply with the correct transaction and propose the agreed tracker update.
- Escalate conflicting updates, complaints, legal questions and uncertain chain status to the negotiator.
The workflow cannot own the transaction.
Professional boundaries
No legal, mortgage, valuation, AML or financial judgement is delegated. The workflow does not advise buyers or sellers.
Communication boundaries
Permitted contacts, message templates, frequencies and approval rules are written down before any live request is prepared.
Technical boundaries
We assess the existing inbox, sales tracker and document locations first. Compatibility with a named agency platform is not assumed.
Access and processing terms, supplier use, retention, pause controls and the record of workflow actions are agreed before access is granted.
A useful fit-call example
Bring one sale from the point at which it entered progression, with personal information removed if needed.
- Show the status fields the branch updates today.
- Identify the approved contacts and the messages staff already use.
- Mark every point that requires a negotiator to interpret the reply.
- Explain how complaints, vulnerability or sensitive information are escalated.
Bring one sales-progression loop.
We will tell you whether it is bounded enough to support safely.