Philippines staffing guide · Published
On this page
Set up a document request tracker for client onboarding
A tracker that lists onboarding documents by purpose, separates receipt from acceptance, and chases missing items on a fixed schedule.
Client onboarding stalls on documents more often than on signatures or setup calls. The assistant asks for a list of items, some arrive in different formats, and nobody is sure which ones are complete. A tracker gives every document a status and an owner so the team can see what is missing without rereading the email thread. It also gives the client a clear picture of what remains.
The tracker should distinguish a document that arrived from a document that was accepted. Many files arrive incomplete or in the wrong version, and marking them received hides the remaining work. Build the statuses, the chase schedule, and the acceptance rule before the first client is onboarded. Then use the same tracker for every client so the team can compare timelines.
List documents by purpose
Group the requested documents by what they establish, such as identity, authority to sign, tax status, or banking details. Purpose helps the client understand why each item is needed and helps the assistant spot a missing category. Avoid a flat list of twenty filenames with no explanation. A short note beside each group tells the client what the item proves and why the file must be current. A grouped list of five categories is easier to complete and review; name each category in the client's own words so the request does not sound like an internal audit.
For each document, write the accepted format, the version required, and whether a certified copy is needed. State who at the client can provide it and whether an alternative is acceptable. If the agreement allows a substitute, record the condition in the tracker. Clear acceptance rules prevent a file from bouncing back and forth for a week. They also give the assistant a factual reason to send back a file that does not meet the rule.
Assign an owner and a due date
Every item needs a client-side owner and a team-side owner, even when the same person chases and receives it. Add a due date based on the onboarding milestone rather than on a generic ten-day window. If the first review depends on the tax document, that document gets the earlier date. Dates tied to real dependencies are easier to defend than arbitrary deadlines. Write the dependency in the row so the client can see why an early item matters.
Record who can approve a substitute when a document cannot be produced. Some clients genuinely cannot supply an old statement or a specific certificate. Ask what they can provide instead of repeating the same request for a third week. The tracker should show the exception, the approver, and the reason instead of leaving the item overdue forever. An approved exception is a completed item, not a missing one; review the exception at the next onboarding so a substitute does not quietly become the new requirement.
Separate receipt from acceptance
Use distinct statuses for requested, received, accepted, and rejected. Received means the file arrived, while accepted means it meets the format and content rule. Rejected needs a reason and the specific action the client must take. The assistant should never move an item to accepted without opening and checking it. If the check fails, the rejection note should say exactly what to resend and in what format.
When a document is accepted, record the date, the reviewer, and the location where it is stored. If the client sends a replacement, keep the earlier version only as long as the retention rule requires. Link the stored file to the tracker row so a later reviewer can find it without searching. The tracker is an index, not the storage system. Back up the storage location and test a restore before the first client file is added.
Chase on a fixed schedule
Set chase intervals such as day three, day seven, and day ten after the request. Each chase should name the missing item and the consequence of delay rather than repeat the original list. Copy the client owner when an item passes the second interval. A predictable schedule reduces the temptation to send daily reminders that get ignored. It also makes the chase history readable when a supervisor asks why an item is still open.
Keep the chase message short and specific, with one link to the tracker or the upload folder. Avoid chasing every item in one long email when only two are outstanding. A focused message is easier to answer and creates a cleaner record of what was asked. If the client is unresponsive, escalate to the onboarding owner with the dates and messages attached. The escalation path should be in the tracker header, not discovered during a crisis, and tested once with a practice item before a real client depends on it.
Close the tracker with a review
Before marking onboarding complete, confirm that every item is accepted or has an approved exception. Check that stored files match the tracker rows and that access is limited to the people who need it. Send the client a short completion note listing what was received and what remains outstanding. The note prevents a later disagreement about whether a document was ever provided. It also gives the client a clear moment to confirm that nothing else is expected.
Review the tracker after each onboarding to see which items caused the longest delay. If the same document is always late, ask whether it can be requested earlier or replaced with a simpler proof. Update the template and the client instructions with what the review found. Each onboarding should need fewer chase messages than the last. Keep the review notes with the template so the next client starts from what was learned.
Questions and operating boundary
Should the client see the tracker?
A read-only view or a short status summary works well. Keep internal notes and reviewer comments out of the client view.
What if a document is sensitive?
Use the agreed secure channel, limit access, and record who viewed it. Do not send sensitive files as ordinary email attachments.
How long should onboarding documents be kept?
Follow the client agreement and the applicable retention rule. Record the retention period in the tracker header.
Source
irs.gov provides authoritative background and does not endorse this service.