Thinking about this more - some things that may or may not help you (forgive me - I don't know if you use Cinema yourself, so ignore if you know all this):
1. I always name my objects in VW - or at least name the group they are in. Those names will carry over to Cinema so your client can see the names in the Cinema object manager. If not named, they will get 1000 objects named extrude...... 1786 objects named Solid Addition, etc.
2. I try to solid model as much as possible instead of POIs and convert things to generic solids once I'm ready to export final model. Keeps things cleaner - though if you do this, name it AFTER you convert.
3. In Cinema, you have to be careful of complex or PIO objects splitting into dozens of polygons and should be fused back together to keep the file running efficiently (Connect objects + Delete command in Cinema. For example - a stick of truss will come into Cinema as a folder with each chord and each piece of lacing as a separate object. Multiple this by all the truss and your got thousands of objects slowing down the scene when not needed. I go through and connect them for efficiency sake.
4. Layers translate to master folders in Cinema (called Nulls) - so if you have all the truss on it's own layer, your client will automatically get a folder in cinema with all the truss in it (and anything else on that layer) - so use layers with that in mind. I certainly use more layers then I normally would in VW, knowing that this will help me stay organized in Cinema later.
5. I always use "Export to Cinema (3d Only)" and never use Send to Cinema. I found it buggy, but haven't tested in recent versions. I prefer to export and open the generated file in a clean shuttle file and then copy and paste into my master document.
6. Find out what render engine they are using. If native cinema, then you can texture in VW and they will carry over. But if they are using a 3rd party render engine (Redshift, Octane, Arnold, Corona, etc.) they would have to rebuild the textures anyway. So you could still make texture for unique materials (concrete, glass, Iron beams) but those could just be all white with no dialed in properties. Then they come through as white and assigned correctly, and the client can just swap your blank concrete for their, say, Redshift concrete and go. Make sense? No point in using specific materials in VW if they are using 3rd party materials in the end since they will have to rebuild. There are material converters, but honestly, they don't do a great job and get messy fast.
7. If you are adding lighting instruments (as lighting instrument objects instead of just symbols) - do some tests with client. Lighting instruments lose their rotation and focus when you export a lot, so dial this in with some test files first.
I realize a lot of this is more on your clients side, but might be useful information. Let us know how you get on.