diff --git a/mentoring/processes/group-mentoring.md b/mentoring/processes/group-mentoring.md
index a3fc7fe70..ef34836d5 100644
--- a/mentoring/processes/group-mentoring.md
+++ b/mentoring/processes/group-mentoring.md
@@ -22,10 +22,11 @@ suggestions:
   
 *Reviewer*  
 - Enhancements  
-- Overview of Release Cycle  
+- Overview of Release Cycle 
+- Overview of SIGs subprojects
 - Development
   - Triage
-  - Reviews
+  - Reviews - detailed walk thrus
   - API Changes
   - Testing
 - Code Freeze
@@ -54,24 +55,32 @@ Examples:
 0. Need is established and SIG provides a mentor*
 1. ContribEx kicks off two issues, sets a target start and end date, and selects
 a coordinator
-  - issue #1: outreach issue to collect folks who are interested, issue will 
-  close when there are the max participants needed
-  - issue #2 setting up infra - template here: [TODO link to example]
-2. ContribEx or SIG member posts the issue to the following places:
-  - SIG and k-dev mailing lists
+  - issue #1: outreach issue to collect folks who are interested and set up 
+  infra, issue will close when there are the max participants needed  
+ example: https://github.com/kubernetes/community/issues/5962  
+ key bits of info: target, start/end date, sign up and requirements, slack info,
+  mentors, coordinators 
+ - issue #2: structure of sessions and assign guest speakers 
+ start with a hackmd to coordinate with mentors and then set issue
+1. ContribEx Coordinator(s) posts issue #1 to the following places:
+  - SIG list first and then k-dev mailing lists with timeboxes for responses
   - #diversity, #kubernetes-contributors, #sig-[name], and other slack channels
-3. Coordinator arranges a doodle for the kick off meeting and days/times that 
-would be best for the mentor and group for slack standups and touch points. Once conscensus is reached, coordinator schedules it.
-4. Mentor creates template that serves as a reference guide for the group. See
+3. Slack stand ups happen on the day of the SIG meetings but the 30-min
+bi-weekly meetings will need to be arranged. Coorindator should send out a 
+doodle to the selected group with a few times that work for the mentors.
+4. Coorindator and mentors work together on the three-month plan template. 
+Coordinator will schedule the speakers and create a calendar for the group.
+example here: https://hackmd.io/1aAIaMChR8Gfi31aOKBHlA 
+5. Mentor creates template that serves as a reference guide for the group. See
 a sig-node example here: https://hackmd.io/8i8prErgSOamUmEZDDZPWA
-5. Program begins at the kick off meeting
+6. Program begins at the kick off meeting
   - [TODO add kick off template]
-6. Feedback is continuous as you stand up weekly; however, the ContribEx 
+7. Feedback is continuous as you stand up weekly; however, the ContribEx 
 Coorindator will set a mid program check-in. In this check-in, members of the 
 group will start their application process for their roles and any group members
  who have not had the time. 
   - [TODO add community membership template]
-7. By this point, folks should know where they stand. At the end of the program,
+8. By this point, folks should know where they stand. At the end of the program,
  mentors and/or individuals will start the PR process in OWNERS files or 
  sigs.yaml for leadership roles for those who are ready