Transportation Specialist Pipeline Example Data

Transportation Specialist Pipeline

Example Data

Filter By BioMed Geography

Sankey

Waiting Age
Age: In This Stage

Progressed Waiting / Other Outcome

Aging starts when someone enters the waiting stage. The day ranges are examples, not official service targets. Total time since application is a separate measure.

How This Works
About This Example

Invented applicant data with reference geography and fixed donation-site names. This demonstrates a proposed reporting design. Waiting is not withdrawal; band width represents people.

What Amy Is Asking

Understand application volume, time in each stage, progression and confirmed exits, actual first service and continued participation. Compare national, division, region and site views only when their definitions and source coverage agree.

The Lucid process map explains the steps and responsibilities. The proposed Sankey measures linked paths through those steps. Aging makes the backlog actionable.

What The Data Must Provide

In This Stage counts days since entry to the current waiting stage. Since Application includes earlier stages. Both use the reporting cutoff; unknown dates need their own bucket in real data. This demonstration uses invented day values.

  • An approved stable applicant identifier and a distinct application or referral identifier where repeat applications occur.
  • Dated stage entries, approvals, training completion, actual completed service and verified exit events.
  • Current responsible team and source-backed location codes.
  • A reporting cutoff, source refresh date and explicit missing-history category.

Only aggregate output belongs on this page. Keep personnel records in their approved private environment. No data is imported by this demonstration.

How To Read Outcomes Fairly

A registration is a booking, not completed service. No later service recorded is not a proven withdrawal. Unknown dates belong in an explicit unknown bucket. Only assess ninety-day participation for people whose observation window is complete; define the start date and qualifying service before calculating it.

Suggested Improvements
  1. Give each waiting stage an accountable team and a clearly defined next action.
  2. Agree on service targets before flagging a delay as overdue.
  3. Separate applicant withdrawal, declined placement, administrative cancellation and missing history.
  4. Show whether the backlog is growing or shrinking alongside its age.
  5. Use completed shifts and service capacity to assess staffing; approval counts alone are insufficient.
Sources, Assumptions & Open Questions

Source basis: user-supplied Transportation Specialist Lucid screenshots discussed October 7, 2026; original diagram publication date and current owner unverified. The October 6 applicant-pipeline request is summarized in the existing research source register (S41); the user-supplied reporting lead is registered as S46.

The simplified stages combine several handoffs. Current entry routes, team abbreviations, precise training order, report fields and permission scope need owner confirmation. The diagram does not establish that historical event data is available.

Geography labels and division-to-region grouping: existing BioMed app reference, reviewed October 7, 2026 (six divisions, 34 regions). Original effective date is unstated; this is not certification of today’s complete organization. District assignments and site coverage are not implemented. No boundaries, donor totals or personnel records were copied.

All Sankey counts, waiting-age distributions, ninety-day outcomes and monthly balance figures here are invented educational examples. Responsibilities shown below are provisional interpretations of the supplied diagram. No figure is a finding about real applicants.

Transportation Specialist Pipeline

Interactive reporting prototype · Example data

From Application To Service

See who progresses, who is waiting, and how long each step takes.

Follow The Same Applicants

Read the flow from top to bottom. Band width represents people; waiting is not withdrawal.

How To Use It

  • Filter: choose a division, region, then a listed fixed donation site. The whole flow updates.
  • Open a stage: select its heading to bring its KPIs and age distribution into view.
  • Switch clocks: In This Stage measures the current wait; Since Application includes earlier steps.
  • Read quintiles: five roughly equal groups show the shortest through longest overall waits.
  • Print: produce a three-page guide for your selected geography and clock.

Example Targets

Green/red compares median wait with an illustrative 14-day stage limit. Since Application compares average elapsed days with cumulative targets: 14, 28, 42 and 56 days through the first four stages; continued participation uses an illustrative 80% target. Invented regional timing intentionally varies to demonstrate green, mixed and above-limit views. These are design examples, not approved Red Cross standards. The follow-up rate excludes people too early to assess.

Data And Limits

Applicant counts, ages and outcomes are invented. Geography labels come from BioMed reference material. The 183 listed donation-site names are a partial snapshot, not confirmed transportation operating locations; site applicant counts are synthetic allocations.

First service means a completed shift. No later service recorded is not a confirmed exit. Ninety-day follow-up needs a consistent start event and service definition.

Question or suggestions? Email Jeff Franzen

A lightweight web prototype built with HTML, CSS and JavaScript.