In this article we consider the ''design for orchestration'' concept and introduce a set of notions to clarify matters of concern. We propose to distinguish orchestration technology and orchestrable technology, to define orchestration as a combination of scripting and conducting, and to differentiate primo-scripting and run-time scripting. As a way to see how these different notions relate one to another, we take the example of CSCL scripts.