No binding, no deleting anything, no changing anything. Just upload that sucker. You dont even have to Detach From Central, if it is workshared, because they have to DFC when they get it.

You should have this conversation with the people you are sending your model to.

I assume you've linked their models to yours using Auto - Origin to Origin. If not then they'll have some difficulty aligning your model to theres unless you give them some marker like at the grid intersection of A-1. You do not need to bind their files. They have their own they don't need another link to their own data.

Some advocate removing sheet views before posting your file but I'm not a fan of that, definitely not so early in the project.

You say no worksets, does that mean you aren't using a central file or just haven't created any of your own worksets? If you aren't using a local/central file then disregard the following stuff.

If you are using worksets, just not expanded on them at all yet, you should open the project and use the Detach from Central option to store a new version of your project file in a separate folder as an archive of what you sent to the other trades. I recommend doing this, not because of them but if someone internally accesses the file later it will prevent this copy from thinking it is a local file looking for the original central file, which technically still exists. You send them this detached file. They'll need to create a new central file on their end to avoid having their copy thinking it is a local file "looking" for the central file you sent them.

Steve,

I linked one file in using origin to origin. The second when done this way never lined up so I had to re-insert it as Auto-By shared coordinates which then lined them up.

With regards to the worksets and a central file, which admittedly I know little about. What we have is a filespace where we all upload to, I've taken the arch and structural models and put them on our system and linked them into my project. I haven't created my own worksets but I’m unsure if the method I just explained describes a central file or not.

As mentioned above, dont ever bind in anyone else's files to yours when issuing, especially when using a file sharing system where all the consultants files sit side by side. If they want access to the Arch model, download and link it, if they want the structures, download and link it. Once you start binding other peoples work into yours, you could be assuming all sorts of responsibility / ownership of stuff you didn't want to. Not to mention the complications people will then have of switching off stuff etc, and deciding whats current and what isnt. (I know this because we work with some real newbies on this sort of thing)

Also, you should have some sort of indication between you all, of what LOD you maybe working to. This means that although some items maybe shown in your files, they could just be markers for other objects that will evolve with the design (especially true in terms of plant items etc). Architects will use what they see as being the right size / place unless you tell them otherwise. they will be using that file as verbatim from the point they download it. The level of detail / development allows you to say, "this piece of plant is generic at this stage, and is subject to change" if that is the case.

Another think worth looking at in a collaborative environment, is the Responsibility Matrix. This sets out who is responsible for which model element. One think we are finding at the moment, is too many people arent taking this initial phase seriously, ie things that can be decided in the BIM Execution Plan, BIM kick off meeting etc. Depends what level of sharing people are at, and what the purpose of the models are actually for ie, just a bit of file sharing and layouts etc, or a full BIM.