It's a good question  and given your experience I guess you're not just looking at the out of the box create a package process. There are a lot of things to consider with outsourcing in real life as you well know and I don't believe I have ever come across a single resource or tutorial that attempted to tackle this in a practical and honest way.

I think it would be a good exercise to look at something like this and would probably require a collaboration of people to ensure the best approach was used for all usecases.  Probably needs to address things like:

1. Studio project package workflow (as Fas suggested)
   1. error handling processes is an important topic that should be documented here
   2. dealing with plugins that may or may not be installed on the outsource machine
2. bilingual file conversion to formats more suitable for resources not working with Studio
   1. important if you want to retain control and knowledge of what's happening to the file
   2. reduces errors caused by allowing less qualified people to do the conversions
3. translation memory conversion
   1. probably TMX... but how to handle fields & attributes in other tools?
4. terminology conversion
   1. potentially trickier than translation memories because of the variety of formats used by other tools
5. can you make use of other resources?
   1. autocorrect lists
   2. machine translation
   3. plugins
   4. spell checkers
   5. QA rules
   6. segmentation
   7. variable lists
   8. etc...
6. server based solutions
   1. GroupShare
   2. WorldServer
   3. SDL TMS
7. etc... etc...

I believe you are probably coming at this from a different angle, and in this regard I think there are a lot of things to consider.  It would make a good book, but would probably be out of date by the time it was finished!  Perhaps a series of articles or webinars would be an interesting approach.

It's a good question  and given your experience I guess you're not just looking at the out of the box create a package process. There are a lot of things to consider with outsourcing in real life as you well know and I don't believe I have ever come across a single resource or tutorial that attempted to tackle this in a practical and honest way.

I think it would be a good exercise to look at something like this and would probably require a collaboration of people to ensure the best approach was used for all usecases.  Probably needs to address things like:

1. Studio project package workflow (as Fas suggested)
   1. error handling processes is an important topic that should be documented here
   2. dealing with plugins that may or may not be installed on the outsource machine
2. bilingual file conversion to formats more suitable for resources not working with Studio
   1. important if you want to retain control and knowledge of what's happening to the file
   2. reduces errors caused by allowing less qualified people to do the conversions
3. translation memory conversion
   1. probably TMX... but how to handle fields & attributes in other tools?
4. terminology conversion
   1. potentially trickier than translation memories because of the variety of formats used by other tools
5. can you make use of other resources?
   1. autocorrect lists
   2. machine translation
   3. plugins
   4. spell checkers
   5. QA rules
   6. segmentation
   7. variable lists
   8. etc...
6. server based solutions
   1. GroupShare
   2. WorldServer
   3. SDL TMS
7. etc... etc...

I believe you are probably coming at this from a different angle, and in this regard I think there are a lot of things to consider.  It would make a good book, but would probably be out of date by the time it was finished!  Perhaps a series of articles or webinars would be an interesting approach.