Blog

When Your File Disagrees With Itself: How to Brief a Skip Tracer on Conflicting Addresses, Shared Names, and Stale Leads

October 1, 2026•15 min read•By Skip Trace Services

You open the file to send it out for a locate. Within five minutes you find three problems. The intake sheet lists one address. A letter from last spring went to a different address. A note from a colleague says the subject "may have moved in with family." There is also a second person with the same name living two towns over.

Most attorneys, collection managers, process servers, and investors have opened a file like this. The usual reaction is to pick the most recent-looking data, send it along, and hope the skip tracer sorts it out. That habit costs you more than you might expect. When contradictions go into a request unlabeled, they come back as confusion. That confusion can show up as a report on the wrong person, a search for the wrong kind of result, or a long exchange of clarifying emails.

This article does not cover what to collect at intake. It covers what to do when the information you already have contradicts itself. Here's what you need to know: a contradictory file is workable if you brief it honestly. Below we walk through four common contradictions, using clearly labeled hypothetical scenarios. For each one, we show how to brief your provider. At the end you'll find a one-page conflict brief template you can adapt for your own matters.

Why Contradictions Are a Briefing Problem, Not a Dead End

A file that disagrees with itself is not a failed file. It is a normal file. People move, share names with relatives, rent rooms informally, and leave behind records that update on different schedules. The real problem starts when those disagreements are flattened. That happens when the person preparing the request quietly picks one version of the truth and presents it as fact.

When you flatten a conflict, you remove the information your skip tracer most needs. An address you believe is current but haven't confirmed looks the same as one you verified yesterday. A relative with the same name becomes invisible. The provider has to rediscover the conflict on their own, or may never learn it existed.

Borrowing a Useful Concept: Data Provenance

The National Institute of Standards and Technology published the Artificial Intelligence Risk Management Framework (AI RMF 1.0) as a general framework for managing risk in AI systems. It is not a skip tracing standard. It contains no locate-specific guidance or benchmarks, and it does not endorse any vendor's approach. Still, it describes a concept that maps neatly onto the briefing problem: data provenance, meaning the documented origin and history of a piece of information. The same framework also stresses related ideas such as traceability and human verification.

The lesson for your file is simple. A data point without a source and a date is hard to weigh. "123 Main Street" tells your provider very little. "123 Main Street, from the original credit application, dated four years ago, never confirmed since" tells them a great deal. Provenance does not make your data more accurate. It makes the data's reliability visible, so the person working your file can decide how much weight to give it.

The Four Briefing Habits That Apply to Every Conflict

Every scenario below uses the same four habits:

Label every data point with its source and date. Where did it come from, and when was it last true as far as you know?
Separate what is confirmed from what is assumed. Confirmed means someone verified it. Assumed means it seemed reasonable.
Flag known duplicates or relatives. If you know someone shares the subject's name or household, say so plainly.
State the outcome you need. A current residential address, a place of employment, and asset information are different requests. Say which one matters.

Scenario One: The Stale Address You Believe Is Current

Hypothetical scenario, for illustration only. A small property management client refers a collection matter on a former tenant. The client's records show a forwarding address the tenant gave verbally at move-out about 18 months ago. The client says the tenant "definitely lives there." When asked, the client admits no one has sent anything to that address or checked it since.

What Goes Wrong If You Brief It As-Is

If the forwarding address goes into the request as the subject's current address, it carries false authority. The provider may treat confirming it as the main task, when the real question is whether it was ever accurate at all. A verbal forwarding address given at a stressful moment can be a real residence. It can also be a friend's place, a mailing convenience, or a guess.

How to Brief It

Present the address with its full context:

Source: Verbal statement by the subject to the property manager at move-out.
Date: Approximately 18 months before the request.
Status: Unconfirmed. No mail sent, no visit, no independent check.
Client belief: The client believes it is current. Note this as a belief, not a finding.

Then add the sentence that matters most: "Treat this address as a lead, not a starting assumption." This one line changes how your request is read. It tells the provider that a different, more current result is acceptable and expected. It also tells them that you don't need the old address defended.

One practical tip: if your client is emotionally attached to a particular address, document their confidence separately from the evidence. Writing "Client is highly confident; basis for confidence is the move-out conversation" keeps the client's view in the file without letting it outrank the facts.

