Research · Published · Updated
Intake Completeness for Outsourced Work
What share of work requests include the source, expected output, owner, and due date?
On this page
Headline signal
A local review protocol, not a universal benchmark. (https://www.nist.gov/). Treat this as context for planning, not a guarantee about a particular assistant or operating result.
Analysis and operating context
## Question and scope
What share of work requests include the source, expected output, owner, and due date? The scope is the work record and the events the team can observe in a defined window. It does not estimate an industry rate or a legal conclusion.
## Population and unit
Requests received in a defined month, sampled by work type and client. The unit is one request, handoff, assistant, or invoice. Linked events are recorded separately so a correction is not counted as an independent success.
## Definitions and measures
Field completeness, missing source, rework, and time to first action. Define the window and evidence standard before the sample begins. A count without its denominator and source is not a measure.
## Where the record fails
Missing source and output definitions are the most common gaps. A failure needs a reason code, a next owner, and a recheck date. Silence is not a disposition.
## Worked example
A complete request can still be wrong; check the expected output against the source. The numbers are illustrative. The value is the stage split, which shows whether the delay belongs to intake, review, the destination, or the client.
## Evidence and limits
Public guidance can frame the questions but cannot prove a local result. Samples may exclude untracked work, offline notes, or records that never reached the client system. Record the sample frame, extraction time, and fields that were unavailable.
## Practical use
Change one controlled element at a time: the intake field, the owner, the review cadence, or the stop rule. Recheck the same measure after two cycles.