FORMAT
Generally try and use ACIS export (.sat) from Rhino. Rhino makes slight changes to geometry when converting to polysurfaces, even when done within Rhino.
Try and avoid meshes. Revit’s underlying engine is NURBs based so meshes don’t help.
Meshes look messy because of all the edges and can be so large they slow Revit right down, and in some instances take 100 times longer to print because there are so many lines.
Export from Rhino as a straight .SAT file if the export is simple (e.g. a mass shape). To get better control over colours in Revit export as an AutoCAD DWG with ACIS solids selected. This provides an import with layers that can be manipulated in Revit.
IN REVIT
In Revit you have to import the .SAT or .DWG into a family, usually Generic Model, or Mass if you want to use it to host walls, roofs etc. If you will need to scale your import use the Planting category. It can be a separate family (.rfa) file, or within the project as an in-place family. Putting the import within a cuttable family (don't use Furniture or Plumbing Fixtures for example) ensures the import will be cut by plans and sections. If you don’t do this the import will always display in elevation.
Solids imported can’t be snapped to in 3D, although you can in plans, sections and elevations. If you need to snap to an import (because you want to 'trace' it with a Revit mass) create a Rhino export that is just lines and export it as a DWG mesh file.
Keep in mind that an import in Revit is just a dumb object. You can’t do anything with it except look at it. You can't alter it in any way and only change its appearance in very limited ways. Although it can be cut in plan and section the results are not very good because what is being cut are usually isolated thin planes.
The best workflow is to link a .sat file into a Mass family, then host walls, roofs, floors on the mass. When the Rhino file updates the mass will update in Revit (you will still need to manually update hosted walls etc.).
But it is always better to do things in Revit if possible. If the shape from Rhino is simple, there is no reason it couldn't be done in Revit.
IN CONCEPTUAL MASS
An imported Rhino .sat file can be exploded in a Conceptual Mass family.
However if any part of the Rhino import represents a viable solid shape Revit will turn it into a solid.
If not it will delete the Rhino geometry.
Rhino to Revit workflow guidelines from parametricmonkey.com
It is also possible to import Revit geometry in to Rhino:
Whereas as 3D Max can actually link Revit files...