The client-intake document completeness benchmark measures whether a file contains the documents the agency's own intake policy requires and whether every missing item has an owner and follow-up date. It is not a clinical or legal determination.
Create the checklist from approved policy
List required demographic, consent, service, payer, emergency-contact, and other intake fields only after the agency's responsible owner approves them. Record the source of each item, date received, review status, missing reason, owner, and next action.
Review a stable sample
Review 25 files from one service line or the full population when smaller. Mark record identity, required-field completion, document legibility or validity where applicable, approval status, and missing-item follow-up.
| Check | Result |
|---|---|
| Correct client and service identified | ___ / ___ |
| Required intake fields present | ___ / ___ |
| Missing items have a reason | ___ / ___ |
| Owner and next action recorded | ___ / ___ |
| Review or approval evidence present | ___ / ___ |
Separate “not applicable,” “waiting on client,” and “not yet reviewed.” A single incomplete bucket makes it difficult to choose the right process repair.
Where a virtual assistant fits
A trained assistant can maintain the checklist, request approved documents, flag duplicates, and prepare an aging view. The agency should decide what information is necessary, approve exceptions, and handle clinical or legal questions.
Use the approved system, minimum necessary access, and an audit trail for changes. Avoid sending sensitive documents through unapproved personal channels.
Source and guardrail
The HHS HIPAA Security Rule guidance explains that entities should understand where electronic protected health information is created, received, maintained, or transmitted. Apply the agency's privacy and intake policy to the specific workflow.

