Email attachment
- Best suited to
- One or two simple files in a one off exchange
- Client experience
- Familiar and direct
- Tracking what is missing
- Usually manual
- Repeated requests
- Becomes repetitive quickly
Structured client file collection
Request files from clients and keep track of what's missing
If you only need one file from a client once, email may be enough. The process becomes harder when you need several documents, answers or confirmations, especially when the client sends some items now and the rest later.
The key is not only giving the client somewhere to upload. It is making the request clear enough that both sides can see what was requested, what has arrived and what is still outstanding.
FileTRX lets you create a structured client request, share one browser based link, collect files and other requested information, and track progress as the client responds.
See partial completion at a glance
The owner view keeps the completed count, percentage and outstanding checklist state together.
Choose the simplest method that fits the request
There is no single best way to request files from every client. The right method depends on how much you need, how often the process repeats and whether you need to track individual outstanding items.
Shared folder or basic upload link
- Best suited to
- Giving a client one place to add files
- Client experience
- Simple destination, depending on the provider and setup
- Tracking what is missing
- Often focused on what was uploaded rather than what was requested
- Repeated requests
- Can work for simple recurring exchanges
A clear middle ground
Structured file request
- Best suited to
- Several specific files, answers or confirmations that may arrive in stages
- Client experience
- A clear list of requested items
- Tracking what is missing
- Progress can be tracked against the request
- Repeated requests
- Well suited to repeatable client collection workflows
Full client portal
- Best suited to
- A broader ongoing client relationship with multiple services or workflows
- Client experience
- More complete client environment, often with more setup
- Tracking what is missing
- Can support wider workflow tracking
- Repeated requests
- Suited to organisations that need a broader portal experience
For a one off request, adding another system can create unnecessary work. For a multi item request, the ability to define each item and see what remains can become more useful than simply providing an upload destination.
An upload link answers where. A structured request also answers what is missing.
A basic upload link solves an important problem: Where should the client put the files? That may be all you need.
But if your request contains six documents and the client sends four, you now have a different problem: Which two items are still outstanding?
A structured request makes each required item explicit. Instead of sending a message such as “please send the documents we discussed”, you can present the client with a checklist of the files and information you actually need.
That checklist can also include information that is not a file. For example, you may need the client to answer a question, choose an option, provide a date or confirm that the information supplied is current.
This makes the request itself the source of truth rather than relying on an email thread, a folder and a separate list of missing items.
If you are evaluating products for this workflow, you can also compare file request software capabilities.
A useful test
Can you answer “what exactly do I still need from this client?” without checking another list?
If the answer depends on comparing an inbox, a folder and your notes, the request may benefit from more structure.
What should a good client file request include?
A professional request should make it easy for the client to understand what you need and easy for you to see whether the request is complete.
Client File Request Quality Checklist
- 01
Give the request a clear name. Use a title the client will recognise, such as “New client information” or “March bookkeeping records”.
- 02
List each requested item separately. Avoid hiding several documents inside one long instruction when they need to be tracked individually.
- 03
Explain anything that could be ambiguous. If you need a particular period, version or type of document, say so beside the relevant item.
- 04
Make optional items obvious. Clients should be able to distinguish what is required from what is useful only when available.
- 05
State relevant file requirements. If a specific format or file size matters, tell the client before they try to submit the file.
- 06
Give a realistic deadline or expiry where appropriate. Make the timing visible instead of leaving it buried in a separate email.
- 07
Provide one consistent place to respond. Avoid asking the client to use several channels unless the workflow genuinely requires it.
- 08
Make received items easy to recognise. The client should not have to guess whether something has already been supplied.
- 09
Keep outstanding items visible. Partial completion is normal. A useful request should make the remaining work clear.
- 10
Allow room for an explanation when needed. Give the client a clear way to say when an item does not exist or cannot yet be supplied.
You can use this checklist with email, a shared folder or another process. The more often the same type of request repeats, the more useful it becomes to turn the checklist into a reusable workflow.
A practical example
Example: a structured new client request
Imagine you are starting work with a new client and need several items before you can begin. Instead of sending one message with a paragraph of instructions, the request could be structured like this:
New client information and documents
- Existing agreement or reference document
- File required
- Current project or account records
- File required. Allow multiple files if several records are relevant.
- Supporting material
- File optional
- Preferred contact method
- Select one option
- Relevant start date
- Date
- Information confirmation
- Confirm that the information supplied is the latest available
The request is not simply “open” or “closed”. It is partially complete, with specific outstanding items still visible.
The FileTRX workflow
How requesting files works in FileTRX
1.Create the request
Start with a clear request title, client details and instructions, then add the items you need. A request can include file uploads, short or long text answers, yes or no questions, dropdown choices, dates and confirmations. File items can accept more than one file and can use format or size rules where relevant.
2.Share one request link
Send the client the request link rather than dividing the request across several email attachments and messages. For an open FileTRX request, the client can use the browser based link without creating a FileTRX account.
3.Let the client respond in stages
The client can upload requested files and provide the other information in the request. If everything is not available at once, the request can remain partially complete while outstanding items are still visible.
4.Track progress
As items are completed, FileTRX shows request progress so you can see what has arrived and what is still missing.
5.Manage the request lifecycle
When needed, the request owner can close, reopen, revoke or extend a request. Scheduled reminder emails are also available for outstanding requests, and recurring request structures can be reused through templates.
The aim is not to turn a simple file exchange into a large workflow. It is to give repeated or multi item client requests enough structure to remain clear.
What does the client see?
A client receiving an open FileTRX request sees a browser based request rather than a blank storage folder.
- The individual files or pieces of information being requested
- Instructions for specific items
- Which items are required or optional where configured
- Clear completion state against the relevant checklist items
- Questions, choices, dates or confirmations that need a response
- The progress of the request as items are completed
For open requests, the client does not need to create a FileTRX account to upload files and respond. The client can work through one list instead of interpreting a long email and deciding where each item belongs.
What can the request owner track and manage?
Once the request is sent, the owner can focus on the state of the request rather than reconstructing it from messages and attachments.
- See overall request progress
- See which requested items have been completed and which remain outstanding
- Receive multiple files against the same checklist item where needed
- Search and manage requests from the owner workspace
- Close, reopen, revoke or extend requests as the situation changes
- Reuse ready made templates or save your own recurring request structures
- Send scheduled reminder emails for outstanding requests
- Review request activity history when useful
You do not need every capability for every client. The value comes from choosing enough structure for the workflow you actually have.
Where structured requests are useful
Accountants and bookkeepers
A recurring monthly request might ask separately for bank statements, sales records, expense documents and a confirmation that the available records have been supplied. When the client provides only some of them, the remaining items stay clear.
Agencies and freelancers
A project request might collect logo files, brand guidance, existing copy, photographs and a few project answers in the same request rather than spreading assets and information across several email threads.
Recruiters and consultants
A request might combine a CV or supporting documents with availability information, a date and a confirmation. Files and answers remain part of the same client request instead of becoming separate tasks to reconcile later.
These are intentionally simple examples. The exact request should reflect the work you actually need from the client rather than forcing every workflow into the same template.
Reusable workflows
Reuse a good request instead of rebuilding it
If you ask different clients for the same type of material, rebuilding the request each time creates unnecessary repetition.
FileTRX includes ready made templates and lets you save your own recurring request structures. You can start from a suitable structure, review it for the current client and then send the request.
Frequently asked questions
What is the best way to request files from a client?
Use the simplest method that matches the job. Email can be enough for one or two files in a one off exchange. A basic upload link is useful when the main problem is giving the client one place to send files. A structured file request becomes more useful when you need several specific items, expect partial completion, need answers alongside files or repeat the same process with multiple clients. A full client portal may make more sense when file collection is only one part of a broader ongoing client relationship.
Can clients upload files without creating an account?
With an open FileTRX request, yes. The client can open the request in a browser and upload files without creating a FileTRX account. FileTRX also has other request access modes, so the no account statement should be understood specifically in the context of open requests.
How do I request multiple documents from one client?
List each document as a separate requested item rather than putting the whole list into one paragraph. This makes the request clearer and makes partial completion easier to understand. In FileTRX, a request can contain several file items, and an individual item can also accept multiple files when needed.
How can I track which client documents are still missing?
Use a request structure that tracks completion against each requested item. If five items were requested and three have been supplied, the remaining two should stay visible as outstanding. FileTRX provides request progress and item level completion so the owner can see what has arrived and what remains.
Is a file request different from a shared folder?
Yes, although both can be useful. A shared folder mainly gives the client a destination for files. A structured file request defines the individual items you need and can track progress against that list. If the main problem is simply where the client should upload, a folder or basic upload link may be sufficient. If the problem is knowing exactly what is still missing, a structured request is usually a better fit.
When is email good enough for requesting files?
Email is often perfectly reasonable when the request is small, clear and unlikely to repeat. If you need one document from one client and there is little chance of confusion, adding another workflow may not help. The case for a structured request becomes stronger as the number of items, clients, follow ups or repeated requests grows.
What should I include in a professional client document request?
Give the request a clear title, list each item separately, explain anything ambiguous, distinguish required and optional items, include relevant file requirements, provide a deadline where appropriate and make it easy to see what has already been supplied and what remains outstanding. If an item might not be available, give the client a way to explain that.
Can I collect answers as well as files?
Yes. A FileTRX request can combine file uploads with short or long text answers, yes or no questions, dropdown choices, dates and confirmations. That is useful when a client request includes both documents and the information needed to interpret or complete the work.
Can I reuse the same request structure for other clients?
Yes. FileTRX includes ready made templates and lets you save your own recurring request structures, so a useful checklist can be reused instead of rebuilt from the beginning each time.
Turn your next client request into a clear checklist
If you need several files or pieces of information from a client, define the request once, share one link and keep the outstanding items visible as the client responds.