The FTC's 5-Point Disclosure Mandate: What Platforms Must Show You Now

The February 2026 FTC enforcement priority didn't just signal intent — it codified five specific data points that gig platforms must surface to workers before order acceptance. Understanding exactly what you're legally entitled to see transforms every shift offer from a gamble into a calculable decision.

Under the FTC's "Control Without Responsibility" enforcement framework, platforms must now disclose all five of the following components at the pre-acceptance screen:

1. Base pay amount — the flat dollar figure before any multipliers or adjustments
2. Surge/multiplier percentage — the exact active multiplier at the moment of offer, expressed as a decimal (e.g., 1.8x), not a vague "busy area" badge
3. Estimated tip range — a low-to-high band derived from comparable recent orders on that route or task type
4. Platform fees deducted — the gross service fee percentage the platform retains from the customer payment before your cut is calculated
5. Minimum guaranteed hourly rate — if the platform advertises any earnings floor, that figure must appear explicitly, not buried in a help article

Critically, the CFPB's digital payment oversight rule — effective January 9, 2025 — establishes a parity standard requiring that disclosure timing for gig pay must be functionally equivalent to traditional payroll transparency. That means no post-acceptance reveals. If a platform shows you a pay figure that changes materially after you accept, that gap is now a documented compliance violation, not a terms-of-service footnote. Screenshot every pre-acceptance screen. That image is your evidence baseline.

The Wage Verification Checklist: Audit Your Hourly Rate in Real Time

Knowing what platforms must disclose is only half the equation. The other half is running the math yourself — before you tap "Accept." Use this formula as your non-negotiable filter:

The Real Hourly Rate Formula

Variable	Where to Find It	Example Value
Base Pay	FTC-mandated pre-acceptance screen	$6.50
+ Estimated Tip (midpoint of range)	Disclosed tip range ÷ 2	$3.00
− Platform Fee	Disclosed fee percentage × order total	−$1.20
÷ Estimated Minutes	In-app estimate ÷ 60	÷ 0.35 hr
= Real Hourly Rate		$23.71/hr

Formula: (Base Pay + Estimated Tips − Platform Fees) ÷ Estimated Hours = Real Hourly Rate

The Screenshot-Capture Protocol

• Screenshot the pre-acceptance offer screen immediately — timestamp metadata is legally meaningful
• Screenshot your final earnings summary upon completion
• Store both in a dated folder (weekly batches work well) — this creates an audit trail if you file a platform dispute

For deduction documentation, IRS Publication 587 (Business Use of Home) establishes the recordkeeping standard for self-employed individuals: contemporaneous logs with date, amount, and business purpose. Apply that same discipline to your per-shift pay screenshots. If you ever face an IRS inquiry or a platform wage dispute, your documentation standard should mirror what the IRS already expects from Schedule C filers.

Red Flag Scenario #1: The Silent Surge Collapse (How to Spot It)

The most financially damaging algorithmic pattern in the gig economy isn't a dramatic pay cut — it's a quiet one. The "Silent Surge Collapse" occurs when a surge multiplier advertised at shift acceptance degrades mid-execution, with no notification pushed to the worker.

How It Plays Out

Consider a documented pattern on Uber Eats: a surge advertised at 1.8x at acceptance collapses to 1.2x by delivery completion. On a $10 base order, that's the difference between $18.00 and $12.00 — a 33% pay reduction the worker never consented to. Multiplied across a four-hour dinner rush, that silent collapse can erase $20–$35 in expected earnings.

Under the FTC's "Control Without Responsibility" doctrine, the burden of proof has now shifted. Platforms must demonstrate that any mid-shift algorithmic change was driven by genuine, real-time market conditions — not internal revenue optimization. The platform can no longer simply assert that "surge conditions changed." They must produce the algorithmic inputs that triggered the adjustment.

How to Catch It Before It Costs You

• Log your accepted multiplier via screenshot at acceptance (see checklist above)
• Compare to final earnings — divide your actual payout by the base pay to reverse-engineer the effective multiplier applied
• If the gap exceeds 0.2x, file a surge-rate audit log request through the platform's support channel, citing CFPB transparency parity rules
• Escalate unresolved discrepancies to the FTC's ReportFraud.ftc.gov portal — documented patterns across multiple workers are exactly the evidence base the February 2026 enforcement priority was designed to act on

The key behavioral shift: treat every accepted surge offer as a contract term, not a suggestion. Your screenshot is the signed agreement. Any deviation is a breach — and now, regulatorily, it's the platform's problem to explain.

Red Flag Scenario #2: The Hidden Fee Extraction (Deductions You Never Authorized)

Surge pricing transparency was just the opening act. The more insidious wage drain happens after you accept — through a layered fee architecture that platforms deliberately obscure until your payout hits your account. This is no longer just an ethical problem. Under the FTC's February 2026 enforcement priority, it's a regulatory violation.

Here's the anatomy of a real deduction stack. DoorDash's disclosed commission structure reads as approximately 30% base commission — but that figure is a floor, not a ceiling. Layer in a 3% payment processing fee and a 2% "driver support" charge, and your actual deduction reaches 35% of the customer-facing order total. The critical problem: none of these line items are individually surfaced at the pre-acceptance screen. You see an estimated payout. You do not see the deduction waterfall producing it.

The FTC's February 2026 ruling directly targets this architecture, requiring platforms to provide itemized fee disclosure before a worker accepts any shift or order. Each deduction category must be named, quantified as a percentage, and expressed in dollar terms against the specific offer on screen. "Platform maintenance," "driver support," and similar vague line items are now required to have defined service descriptions.