Scenario Two: Shared Names in the Same Household or Metro Area

Hypothetical scenario, for illustration only. A law firm needs to locate an individual for a civil matter. The subject shares a first and last name with a parent, and the two have lived at the same address at different points. Separately, the surname is common in the subject's metro area. A quick search by the paralegal turns up several adults with the same name within the same county.

What Goes Wrong If You Brief It As-Is

Shared-name files carry the highest risk of a confident wrong answer. Without a flag, a provider may get a clean, well-supported result that belongs to the parent, not the subject. Records that blend two people can make one person look like they have an unusually long or scattered history. The danger is not a lack of results. The danger is a plausible result about the wrong individual.

How to Brief It

Name the duplication problem at the top of your brief, not buried in the notes:

Known namesake: State that a parent shares the subject's full name. Include any distinguishing details you lawfully hold, such as an approximate age difference or a generational suffix if one is used.
Shared address history: Note which addresses you believe belong to the parent, which to the subject, and which are unclear. Label each with its source and date.
Common surname warning: State that multiple same-name adults appear in the metro area. If you have already ruled any out, explain why and how.
Distinguishing identifiers: List what you hold that separates your subject from the others. Mark each identifier as confirmed or assumed.

If you're unsure whether a detail belongs to the subject or the namesake, say so. "Unknown which individual this belongs to" is a valid and useful entry. It is far better than assigning the detail to the subject and hoping. You should also say what would count as a mismatch. For example: "Any result showing an age above a certain range is likely the parent and should be flagged rather than reported as the subject."

Scenario Three: The Broken Prior-Address Chain

Hypothetical scenario, for illustration only. A real estate investor is trying to reach the owner of a vacant property. The investor's research shows the owner at one address roughly seven years ago and at another address about two years ago. Nothing covers the five years between, and nothing appears after the more recent address. The investor isn't sure the two addresses even belong to the same person.

What Goes Wrong If You Brief It As-Is

A gap in the address history often gets treated as noise, so the request lists only the most recent address. But the gap itself is information. It can point to a move out of state, a period of living with others, institutional housing, military service, or simply records that didn't capture a period. When you leave out the older address and the gap, your provider loses context about where the chain broke and how wide the break is.

How to Brief It

Lay out the chain as a timeline, with the gaps shown openly:

Address A: Source, approximate date range, and whether it is confirmed.
Gap: State the approximate period with no known address. Note any theories you have and label them as theories.
Address B: Source, approximate date range, and confirmation status.
After Address B: State that you have nothing, and when the trail went cold.
Link confidence: Say whether you're confident Addresses A and B belong to the same individual, and why.

That last point matters more than people realize. If you're not sure the two addresses connect to one person, you may actually have a shared-name problem dressed up as an address gap. Flag that possibility directly. A timeline with honest gaps is much more useful than a single address presented as the whole story.

Scenario Four: Records That Simply Disagree

Hypothetical scenario, for illustration only. A collection agency's file on a covered consumer debt account has two addresses, each from a reasonable source. The original account application shows one city. A more recent payment record, from about a year ago, shows a different city in another state. A note from an earlier contact attempt says mail to the first address was not returned. No one can say which address is current, and each has some support.

What Goes Wrong If You Brief It As-Is

When records truly conflict, the urge is to resolve the conflict yourself before sending the file out. You pick the newer one, or the one from the "better" source, or the one that fits your expectation. That choice may be right. But if it's wrong, you've hidden the evidence that would have pointed your provider in the right direction.

How to Brief It

Present the conflict as a conflict:

Record 1: Address, source, date, and supporting evidence (for example, "mail not returned, which does not confirm residence").
Record 2: Address, source, date, and supporting evidence.
What you know about the conflict: Anything that might explain it, such as a known job change or relocation, labeled as confirmed or assumed.
Your current lean, if any: If you lean toward one record, say so and explain why. Make clear it's a lean, not a conclusion.

Note the careful wording about returned mail. Mail that isn't returned is weak evidence. It may mean the subject lives there, or that a current resident simply discarded it. Describe what each piece of evidence actually shows, not what you hope it shows.

A Word on Compliance Context

