Package Journey

Submission → review → processed: where packages stall, and what each path costs in time

snapshot

Range

The funnel

Submission-day cohorts in the selected range · green = went straight through, purple = stopped in review first, grey = not (yet) processed

Path mix per day

Processed packages by path — direct vs. via review — plus not-yet-processed remainder · line = review rate (right axis)

Time to processed, by path

Daily median submission→processed for each path, and median review dwell (first review→processed) · log scale

Methodology. Cohorts by package submission day (Eastern), internal/test tenants excluded (same list as the Revenue Report). Stage timestamps come from packages_historicalloanpackage: first status-3 row = entered review, first status-2 row = processed; the window starts 2026-04-13 because earlier history contains backfill artifacts. "Direct" = processed without ever entering review. Review dwell = first review → first processed. Caveat: while files process concurrently the package status recomputes and can flap between states for seconds — first-transition timestamps are robust to this, but counting review re-entries is not, so no "bounce" metric is shown. Durations are inlined as daily medians (exact per day); the KPI values for multi-day ranges are completion-weighted averages of daily medians, marked ~. Weekends (Sat/Sun) excluded; duration lines smoothed with a centered moving average (3-day at 30d, 5-day at 90d; none at 7d). laminr-prod.