Skip Tracing Goes Federal: ICE Awards $281M in Nationwide Contracts
Federal money does not make a bad address good. It does not turn a possible match into the right person. That is my first thought when I look at the $281M nationwide skip tracing contracts surrounding ICE's locate work.
My next thought is that every process server and investigator should pay attention, even if government contracts are nowhere in your business plan. The tools getting attention here overlap with the tools we use to find people, verify addresses, and decide where to make the next attempt.
I built my process serving company in Redding, in Northern California. Finding the subject is often the hard part of getting papers served. A client can send a complete packet and still leave you with an address that goes nowhere.
This is not legal advice. Verify current laws, licensing requirements, database permissions, and the rules governing your assignment. A federal contract is not permission for a private business to use the same methods or access the same information.
What the federal contracts actually tell us
Beginning in late 2025, U.S. Immigration and Customs Enforcement awarded multiple contracts for nationwide skip tracing. The work supports Enforcement and Removal Operations, known as ERO, in locating people and verifying addresses.
The $281M framing describes the nationwide contract initiative. It should not be confused with a single contractor's award or presented as money already paid out for completed work.
One example in the source reporting is AI Solutions 87 LLC. It received an indefinite-delivery contract in December 2025 with a reported ceiling of approximately $48.5 million through December 2027. That contract structure allows task orders as services are needed. A ceiling is not the same thing as a guarantee that the full amount will be spent.
The broader effort includes companies named in the source as BI Incorporated, SOS International, Capgemini Government Solutions, and AI Solutions 87. What matters for our industry is the direction: location research and address verification are being treated as substantial, organized services, not an afterthought attached to somebody else's assignment.
The work is familiar. The scale is different.
Skip tracing means locating someone whose current whereabouts are unknown or need verification. Process servers, private investigators, debt collectors, attorneys, recovery professionals, and government agencies all use it.
That does not make every assignment equivalent. The purpose, legal authority, permitted information, and consequences can be very different. But the underlying research problem is recognizable: records point somewhere, and someone has to decide whether that information is reliable.
The source describes batches involving tens of thousands of records needing address or location verification. At that scale, companies need more than individual searches. They need ways to organize information, compare records, flag conflicts, and put useful leads in front of investigators.
For a local server, the workload may be smaller, but the lesson still applies. A confusing research file does not become useful just because it contains more information. Your system should help you make a defensible decision about the next step.
AI can organize the search. It cannot own the conclusion.
I see a practical role for AI in locate work. It can help match addresses across records, identify possible relationships, detect residence changes, prioritize leads, and organize material for human review.
Those are useful tasks. Sorting through repetitive information takes time, and a good tool can help an investigator focus attention where it belongs.
But a suggested connection is not a verified fact. An address associated with a name is not automatically that person's current residence. A relationship between records does not establish where somebody can actually be found.
Bad data does not become better when software processes it faster. It can become a bad lead that moves through the workflow before anyone stops to question it.
My rule would be simple: let technology suggest what to examine, not what to swear is true. If the system gives me a result I cannot explain, I need more verification, not a more confident label on the report.
Before the next attempt, separate leads from facts
The practical question for a process server is not whether a database can produce an address. It is whether that address deserves an attempt, and how honestly you describe what you know.
I would build the review around questions like these:
Does the identifying information fit the subject, rather than somebody with a similar name?
Is the address information current enough to justify relying on it?
Do other lawfully available records support the connection?
Are there conflicting addresses or details that still need explanation?
What has been confirmed, and what remains only a possible lead?
That is a working checklist, not a legal standard or a promise that any particular search will succeed.
When fieldwork is appropriate and lawful, use it to test the research rather than force the research to fit. If the information at the location contradicts the lead, document the contradiction. Do not quietly turn uncertainty into confirmation because the client wants movement.
A clear negative result can be more valuable than an impressive-looking report that sends the next server back to the same wrong place.
What this means for your process serving business
Clients may increasingly expect locate services alongside service of process. That creates an opportunity, but it also creates room for confusion about what they are buying.
I would explain the scope before the job starts. Are you attempting an address the client supplied? Are you researching possible new addresses? Are you coordinating with an investigator? What will the client receive if the research produces leads but no confirmed location?
Keep those distinctions clear in your updates. Research completed is not the same as a person located. A possible address is not the same as successful service.
The federal investment does not mean you need to chase government work or buy every new research platform. It means the locate side of our profession deserves deliberate attention.
For me, the practical priorities would be:
Know what locate work you can lawfully perform.
Use information sources permitted for your purpose.
Explain the difference between research and verification.
Keep useful notes about sources, conflicts, and follow-up.
Tell the client when an address is uncertain instead of overselling it.
Your reputation rides on the quality of those decisions, not the number of search results you can attach to an email.
Investigators need more than another database login
For private investigators, I think the strongest approach is the combination described in the source: public records, commercial databases, AI-assisted research, field investigation, and human verification.
No single part of that combination should carry the entire conclusion. A database may produce a useful starting point. AI may help organize it. Public records may support or complicate it. Field investigation may show whether the lead holds up.
The value is in knowing what to trust and what to question.
If you are evaluating a new tool, ask practical questions. Can you review the information supporting a suggested match? Can you recognize conflicts? Can you explain the result to a client without hiding behind the software?
I would rather work with an investigator who can explain a careful conclusion than one who promises certainty because a platform returned a confident answer. Technology should strengthen professional judgment, not become an excuse to stop using it.
Privacy is part of the job, not a separate conversation
The ICE initiative has drawn attention to privacy, surveillance, accuracy, and the incentives attached to large-scale investigative work.
Those concerns are not limited to federal enforcement. Process servers and investigators also work with personal information. The fact that information can be found does not answer whether it should be accessed, retained, shared, or used for a particular assignment.
I would want my workflow to answer basic questions: Why are we collecting this information? Are we allowed to use this source for this purpose? Who needs access? What supports our conclusion? What should happen to the information when the work is finished?
Those are practical review questions, not a claim that every jurisdiction has identical requirements. Get qualified guidance on the rules that actually apply.
Accuracy belongs in the privacy discussion too. Connecting the wrong person to an address can affect somebody who has nothing to do with the assignment. Human review matters because the records describe people, not just entries on a screen.
Capgemini is a reminder that reputation travels
Capgemini Government Solutions received an ICE skip tracing contract in December 2025. The work generated backlash in France. In February 2026, Capgemini announced plans to divest Capgemini Government Solutions following that controversy.
That is an announced plan, not a claim here that the divestiture has been completed.
For a local investigative business, the takeaway is not that your assignments will attract the same attention. It is that technical ability and contract terms are not the only considerations in accepting work.
I would ask whether I understand the assignment, its purpose, its boundaries, and the way the information will be used. If I cannot comfortably explain my methods and role, that deserves attention before I accept the job, not after somebody questions it.
What I am watching in 2026
The source identifies several developments worth following: additional ICE task orders, AI-based research platforms, privacy legislation, data broker regulation, court decisions involving surveillance and location data, investigator licensing, and documentation standards.
I would watch those issues without pretending the outcome is settled. Possible regulation is not an enacted requirement. A proposal aimed at government contractors does not automatically impose the same obligations on every process server.
Still, waiting until a rule changes is not a reason to ignore the discussion. Understand your current practices now so you can evaluate what a future change might affect.
Keep track of the information you use, the purposes you use it for, and how you verify results. If standards change, a clear workflow gives you something concrete to review. A collection of undocumented habits does not.
Frequently asked questions
What is skip tracing?
It is the work of locating someone whose current whereabouts are unknown or need verification. For a server, it may be the research needed before a useful service attempt can happen.
Why is ICE hiring private companies?
Its ERO division uses contractors to help locate individuals and verify addresses for enforcement operations. The nationwide initiative combines private research capabilities with government locate needs.
Does that mean private investigators are involved?
The contracts are with private companies performing skip tracing and address-verification work. Depending on the contractor and assignment, the work can include database research, digital investigation, and field verification. That does not establish a particular investigator's role or credentials.
What can AI do in skip tracing?
It can help compare records, find possible connections, prioritize leads, and organize research. Those capabilities do not remove the need to check identities, resolve conflicts, and verify conclusions.
Why should a process server care about federal contracts?
The initiative puts attention on locate services, investigative technology, privacy, and accuracy. Those subjects can affect client expectations and the wider discussion of how our tools should be used.
Will AI replace investigators?
I see it changing the work, not eliminating the need for judgment. Someone still has to determine whether a lead is reliable and whether the next step is lawful and appropriate.
Better technology still needs somebody willing to question it
The federal contracts make a big headline. The everyday lesson for me is smaller and more practical: finding an address and knowing it is the right address are different accomplishments.
Use the technology. Learn what it does well. Understand where it can mislead you. Then do the verification and keep the documentation that makes your conclusion worth trusting.
Our value is not that we can repeat what a screen tells us. It is that we can use information responsibly, recognize uncertainty, and make sound decisions about real people. That is where human judgment still earns its place.
Stay sharp. Stay informed. Live Mighty!
Read the full article at www.mightyprocessserver.com
This article is published by Process Server Daily, powered by MightyAutomation.ai, the leader in legal support intelligence.
