<p>I don't get it, you say you have a household ID. If it is the same across waves, then it is the same household over waves. Most likely the people who collected the data will be able to answer the question of whether this is the same household better than you.</p>
<p>The exact definition of who constitutes a household is necessarily arbitrary and varies to some degree between countries. However, the large surveys tend to gravitate around a definition that includes everybody who has lived in the same &quot;building&quot; (whatever that may be) and at least one meal together for more than 6 months in the last year. Then they tend to narrow this down e.g. excluding workers being paid while living there etc. You can check out a questionnaire from a large survey, for instance Living Standard Measurement Survey by the World Bank, at the beginning of the household roster they usually have a section describing who is part of the household.</p>
<p>Households will be given a unique id the first time they are interviewed and followed using this id over the subsequent waves (there is no kind of probability-based matching going on). To re-identify the same households, surveys will use address / GPS, name, and contact details.</p>
<p>In sum: There is really not much point worrying about this. Just group based on hhid and spend your time on other problems in the data (which likely there will be enough of ;))</p>

CC BY-SA 4.0
2021-02-19T18:08:39.283Z
Thanks for your answer. The issue is that I want to track "the same" household over multiple waves of the survey - but each household is assigned a new identifier for each year. For each individual, I know which household ID they had in previous waves. Obviously, household composition changes over time, so that doesn't help me decide which of the individuals belongs to the "old" household, and which has split off.
Alison
CC BY-SA 4.0
2021-02-20T13:52:43.343Z
Ah, now I get it. And can you follow individuals over time, do you have unique person id?
Papayapap
CC BY-SA 4.0
2021-02-20T13:56:59.073Z
I haven't used LSMS, but if it is a panel survey then there should be a merge identifier and it should usually be laid out in the data documentation. No way the survey collectors would distribute the data without a merger, unless it is different households in each wave.
Papayapap
CC BY-SA 4.0
2021-02-20T18:11:59.513Z
The merge identifier is the individual ID! Hence the difficulty in deciding what constitutes a household.
Alison
CC BY-SA 4.0
2021-02-20T19:50:24.583Z
Okay, in case you have Info on household Head (?) then you can use the previous wave hhid from this person and all people with the same current hhid?
Papayapap
CC BY-SA 4.0
2021-02-22T14:47:36.900Z
I think that's my safest bet right now. Thanks a lot for your help!
Alison
CC BY-SA 4.0
2021-02-19T14:09:16.337Z
2021-02-19T14:09:16.337Z
Papayapap
<p>For my thesis, I'm working with a panel dataset that tracks individuals within households. To allow for merging, the dataset provides the household ID in the previous round for each individual. What I'm wondering is how to decide based on this information that a household is &quot;the same&quot; in two different rounds of data collection.</p>
<p>As I'm looking at the socio-economic outcomes of various farming practices, my concern is that there are unobservable household characteristics that influence the farmer's returns to farming but then also correlate with various household outcomes, such as education, assets, etc. To control for this, I'd like to use household fixed effects.</p>
<p>However, I'm wondering which features of a household would justify me saying &quot;this is the same household and these effects are fixed over time&quot;. For instance, I don't want to use the household head because if the head changes and every other aspect of the household is identical, the impacts on farming outcomes shouldn't be too large. My question hence is whether there are commonly accepted characteristics for identifying households over time?</p>
<p>For reference, the data I'm using is the Living Standards Measurement Survey - Integrated Surveys on Agriculture, by the World Bank.</p>

<paneldata><empirical-methods>
Identifying Households in Panel Data
Alison
# Identifying Households in Panel Data

(Asked by: username_0 on 2021-02-18)

For my thesis, I'm working with a panel dataset that tracks individuals within households. To allow for merging, the dataset provides the household ID in the previous round for each individual. What I'm wondering is how to decide based on this information that a household is "the same" in two different rounds of data collection.

As I'm looking at the socio-economic outcomes of various farming practices, my concern is that there are unobservable household characteristics that influence the farmer's returns to farming but then also correlate with various household outcomes, such as education, assets, etc. To control for this, I'd like to use household fixed effects.

However, I'm wondering which features of a household would justify me saying "this is the same household and these effects are fixed over time". For instance, I don't want to use the household head because if the head changes and every other aspect of the household is identical, the impacts on farming outcomes shouldn't be too large. My question hence is whether there are commonly accepted characteristics for identifying households over time?

For reference, the data I'm using is the Living Standards Measurement Survey - Integrated Surveys on Agriculture, by the World Bank.

**Tags:** paneldata, empirical-methods

---

## 1 answers

### Answer by username_1 on 2021-02-19. Score: 1

I don't get it, you say you have a household ID. If it is the same across waves, then it is the same household over waves. Most likely the people who collected the data will be able to answer the question of whether this is the same household better than you.

The exact definition of who constitutes a household is necessarily arbitrary and varies to some degree between countries. However, the large surveys tend to gravitate around a definition that includes everybody who has lived in the same "building" (whatever that may be) and at least one meal together for more than 6 months in the last year. Then they tend to narrow this down e.g. excluding workers being paid while living there etc. You can check out a questionnaire from a large survey, for instance Living Standard Measurement Survey by the World Bank, at the beginning of the household roster they usually have a section describing who is part of the household.

Households will be given a unique id the first time they are interviewed and followed using this id over the subsequent waves (there is no kind of probability-based matching going on). To re-identify the same households, surveys will use address / GPS, name, and contact details.

In sum: There is really not much point worrying about this. Just group based on hhid and spend your time on other problems in the data (which likely there will be enough of ;))

> **Comments:**
> **username_0**: Thanks for your answer. The issue is that I want to track "the same" household over multiple waves of the survey - but each household is assigned a new identifier for each year. For each individual, I know which household ID they had in previous waves. Obviously, household composition changes over time, so that doesn't help me decide which of the individuals belongs to the "old" household, and which has split off.  
> **username_1**: Ah, now I get it. And can you follow individuals over time, do you have unique person id?  
> **username_1**: I haven't used LSMS, but if it is a panel survey then there should be a merge identifier and it should usually be laid out in the data documentation. No way the survey collectors would distribute the data without a merger, unless it is different households in each wave.  
> **username_0**: The merge identifier is the individual ID! Hence the difficulty in deciding what constitutes a household.  
> **username_1**: Okay, in case you have Info on household Head (?) then you can use the previous wave hhid from this person and all people with the same current hhid?  
> **username_0**: I think that's my safest bet right now. Thanks a lot for your help!  

---

