Is CDO built for roofing crews specifically?
Yes — CDO is piloting with a 65-person roof tear-off crew in Southern California, and the product was shaped around that reality: gloves, sun, Spanish, GPS, and the wage-and-hour rules that hit outdoor trades hardest.
How does CDO handle heat-recovery breaks?
Cal/OSHA entitles outdoor workers to paid cool-down recovery periods whenever needed — and denying one costs the same one-hour premium as a missed rest break. CDO tracks breaks live and keeps the record that proves recovery was provided. The full rules — shade at 80°F and high-heat procedures at 95°F — are in the Cal/OSHA §3395 guide.
Can my crew clock in with gloves on?
Yes — 56dp touch targets, a high-contrast theme built for direct sun, bilingual prompts, and GPS geofence verification in the same gesture as the punch.
What does CDO cost for a roofing company?
$29–49 per user per month — $29 for 1–10 people, $39 for 11–40, $49 for 41 or more — with no setup fees, every AI feature on every plan, and a first-month guarantee. For a 20-person roofing outfit that's $780 a month.
Does CDO replace AccuLynx or JobNimbus?
Usually not — they solve a different half of the business. Roofing-specific platforms are built around selling and documenting the job: estimating, aerial measurement, insurance supplements, photo documentation, sales pipeline. CDO is built around the crew and the law: the time clock, GPS verification, break and overtime compliance, payroll, safety, and HR records. Many roofing companies keep both. If you want CDO to carry estimating and invoicing too, it does that natively — but the deep insurance-claim workflows live on the roofing tools.
Is drive time from the yard paid for roofing crews?
In California, generally yes. Under Morillion v. Royal Packing (2000), travel the employer requires — such as riding a company truck from the yard to the site when the company requires the ride — is compensable hours worked, because the worker is under the employer's control. The consequence most crews miss is the knock-on effect: if the day started at the yard at 5:40 AM, the meal must start no later than the end of the fifth hour, 10:40 AM, not 11:40. CDO captures truck-start, arrival, and departure as distinct events so the meal clock runs from the right moment.
What about crews working in more than one state?
The rule engine applies the law of the state the work happened in, not a single global setting. That matters more than it sounds: Nevada has daily overtime but only below a pay threshold, Colorado owes overtime past 12 consecutive hours regardless of calendar day, Washington and Oregon have enforceable outdoor heat standards while Texas and Florida have laws preempting local ones. See labor rules by state for the full picture.
Our crew is mostly Spanish-speaking. How well does that actually work?
Spanish is the default, not a translation layer. Every prompt, break attestation, exception explanation, safety acknowledgment, and policy document exists in both languages, auto-detected per worker — and both versions are kept for the legal retention period. That last part is the one that matters legally: if a worker signed a meal-period waiver in Spanish, the Spanish document is what an auditor or hearing officer reads, timestamped, rather than an English record of a Spanish moment.