Weather days, cancelled loads, and "there's no work today, go home" are ordinary operating events. Under the wage orders they are also pay events, and the construction wage order handles them differently from every other one.
An employee shows up for a scheduled ten-hour day. The pour is called off at 6:40 because the ready-mix cannot get up the access road. Everyone goes home at seven.
Nothing about that morning feels like a wage-and-hour event. Nobody worked off the clock, nobody skipped a break, the crew got an unexpected day, and the foreman is thinking about the schedule slip, not about payroll. But the wage orders treat it as a pay event, the obligation is small enough per occurrence that it rarely gets noticed, and it repeats across every employee on every volatile day for years — which is precisely the profile of a claim that shows up as one line in a PAGA notice and turns out to reach the whole workforce.
Neither obligation is in the Labor Code. Both are in the IWC wage orders, which is why they are easy to miss for anyone who compliance-checks by reading statutes. They reach PAGA through Labor Code §1198, which makes employment under conditions prohibited by the applicable wage order unlawful.
Reporting-time pay. An employee who reports for work as scheduled but is furnished less than half the scheduled day's work is owed pay for half the scheduled day — a minimum of two hours and a maximum of four. The employee in the example above was scheduled for ten hours, worked something under one, and is owed four.
Split-shift premium. Where the day is broken into nonconsecutive work periods separated by more than a meal period, most wage orders add one hour at the minimum wage. The classic version is the morning-and-evening schedule with a five-hour hole in it; the version operators actually create is the crew sent home at eleven and called back at three because the inspector finally showed.
Both are wages, with the ordinary three-year look-back. In a PAGA action, the wage-order violation carries the post-reform default civil penalty per aggrieved employee per pay period, distributed 65 percent to the LWDA and 35 percent to employees. The reasonable-steps caps at §2699(g) and (h) sit on that penalty the way they sit on every wage-and-hour penalty, with the qualifications that make them a ceiling and not a number.
If the work is construction, drilling, logging, or mining, the governing instrument is Wage Order 16, and it differs from Orders 1 through 15 in ways that change the answer rather than the phrasing. Two of the differences hand the employer something. One takes something back. All three are invisible to a payroll configuration copied from a general-industry template, which is where most payroll configurations come from.
There is no split-shift premium in Wage Order 16. The order defines "split shift" — but it does so in §2(Q), for the purpose of the §6 records requirement, not to create a premium. A construction employer that splits a day does not owe the extra hour. It does still have to record the split-shift interval, and a great many do not, because they were never told there was anything to record.
Reporting time carries the same formula and a different trigger. Section 5(B) pays what the general orders pay — half the usual or scheduled day's work, two-hour minimum, four-hour maximum, at the regular rate. The trigger is worded differently, and the difference is not cosmetic. The general orders are keyed to an employee "required to report for work and does report." Wage Order 16 says "required to report to the work site and does report." One phrase is about presenting yourself as the employer directed; the other names a place. Wage Order 16 also omits the second-reporting rule the general orders carry, under which an employee required to report a second time in a day and furnished less than two hours of work is owed two hours.
Travel between reporting locations is separately compensable. Section 5(A) requires payment for employer-mandated travel after the first reporting location — a rule with no counterpart in the general orders, and one that fits construction's actual geometry, where the yard is where you report and the site is where you work.
And there is a CBA lever: §5(D) permits a valid collective bargaining agreement to expressly provide otherwise on reporting time. That is separate from the PAGA exemption at Labor Code §2699.6, which can put covered construction work outside PAGA altogether where every one of its conditions is met — a per-agreement question for counsel, never a status to assume from the fact that a CBA exists.
The net of it is worth sitting with: a construction employer running general-industry payroll settings can be paying a split-shift premium the governing order does not require, while missing the travel payment §5(A) does. Both errors come from one source, which is a template that was never checked against the order that actually applies.
For logistics, there is no equivalent carve-out. Warehouse and driver populations under Wage Order 9 get the full set of provisions — including the second-reporting rule, and including the "report for work" trigger the general orders share. The recurring fact pattern is the cancelled load: a driver reports for a dispatch that evaporates and is released after twenty minutes.
That trigger wording is also where the less familiar half of this rule lives. The send-home is the half everybody pictures: a crew drove to the yard, so it plainly reported. The other half is the schedule that asks an employee to make contact before the shift instead of showing up for it — call the dispatcher two hours out, check the app the night before, watch the group text for a yes or a no. Whether that contact is itself reporting for work has been the subject of California litigation, and it is a legal question on your facts. Ask your counsel rather than a vendor, including us.
What an operator can settle without reaching any legal conclusion is whether the practice exists and whether it is written down anywhere. Most call-in scheduling is not a policy. It is a habit that grew out of a group text, has never been described in a document, and is known only to the dispatcher who runs it and the people who answer him. A practice nobody wrote down is a practice the employer cannot describe later — which leaves the describing to whoever is doing it in a deposition.
Operators tend to believe an act of God ends the analysis. Something like that is in the order, and the boundary is narrower than the version repeated on job sites.
Section 5(C) of Wage Order 16 says the reporting time pay provisions "are not applicable when: (1) Operations cannot commence or continue due to threats to employees or property; or when recommended by civil authorities; or (2) Public utilities fail to supply electricity, water, or gas, or there is a failure in the public utilities, or sewer system; or (3) The interruption of work is caused by an Act of God or other cause not within the employer's control." Provisions to similar effect appear in the other orders, and they are worth reading in the order that governs a given population rather than assumed from this one.
The load-bearing words are the last seven: "or other cause not within the employer's control."
Read that against the ordinary rain day. Rain that makes a pour inadvisable is a scheduling decision by an employer about a foreseeable condition. Rain that flooded the site or dropped the power is a different fact. Everything turns on whether the cause was within the employer's control — which is a question about what happened on one particular morning, and a question of that kind is answered with evidence or it is not answered at all.
Which produces the operational point of the whole post. The exception is real, it is available, and it is available only to an employer who can say what happened. It is proved by a note somebody wrote at 6:45 that morning, naming the condition and naming who made the call. It is not proved two years later by a lawyer with a weather archive and a foreman who does not remember the day.
Four artifacts, none of them expensive, all of them worth more created contemporaneously than assembled later:
Then the second half, which is the half that decides cases: when a send-home occurs and no premium is paid, something in the file has to say why — the exception relied on, and the facts as of that morning. A log with entries and no dispositions is a documented series of pay events with a documented absence of any response to them, and that is a worse artifact than no log.
Stated plainly: per event, these are small numbers. The premium is capped at four hours, and no single send-home is a case.
What earns this row a line in a diagnostic is that it never stays a single send-home. The count is scheduling volatility times headcount times three years, and scheduling volatility is the defining characteristic of both construction and freight — that is what weather is, and that is what a cancelled load is. It accumulates without a single person complaining, because nobody in the field knows the rule exists.
And the premium does not travel alone. An amount that was owed and never paid is also an hours-and-wages figure that never reached the wage statement, and §226(e)(2)(B) asks whether an employee can determine the required information "from the wage statement alone." Whether a given statement falls short of §226(a) is counsel's call. Whether the amount appears on it at all is not a legal question, and it is answered by pulling one stub from a week somebody got sent home.
The discovery call is the right starting point if you want your send-home practice read against the wage order that governs each of your populations. Bring one season of schedules and the payroll register for the same season. We can tell you which days show a crew scheduled long and furnished short, and whether anything in payroll was ever coded against those days. Whether a premium was owed on a given morning, and whether that morning fell inside an exception, is a legal question on your facts and it belongs with your counsel.