Answers.Body: <p>We have worked with a union that needed this. They have 3 types of Cases</p>
  <ul>
  <li>Individual</li>
  <li>Collective</li>
  <li>Enterprise Agreement</li>
  </ul>
  <p>For Collective ones, the business is registered as the 'client' and the members involved are related to the Case via a separate Relationship. So there is just one Case that encompasses all the affected workers.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-12-21T00:27:44.523Z
Answers.Text: Thanks for the suggestions. I suspected your suggestion might be the way to go, but the fact that others have used this approach successfully is comforting.
Answers.UserDisplayName: Dave Smith
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-12-21T02:07:06.523Z
Answers.Text: Sweet. Ours was using a Drupal platform so most of the UI was via webforms and views. am sure native civi can handle it better now but we needed lots of dashboards to help the case managers and their managers all keep really good tabs on what the current state of play was. also in inbound emails as Activities to ensure email threads with clients were kept in the case.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-12-21T02:07:47.987Z
Answers.Text: https://civicrm.org/extensions/documents was also really important part of their toolkit which we had to extend to ensure it all played nicely with webforms but would have contributed code back to the maintainers
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-12-15T23:29:11.470Z
Answers.LastActivityDate: 2024-12-15T23:29:11.470Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <p>Sometimes the answer to these types of questions is determined by &quot;what reports do you need&quot;, but here's some ideas:</p>
  <ol>
  <li><p>Create a separate case for each employee, and use the &quot;link cases&quot; feature to link them together. This might be useful for orgs that have extra privacy rules where you need to keep the information separate, or makes it easier if they ask for their file then you can give it to them without weeding stuff out.</p>
  </li>
  <li><p>Create a contact subtype for orgs called something like &quot;group claim&quot;. Make org contacts with that subtype representing each group. Give the relevant employees an employee relationship (or some other relationship) to that org. Then make the case client be that org.</p>
  </li>
  <li><p>Pick someone as the &quot;spokesperson&quot; for the group, and make them the case client. Give the other people roles on the case.</p>
  </li>
  </ol>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-12-21T00:30:14.060Z
Answers.Text: Thanks for the suggestion. I think suggestion 2. might be a favourite to explore.
Answers.UserDisplayName: Dave Smith
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-12-15T04:18:01.840Z
Answers.LastActivityDate: 2024-12-15T04:18:01.840Z
Answers.UserDisplayName: Demerit
Body: <p>We are a trade union. Most of our cases involve representing one worker against one employer. However, sometimes, we get group issues involving as many as 20 or 30 workers. Does anyone have suggestions on the most effective way of collectively dealing with group cases?</p>
  
Tags: <civicase>
Title: Linking/consolidating cases
ThreadText: # Linking/consolidating cases
  
  (Asked by: username_0 on 2024-12-15)
  
  We are a trade union. Most of our cases involve representing one worker against one employer. However, sometimes, we get group issues involving as many as 20 or 30 workers. Does anyone have suggestions on the most effective way of collectively dealing with group cases?
  
  **Tags:** civicase
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2024-12-15. Score: 1
  
  We have worked with a union that needed this. They have 3 types of Cases
  
  * Individual
  * Collective
  * Enterprise Agreement
  
  For Collective ones, the business is registered as the 'client' and the members involved are related to the Case via a separate Relationship. So there is just one Case that encompasses all the affected workers.
  
  > **Comments:**
  > **username_0**: Thanks for the suggestions. I suspected your suggestion might be the way to go, but the fact that others have used this approach successfully is comforting.  
  > **username_1**: Sweet. Ours was using a Drupal platform so most of the UI was via webforms and views. am sure native civi can handle it better now but we needed lots of dashboards to help the case managers and their managers all keep really good tabs on what the current state of play was. also in inbound emails as Activities to ensure email threads with clients were kept in the case.  
  > **username_1**: https://civicrm.org/extensions/documents was also really important part of their toolkit which we had to extend to ensure it all played nicely with webforms but would have contributed code back to the maintainers  
  
  ---
  
  ### Answer by username_2 on 2024-12-15. Score: 1
  
  Sometimes the answer to these types of questions is determined by "what reports do you need", but here's some ideas:
  
  1. Create a separate case for each employee, and use the "link cases" feature to link them together. This might be useful for orgs that have extra privacy rules where you need to keep the information separate, or makes it easier if they ask for their file then you can give it to them without weeding stuff out.
  2. Create a contact subtype for orgs called something like "group claim". Make org contacts with that subtype representing each group. Give the relevant employees an employee relationship (or some other relationship) to that org. Then make the case client be that org.
  3. Pick someone as the "spokesperson" for the group, and make them the case client. Give the other people roles on the case.
  
  > **Comments:**
  > **username_0**: Thanks for the suggestion. I think suggestion 2. might be a favourite to explore.  
  
  ---
  
  