Small-business outsourcing research

How long does new-client document collection take after the sales handoff?

A protocol for measuring the time from sales handoff to a complete client document file, with stage times and the causes of delay.

How long does new-client document collection take after the sales handoff?

Research question and scope

This protocol asks how long a new client's document file takes to become complete after the sales handoff. The unit is one new client engagement followed from the handoff date to the date the last required document is verified. The study measures the time spent waiting on the client, the time spent waiting on internal review, and the number of reminders. It does not judge the quality of the sales conversation or the client relationship.

Set the scope to one business, one service line, and one document list. Record the intake form, the upload location, and the reviewer who verifies each document. If the business changes the document list during the window, keep the original list for clients already in progress and analyze later clients separately. A shorter list can improve the time without any change in client responsiveness.

Define the population as every new client who signed during the window and was expected to provide documents. Include clients who withdrew before completion, because their time is part of the result. Exclude clients whose service required no documents and state that exclusion. Test the definition on two recent engagements before collection begins.

Definitions that make the measure reproducible

Define the start as the date the sales handoff record was created, not the date the contract was signed or the first call was held. Define complete as every required document received, legible, and verified against the client record. A document that arrived but was rejected is not complete. Record the rejection and the date the replacement arrived.

Measure calendar days and also record the business days between the handoff and the first request. A delay before the first request is an internal delay, while a delay after the request is more likely a client delay. Report the two stages separately so the fix lands in the right place. Do not count a reminder as progress unless it produced a document or a response.

Record the time to the first request, the time to the first document, the time to the last document, and the time to verification. These stages show whether the process is slow to start, slow to collect, or slow to review. A fast first request followed by a long silence is a different problem from a late first request. A stage with no timestamp should be reported as unknown rather than estimated.

Evidence standard and data dictionary

For each client, capture the handoff date, the service, the document list version, and the assigned coordinator. Add the request date, the reminder dates, the receipt dates, the verification dates, and the reviewer. Record whether the client used the approved upload location or sent files through another channel. Keep the handoff record and the document index linked to the case.

Capture the reason for each delay when it is documented: client travel, a missing signer, an unclear request, a rejected document, or an internal review backlog. Do not infer a reason from silence. If the reason is unknown, mark it unknown and keep it in the denominator. A guessed reason makes the process look better understood than it is.

Record the number of documents required, received, rejected, and waived. A client with ten required documents will usually take longer than one with three, so report the list size beside the time. A waiver should have an approver and a reason. An undocumented waiver is a missing document with a friendlier name.

Sampling and collection

Collect every new client in the window, or a random sample drawn from the signed-client list with the method recorded. Do not select only the clients who completed quickly, because the slow cases are the ones that reveal the process. Record the export date, the filters, and the number of clients excluded. Keep the sampling frame with the export so the denominator can be rebuilt.

If the business has several coordinators or service lines, collect each separately and record the group. A combined median can hide one coordinator with a persistent backlog. Report the number of clients and the document counts behind every time. A time without its list size is hard to compare.

Ask the coordinator to identify the clients who needed the most reminders and why. A missing signer, an unclear request, and a rejected scan each point to a different repair. Record the reason before looking at the overall time so the explanation is not fitted to the result. Use the same reason codes across clients.

Analysis and reporting

Report the median and range for the total time and for each stage. Show the share of clients complete within one week, two weeks, and one month. Present the results by coordinator, service, and document count. Report clients still incomplete at the end of the window separately so they do not disappear from the denominator.

Separate internal delay from client delay and report both. A business may be fast once documents arrive but slow to ask for them, or the reverse. Compare the stage times with the reminder schedule and the review capacity. The reader should be able to see which stage would shorten the most cases.

Inspect the slowest cases and describe the dominant stage without naming the client. A missing signature, a rejected document, and a review backlog each lead to a different change. Report the number of reminders beside the time. A long collection with no reminders is a queue ownership problem, not a client problem.

Limits of the evidence

The record can show when a document was received, but it cannot show when the client actually sent it. A file uploaded late at night may be recorded the next morning. The protocol also cannot capture a document handed over in person and entered later. State that limitation before presenting the time.

A small business may have too few new clients to support a stable median. Describe the cases and the document counts instead of ranking coordinators. If one person handles every onboarding, the result may reflect that person's availability more than the process design. Do not use the time as a performance score without the context of leave and service mix.

Do not compare a business that collects documents before the kickoff with one that collects them during delivery. The two have different clocks even when the total looks similar. Report the collection policy beside the result. A target that can be met by refusing to start work is not a service target.

What to change

Give the result to the coordinator and the owner and ask them to choose one observable change. The change might be a single upload link, a pre-filled document list, a verification slot on the first day, or a named backup reviewer. Record the owner, the effective date, and the measure that will show whether the change worked. Bring the case records to that review so the choice is based on evidence.

If the first-request time falls but the total time does not, the bottleneck may have moved to client response or review. If the total falls but rejections rise, the request may be too vague. Report the movements together before declaring success. Close the review when the owner accepts the finding and the next collection date is set.

Ask the last two clients which document was hardest to provide and why. A concrete answer is more useful than a satisfaction score. Update the request with the missing explanation and the owner. The next measurement should test whether that document arrives sooner.

Sources

Frequently asked questions

Does a favorable sample prove the routine caused the result?

No. The design is observational and supports a bounded operating decision, not a universal causal claim.

What should an owner review first?

Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.

Related research