Hypothetical applied case
Platform Markets and Gig Work
How should a city compare flexibility, net earnings, waiting time and worker protection?
Scenario
In a fictional city, a delivery platform reports gross pay of $24 per active hour. A sample worker logs 20 hours in the app, completes deliveries for 13 of them, earns $312 before expenses and pays $62 for fuel, maintenance and insurance allocated to the week.
Net app-on hourly earnings = ($312 − $62) / 20 = $12.50. Net active-hour earnings = $250 / 13 = $19.23. Both are mathematically valid, but they answer different labor questions.
The numbers are invented. A representative estimate would require a documented sampling frame, expense rules, taxes, tips, multi-apping and worker heterogeneity.
Policy channels
Pay floor: Define whether waiting time, accepted-job time or all logged-in time enters the denominator.
Matching: A fee or floor can change worker supply, customer demand, wait times and geographic coverage.
Risk allocation: Insurance, injury, equipment, demand volatility, deactivation and benefits must be measured separately from gross pay.
Evidence dashboard
Decision task
Design a pay or benefits rule. Define covered time, reimbursable expense, data-audit access, appeal rights and one expected market response. State whose welfare could fall.
Sources and correction
The earlier page used secure internet servers per million people as a gig-work “data snapshot.” That infrastructure indicator does not measure earnings, job quality, market power or worker status and has therefore been removed. Sources checked 10 October 2026.