An address change signal is not an address change. A returned envelope, a forwarding notice, a family phone call, and a data-service match all suggest that the record may be stale, but they do not prove the owner's current legal address or the owner's identity. Treating a signal as a confirmed update is how bad addresses get into payment files.
This study design describes how to evaluate address-change signals in mineral owner records. It is an administrative measurement protocol. It does not determine ownership, heirship, or the legal sufficiency of notice.
Mineral Owner Address Change Signal Study: Research question and boundary
The primary question is: for a defined set of address-change signals, what proportion leads to a confirmed update, what proportion is a false positive, and how long does resolution take?
The unit is one owner record and one signal event. An owner with two signals in a quarter produces two units, linked to the same owner record. A signal that is later reversed remains in the dataset as a resolved false positive, not as a deleted row.
The study covers administrative contact data. It does not decide whether an address is legally adequate for a particular notice, whether an heir is entitled, or whether an owner has consented to a contact channel.
Four signal classes
Signals fall into four classes, and each has a different precision profile.
The first is mail return. A returned envelope with a forwarding label or a reason code is a direct signal that the address did not work. It is strong evidence of a delivery failure, but it may not identify the correct new address.
The second is owner-initiated contact. A signed change-of-address form, a written email, or a completed owner portal update is usually stronger than a data-service match because it comes from the owner or representative. It still needs identity and authority checks when the person is not the named owner.
The third is document-derived. A probate filing, trust document, or recorded instrument may state an address. The address may be current for the document date, not for today. Record the document date and the source.
The fourth is third-party data. A national change-of-address file or a commercial data service can suggest a match. These sources are useful for prioritization, but a match is not a confirmation. The USPS forwarding page describes the mail-forwarding service; it does not establish ownership or a permanent legal address.
Why false positives matter
A false positive can create more harm than a missed signal. If a data-service match is accepted without confirmation, a payment or notice may go to a person who is not the owner or who is not authorized to receive it. The owner may not learn about the change until a payment is missed.
False positives also distort the measure. A team that counts every data-service match as an update will report a high resolution rate and a low address quality. The study should count confirmed updates separately from proposed matches and rejected matches.
Data sources and methodology
Build the cohort from the address-change queue or the returned-mail log, not from a list of records that someone happened to clean. Record the extraction date, the signal source, the owner record status, and the workflow version.
| Measure |
Numerator |
Denominator |
Reported with |
| Signal confirmation rate |
Signals with a confirmed update |
Signals reviewed |
Source and reviewer |
| False positive rate |
Signals rejected or reversed |
Signals reviewed |
Reason mix |
| Time to resolution |
Confirmed or rejected signals |
Signals with a resolution date |
Median and age bands |
| Recurrence rate |
Owners with a second signal within 12 months |
Owners with a first signal |
Signal class |
| Contactability rate |
Active owners with a verified channel |
Active owners |
Channel type |
| Coverage |
Owners verified in the period |
Owners due for verification |
Cadence tier |
The evidence base provides general context on mail, population movement, death records, tax administration, privacy, and data quality. It does not establish a required verification interval.
- USPS mail forwarding
- Census migration data
- CDC/NCHS death data
- IRS Form 1310
- IRS Form 56
- NIST Privacy Framework
- NARA Records Management
- GAO Data Reliability Assessment
- BLM land records
- Census economic census
Cohort and stratification
Stratify by signal class, owner type, payment activity, and project. A returned check is a higher-cost signal than a returned newsletter. An owner with a suspended balance deserves a faster review than a dormant owner with no activity.
If the population is large, draw a reproducible sample before reviewing outcomes. If the question is about a specific signal source, such as a data-service match, use a targeted cohort and describe it as such. Do not present a targeted cohort as a prevalence estimate for all owners.
Outcome definitions
A confirmed update requires a source, a date, and a reviewer acceptance. The source may be a signed owner response, a document, or a verified contact that leads to a written confirmation. A proposed update is a signal that has not been confirmed. A rejected update is a signal that was reviewed and not accepted. A reversed update is a confirmed update that was later found to be wrong.
Keep the prior address and the new address. Do not overwrite the old value. The history is needed to reconstruct what was sent and when.
Reliability review
Two reviewers should classify a planned subset. The codebook should define what counts as confirmation, how a phone confirmation is documented, and how a name mismatch affects the decision. Report raw agreement and a chance-adjusted statistic when prevalence permits.
Disagreement often appears when a family member provides an address for an owner who has died. The address may be a valid contact for the estate, but it is not proof that the family member is the owner. The codebook should separate contact confirmation from ownership review.
Analysis and sensitivity
Report the signal confirmation rate, false positive rate, and time to resolution together. A high confirmation rate with a long resolution time may be worse than a lower rate with fast review, depending on the mailing risk. A high false positive rate may indicate a weak source or an overly permissive match rule.
Run sensitivity checks with and without data-service signals, with strict and operational confirmation definitions, and with open signals assigned to the oldest age band. If the ranking of sources changes, report the instability.
Bias and alternate explanations
Address signals are not evenly distributed. Owners with more mail activity generate more returns. Owners with estate changes generate more document-derived signals. A project with a high mailing volume may look worse on returns simply because it sends more mail.
A decline in returns may reflect a better address file, or it may reflect a reduction in mail volume. Report both the numerator and the mailing denominator.
Address data is personal information. Limit access, use approved storage, and avoid putting full addresses or family details in the analytic table. If a data service is used, follow its permitted-use terms and the client's privacy policy. Suppress small cells that could identify an owner.
Interpretation limits
The study describes signal performance in a defined workflow. It cannot establish ownership, heirship, or the legal adequacy of notice. It also cannot prove that a confirmed address is current today. Address data decays continuously, which is why the cadence matters more than a one-time cleanup.
Decision threshold
Define what result triggers a source review, a cadence change, a reviewer training, or a larger sample. A high false positive rate for one source may trigger a rule change. A high recurrence rate may trigger a shorter cadence for that owner tier.
Worked analytic scenario
A team extracts one quarter of address signals from the returned-mail log and the owner-update queue. It classifies each signal, confirms or rejects the update, and records the resolution date. Two reviewers classify a subset and clarify the treatment of a family-provided address for a deceased owner.
The analyst reports confirmation, false positives, time to resolution, and recurrence by signal class. The team uses the result to adjust the source mix and the cadence, not to declare the owner file clean.
Limitations
The design depends on the queue capturing signals. A returned envelope that is discarded before it is logged will not appear. A data-service match that is never reviewed will appear as open, not as a false positive. The report should describe the capture process and the open-item age.
Frequently asked questions
Is a forwarding address a confirmed update?
Not by itself. Treat it as a proposed update and confirm it with the owner or another document before relying on it for a payment or legal notice.
Should every data-service match be reviewed?
Review the matches that affect payments, notices, or high-value owner relationships first. A match that is never reviewed should remain proposed.
Can the study measure legal notice adequacy?
No. It measures administrative contact data. Legal adequacy is a reviewer question that depends on the document, the jurisdiction, and the notice process.
Conclusion
Address-change signals are leads, not conclusions. A useful study reports confirmation, false positives, and time to resolution together, and it keeps contact data separate from ownership decisions. That gives the team a way to improve the address file without creating a new set of unsupported assumptions.
To review an owner address workflow, Book a free consultation. The mineral owner address verification cadence describes the operating cadence that this study is designed to evaluate.
