Unproven lineage and restricted priestly access

These verses sit inside a long list of names and numbers in Nehemiah 7, where Nehemiah uses a register to organize the repopulation and ordering of Jerusalem. The list closely tracks an earlier return list (compare the pattern in Ezra), aiming to identify who belongs where and who is eligible for which roles. In that larger flow, the narrative pauses to highlight an edge case: people who returned with the community but cannot document their ancestry. The logic is administrative: verified identity supports ordered settlement and protected worship practice.

The setting is the Persian-period return to Judah, when communities were being re-established after displacement and when land, offices, and temple duties were tied to family membership. Written records and oral family claims did not always match, especially after generations of exile, migration, and intermarriage. In that world, priestly work and access to certain food portions depended on recognized descent and community confirmation. The text reflects a community trying to rebuild stability by relying on registries, while also acknowledging that some questions could not be settled immediately.

Shared ground

Nehemiah 7:61–65 pauses the larger census list to describe an “edge case”: some returnees could not verify their family lines from available records. The text explicitly says they could not show their “fathers’ houses” or their “seed,” and so they could not confirm “whether they were of Israel.” Even so, they are still counted (642) as real members of the returning group.

The most serious case involves people who claimed priestly status. They searched for their entry in the genealogical register, but it was not found. As a result, they were treated as “polluted” for priestly purposes and removed from the priesthood. The governor then restricted them from eating “the most holy things” until a future, authorized determination could be made (a priest with Urim and Thummim).

Where interpretation differs

Two main questions come up from details the text does not fully explain.

1. What exactly is meant by “polluted”? Some read it mainly as a ritual label connected to temple holiness: without verified priestly descent, they are treated as unclean for priestly functions and foods. Others read it more as an office-status judgment: they are disqualified from serving as priests because they cannot prove eligibility, even if their everyday ritual state is not in view.

2. What is the expected role of Urim and Thummim? Some read verse 65 as expecting a direct, God-guided decision that could settle disputed cases beyond what records can prove. Others read it as a way of saying: “No final decision can be made right now,” since Urim and Thummim are not shown functioning in this period; therefore the restriction stands as a practical, long-term safeguard.

Why the disagreement exists The passage reports outcomes (excluded from priesthood; barred from most holy food) but does not spell out the mechanics: it does not define “polluted,” does not show Urim and Thummim being used here, and does not say whether the problem is missing documents, broken lines of descent, name changes, or a mix. The note about Barzillai highlights how family naming could complicate identification, but the text stops short of explaining the full process.

What this passage clearly contributes This section shows that community membership and temple roles were handled differently: people could be counted among returnees even when their lineage could not be proven, while priestly access required a higher level of verified ancestry. It also shows a precautionary approach to sacred privileges—restricted foods and priestly service were withheld when eligibility could not be confirmed, pending an authorized means of resolution. The passage ties worship order to publicly recognized identity rather than to private claims alone (compare Ezra 2:61–63).