Door hardware sets for Revit

Door hardware, organized inside Revit.

Group doors into hardware sets, let built-in checks catch the door that doesn’t belong, and write set names straight to your door schedule. No spreadsheets. No retyping.

Plan diagram: every patient room door in one hardware setA hospital corridor with eleven doors. The seven doors that open into patient rooms are in hardware set HW-04, its checks pass, and each door is tagged HW-04. The stair, utility rooms, and nurse station doors are in other sets.SET HW-04 · Patient room✓ Same rating ✓ Hinges ✓ LockingPATIENT201PATIENT202CLEAN UTIL203PATIENT204PATIENT205STAIR206NURSE STN210PATIENT211PATIENT212SOILED UTIL213PATIENT214HW-04HW-04203HW-04HW-04206210HW-04HW-04213HW-04CORRIDORHW-04 · Patient room · 7 of 11 doors
Fig. 1 — One set, seven doors, checked and on the schedule.
01The problem

Nobody edits walls one at a time. Why do it with door hardware?

Walls, rooms, finishes, and equipment all live in the model as connected data. If every one-hour wall changes, the model finds them. Door hardware still runs on spreadsheets, spec books, and markups, with the architect cross-referencing it all by hand.

  1. 01.1

    Sets live outside the model

    Hardware sets tracked in spreadsheets drift out of sync the moment the plan changes.

  2. 01.2

    Every door checked by hand

    Room names, door types, fire ratings, and owner standards cross-referenced one opening at a time.

  3. 01.3

    The wrong question

    Teams ask “which doors do I need to update?” The better question is “what defines this group of doors?”

That’s not a hardware problem. It’s a workflow problem.

02How it works

Group the doors. dRVT checks the set.

  1. Add doors to a set in one move

    Every door in the model, in one list. Select the ones that share hardware and add them to a set together. Pick the hardware once for the whole set.

  2. dRVT checks they belong together

    Same fire rating, hinges that suit the sizes, locking picked. A door that doesn’t match gets flagged before it reaches the schedule.

    SET   03 Office · 18 doors
    CHECK ✓ Same rating (non-rated)
    CHECK ✓ Hinges suit the door sizes
    CHECK ✓ Locking picked
    WRITE Hardware Set = "03 Office"
  3. Onto the schedule, and into your specs

    dRVT writes the hardware set name to each door, so your door schedule is current without retyping a cell. Then export every set to Word for your firm’s specifications.

The full workflow, and what’s next

03What it does today

What it does now, and what’s next.

Here is exactly what dRVT does today, and what we’re building next. Early users help decide the order.

Available now

  • Add doors to a set in one move

    Every door in the model in one list. Search, filter by level and phase, select the doors that share hardware, and add them to a set together.

  • Built-in checks on every set

    Each set checks that its doors belong together: same fire rating, hinges that suit the sizes, locking picked. Doors that don’t match get flagged.

  • Specify hardware once per set

    Pick hinges, locks, stops, and silencers for the set, not door by door. Every door in the set gets it.

  • Write the set name to your schedule

    Apply to model writes the set name to the door parameter your schedule already reads. No separate spreadsheet to keep in sync.

  • Export sets for your specifications

    Export every set to a Word document: a description, its doors, and each component with quantity, finish, and manufacturer. Bring it into your firm’s own specifications.

On the roadmap

  • Sets that keep up with the plan

    Save what defines a set and run it again, so new and changed doors pick up the right hardware.

  • More checks

    Flag more common conflicts, like hardware that doesn’t suit a door’s type or rating, or your office standards.

  • Reusable set libraries

    Carry your office’s hardware sets from project to project instead of rebuilding them.

  • Assignment history

    A record of what changed, when, so a set revision is easy to review.

Roadmap items are planned, not promised. dRVT supports your judgment and your consultant’s review; it does not certify code compliance.

04From the blog

Notes on hardware, code, and workflow.

All posts
05 · Waitlist

Stop managing doors one at a time.

Join the waitlist for early access to dRVT. Tell us how your firm handles hardware today and help shape what gets built next.

Join the waitlist