Define the request and its purpose
Have the responsible practice professional specify the required documents and the work they support. Use client-friendly labels rather than internal abbreviations the recipient may not understand. Record the relevant period or entity where the professional requires it. Do not let automation invent requirements based on a similar client file. A fictional practice might request two named documents for an existing engagement; the intake workflow should preserve those exact requirements instead of expanding the list with plausible extras. Professional judgement remains with the practice.
Choose one communication owner
Name the person responsible for coordinating the request, even when several staff members need the documents. That person should see new requests before another team sends a separate chase. Define cover for leave and workload changes. A shared mailbox can support ownership if assignment and outstanding work are visible. Forwarding a message alone should not transfer responsibility unless the receiving person accepts it through the agreed process. Keep client-facing commitments attached to the request so a handover does not silently change what the client has been told.
Separate requested, received and reviewed
Use distinct states for an item still requested, a file received and a document reviewed by the authorised professional. An attachment arriving does not establish that it is the right document, covers the right period or satisfies the request. Mark uncertainty for review rather than closing the item automatically. If a file is replaced, preserve its relationship to the original request. The client can be told that material arrived without implying the engagement is ready for completion or that a professional has accepted its contents.
Send a consolidated outstanding list
Before preparing a reminder, check the latest receipt and review states. Ask only for items that remain outstanding under the approved rules. Include a clear submission route and any professional-approved explanation needed to identify the document. Do not expose unrelated client information in a combined request. If one item is under review, describe that state accurately rather than requesting it again. Let the owner review unusual cases, such as a client saying the document does not exist, instead of repeating the same automated message indefinitely.
Keep follow-up within the agreed process
The practice should approve the timing, recipients and stopping rules for follow-up. Do not turn an internal target into an external deadline or claim a consequence the professional has not authorised. Pause a reminder when the owner is discussing the request with the client or when a response needs assessment. Record attempts separately from replies received. If the client responds through another channel, link that update to the same task. The workflow should reduce conflicting requests, not add another independent stream of communication.
Review the oldest unresolved requests
Inspect items that remain open, requests transferred repeatedly and documents chased after receipt. Use the findings to improve wording or ownership before adding more reminders. Test with fictional cases involving partial submission, a replacement file and an owner on leave. Confirm that only the approved outstanding items appear in the proposed message. Count administratively received documents separately from professionally reviewed work. The process is working when staff and the client can see what remains needed and who will decide whether the response is sufficient.