Answers.Body: <p>It depends on why you're using households. If your only goal with householding is to avoid duplicate paper mailing, then I find that you don't need them at all, you can just use the export option to merge contacts with the same address. I used the household contact type early on but then stopped using them due to confusion and have never found a reason to use them since.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-13T22:32:46.057Z
Answers.Text: Some people need to use households in order to acknowledge members of a household as donors, by recording a contribution or soft credit to the household, even though the contribution itself was made by one person or another. We found that just making labels from a donor list wasn't inclusive enough.
Answers.UserDisplayName: Christia
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-15T16:24:51.600Z
Answers.Text: Yes, agreed that there are valid use cases for households.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-13T21:08:34.910Z
Answers.LastActivityDate: 2016-12-13T21:08:34.910Z
Answers.UserDisplayName: Alan Dixon
Answers.Body: <p>We have been going over this a lot with my fundraising team, trying to find a happy medium. When generating labels or PDF letters for one per household, be sure to create labels with only households. Then, you can even create a smart group that consists of individuals that are also part of a household and exclude that group from the rest of the "individuals" mailing list so that you don't get labels with both households and the same people individually. </p>
  
  <p>Every time someone proofs the labels for duplicate members of the household, they should mark it up and have someone change the data in the CRM to add them to a household. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-13T18:17:25.067Z
Answers.Text: This is not exactly adding to the answer, but might be very helpful for anybody dealing with households: This extension here provides some more userfriendly workflows, e.g. merging contacts directly from search results into households: https://github.com/systopia/de.systopia.householdmerge/
Answers.UserDisplayName: Martin Peth
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-13T20:55:27.343Z
Answers.Text: You don't say what version of Civi  you are running but if you are running 4.7.x the extension that Martin posted above doesn't work with 4.7.x. I wish it did though.
Answers.UserDisplayName: frTommy
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-14T04:36:22.483Z
Answers.Text: @Christia, It is definitely a correct answer but not the one I was looking for. We already operate in a similar way. I was hoping there was an easier more streamlined way of doing this.
Answers.UserDisplayName: Yossi
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-14T18:26:39.263Z
Answers.Text: If you create one smart group with all the parameters, then you don't have to do all the work moving forward, you just print labels from the smart group. The smart group would be set up to exclude other smart groups that you created, such as people that are also in a household.
Answers.UserDisplayName: Christia
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-12-13T00:42:31.707Z
Answers.LastActivityDate: 2016-12-13T00:42:31.707Z
Answers.UserDisplayName: Christia
Body: <p>What are the best practices for storing couples and households?
  Currently, every contact is an individual and a household is created for couples and families only. 
  This causes two undesirable outcomes. </p>
  
  <p>1) When creating labels, if I select the 'merge all contacts of the same household' option, the children are also included in the label. I just want the parents. </p>
  
  <p>2) When making PDF letters for all my contacts, I only want 1 letter per household but I end up with one for each spouse.</p>
  
  <p>How do you avoid this situation?</p>
  
Tags: <contacts><households>
Title: Contact Management - Best practices for couples and households
ThreadText: # Contact Management - Best practices for couples and households
  
  (Asked by: username_0 on 2016-12-12)
  
  What are the best practices for storing couples and households?
  Currently, every contact is an individual and a household is created for couples and families only.
  This causes two undesirable outcomes.
  
  1) When creating labels, if I select the 'merge all contacts of the same household' option, the children are also included in the label. I just want the parents.
  
  2) When making PDF letters for all my contacts, I only want 1 letter per household but I end up with one for each spouse.
  
  How do you avoid this situation?
  
  **Tags:** contacts, households
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-12-13. Score: 5 | Accepted answer
  
  We have been going over this a lot with my fundraising team, trying to find a happy medium. When generating labels or PDF letters for one per household, be sure to create labels with only households. Then, you can even create a smart group that consists of individuals that are also part of a household and exclude that group from the rest of the "individuals" mailing list so that you don't get labels with both households and the same people individually.
  
  Every time someone proofs the labels for duplicate members of the household, they should mark it up and have someone change the data in the CRM to add them to a household.
  
  > **Comments:**
  > **username_3**: This is not exactly adding to the answer, but might be very helpful for anybody dealing with households: This extension here provides some more userfriendly workflows, e.g. merging contacts directly from search results into households: https://github.com/systopia/de.systopia.householdmerge/  
  > **username_4**: You don't say what version of Civi  you are running but if you are running 4.7.x the extension that Martin posted above doesn't work with 4.7.x. I wish it did though.  
  > **username_0**: @username_2, It is definitely a correct answer but not the one I was looking for. We already operate in a similar way. I was hoping there was an easier more streamlined way of doing this.  
  > **username_2**: If you create one smart group with all the parameters, then you don't have to do all the work moving forward, you just print labels from the smart group. The smart group would be set up to exclude other smart groups that you created, such as people that are also in a household.  
  
  ---
  
  ### Answer by username_1 on 2016-12-13. Score: 0
  
  It depends on why you're using households. If your only goal with householding is to avoid duplicate paper mailing, then I find that you don't need them at all, you can just use the export option to merge contacts with the same address. I used the household contact type early on but then stopped using them due to confusion and have never found a reason to use them since.
  
  > **Comments:**
  > **username_2**: Some people need to use households in order to acknowledge members of a household as donors, by recording a contribution or soft credit to the household, even though the contribution itself was made by one person or another. We found that just making labels from a donor list wasn't inclusive enough.  
  > **username_1**: Yes, agreed that there are valid use cases for households.  
  
  ---
  
  