Rhino Standards for Architectural Practice

Does anyone work in a architectural design practice that mainly uses rhino for their design and documentation?

I am in the process of creating/compiling a set of standards for my practice and would like to understand how to go about it; and would love to find examples of what worked or didn’t from anyone else who has done this, or felt the need to.

our rhino users range from advanced to amateur, and the intent of this standards guide is to organize the files and layers making things easy to find and cross reference, and also standardize the output quality. It might help people who are averse to troubleshooting and looking for solutions online, and make the amateur users improve their skills but that is not the intention.

do you have a set of standards- such as file naming, block management, layer structures and names etc. and guides/manuals for the users?

Would anyone be willing to share them? I understand that it would be unique to that practice, and might not even be applicable to somebody else’s way of working. ( some of it might even be ‘proprietary’)

It goes without saying that a lot of the stuff from the rhino manuals from mcneel and forum discussions will find its way into this rhino standards document- and I will set up a google drive if anyone wants to see what i am up to.


1 Like

This is a good question, I would like to Bumb this thread.

Also Aditya if you have found anything interesting since you posted this I would be interested in viewing the google drive that you mentioned.

If I find anything interesting to I will share it.

I was creating a template for Rhino and Visual ARQ but I’ve had to put that project to the side. I was basically getting killed by 1,000 papercuts. I’m about to consolidate my work and share it; either this weekend or next. And maybe I’ll jump back on the project at a later date which could be either before or after Rhino 8 is released. I’ve created really good standards for both AutoCAD and Revit but found this project to be far more time intensive. The potential is definitely there however. My goal was to fuel more interest and collaboration towards creating a much easier starting point for those of us wanting to use Rhino as their main design program. It takes far too much time for most to start from scratch.

As far as advice goes I’m not sure I’d be of much help. I find that with creating standards you actually have to build 1-3 real (or realistic) projects to know how well your standards work, then tweak and refine them to suit. I’ve created exactly zero projects so far :frowning: .


Hi Keith, I would like to see your template sounds very interesting

1 Like