A good request reduces back-and-forth. It does not need to sound automated or legalistic.

“Please send your documents” makes the applicant do the work of figuring out what the team needs. A strong request names the item, explains what makes a usable copy, tells the applicant how to send it, and gives a simple way to ask for help.

Use one request per clear action

Group related files when that helps, but avoid a long paragraph with ten different requirements. Make each item scannable. If the request is for a complete passport copy, say which pages are expected. If the team needs all pages of a statement, say that directly. Keep instructions aligned with the firm’s approved process.

A clearer request

Employment letter
Please upload the signed employment letter as a PDF or clear photo. We need the pages that show your role and employment dates. If you do not have this letter yet, choose “I need help getting it” and we’ll note that for the team.

Explain the next step

Applicants are more likely to respond when they understand what will happen after they upload a file. Tell them that a team member will review it, and that you may ask for a clearer or more complete copy. Avoid implying that the upload alone proves eligibility or guarantees a result.

Track request state, not just message history

For each checklist item, keep a state such as missing, requested, received, under review, accepted, or resubmission needed. Record when the request was sent and whether it was delivered. When a file arrives, cancel any reminder that is no longer relevant. A generic reminder sent after an upload makes the service feel inattentive.

  • Assign an owner for unusual or overdue items.
  • Use a reasonable reminder cadence and respect channel preferences.
  • Provide a secure upload route and a contact option for accessibility needs.
  • Keep the original request and every later change in the case history.

Make the team’s language consistent

Use a shared request template, then personalize the item name, quality issue, and due date. Avoid unexplained acronyms. If the applicant prefers another language, use reviewed translations and retain the English field labels your internal reviewers need.

This article describes operational communication practices, not legal document requirements. The firm or attorney should set the actual case checklist.