Client Document Request Kit

Write one request per item. Include the document name, entity, date range, acceptable format, deadline and delivery method. If an alternative is acceptable, explain it before the client spends time producing something unnecessary. A current export might work for one engagement while another requires the original issued document. The person reviewing the file should decide that requirement.

Choose a contact who can coordinate the request. That person does not have to create every document personally. Give them enough context to route the request to finance, operations or an authorised adviser. Avoid asking a whole team to own the same missing item: shared responsibility can leave nobody accountable.

Use the blank request template below. Replace every bracket before sending. If the list is long, group related items and identify which ones block work first. Do not manufacture urgency; state the genuine dependency and offer a way to flag unavailable items.

Keep a stable request ID when a replacement arrives. Add the replacement reference and update the review issue rather than creating an unrelated second request. This makes the history understandable and avoids reminding a client about an item already supplied. Review new arrivals before preparing the next reminder.

For each file, check the requested entity, period, completeness, readability and access. Record a short, factual issue: “September requested; August supplied” is better than “incorrect.” Avoid copying account numbers or personal information into a general-purpose tracker. Store actual documents in your approved workspace, with access suitable for the engagement.

In the fictional example, three requests are at different stages. REQ-02 needs no reminder. REQ-01 needs a replacement, not another generic request. REQ-03 is still outstanding. That distinction lets you send one helpful message naming the exact remaining work.

Ask for a revised date when a document cannot be provided. If an item genuinely does not exist, record that explanation and send it to the reviewer for an alternative decision. Do not turn “not available” into “not applicable” without approval. Those statuses answer different questions.

Agree a sensible reminder cadence with the client. A looming filing date may justify a different schedule from a routine planning exercise. There is no universal interval that works for every engagement. Escalate to the named coordinator when missing information blocks agreed work, and explain the consequence rather than sending repeated vague nudges.

Close the request only after review. Where a deadline changes, update the tracker and tell the affected owner. Keep the message calm: the goal is to obtain usable information, not to score the client’s responsiveness. A specific replacement request often saves more time than a longer explanation of why document collection matters.

Before using the template, remove sample rows, set the correct period and agree who will review each request. Keep a client-facing list separate from internal review notes if the notes contain sensitive observations. Do not give one client access to a tracker containing other clients’ details.

The completion check is simple: every required item is accepted, explicitly deferred with an owner and date, or approved as not applicable. Received alone is not a final state. If work proceeds with a missing item, record who approved the exception and what limitation remains.

For recurring engagements, duplicate the blank template for the next period. Keep previous-period records intact instead of overwriting them. Update the period in both the request and the tracker so an old document is not accidentally treated as current. Reuse the structure; reconsider the scope each time.