As your Revit usage expands, or even when you just start using it, it is inevitable that you are going to need to make your own parameters. At its core, Revit is a database, and parameters are how it holds onto data. The ease and speed of being able to make your own parameters is a bigger benefit than many realize, but as always, with great power comes… the need for standards.
We have a lot of Revit nerds here at CADD, and we all have our own ideas about Revit parameter naming conventions. I’ve organized a handful of tips; there is no definite way you should name your parameters. Some of the tips below might even contradict each other, so understand that they shouldn’t all be adopted. The key is to develop a set of naming rules that makes sense for your workflow, and STICK TO IT. No cheating.
- Do not repeat parameter names – OK, this is one that you should 100% follow. You do not want to use a parameter name that either Revit already uses, or that you have already used. Each parameter should have a unique name. Duplicate names can lead to confusion, wasted effort, and bad data. And remember, in BIM, data is king.
- Use upper case – this is a quick way to recognize what parameters are yours vs. what are the Out of the Box (OOTB) parameters.
- No spaces – use a period “.” or a dash “-” in lieu of spaces for your parameter names. Sometimes you might have a piece of third party software that wants to pull data from your Revit model. Sometimes spaces makes it go a little wonky.
- Append the name with your organization’s initials – if you put your firm or group’s abbreviation at the end of each custom parameter, you are going to be doubly sure what parameter you made vs. OOTB ones, or ones from other clients. We suggest you put it at the end of the name instead of the beginning because if you have a list of parameters and they all start with the same word, it gets in the way of seeing what the rest of the parameter name is.
- Avoid wacky characters – this is another strong recommendation. Numbers, spaces, periods, dashes, and letters only. Revit will permit some characters but it’s best just to avoid them.
- No stupid names – we don’t see a lot of parameters named “Temp” or “ASDF” but they’re out there. Make your parameter names short but clear and descriptive enough that folks know what they mean.
Again most of these are not “definitely do this” standards. The important thing is to develop naming conventions, make sure everyone complies, and be consistent.