 So I would say that, first of all, it's of course about a common topic that the different partners are working on. Of course, the topic with relevance for the different working realities of the different partners that are on board of the partnership. Then, of course, speaking about this context, it's also about the question of what every partner is actually bringing into the partnership, but also what every partner can take out of this common project. And of course, then we're speaking about the European programmes, so it also means including the European dimension, which means this aspect of having different countries working together on a common topic that might have different aspects also with the different backgrounds that partner will bring in. So for me, it's a lot actually about the multiple perspectives that will be visible, for example in the application form. This would mean that, for example, the needs are clearly described for every partner that is involved in partnership, but of course showing very clearly which kind of competence every partner can bring in, but also what every partner might learn during this partnership. Of course, also this whole question of the balance, like who will take over what kind of task and also why would partner take over this kind of task to make really clear what are the competences partners will bring in and how they will learn from each other and how they will actually also bring this whole knowledge back to their own organisational context. One important aspect, it's the one I just mentioned before, it's really also about learning from each other. So I think one important point is that competences might not only mean knowledge, like knowledge on the topic, but of course there can be a lot of more diverse competences within a partnership. So for example, it could also be one partner bringing in competence about project management being really experienced in this kind of field, but maybe also on specific access to a specific target group or one partner with a specific expertise on dissemination. So in the end, it's a lot about the mixture, I would say. It doesn't necessarily make sense to have the very similar expertise with the different partners, but more to see what is there and how you can use it as a puzzle and make a clear picture from all those competences and skills that might be with the partners that are on board of the partnership. So one very important aspect I would see here is actually to think of the fact that equality of the partnership should begin before the start of the project itself. So it's also a lot about preparing things together and having this whole process until the application together. This is one part that's actually also really visible when you read applications. Then of course I would also see this whole question of commitment connected here. So the project should really be like something where every partner is committed to and that will bring added value for every partner, which also means it should not be only like the coordinator being mainly responsible and being the one pushing through things, but more like really this equal approach and this balanced approach like everyone bringing something in and trying to move things forward. And so another important aspect for me would also be this question of the reason why to have this partnership. So having a clear picture of what specific expertise partners will bring in. For example it might not make too much sense to have like three partners with very similar expertise from the same country because then it's not really clear why it makes sense to work in this constellation. And of course then also one important aspect might be not only to think from the perspective who are the partners I know, who am I already working with, but really more taking maybe the opposite view, thinking okay this is what we aim for, what is actually the competence and expertise we might need and if I identify that there is like something missing it might be also a hint to look for a new partner maybe to bring on board who can bring in this very specific expertise that might actually be missing so far with the well-known partner. So sharing the needs of each partner also in the preparation process I think it's a very central aspect because in order to actually have an impact of the project for every partner that's on board it's also very important to know what are the different needs that might be in the room. And it should not only be about the needs of one or two partners out of the partnership but really having a look at okay what is it what every partner would need related to this topic and what can we actually work on together in order to provide to every partner who is on board impact for his own work in the future and also for using what's coming out of the project after the project ends actually. So when I think about good projects what immediately comes to my mind is actually to really be able to read especially also between the lines or to see that the application actually had already been prepared together by all the partners it's visible because for example the needs are clearly described for each and every partner but you can also read or see the reflection that has been going on in the preparation process for example discussing concepts there are usually clear hints about what do we mean what might we not mean actually and then a second very important aspect would actually be also of course the impact it's also the part where it's usually really visible and what might make the difference to really see also at the end of the application what kind of thinking took place in the preparation process how can every partner on board take back what will be worked on to his own working context apply it use it of course and share it with own colleagues this question of expertise that's brought into the project so I think it's also making a huge difference if it's visible that actually there has been a clear choice also to see and what kind of expertise every partner can bring in the project and how is it going to be combined and used and not just like yeah several partners having exactly the same approach and skills and not very clear what's going to come out of it. I would say that the most common error is actually to have the application only written through the perspective of the applicant for example so it's not very clear what about the other partners and it's only described about needs for one or two partners and the impact is not clear for the other organizations on board so this is very common or especially also in cases where there might be a mix between known and new partners also to have a disbalance between what's described or the partners that already work together pretty often and the ones that might be new on board very often those ones are kind of forgotten a bit or can be forgotten a bit in the description of the application form. Then I would say another aspect that's sometimes missing or not very clear a sign that maybe things haven't been developed that well together and beforehand is also a dismissing part of learning from each other so really more focused on producing outcome for others but not including actually reflection on what are we going to learn as a partnership and what is it what partners are going to take out of this common project. One other aspect I would see here is also a disbalance between maybe partners only bringing in knowledge and input and others only learning something and let's say taking things but not having both aspects for each partner this is a very central point. Another thing is which also could be like a common mistake or error would be to kind of forget about this whole part of having room for exchanging and discussing concepts actually really exchanging about how do we understand this and what is how do I approach this how do you approach that and so having more this bigger orientation on only producing outcomes but not really this aspect of actually working together and the things. One of the first things that come to my mind here is really this aspect of capacity building which means that very often I guess it's there's an assumption but it's not written that actually it's also about having this organizational development for the partners that are on board and development for the staff but also for the organization as such as a whole so this is one very important aspect. Then quite some projects or applicants or partnerships actually tend to forget to describe what they already did beforehand so there might be only a very short mentioning of yeah we had one common project but they don't describe really in detail this whole common preparation phase or also where does the idea come from how did it come up in which context even though this would actually be a very important aspect actually when it comes to the application. So another part that's quite often forgotten is actually this whole question of how decisions are taken in the partnership like which ones are going to be taken commonly or who is maybe going to take what decision on his or her own and which are actually a bigger question that has to be discussed with the whole group. Yeah and then as a last point I would still add again here and this whole question of actually learning from each other especially when there are like project results involved this is something that's very easily forgotten to be described because of course there's also this big focus on what do others take from it how can we disseminate it how can the whole field actually use it but this aspect of actually also always having this idea in the background of the head of what is actually going to happen within the partnership and how can we learn from each other and yeah grow together actually this is also something that can be focused in the application form and that is forgotten quite often.