Before You Hire: A Litigator's Due-Diligence Framework for Process Servers

Every attorney has a story about an affidavit that fell apart. The serve that was supposedly completed on a defendant who had moved out months earlier. The declaration with no times, no descriptions, no corroborating detail. The server who could not be located when opposing counsel subpoenaed him to testify.

These stories share a common root: nobody vetted the server before the work mattered. In our view, that is a practice-management failure as much as a service failure. Here is how to fix it.

Seven Red Flags That Should End the Conversation

1. Vague affidavits. A competent affidavit states the date, time, address, method of service, and a physical description of the person served. A one-line certification is a liability, not a record.

2. No GPS or timestamp data. Modern servers can and should capture geolocation and time stamps on every attempt. If a provider treats this as optional, they are operating a decade behind the standard.

3. Suspiciously fast results. A same-day serve on a defendant known to be evasive is possible — but rare. When a server reports success on an impossible timeline, ask questions.

4. No licensing or registration where required. Many states require registration, bonding, or licensing for process servers. A provider who cannot produce credentials for the relevant jurisdiction is a nonstarter.

5. No insurance. Errors happen. A professional carries liability coverage precisely because a botched serve can trigger sanctions, re-service costs, and malpractice exposure.

6. Poor communication between attempts. If you cannot learn the status of attempts without chasing the provider, your docket is being managed by silence.

7. Unwillingness to testify. Some servers are unavailable, uncooperative, or simply gone when a hearing requires their presence. Ask upfront about testimony availability and any associated fees.

The Four-Part Vetting Framework

We recommend treating server selection like any other expert engagement. Before you retain a provider, run them through four screens.

Licensing and standing. Verify any required state registration or county licensing, confirm bond or insurance coverage, and check for disciplinary history where records are public.

Proof-of-attempt practices. Ask to see a sample affidavit and a sample attempt log. Look for GPS coordinates, photographs where lawful, timestamps, and narrative detail. Technology-enabled providers can typically produce real-time status dashboards — if the sample looks like a form from 1995, keep looking.

Communication standards. Establish expectations before the first attempt: how often you will receive updates, through what channel, and who is accountable. A provider that resists defining this is telling you something.

Track record under pressure. Ask how the provider handles difficult serves — evasive recipients, gated access, rural addresses — and whether their servers are available to testify. References from litigation firms, not just volume clients, are worth more than any marketing claim.

Why the Stakes Keep Rising

Courts are increasingly willing to scrutinize service affidavits, particularly where defendants contest jurisdiction. Digital documentation — GPS trails, timestamped photos, electronic attempt logs — has shifted from a differentiator to a baseline expectation. Attorneys who retain servers operating below that baseline are importing risk into every default judgment they pursue.

The cheapest process server is rarely the least expensive option once you account for re-service costs, motion practice, and the possibility of dismissal. Diligence at the hiring stage is the least expensive insurance available in litigation support.