Pennsylvania reports document-quality gains while keeping eligibility decisions with staff

Explore unreadable-document rework with benefits operations, caseworkers, digital service leaders and resident advocates. Ask how often uploads require resubmission, how much staff time this consumes, and which residents face the greatest barriers. A bounded engagement could measure the existing upload journey and trial quality feedback on representative documents. The value hypothesis is fewer avoidable resubmissions. Do not promise the reported percentage or staff-hour benefit elsewhere, and do not describe this as automated eligibility determination. Require evidence of improved applicant experience as well as reduced internal work before proposing expansion.

Prototype an upload-quality service behind the existing application interface with human override and an accessible alternative. Require a labeled, approved document set spanning devices, formats and difficult images. Separate quality assessment from extraction and eligibility logic; a flag must not silently become a denial. Validate false rejection and missed-defect rates, latency and retention behavior against a manual review baseline. Trace retries and service failures. Hosting, model selection and vendor interfaces need local discovery. These checks address the missing accuracy and measurement detail without assuming that the reported aggregate improvement proves safe performance.

Have benefits operations own the workflow, caseworker supervisors own exceptions and IT own integration and monitoring. Dependencies include document permissions, usability testing, staff training and a usable fallback. Pilot with explicit review checkpoints and capture applicant completion, repeat uploads, handling time and false flags.

Proposed acceptance criteria

every flagged document has a documented recovery path, no quality flag alone determines eligibility, and measured errors remain within thresholds agreed before testing. Compare outcomes across accessibility and device scenarios before rollout. Risks include applicant abandonment, biased quality thresholds, sensitive-document exposure and overstated savings that omit support work.