I'm currently using Revit 2025. I'm setting up a door schedule and door hardware schedule, and find the Schedule Keys to be a useful, but restricted feature. Doors are frequently scheduled in more than one grouping, typically this might be Internal Doors and External Doors. The former often by an internal works contractor, the latter by a facade specialist. The projects I work on, we actually typically have 3 different schedules for new-build works, split between a cleanroom area, non-cleanroom internal works, and external facade related work. In this breakdown, there will be numerous elements that are common, but it is also quite possible for there to be differing ones between each door location group. Weatherstripping would not apply internally, an external door might not have some other feature, card readers are unlikely outside of key rooms. In Architectural documentation, rather than having a schedule printed out long form, with every possible parameter indicated, it is quite usual for their to be hardware groups instead, with the door schedule referring to the hardware group, and the group itself scheduled separately. The user looks at the hardware group only, then applies to the doors as required. This is easier to manage and simpler to understand. Revit gets part of the way there, allowing for Schedule Keys to manage the list in groups, but gives no way to display this differently, for differing circumstances. It's all or nothing, whether it applies, or not. A differing scenario might be room finishes, where one room group is (say) offices, and another is (say) bathrooms. Because some of the same fields might be used, one schedule key only can created and published, when it would make sense to have some difference between them. I can understand it from the viewpoint that data can only have one value, but there is also only one way for this to be reflected in a printed schedule, as there is no way to apply a view template where some of the fields could be hidden, so at least the content could be different where required, otherwise the one schedule could be providing information that absolutely will never apply, simply because Revit is forcing it. This restriction makes no sense to me. Could there be some flexibility in how Schedule Keys are done, to make this an actual useful tool please, preferably before I retire in the next 15 years.
Show More