How reliable is a client task list as a measure of workload?

Overview

Research question and scope

This is a proposed research protocol, not a report of completed findings. It asks how well a client's task list reflects the real volume, effort, and waiting time in a virtual assistant role. The result would help a buyer judge whether the list can support staffing or priority decisions. Record the exception and the person who approved it.

The protocol does not measure the assistant's productivity. It measures the list as a record. The sponsor should name the workload decision the result could inform. Keep the boundary visible in the place where the work is assigned.

Population and unit of analysis

Define the population as all task items on the client's list during a stated period, plus the work the assistant recorded outside the list. The unit is one task item, with the source, the estimated effort, the actual time, and the wait time recorded. Items that were never completed should remain visible. Review the first few notes together before the process expands.

Decide how to treat a task that appears on the list more than once. Link the duplicates to one item and record the duplication. The list-level count and the unique-task count should both be reported. If the source is unclear, route the question instead of guessing.

Philippines evidence beside global context

The table keeps national indicators separate from the checks a buyer must run on one candidate. Values come from the direct sources listed below, and each year stays visible so unlike periods are not presented as the same measurement.

Definitions and measures

Define coverage as the share of actual work that appears on the list. Define effort as the time spent on the task, including waiting and rework. Define wait time as the time between the request and the first substantive action. If the source is unclear, route the question instead of guessing.

Report coverage, effort, and wait time separately. A list can cover most tasks but miss the few that take the most time. The combination is what determines whether the list is a useful workload measure. Record the exception and the person who approved it.

Evidence standard

Link each task to the request, the list entry, and the time record. A task that is only remembered is not evidence of coverage. For the work outside the list, use a dated note or a system record. Name the owner in the same line as the action.

Keep the original list export and the assistant's log side by side. A reconciled list that has already been edited cannot show what was missing. The gap between the two is the finding. Record the observation time so the next reviewer can tell when the evidence was checked.

Sampling and collection

Use a census of the period if the role is small. If sampling is necessary, stratify by task type and by whether the task appears on the list. Select the sample before reviewing effort and keep a log of replacements. A short note with four fields is easier to use than a long narrative.

Pilot the matching on a few tasks and compare the reviewers' classifications. Clarify how a task that was split or merged is counted. Record the rules and apply them consistently. Keep the original note beside the corrected version.

Analysis and reporting

Report coverage by task type and by client. Show the effort and wait time for tasks on the list and off the list. A high coverage rate with a low effort share may mean the list captures the easy work. Write the deadline as a date and a local time.

Present the results as a description of the list, not a judgment about the assistant. A list may be incomplete because the client did not record a request or because the assistant absorbed the work quietly. Name the possible causes. Record the observation time so the next reviewer can tell when the evidence was checked.

Limits and sources of error

The assistant's time log may be incomplete or rounded. The client's list may change during the period. State the source of each time record and whether it was reconstructed. A short note with four fields is easier to use than a long narrative.

The study may not capture work that was done outside the role's formal scope. Record the boundary used and the tasks that were excluded. The reader should be able to see what the measure does not include. If the source is unclear, route the question instead of guessing.

Review cadence

Repeat the review after a change to the task list or the role. Compare the same coverage and effort measures. A second review can test whether a new intake step improved coverage. Write the deadline as a date and a local time.

Assign the follow-up to the buyer's operations owner and set a date. The protocol should produce a specific decision about whether the list can support the workload decision it is being used for. Name the owner in the same line as the action. Test the rule on one real task before applying it to the queue.

For the operating context behind this protocol, review the services page and the boundaries it describes. Use the contact page when the study design needs a written approval or a scoped review. The references below support the definitions and the recordkeeping approach rather than a performance claim. Keep this protocol with the data so a later reviewer can repeat the method.