• Registration is manually approved during the forum's testing period Регистрация одобряется вручную на период тестирования форума

Cable tray schedules that stay useful after route changes in Revit

web3d

Administrator
Staff member
After a few rounds of coordination, cable tray routes rarely remain as first modeled. The drawing still communicates the path, but the schedule can become hard to trust if fittings, risers, and branches are represented differently by each person.

What information do you include in a Revit cable tray schedule so it stays useful for design review and handoff when routes change?

  • Do you schedule tray runs by system, area, or another grouping that makes review easier?
  • How do you account for fittings and vertical transitions without making the schedule unreadable?
  • Which fields help you spot disconnected or misclassified segments after a route edit?
  • Do you compare scheduled lengths with a separate takeoff, or rely on the model alone?

Im interested in practical schedule layouts that give the team enough detail without creating a maintenance burden. If you have a template or checking routine that works, please share what you include.
 
Hey, this is a constant headache on our jobs too. After a few coordination rounds those trays never stay where they were first modeled.

We keep the schedule useful by grouping first by Level, then by System (Power, Lighting, LV/Data, Fire). Reviewers can jump to a floor and a trade without scrolling forever.

Straight runs go in one schedule: Type, Width x Height, Length, Level, and a simple From/To zone or room parameter. Fittings and verticals stay out of that length list. They get a separate count schedule — elbows, tees, crosses, reducers, vertical bends — grouped by size and type. We add a short Yes/No or “Riser” parameter so vertical transitions don’t disappear into the horizontal totals and the sheet stays readable.

Fields that catch trouble after an edit: Length (zero or tiny pieces usually mean a disconnect), System Classification (blank or wrong trade), Size consistency at connections, and a Comments field we make the team fill after any route change. Mark still matches the drawing callout so the schedule talks to the sheets.

We don’t rely on the model alone for quantities. We export to Excel and compare totals by system against a quick colored 3D takeoff or Navis check. If they diverge more than a couple percent, someone walks the changed areas.

The template stays lean on purpose — no extra parameters nobody will maintain. After each coordination round we filter for blanks, zero lengths, and mismatched sizes, then do a short 3D fly-through of the edited zones. That keeps it useful without becoming a second job.

How are you handling the verticals on your side? Those always mess with the totals.
 
Back
Top