Hey All.  I want to go through a few key things you should think about when starting a Revit-based project.  I have to say, first of all, let’s start referring to these projects as a “Revit-based Project” as opposed to a “Revit Project”.  I think it takes the emphasis off of what type of software is being used and puts it, more appropriately, on the fact that it’s an architectural project.  Anyway, here are five things that you should consider, and document, when starting a project:

1. Software Version and Build (internally and externally) – It’s important to make sure that not only are all of your internal Revit users using the same version (and build) of Revit, but also that all consultants are using the same version.  This will ensure that there is no loss of data when sending your model to a consultant.  It’s also import to note that even if your consultant is not working on the architectural aspects of the project (ie. they’re using Revit Structure or Revit MEP), they still must be using the same release of Revit (in this case, the build version can be ignored).
2. Working with Consultants – Be aware of what software (and versions of those applications) that your consultants are using.  Once this data is compiled, document the process by which your Revit model is exported to each piece of software.  For example, if a consultant is using AutoCAD, make sure that the text file which describes how Revit objects are translated into layers has been updated to conform to your office standards and that all team members are aware of its location.
3. Single or Multiple RVT Model Files – The process of sending data to a consultant differs when your project uses a single model file or multiple model files.  Therefore, document the names of the model files contained within the project as well as a description of what each model file contains.  Taking a step back from that, decide whether or not you actually want to use multiple model files.  If so, make sure all team members know how the project is organized, within which file they should be working (and modeling) and, more specifically, which model file should be printed from.
4. Worksets – On the same topic of organization, document the worksets being used in your project and what types of objects should be put on them.  It’s important to keep this list shorter rather than longer because, as similar as worksets might seem to layers in AutoCAD, they are not interchangeable and users should be able to keep the idea of them in the background.  Also, the Revit leaders on the team should have a process by which they can check to see if objects are on the correct workset and, if they’re not, how to correct the error.
5. Level of Detail Based on Project Phase – As I have mentioned in previous posts, the level of detail applied to a model should be based on the phase of the project.  For example, in earlier phases, such as Schematic Design, the detailed structure of walls should be left out and the types should be set to generic.  Material-wise, the walls should have the basic grey material or transparent blue material.  Be sure to document exactly how detailed object-types should be brought to.  For clarification purposes, document the levels of detail for objects for the upcoming phases.  This will allow users to keep in mind how the model will be developed over time.

While these are just five things to consider, there are many others as well.  At its heart, however, this is both a preparation-based as well as a future planning-based process.  Considering these things will eliminate confusion and will provide a road-map for working on a Revit-based project.