This intersects with CFPB authority under 12 CFR 1026.34, which prohibits "unfair or deceptive" fee practices in financial transactions — a standard the CFPB has now extended to gig platform payment flows following its January 2025 rule subjecting high-volume digital payment processors to federal supervision.

Your Pre-Acceptance Fee Audit Checklist

• Screenshot the offer screen before accepting — timestamp included
• Compare gross offer to net deposit within your earnings dashboard post-completion
• Calculate your effective deduction rate: (Gross Offer − Net Deposit) ÷ Gross Offer × 100
• If effective deduction exceeds disclosed commission by more than 2 percentage points, you have a documented discrepancy
• Flag any fee labeled "support," "maintenance," or "processing" that lacks a dollar-amount disclosure at offer screen

Any deduction not itemized at acceptance is now presumptively non-compliant under the February 2026 mandate. Your earnings dashboard is not a disclosure — it's a receipt. The disclosure must come first.

Red Flag Scenario #3: The Blinded Block Trap (Route Roulette's Legal Exposure)

"Route Roulette" has a legal definition now. The FTC's February 2026 enforcement framework explicitly classifies accept-first, destination-later shift structures as a transparency violation when the withheld information would materially affect a worker's decision to accept — and destination, distance, and estimated duration always qualify as material.

The operational mechanics are well-documented: Lyft and Uber block shifts, Amazon Flex blocks, and certain DoorDash "Earn by Time" offers present workers with a flat hourly rate and a shift window, but withhold pickup and dropoff geography until after acceptance. The real-world consequence is severe. A worker accepting a three-hour block at a disclosed $18/hour rate may discover a 45-minute unpaid highway repositioning commute at the block's start — effectively compressing three hours of paid time into 2.25 productive hours, dropping their real rate to approximately $13.50/hour before fuel costs.

Under the FTC's 2026 gig enforcement priority, platforms must now disclose estimated trip duration, total distance, and destination region before a worker accepts any block or shift structure. "Destination region" is defined as sufficient geographic specificity to allow a reasonable worker to estimate drive time and fuel cost.

What You Can Legally Demand Before Accepting a Block

1. Estimated total distance (pickup to final dropoff, not just segment-by-segment)
2. Estimated trip duration inclusive of any repositioning time
3. Destination region at minimum zip-code-level granularity
4. Effective hourly rate calculation based on disclosed duration vs. block pay

Critically, workers now have the legal standing to refuse blocks that don't meet their disclosed hourly-rate threshold without algorithmic penalty — meaning platforms cannot deprioritize your offer queue for declining non-compliant blocks. If your platform's acceptance-rate metric penalizes you for refusing an undisclosed-destination block, that penalty mechanism itself is a secondary FTC violation. Document every refusal with a screenshot of the non-disclosing offer screen.

Your Recourse Playbook: Filing an FTC Wage Complaint & Documenting Evidence

Knowing your rights is worthless without a filing mechanism. Here is the exact operational sequence for converting a documented wage-transparency violation into a formal federal complaint — one that carries real enforcement weight under the February 2026 framework.

Step 1: File at reportfraud.ftc.gov. Select "Gig Economy / Wage Transparency" as your complaint category. The FTC's February 2026 enforcement memo commits to a 90-day investigation window for wage-opacity complaints — a defined timeline that did not previously exist and signals genuine enforcement intent rather than complaint archiving.

Required Documentation Package

• Pre-acceptance screenshots: Timestamped offer screens showing disclosed pay, fees, and any destination/duration information (or its absence)
• Post-completion earnings records: Platform earnings dashboard exports showing actual net deposits
• Variance calculation: A simple spreadsheet comparing disclosed vs. actual pay across a minimum of five shifts
• Fee itemization gaps: Screenshots where deduction categories appear in your deposit record but were absent from the pre-acceptance screen
• Shift timestamps: Start/end times cross-referenced against platform-reported active time to identify unpaid repositioning periods

Beyond the FTC process, wage-opacity violations carry potential Fair Labor Standards Act (FLSA) exposure when platform deductions push effective hourly compensation below the federal minimum wage of $7.25/hour — or below applicable state minimums. If your documented net hourly rate (total deposit ÷ total hours including unpaid repositioning) falls below your state's minimum wage floor, you have a concurrent FLSA claim that can be filed with the Department of Labor's Wage and Hour Division, independent of your FTC complaint.

Class-action leverage is the downstream multiplier. Individual FTC complaints that share a common algorithmic mechanism — identical undisclosed fee structures, identical blinded-block architectures — are being aggregated by plaintiff's firms monitoring the FTC complaint database. Your individual filing contributes to the evidentiary record that triggers class certification. The documentation discipline you apply to a single shift dispute may ultimately fund a settlement that covers thousands of workers on the same platform.

The Bottom Line

Start documenting your pay disclosures today by screenshotting the promised hourly rate before accepting your next five shifts, then compare actual earnings against what was shown. If your real hourly rate falls short of the disclosed amount, file an FTC complaint immediately with your screenshots attached. This single action creates an official record that strengthens class action cases against gig platforms and directly contributes to settlements benefiting thousands of workers. Your documentation discipline matters—each complaint filed adds weight to the evidentiary record that regulators and courts use to hold platforms accountable for wage violations.

For the complete 2026 picture, read our full guide →

This content is for informational purposes only and does not constitute financial advice. Always consult a qualified financial professional.