Common Causes of OS/OW Route Failure

Common Causes of OS/OW Route Failure

Most route failures happen before permits are filed — caused by missing constraints, unverified assumptions, and fragmented data.

Read time: 5 min

Route failures rarely happen because of physics. They happen because of process breakdowns.

**1. Missing Constraints** Field conditions that weren't surveyed or weren't documented. The bridge that was "probably fine" but wasn't. The utility line that grew lower over time.

**2. Unverified Assumptions** Published data used without field verification. Height clearances from databases that haven't been updated in years. Weight limits that changed after a bridge inspection.

**3. Poor Communication** Information that existed but didn't reach the right people. The surveyor knew about the constraint. The permit application didn't mention it. The driver wasn't briefed.

**4. Fragmented Data** Survey data in one system. Photos on someone's phone. Permits in email. Route changes tracked nowhere. When information is scattered, decisions are made without complete context.

**5. Decision Drift** Routes approved based on one load configuration, then executed with a different configuration. Assumptions that were valid last month may not be valid today.

The solution is not more data — it's structured data, verified data, connected data, and traceable decisions.

Knowledge Base · Fundamentals