My $2,800 Spec Mistake: What a Dorner Vineyard Project Taught Me About Details

Posted on 2026-06-05

Industrial article header

I didn't believe in double‑checking spec sheets until I wasted $2,800 on a single order. That was in 2013—the same year the Christopher Dorner manhunt dominated headlines, though I was too buried in my own mess to pay attention.

At the time I was handling my first major install for a vineyard in Tehachapi. The client, a small family winery, had ordered a custom Dorner 2200 conveyor system to move grape crates from the press to the barrel room. I was eager to impress—and stupidly overconfident.

My team had two senior technicians: Trevor and Chauvin. Trevor kept nagging me to confirm the belt material before we placed the order. "You sure about hawk vs eagle?" he'd ask. "They look similar but the load ratings are totally different." I waved him off. Chauvin, who had more years on the job, said, "Relax, these spec sheets are standard. Just order what matches the drawing."

I went with Chauvin's advice. The drawing said "belt type: HD‑Eagle," but I skimmed it and saw "HD‑Hawk" in a different version of the file. I ordered 150 feet of Hawk grade belting at $18.70 per foot—$2,805 total, not counting freight. The order was placed on a Friday. Monday morning, the vineyard manager called: "The belt you sent says Hawk. Our system was spec'd for Eagle. Hawk won't handle the weight—it'll stretch and slip within a month."

I felt my stomach drop. I checked the file again. There it was, clear as day: Eagle. I had clicked the wrong dropdown. The vendor, Dorner Inc., had shipped exactly what I ordered. No returns on custom-cut belting. $2,805 down the drain, plus a two‑week delay while we sourced Eagle belt at rush pricing.

That mistake hit hard. It wasn't just the money—it was the embarrassment. Trevor had warned me three times. I had dismissed him. Chauvin's casual confidence had been wrong in this case, but I was the one who signed off. I spent the next month writing a detailed specification checklist that I still use today.

Looking back, the real lesson wasn't "always check specs"—I knew that. It was how to check. I now force myself to read the spec aloud to someone else before I approve. I also flag any ambiguity like "Hawk vs Eagle" as a red flag and demand written confirmation from the client.

Since that incident, our team has caught 47 potential spec errors using this checklist in the past 18 months. Total savings? Roughly $38,000 in prevented re‑orders. Not bad for a lesson that cost me $2,800 and a bruised ego.

The bottom line: even if you've done a hundred orders, the one you rush through is the one that bites you. That vineyard in Tehachapi? They eventually got their Eagle belt and the system ran fine. But I'll never forget how my shortcut made their harvest season more stressful than it needed to be.