LB771 amends Neb. Rev.
Stat. §75-327 to impose explicit consumer-disclosure and rate-filing obligations on transportation network companies (TNCs) that use dynamic pricing, while also changing how surge pricing is treated during gubernatorially declared states of emergency. The bill requires TNCs to file the rates and any dynamic-pricing methodology with the commission, to keep filings current, and to charge consistently with those filings.
In addition to the filing duty, the bill mandates three app-level consumer protections: a clear visible notice when dynamic pricing is active, an express passenger confirmation before completing a request, and a fare estimator that provides a pre-request cost estimate. The text also inserts language about gubernatorial control over dynamic pricing during declared emergencies but contains internal contradictions that will create implementation and enforcement questions for regulators and platforms alike.
At a Glance
What It Does
LB771 requires TNCs to file the rates and any dynamic-pricing mechanisms they use with the commission and to charge in accordance with those filings. It mandates three concrete in-app consumer protections: visible notice when surge pricing applies, an affirmative passenger confirmation to proceed, and a pre-request fare estimator.
Who It Affects
The bill directly affects any transportation network company operating in Nebraska and their online-enabled applications or platforms, the participating drivers who supply rides, and passengers who request rides — especially during emergencies. The commission (the statutorily referenced regulator) will receive and monitor rate filings.
Why It Matters
The measure increases regulatory oversight of opaque surge-pricing algorithms and elevates consumer-facing safeguards, potentially forcing app redesign and new compliance workflows. It also changes the legal landscape for surge pricing during state emergencies, creating uncertainty for emergency managers, platforms, and consumers about when surge pricing is lawful.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
LB771 keeps several baseline rules already in §75-327 — notably that rides must be prearranged and that a participating driver cannot be on duty more than twelve hours in any 24-hour period — but the primary changes focus on pricing and transparency. The bill makes explicit that TNCs must file the rates they use to compute fares, including any dynamic-pricing methodology, with “the commission.” It requires those filings to be kept current and obliges companies to charge fares consistent with the filed schedules or mechanisms.
On the consumer side, the statute now prescribes three specific app features. First, the platform must display a clear, visible indicator that dynamic pricing is active before a passenger submits a ride request.
Second, the app must force the passenger to provide an express confirmation that they understand dynamic pricing will apply as a precondition to completing the request. Third, the platform must offer a fare estimator that allows the passenger to estimate the cost under dynamic pricing before requesting the ride.
Those requirements are mechanically precise but leave open implementation questions — for example, what level of granularity the estimator must provide (a range versus a calculated amount) and how long disclosures must remain visible.The bill also revises the statutory treatment of dynamic pricing during states of emergency. One clause empowers the Governor to permit dynamic pricing in political subdivisions specified in a state-of-emergency declaration unless the Governor explicitly prohibits it in the proclamation or an executive order.
Another clause, however, states categorically that "dynamic pricing shall not be permitted during any state of emergency declared by the Governor." As written, the language creates a direct conflict about whether surge pricing is allowed in an affected area and under what circumstances, which will force regulators and courts to resolve the inconsistency.Finally, LB771 preserves and restates existing transaction-level transparency: after a prearranged ride concludes, the TNC must send an electronic receipt showing origin and destination, duration and distance, total paid (broken down by base fare and additional charges), and the driver's first name. That receipt requirement sits alongside the new pre-request protections and the filing obligation, forming a package of transparency measures targeted at both pre-sale disclosure and post-trip recordkeeping.
The Five Things You Need to Know
The bill requires TNCs to file the rates and any dynamic-pricing methodology used on their platform with the commission and to keep those filings current and enforceable.
Before a passenger can complete a ride request when dynamic pricing applies, the platform must (1) show a clear visible indicator that surge pricing is active, (2) require the passenger to expressly confirm they understand dynamic pricing, and (3) provide a fare estimator allowing a pre-request cost estimate.
LB771 retains a strict duty for TNCs to send an electronic receipt after each prearranged ride showing origin and destination, total duration and distance, a breakdown of amounts paid, and the driver's first name.
The statutory language attempts to give the Governor control over whether dynamic pricing is permitted in political subdivisions named in a state-of-emergency declaration, but another clause in the same section also states that dynamic pricing is not permitted during any state of emergency.
TNCs remain broadly exempt from traditional rate regulation under sections 75-101 to 75-158, but the filing requirement creates a separate reporting and compliance obligation specific to platform rates and surge algorithms.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Prearranged rides and driver-hour limits
This provision reiterates that rides must be prearranged and caps a participating driver's on-duty time at twelve hours in any twenty-four-hour period. Practically, that preserves safety-oriented work-hour limits and keeps the TNC model within the prearranged-ride framework rather than treating services as on-demand taxi services; enforcement will fall to the entities tasked under the statute, though the bill does not add new enforcement mechanics for these rules.
Rate-exemption plus a new filing duty
Subsection (b) confirms that TNCs are not subject to the state's standard rate-and-charges framework under sections 75-101 to 75-158, preserving a degree of regulatory light-touch. Subsection (c) creates a carve-out: despite that general exemption, TNCs must file the rates they use to calculate fares — explicitly including any dynamic-pricing formulas — with the commission, maintain current filings, and ensure passenger charges align with those filings. That combination keeps algorithmic pricing out of traditional rate caps while subjecting it to a reporting and consistency obligation.
App-level consumer protections for dynamic pricing
These three clauses impose concrete user-interface requirements: a visible notice that dynamic pricing is in effect, an affirmative confirmation step from the passenger, and a fare estimator providing an expected cost under dynamic pricing. For platforms, this means design changes, additional user flows, and potentially logging and audit trails to demonstrate compliance. The statute specifies the obligations but leaves technical specifics (e.g., the precision of the fare estimator or the timing/placement of the notice) to implementation unless the commission adopts later guidance.
Emergency-period dynamic-pricing language
Clause (iv) addresses dynamic pricing during gubernatorial states of emergency. It first states that, at the Governor's discretion, dynamic pricing is permitted in political subdivisions named in a declaration unless the Governor expressly prohibits it. Immediately after, it provides that dynamic pricing "shall not be permitted during any state of emergency declared by the Governor." That contradictory pair of sentences is embedded in the operative text and will create ambiguity about whether a proclamation can allow or prohibit surge pricing and whether the blanket ban applies statewide during an emergency.
Trip receipts and transaction-level transparency
Subsection (3) requires TNCs to send an electronic receipt after completion of a prearranged ride showing origin/destination, total duration and distance, the total amount paid with a breakdown, and the driver's first name. This establishes a minimum post-trip disclosure standard that supports consumer disputes, audits of filed rates, and recordkeeping, but the bill does not specify retention periods, dispute resolution processes, or penalties for noncompliance.
This bill is one of many.
Codify tracks hundreds of bills on Transportation across all five countries.
Explore Transportation in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Passengers in Nebraska — the required visible notice, express confirmation, and fare estimator reduce the chance of surprise surge fares and give consumers meaningful information before they commit to a ride.
- State emergency managers and the Governor's office — the statute centralizes authority over whether dynamic pricing may apply during declared emergencies (even if the language is internally inconsistent), giving the executive branch a lever to influence market behavior during crises.
- Regulators (the commission) — the rate- and-methodology filing obligation provides the commission with more data and a paper trail for oversight and potential audits of platform pricing practices.
- Consumer advocates and litigants — the receipt and pre-request-disclosure requirements create documentary evidence that can be used in complaints, enforcement actions, or litigation over deceptive pricing practices.
Who Bears the Cost
- Transportation network companies — they must update platform UI/UX to add persistent visible indicators, confirmation workflows, and a fare estimator; prepare and maintain rate/dynamic-pricing filings; and implement operational controls to ensure charging consistency with filed rates.
- Smaller or regional platforms — compliance and legal costs to craft filing materials and redesign apps are proportionally larger for smaller operators, which could raise barriers to entry or push consolidation.
- The commission — the agency will receive new filings and will need resources to review and monitor them even though the bill does not appropriate enforcement funding, creating an unfunded administrative duty.
- Drivers — while the bill preserves driver-safety hour limits, drivers may face business-model impacts if emergency-era prohibitions on dynamic pricing remove surge incentives in high-demand or hazardous conditions.
Key Issues
The Core Tension
The bill tries to reconcile two legitimate but competing goals — preventing surprise or exploitative surge pricing for consumers (especially during emergencies) while preserving platforms' ability to use dynamic pricing to allocate scarce driver supply and manage demand — but the drafting forces regulators to choose between strict consumer protection and preserving market responsiveness, a choice the text does not cleanly make.
The most consequential implementation challenge is the bill's self-conflict on emergency pricing. One clause appears to allow the Governor to permit dynamic pricing in named political subdivisions unless expressly prohibited, while another clause flatly bars dynamic pricing during any state of emergency.
That contradiction will require judicial or administrative interpretation, leaving platforms uncertain about whether to disable surge features when a statewide or local emergency is declared and exposing consumers to uneven treatment across jurisdictions.
Beyond the drafting inconsistency, LB771 delegates substantial interpretive work to the commission without specifying review standards, timelines, or penalties for noncompliance. The statute requires filing of "rates" and any dynamic-pricing use, but it does not define how granular a filed methodology must be (e.g., exact algorithm, parameters, caps, or historical multipliers).
That gap creates questions about trade secrets versus disclosure, how the commission will audit algorithmic compliance, and what constitutes charging "consistent with" a filing when real-time factors drive slight deviations. The bill also omits dispute-resolution mechanisms for passengers who receive a fare substantially different from an estimator and provides no explicit enforcement mechanism for the app-disclosure requirements.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.