Small accounting teams often need several pieces of information from the same client at once. Treating every request as equally urgent can produce long emails, repeated chasing and replies that solve the easiest questions rather than the ones blocking the work. A clearer priority process links each request to the work that depends on it.
Identify the blocked task first
Before contacting the client, state internally what cannot progress without the missing information. The dependency might relate to reconciling an account, completing a review, resolving an unexplained balance or preparing work for a responsible colleague. This makes priority a property of the workflow rather than whoever happens to send the loudest reminder.
Separate genuine deadlines from internal preferences
Record any real external or agreed client deadline accurately, but do not manufacture urgency simply to obtain a faster response. Internal target dates can still be useful for planning, provided the team distinguishes them from statutory, contractual or client-agreed dates. Where a deadline has legal or regulatory significance, the responsible professional should confirm the applicable requirement rather than relying on generic wording.
Group requests without hiding the priority
Combining related questions can reduce unnecessary messages, but a long undifferentiated list makes it difficult for the client to know what matters first. Put the blocking items at the top, explain briefly what they affect, then separate lower-priority information that can follow later. If different people at the client hold different records, route the requests accordingly rather than forcing everything through one recipient.
Make each request answerable
Specify the period, account, transaction or document involved and what is needed. “Please send the remaining information” is hard to act on; a precise request lets the client provide the right evidence or explain why it is unavailable. Avoid asking the client to make an accounting judgement when the team only needs factual information or source documents.
Track partial responses properly
A client may answer three questions and leave two unresolved. Update the request register at item level rather than treating the whole message as complete or outstanding. This prevents already-supplied information being chased again and keeps the true blockers visible. It also provides a cleaner handover if responsibility changes within the accounting team.
Escalate based on consequence, not annoyance
Repeated reminders can become noise if the team has not considered what happens when an item remains unanswered. Define an escalation point based on the work at risk and the time available. That might mean involving the client manager or responsible accountant, but escalation should communicate the unresolved dependency clearly rather than simply increasing the tone of urgency.
Close the loop when information arrives
Check that the response actually answers the request and that any document belongs to the right period or transaction. Link it to the working record, update the status and notify whoever was waiting for it. A response that introduces a new discrepancy should create a new or revised query rather than being forced into a closed status.
Review the pattern after the work is complete
Recurring information gaps can reveal a collection process that needs improvement. If the same records repeatedly arrive late or in an unusable form, the firm can agree a clearer future checklist, collection point or timetable with the client. The goal is not to blame the client; it is to reduce avoidable chasing and make future accounting work easier for both sides to progress.