Creating a Client Document Request List

Ask a client to "send everything relating to the matter" and you will usually get three things: the documents you did not need, several copies of the ones you did, and none of the record that actually decides the point. The client is not being unhelpful. A broad request forces them to guess what matters, and a busy person guesses conservatively. A precise request list turns a fishing expedition into a short set of tasks the client can finish in an afternoon, and it protects you when a document surfaces late and someone asks why it was never requested.

Name the record, not the category

"All correspondence" is a category. "The email chain between you and the supplier about the delayed consignment, roughly March to May" is a record. The second version tells the client where to look and lets them know when they are done. Wherever you can, describe a document by its author, its recipient, its subject, and its rough date. If you are unsure a document exists, say so and ask the client to confirm either way rather than leaving silence to be interpreted later.

Tie each item to a period and a purpose

Every request should carry two things the client can see:

• The period it covers, so the client is not scrolling through years of files for a three-month dispute.
• The reason you need it, in one plain sentence. "To confirm the date the goods were accepted" tells the client which document you actually want and helps them offer a better one if the named record is missing.

Purpose lines also discipline your own list. If you cannot say why an item matters, you probably do not need it yet, and every unnecessary request slows the ones that count.

Separate what you hold from what is outstanding

Mark the documents already on file so the client is never asked twice for something they have sent. A request that ignores earlier submissions reads as inattentive and quietly erodes trust. Keep a live view of received, outstanding, and unavailable items so the next follow-up addresses only the real gap. A shared matter workspace such as Juniorlawyer makes this easier, because uploaded documents and the request list sit together and the outstanding items are always visible without rebuilding the list by hand.

Leave room for "this does not exist"

Some records genuinely cannot be produced: the agreement was oral, the invoice was never issued, the file was lost in an office move. If your list has no place to record that, the client either stays silent or invents something. Give each item a simple status the client can set, and add a line for a possible substitute and the person who could confirm it. A named witness to an oral agreement is worth more than a blank where a contract should be.

Keep the list current as things arrive

A request list is a working document, not a one-time email. Update the status the moment a document lands, note the version received, and close items cleanly so the picture of what remains stays honest. When you brief a colleague or the client on progress, the list itself is the answer, and nobody has to reconstruct it from memory.

A good request list does quiet work throughout a matter. It shortens the collection stage, it gives the client confidence that you know exactly what you are building, and months later it explains, item by item, why the file looks the way it does. That record is worth the half hour it takes to draft the list properly at the start.