WSR 23-07-124
PERMANENT RULES
DEPARTMENT OF
LABOR AND INDUSTRIES
[Filed March 21, 2023, 1:03 p.m., effective April 21, 2023]
Effective Date of Rule: Thirty-one days after filing.
Purpose: The amendments correct inadvertent errors in WAC 296-128-99050 and 296-128-99290 and update WAC 296-128-99030 for clarity, all filed under WSR 22-24-034 on November 30, 2022. The adopted language clarifies that a 12-month period is an acceptable interpretation of the 365 calendar day requirement outlined in WAC 296-128-99030 (2)(g) adopted effective January 1, 2023. The adopted amendments only correct typographical errors or clarify language of a rule without changing its effect.
Citation of Rules Affected by this Order: Amending WAC 296-128-99030, 296-128-99050, and 296-128-99290.
Statutory Authority for Adoption: RCW 49.46.300(16); chapter 49.46 RCW.
Adopted under notice filed as WSR 23-03-093 on January 17, 2023.
Number of Sections Adopted in Order to Comply with Federal Statute: New 0, Amended 0, Repealed 0; Federal Rules or Standards: New 0, Amended 0, Repealed 0; or Recently Enacted State Statutes: New 0, Amended 0, Repealed 0.
Number of Sections Adopted at the Request of a Nongovernmental Entity: New 0, Amended 0, Repealed 0.
Number of Sections Adopted on the Agency's own Initiative: New 0, Amended 3, Repealed 0.
Number of Sections Adopted in Order to Clarify, Streamline, or Reform Agency Procedures: New 0, Amended 0, Repealed 0.
Number of Sections Adopted using Negotiated Rule Making: New 0, Amended 0, Repealed 0; Pilot Rule Making: New 0, Amended 0, Repealed 0; or Other Alternative Rule Making: New 0, Amended 0, Repealed 0.
Date Adopted: March 21, 2023.
Joel Sacks
Director
OTS-4298.1
AMENDATORY SECTION(Amending WSR 22-24-034, filed 11/30/22, effective 1/1/23)
WAC 296-128-99030Driver electronic receipts and weekly trip notices.
(1) Electronic receipts. Within 24 hours of each dispatched trip, a transportation network company must transmit to the driver an electronic receipt, available in a communication system, for each unique trip or portion of a unique trip. For the purposes of an electronic receipt, a transportation network company may either provide a downloadable comma-separated values file or searchable PDF format containing a table with rows for each unique trip or portion of the trip and columns for each itemized element contained in the trip receipt. Electronic receipts must be available to the driver for at least two years following the date the transportation network company provided the receipt to the driver. The electronic receipt must itemize the following information for each unique trip, or portion of a unique trip:
(a) The total amount of passenger platform time;
(b) The total mileage driven during passenger platform time;
(c) The applicable rate(s) of pay including, but not limited to, the rate(s) per minute, rate(s) per mile, percentage of passenger fare, and any applicable price multiplier(s) or variable pricing policy in effect including variable rates based on geographic location;
(d) Any tip compensation paid by the passenger within 24 hours of the dispatched trip;
(e) Gross payment;
(f) Net payment after deductions, fees, tolls, surcharges, lease fees, or other charges;
(g) Itemized deductions or fees, including any tolls, surcharges, commissions, lease fees, and other charges;
(h) The applicable date and time frame for each trip and each portion of a trip; and
(i) The passenger pick-up and passenger drop-off locations for each trip and each portion of a trip as described by the street, city, and state in which the passenger pick-up and passenger drop-off occurred; however, if the passenger is an unaccompanied minor, only the city and state need be disclosed.
(2) Weekly trip notices. At least once a week, a transportation network company must transmit to the driver a written notice, available in a communication system, that contains the following information for trips, or portions of trips, which occurred in the prior week:
(a) The driver's total passenger platform time;
(b) Total mileage driven by the driver during passenger platform time;
(c) The driver's total tip compensation received from passengers within the prior week, itemized by the date of each dispatched trip or portion of a dispatched trip;
(d) The driver's gross payment, itemized by:
(i) Rate(s) per minute;
(ii) Rate(s) per mile; and
(iii) Any other method used to calculate pay including, but not limited to, base pay, percentage of passenger fare, or any applicable price multiplier(s) or variable pricing policy in effect for the trip, including variable rates based on geographic location;
(e) The driver's net payment after deductions, fees, tolls, surcharges, lease fees, or other charges;
(f) An itemization of deductions or fees, including all tolls, surcharges, commissions, lease fees, and other charges, from the driver's payment; and
(g) The total passenger platform time performed within the past 365 calendar days or the last 12 full calendar months immediately prior to the date the weekly notice is provided to the driver.
AMENDATORY SECTION(Amending WSR 22-24-034, filed 11/30/22, effective 1/1/23)
WAC 296-128-99050Geographic application of RCW 49.46.300 minimum compensation requirements.
(1) A transportation network company must pay drivers in accordance with RCW 49.46.300(4) as follows:
(a) For a dispatched trip with a passenger pick-up location in Washington all minimum compensation requirements under RCW 49.46.300(4) apply for the entirety of the trip, regardless of the passenger drop-off location; and
(b) For a dispatched trip with a passenger pick-up location outside of Washington all minimum compensation requirements under RCW 49.46.300(4) apply for the portion of a trip that occurs within Washington.
(2) For a dispatched trip with a passenger pick-up location in a city in the state of Washington with a population above 600,000, all minimum compensation requirements under RCW 49.46.300 (4)(a)(i) apply, regardless of the passenger drop-off location.
(3) For a trip with a passenger pick-up location in the state of Washington outside a city with a population above 600,000 and a passenger drop-off location inside a city with a population above 600,000 in the state of Washington, the greater of:
(a) The combined total of:
(i) The per minute and per mile minimum compensation requirements under RCW 49.46.300 (4)(a)(i) applied to the portion of passenger platform time or mileage that occurs within the city with a population above 600,000; and
(ii) The per minute and per mile compensation requirements under RCW 49.46.300 (4)(a)(ii) applied to the portion of passenger platform time or mileage that occurs outside the city with a population above 600,000; or
(b) The per trip minimum for a dispatched trip under RCW 49.46.300 (4)(a)(((1)))(i)(B).
(4) Shared rides. The greater of the per trip minimums in subsections (1), (2), and (3) of this section apply to the entirety of the shared ride if any portion of the shared ride meets the requirements of subsection (1)(a) or (b) of this section.
(5) More favorable standards. If any portion of a dispatched trip or shared ride is subject to a standard established by any applicable federal, state, or local law or ordinance in a locality outside of Washington, or any rule or regulation issued under such law or ordinance, which is more favorable to drivers than these minimum compensation requirements, such standard shall not be affected by this chapter and such other laws, or rules or regulations, shall be in full force and effect and may be enforced as provided by law.
AMENDATORY SECTION(Amending WSR 22-24-034, filed 11/30/22, effective 1/1/23)
WAC 296-128-99290Enforcement—Administrative enforcement supplemental and variance for delayed implementation of accessible system and communication system requirements.
(1) Nothing in these rules limits the department's authority to enforce RCW 49.46.200 through 49.46.350, or associated rules, as otherwise provided under Title 49 RCW.
(2)(a) A transportation network company that qualifies under (b) of this subsection may seek a temporary variance on the requirements for an accessible system or a communication system under this chapter by submitting a written application to the director.
(b) A transportation network company who provides less than 1,000,000 dispatched trips within the state in the preceding calendar year qualifies for the variance in this section. Separate entities that form an integrated enterprise shall be considered a single transportation network company under this rule as provided by RCW 49.46.300 (3)(b).
(c) This variance is limited to the requirements to use an accessible system or a communication system to communicate with drivers. The variance does not change the transportation network company's obligations to provide all notices, receipts, paid sick time balances and any other communications required by chapter 49.46 RCW and associated rules to the driver in an electronic format that is readily accessible through either a smartphone application or an online web portal.
(d) A written application for a variance must contain the following:
(i) A description of the specific requirements the qualifying transportation network company seeks to delay;
(ii) Reasons for the variance request, including good cause for the delayed implementation of the requirements for an accessible system or a communication system being sought;
(iii) The length of delay being sought for the requirement(s) and a timeline showing how the transportation network company plans to come into compliance with the applicable requirements of this chapter;
(iv) An explanation of how the transportation network company will ensure drivers are provided the required notifications under this chapter during the variance period; and
(v) Evidence confirming that the transportation network company qualifies under this subsection ((are met)).
(e) After reviewing the application, the director may grant a temporary variance to remain valid for up to one year if the director determines that the transportation network company meets the requirements of this section, will ensure that drivers are being provided all required notices under this chapter during the variance period, and has established good cause. The director will take into consideration the timeline provided in the variance application in determining the length of the variance.
(f) "Good cause" means the transportation network company can establish that it is infeasible for the company to come into full compliance with the requirements for the use of an accessible system or a communication system within the necessary time frame.
(g) The director may revoke or terminate the variance order at any time, upon at least 30 days' notice to the transportation network company.
(h) Upon further request by a transportation network company, the director may approve an extension of the variance for up to an additional year. An extension request must contain the information outlined in (d) of this subsection.
(i) If a transportation network company obtains a variance under these rules, within 15 days of being granted the variance the transportation network company must provide drivers notice indicating how they will be receiving the required notifications under this chapter. The transportation network company must make this information readily available to all drivers.