Onboarding & handoffs / GUIDE + WORKSHEET
Collect client documents without endless reminders
Create a document collection workflow that distinguishes requested, received, accepted, and missing items with clear reminder rules.
THE STARTING POINT
Track each requested item separately and distinguish receipt from acceptance. Tell the client what is missing, why it is needed, and who can answer a question. Stop automated reminders when an item is accepted, waived, or waiting on your own team rather than the client.
Request only what the next step needs
Group requests around a clear task or milestone. Explain acceptable formats and the time period a document should cover. Identify items that are conditional so clients are not chased for something irrelevant. Use the organization's approved transfer method for sensitive material, and avoid spreading copies across personal inboxes and unrelated tools.
Separate received from usable
A file can arrive while still being the wrong version, incomplete, or unreadable. Assign a reviewer and define acceptance criteria. Let the client see a specific correction request rather than a vague 'documents missing' message. Keep the status tied to the requested item so replacing a file does not create a second unresolved request.
Make reminders aware of the workflow
Before sending a reminder, check current status, recent replies, and whether the outstanding action belongs to the client or your team. Pause when a conversation needs judgment. Decide how an owner handles repeated nonresponse and how the project timeline should reflect the dependency. A reminder engine should not conceal the need for an actual conversation.
WORKED EXAMPLE / ILLUSTRATIVE
A fictional project intake
A client supplies the requested export, but it covers the wrong period. The request becomes 'needs correction' with a precise explanation. Another item awaiting internal review does not trigger a client reminder.
| Item | State | Next action |
|---|---|---|
| Contact list | Accepted | No reminder |
| Activity export | Wrong period | Ask for the agreed date range |
| Process document | Awaiting internal review | Remind reviewer, not client |
MAKE IT USEFUL
Document request register
Use one record per requested item.
Your notes stay in this page and are not sent to Smithers. Download or copy them before leaving; refreshing clears them.
Before you put it to work
- Distinguish receipt from acceptance.
- Make correction requests specific.
- Avoid reminders for internal review delays.
- Use approved handling for sensitive files.
Do not collect extra documents simply because the form allows it. Keep collection focused on the work and follow your organization's retention and access requirements.
IF THIS LOOKS FAMILIAR
Your tools. Your particular mess.
The worksheet is yours to use. If the difficult part is making it work with the systems you already have, that's the kind of thing we help with.
See the industry context