Population measurement and sources · Lesson 1

Population universe and reference date

3 min read

Lesson objectives

  • Define the population, reference date and residence rule; reconcile records before publishing a count.
Reading tools

Population universe and reference date

A population count answers a defined question: who, where and when? Before adding rows, specify the geographic boundary, reference date, unit of count (persons or households), and inclusion rule. One source might enumerate people present on a particular night while another uses usual residence. Different counts do not by themselves prove either source wrong. A visitor does not become a usual resident because they appear in a service register. Nor is a temporarily absent resident automatically excluded. The date forms were collected may differ from the reference date represented by responses. Collection over two weeks can still refer to one common day. Before calling a change between two years population growth, check whether boundaries, inclusion rules and dates match. A raw list may have more than one row for a person following an address transfer or data import. Do not delete a row solely because two names look alike; verify an identifier and record date. Keep a reconciliation table for each adjustment. Actual record linkage requires privacy controls. This invented case does not authorize release of individual information.

Before testing whether two sources agree, check each source's internal reconciliation. If age groups partition everyone exactly once, their sum should match the total for the same boundary and date. A gap may reflect unknown ages or different inclusion rules, not merely an addition error. Keep unknown ages separate rather than allocating them to groups by guesswork. If a register cannot distinguish visitors from usual residents, do not rescue the figure with an arbitrary correction factor. Label the measured population ‘people appearing in the register’ until a verifiable residence rule is available.

Lesson summary

A count needs a defined universe, boundary, date and residence rule; reconcile duplicate rows, visitors and missing residents before use.