On this page

How old is the oldest unanswered request in the assistant queue?

A proposed protocol for measuring the age and ownership of open assistant requests.

Editorial workflow illustration for How old is the oldest unanswered request in the assistant queue?

Headline statistic

9 named sources and 8 protocol sections.

Methodology: A desk review of public guidance translated into a repeatable measurement protocol for task support.

Key stats

  • 9 public sources reviewed
  • 8 protocol sections
  • November 9, 2026 verification date

Key takeaways

  • Define the unit and the denominator before collecting evidence.
  • Report missing and unavailable evidence separately.
  • Keep the owner and the evidence date beside the finding.

Question and scope

This is a proposed research protocol, not a report of completed findings. It asks how old the oldest unanswered request is. The result would describe the queue, not the assistant. Use the same format for every handover so the next reader can scan it.

The protocol does not measure whether the request was important. It measures whether it was owned. Separate what was observed from what was assumed. Keep the boundary visible in the place where the work is assigned.

Question and scope evidence
ItemFinding or controlSource
Unittask supportMethod note
EvidenceRecorded sourcePublic guidance

Population and unit of analysis

Define the population as requests open on a stated date. The unit is one request, with the arrival, owner, and next action recorded. A control that depends on memory is not yet a control. A short note with four fields is easier to use than a long narrative.

Link the request to the requester so the same request is not counted twice. Update the template when the same question appears twice. Keep the evidence with the record rather than in a separate log. Ask whether a new reviewer could act on the record without a conversation.

Population and unit of analysis evidence
ItemFinding or controlSource
Unittask supportMethod note
EvidenceRecorded sourcePublic guidance

Definitions and measures

Define age as the time between the request and the review date. Define ownership as a named person and a next action. Keep the original note beside the corrected version. Review the first few notes together before the process expands.

Report both separately. Name the owner in the same line as the action. A control that depends on memory is not yet a control. Use the same format for every handover so the next reader can scan it.

Definitions and measures evidence
ItemFinding or controlSource
Unittask supportMethod note
EvidenceRecorded sourcePublic guidance

Evidence standard

Use the request log and the task system. A request without an owner is weak. If the source is unclear, route the question instead of guessing. Test the rule on one real request before applying it to the queue.

Record the date and the reviewer. Keep the boundary visible in the place where the work is assigned. Keep the evidence with the record rather than in a separate log. Test the rule on one real request before applying it to the queue.

Evidence standard evidence
ItemFinding or controlSource
Unittask supportMethod note
EvidenceRecorded sourcePublic guidance

Sampling and collection

Use a census of the open requests. If sampling is necessary, stratify by requester. Record the exception and the person who approved it. Review the first few notes together before the process expands.

Pilot the review on a few requests and compare the reviewers. Clarify how a waiting request is treated. Update the template when the same question appears twice. Record the exception and the person who approved it.

Sampling and collection evidence
ItemFinding or controlSource
Unittask supportMethod note
EvidenceRecorded sourcePublic guidance

Analysis and reporting

Report the age distribution and the ownership rate by requester. Show the requests without a next date. Present the results as a description of the queue, not a judgment about the assistant. Record the date and the source so the next reviewer can repeat the check.

Analysis and reporting evidence
ItemFinding or controlSource
Unittask supportMethod note
EvidenceRecorded sourcePublic guidance

Limits and sources of error

The request may arrive through a personal channel. The owner may have changed during the period. Use the same format for every handover so the next reader can scan it. Name the owner in the same line as the action.

Limits and sources of error evidence
ItemFinding or controlSource
Unittask supportMethod note
EvidenceRecorded sourcePublic guidance

Review cadence

Repeat the review after a process change or at the same interval each quarter. Assign the follow-up to the operations lead and set a date. A short note with four fields is easier to use than a long narrative. A control that depends on memory is not yet a control.

Review cadence evidence
ItemFinding or controlSource
Unittask supportMethod note
EvidenceRecorded sourcePublic guidance

Questions people ask

Sources

  1. U.S. Small Business Administration: Public guidance consulted for general context.
  2. GAO Green Book: Public guidance consulted for general context.
  3. U.S. Department of Labor: Public guidance consulted for general context.