A project role needs a clear framework
If you're looking for contributors for a dance project in Karlsruhe, you're offering a collaboration for a limited time. So your post should make clear whether the project is intended to result in a stage performance, a recording, or an internal presentation. A dance film, for example, calls for repeatable movement sequences across multiple takes. The page about dance films and the effect of the camera explains this difference in more detail, without requiring you to have a finished choreography already.
Describe experience in terms of tasks: remembering short movement sequences, starting on counts, repeating material independently, or working with a partner. “Advanced” alone doesn't say much. Roles also become clearer when you distinguish between solo work, ensemble work, and leading or following. A leading role is not an automatic requirement for a particular gender.
Every requirement should relate to an actual task. Acrobatics, floorwork, or close physical contact are not incidental extras. State these requirements explicitly instead of hiding them under “openness.” This helps interested people assess their abilities and boundaries.
Also keep project leadership separate from participation: someone who dances does not automatically take on organizing, sourcing costumes, or public relations. If you want to assign additional tasks, list them separately. The principle from the guide to clearly describing an offer on udansa can be applied here too: first explain the specific task, then invite people to respond.