Scenario four involves a debt collection file, which raises a point worth stating clearly. When a skip tracing assignment is part of debt collection activity covered by the Fair Debt Collection Practices Act, Regulation F § 1006.10 limits what a debt collector may say to third parties when seeking location information. Whether those rules apply depends on the specific activity and facts. They do not cover every locate request, and the reverse is also true: litigation, witness, or investor assignments are not automatically exempt from every debt collection or privacy rule. Your brief should state the purpose of the request honestly so your provider understands the context. For questions about how particular rules apply to your matter, consult your own counsel. This article is not legal advice.

Defining the Outcome You Actually Need

Across all four scenarios, one briefing element is often overlooked: telling your provider what a useful result looks like. A contradictory file pulls in several directions. Without a stated goal, the person working it has to guess which direction you care about.

Common Outcome Types

Be specific about which of these you need, and in what order of priority:

Current residential address: You need to know where the subject lives now.
Employer or place of business: You need a work location, which is a different question from residence.
Asset information: You need to understand property or other assets, which may matter more than location for some matters.
Confirmation or rejection of a specific address: You already have a lead and want to know whether it holds up.
Identity disambiguation: In shared-name files, your first need may simply be confirming which individual is which.

Why Priority Order Matters

If you need a current residence first and asset information second, say so. If an employer address would satisfy your purpose on its own, say that too. A clear priority order keeps the request focused. It also helps you judge any report you receive against what you actually asked for. Stating what you need is not a promise about what will be found. Any locate result depends on what information is available, and no honest provider can guarantee a particular outcome or timeline.

What To Do Now

You don't have to rebuild every file at once. Use this phased approach.

This Week

Pick your three most contradictory open files. Choose the ones where the team disagrees about where the subject is.
Add source and date labels to every address and identifier in those files. Where you don't know the source, write "source unknown." That's useful information too.
Mark each data point as confirmed or assumed. Be strict. If no one verified it, it's assumed.

This Month

Adopt the conflict brief template below for any file with known contradictions before it goes out for a locate.
Brief your team on the four scenarios so staff can recognize stale addresses, shared names, broken chains, and true conflicts when they see them.
Ask your provider what verification information is available with their reports. Knowing what context comes back helps you shape what you send.

This Quarter

Build provenance into intake. Train staff to record the source and date of new information as it arrives, so conflicts are labeled from day one.
Review returned reports against your briefs. Note where clearer labeling would have helped and refine your template.
Set an internal rule that no file with an unresolved contradiction goes out without a completed conflict section.

The One-Page Conflict Brief Template

Use this template as a cover page alongside your standard request. It is not an intake checklist; it assumes you already have basic identifying information. It exists only to document contradictions clearly.

Section 1: Request Purpose and Outcome

Purpose of the request (described honestly and in general terms)
Primary outcome needed (for example, current residential address)
Secondary outcome, if any (for example, employer or asset information)
What would count as a satisfactory result

Section 2: Data Points With Provenance

For each address, phone number, or identifier, list:

The data point
Source (where it came from)
Date (when it was obtained or last believed accurate)
Status: Confirmed or Assumed
Basis for confirmation, if confirmed

Section 3: Known Duplicates and Relatives

Anyone known to share the subject's name
Relationship, if known (parent, child, unrelated)
Data points believed to belong to the namesake rather than the subject
Data points of unknown ownership
What a mismatch would look like

Section 4: Address Timeline and Gaps

Known addresses in date order, each with source and confirmation status
Gaps in the timeline with approximate periods
Theories about gaps, labeled as theories
Confidence that all addresses belong to the same individual

Section 5: Unresolved Conflicts

Each conflicting record, with source and date
What the evidence for each record actually shows
Your current lean, if any, labeled as a lean

Section 6: Notes and Open Questions

Client beliefs, recorded separately from evidence
Questions you want answered
Contact for clarifying questions

Keep it to one page where you can. If a section doesn't apply, write "None known" instead of deleting it. An empty section tells your provider you checked.

The Bottom Line

A file that contradicts itself is normal, and it can still be worked if you brief it honestly. Label every data point with its source and date, separate what you know from what you assume, flag namesakes and relatives, and state exactly what outcome you need. These four habits turn a confusing file into a clear brief your skip tracer can actually use.

Ready to send a file that doesn't add up? Complete your conflict brief and submit it to Skip Trace Services. Our team handles person locate, asset search, and property verification requests nationwide. Feel free to ask what verification information is available for your specific request.