# data[].attributes.body
- very flexible with meetings
- very useful we had all trainings prepared before TS already (more or less)
- plan 2h for meetings
- have 1 moderator
- more prep time for trainers' team on-site before the official start? Saturday and Sunday? or start earlier on Sunday?
- preparation of sessions before TS saved a lot of time on-site
- motivated, interested and inspired trainers team
- meetings well organized and good to meet each other
- prep was nicely handled

# data[].attributes.body
- use tool for online meetings where everybody can activate the webcam (aka not Discord)
- separate orga team and trainers' coordinators
- in general more clear division of tasks. Who does what and is responsible for what?
- list all the things to do and until when. This year there have been a lot of things not thought about and needed to be done in last minute.

# data[].attributes.body
- worked out great but i would not take it for granted that without application it work's all the time like it did this year
- depending on the application process, set clear payment deadlines to complete registration
- ask for mobile phone number and private e-mail address
- set cancellation policies
- a short and easy application process was a good idea but maybe ask 1,2 more questions about their motivation and interest in the event to know something about the PAX and to have them a small invest in the application
- start application process earlier so that PAX have more time to think about it and save the date. Maybe this way there will also be more PAX

# data[].attributes.body
- spot on, again for next year
- It was amazing place where we could spend some time outside and enjoy beautiful nature.
- an outside area that we can use in front of the house would be really useful if corona will still be a topic next year
- not too big even for a small group
- geographical place was good and easy to reach by train with a very nice view!
- good space to give training

# data[].attributes.body
- the kitchen was as excellent as the "file rouge" through the whole week
- I liked the food was very light and delicious every time.
- nothing to improve here
- awesome
- the food was simply stunnung
- add 1-2 people as kitchen helpers next year

# data[].attributes.body
- very efficient and well working machine consisting of all kinds of different gears that all interlocked very well to create something great all together (including orga)
- very efficient meetings with lovely question "What are we thankful for?" at the begininning
- I really appreciate all team members were very helpful, supportive and attentive to each other.
- a big thank you to all trainers for your unconditional support during TS 2020
- more orga and kitchen staff needed

# data[].attributes.body
- 1h for each reflection group, keep number of reflection group (aka GruStu)
- I agree with having at least 45 min for reflection group. But I suggest  skipping reflection group one evening and give PAX the time for reflection / sharing during the Checkout. I saw members of my reflection group were pretty “dead tired” on Tuesday after many (and information-heavy) sessions so they were too tired to think about the day.  I think that Wednesday might work quite well because it was a bit of a relaxing day with hosts.
- start a bit earlier in the morning and have 1,5h lunch break?
- social program should be organized by orga team and not by trainers because it intefers with the trainers' meeting
- Give another free evening to pax - leave out one social program.
-OST and "me as a trainer" session need to be longer (at least 1,5h)
- out of the house experience was super nice! maybe we could shorten it a little bit time-wise?
- question to trainers: how was the workload on-site for trainers? would you liked to give more trainings?
- Try to have one training a day for trainer.

# data[].attributes.body
- My idea is to add a short session about co-delivery (e.g. pentaCON theory). It might have prevented some differences and a small dispute in the "training style" that have appeared during the final delivery because they even had not thought to discuss this topic before in this Buddy group.
- pay attention to keeping all documents updated (including sessions material) and follow up. All trainers can easily look at them and be sure that what is written there, is done as well.
- Kolb's learning cycle got somehow forgotten and trainers had to integrate it short term in the 4mat session, this should not happen
-> suggestion: at least one trainer delivers both trainings so the continuity might be guaranteed more
- some sessions had too much content like the 4MAT session and NA+goal setting session
-suggest to have one topic per training and if topic does not require as much time, just make the training session shorter. - > scripting and debriefing.
- maybe put more importance on some training. Some PAX did not understand the 4MAT which is important for final delivery
-ask Pax to have already decided on a topic to deliver a training on before the start of the event - this way less time is lost deciding on a topic.

# data[].attributes.body
- keep visits in that order and especially this "look in the future" in the middle of the week
- I received the feedback that someone would appreciate having visits more days so PAX could have "less tiring sessions" between "heavy information sessions" more often.
- have 1 visit on Tuesday, 1 visit on Wednesday and 1 visit on Saturday
- shorten SBAP visit on Saturday
- I liked it that Sandro (psyCH president) visited us on Saturday and presented psyCH
- 2,5h with Carl was a bit too long in my opinion

# data[].attributes.body
- good mixture of everything
- I like the idea to open TS for international students as well.
- I also found it unproblematic, even enriching to have non-psychology students
- we might ask PAX for one or two questions to describe themselves in application or in NA before TS (e.g. what animal would describe you in the best way?) It might help Trainers to divide PAX to reflection groups not only according to the first impression at TS.

# data[].attributes.body
- schedule worked out well
- good idea to let Buddy groups decide what time slot they prefer
- I suggest having more prep time during sessions not to just start working on it in a few minutes.
- be sure that all Buddy groups know their topic really on time when they need to work on the delivery already (e.g.Goal setting etc.)
- send list with possible topics for final delivery before TS
- ask PAX to think about 2-3 topics before TS so that the process of agreeing on a topic on-site is quicker
- 1h for final delivery feedback. Ideally in parallel for all particpants (if trainers have only 1 buddy group)
- PAX should do their research for their training prior the training school. There is not enough time for this during the week. PAX sometime focused more on the content than the form of their final delivery.

# data[].attributes.body
- finish Handbook and send it to PAX
- social event with whole trainers' community
- approach psyKo team and ask for training opportunities
- Send handbook beginning of Nov
- Should we also share our training script with PAX?

# data[].attributes.body
- mentoring
- PsyKo 2021
- other training opportunities
- social events
- psyCH Trainers' whatsApp Chat
- training about the tips and tricks how to prepare and deliver online trainings
- a group of 12 students is optimal
- Unformal trainer meeting with everybody from the 2020 TS. Give the opprtunity to see each other and to give training to other on the same level.

# data[].attributes.body
- organize follow-up meeting with mentees soon(Sept/Oct)  to see how TS 2020 reveberates
- contacting mentees, have first meetings already happened?