Hi Angus,
Yes and no. I would not advise only sending him parts of your Wwise project. Either send him the entire Wwise Project (except cache files and .akds) or just the SoundBanks. Here are a few options.
- If you want to give him access to everything in the Project Explorer, he will need the Wwise Project. If you only were to share the Actor-Mixer work unit, that would only be the hierarchal structure of your audio objects and not necessarily needed for integrating the sound into the game.
- If you want to give him the ability to integrate Events, Game Syncs, etc. using Wwise-types, components, or use the Wwise Picker window, he will also need the Wwise project but he won't need to be able to open Wwise necessarily. He just needs to have it located on this computer, so he can fetch the information into his Wwise picker, etc., and integrate it.
- If he just needs playable audio and you can set up the integration yourself, all you need to send him is the SoundBanks.
- Alternatively, you can also send the SoundBanks + a list of Event names, Game Syncs, etc. and he can call it from code by specifying the name of it, but he won't have the nice dropdown Wwise-type picker and the ability to assign things in Wwise components. Also, if you change the name of an Event, game sync, etc, later on, you'd need him to change it as well in code.
Another great thing for collaboration is using a source control solution like GitHub. Especially with option 1 or 2, it makes it so much easier for you to continuously contribute to the game once the Unity developer has already integrated it.
Let me know if this is helpful and what path you choose to take.