diff --git a/common-content/en/blocks/community-roles/index.md b/common-content/en/blocks/community-roles/index.md
new file mode 100644
index 000000000..484f3e40d
--- /dev/null
+++ b/common-content/en/blocks/community-roles/index.md
@@ -0,0 +1,31 @@
++++
+title="Weekly tasks for your community"
+time=15
+hide_from_overview=true
+[build]
+  render = 'never'
+  list = 'local'
+  publishResources = false
+
++++
+**Your local CodeYourFuture community is run by the trainees and volunteers**, who are together every Saturday. There are some tasks that must be done _weekly_, to ensure it all runs smoothly. Let's decide who's can help with what?
+
+We need a Coordinator in the community responsible for finding people weekly to do the tasks.
+The person in this role should NOT be the one who does that tasks every week.
+We suggest changing the coordinator every month, but you can decide what works best.
+If the coordinator is no longer able to do this role, please identify someone else who can do it. 
+
+Steps:
+1. Understand what you should do as coordinator:
+    - **Lunch**: choose someone for every week who will 
+        - make the list of food that is needed, checking leftovers (if applicable)
+        - knowing the community's dietary requirements
+        - choosing who will buy OR communicating with who will buy
+        - choosing who will help on the day (setting up/clearing out)
+    - **Energiser**: choosing who will do the energiser in the following week, ensuring it is done every week.
+    - **Timekeep**: choosing who will time keep, ensure it happens so the class stays on track
+2. Share the coordinator name on your local Community Slack so everyone knows who they are
+3. Coordinator: identify volunteers for the next 1-2 weeks
+4. Repeat this whenever needed
+
+The coordinator role and individual weekly roles are important ways to build a community based on trust and autonomy. But also helps each of you to practice some important **communication, planning and leadership skills**, which you will need for your future jobs in tech. 
\ No newline at end of file
diff --git a/common-content/en/blocks/wrap/index.md b/common-content/en/blocks/wrap/index.md
index 40066a247..ca1be57fe 100644
--- a/common-content/en/blocks/wrap/index.md
+++ b/common-content/en/blocks/wrap/index.md
@@ -7,7 +7,11 @@ time=20
   publishResources = false
 +++
 
-You are done for the day. Take a moment to reflect on what you have learned and achieved.
+You are done for the day. 
+
+Make sure to have assigned the community roles for the next week, if you haven't already.
+
+Take a moment to reflect on what you have learned and achieved.
 
 Stand in a circle and share:
 
diff --git a/org-cyf-itp/content/welcome/day-plan/index.md b/org-cyf-itp/content/welcome/day-plan/index.md
index 9e0965069..cc42a74f7 100644
--- a/org-cyf-itp/content/welcome/day-plan/index.md
+++ b/org-cyf-itp/content/welcome/day-plan/index.md
@@ -45,9 +45,13 @@ time=75
 name="Afternoon break"
 src="blocks/afternoon-break"
 [[blocks]]
+name="Weekly tasks for your community"
+src="blocks/community-roles"
+time=15
+[[blocks]]
 name="Next Steps"
 src="module/fundamentals/next-steps"
-time=45
+time=30
 [[blocks]]
 name="Wrap"
 src="blocks/wrap"