SERVEDWIRE
Compliance

3 Attempts or Bust: How California Process Servers Are Adapting to AB 747's New Diligence Standard

By Pete Campbell ·
Disclosure: Some links in this article are affiliate links. If you click and buy, I may earn a small commission at no extra cost to you. I only recommend tools I'd actually use.

This article contains affiliate links. If you purchase through them, Served Wire earns a small commission at no extra cost to you.


3 Attempts or Bust: How California Process Servers Are Adapting to AB 747’s New Diligence Standard

For most of California’s process serving history, “diligent search” meant whatever you could defend in court if someone pushed back. Two trips, three trips, a note on the door — judges gave reasonable deference, and most servers gave reasonable effort.

AB 747 is changing that calculation. Not by inventing a new standard, but by putting teeth on the existing one.

The law — which takes full effect January 1, 2027 — requires GPS-verified, timestamped photographic proof for every service attempt, not just the final successful serve. Combined with California’s existing reasonable diligence requirement for substituted service, the practical result is this: if you can’t prove you were there, you weren’t there.

Here’s how the industry is actually responding.


The Standard Servers Are Coalescing Around

Ask attorneys on the plaintiff side what they’re putting in their service instructions now, and you’ll hear a consistent answer: three attempts, spread across different days, at different times of day.

This isn’t word-for-word statutory language. The California Code of Civil Procedure requires “reasonable diligence” for substituted service — courts have always had to interpret what that means in context. But after years of litigation over what “reasonable” looks like, a working consensus has formed:

  • Three separate attempts
  • Spread across at least two or three different calendar days
  • Covering meaningfully different time windows — not three morning trips in a week

AB 747 doesn’t change that standard. What it changes is the documentation: every attempt now needs photo proof with GPS coordinates. For the first time, “I tried three times” needs to be verifiable, not just assertable.

The servers adapting fastest are the ones who already understood that the standard existed — they’re just adding the documentation layer. The ones struggling are those who relied on the flexibility of an unverified record.


What’s Actually Changing in the Field

Talk to working process servers in California right now and you’ll hear the same themes.

Routing is getting more deliberate

The old model: drive to an address, knock, log a note, move on. Come back when the calendar allows.

The new model: plan three-day windows per serve from the start, and route based on geographic clusters so you’re not driving across the county for attempt number two.

This sounds minor. It isn’t. A server handling 30 active cases doesn’t have the mental bandwidth to track “where am I in the attempt cycle on each of these” without a system. The servers who are adapting well have moved to case management apps that surface this automatically — you open the app, it tells you which cases are due for attempt 2 or 3 today, in what neighborhood, in what time window.

The time-of-day variable is getting real attention

One of the quiet shifts happening right now: servers are actually thinking about when they knock.

Under the old model, plenty of servers did all their personal service attempts during business hours — 9am to 5pm, whatever their schedule allowed. That works if the subject is home during the day. If they’re not, three morning attempts at 9am doesn’t demonstrate diligent search in any meaningful sense.

Courts have dinged this before. But without a timestamped record, it was hard to prove that a server’s “three attempts” were all on Tuesday morning before lunch.

Now the timestamps come with the territory. Attorneys who’ve had substituted service challenged are explicitly writing “must include one attempt after 5pm” or “must include one weekend attempt” into their service instructions. Servers are adapting their schedules accordingly — often adding one early-evening run to their weekly route.

Photography is becoming a professional skill

This sounds absurd until you’ve seen a photo that wouldn’t hold up in court.

A blurry shot of the sidewalk, taken from inside your car, with no visible address number — that’s not documentation. That’s a liability.

The servers taking this seriously are learning to take the right photo: address number visible, front of the property identifiable, taken at the door (not from the curb), good enough lighting to see it was taken at the time of day you claim.

For servers who’ve been in the industry for decades and never thought much about photography, this is a real skill shift. Not complicated — but deliberate.


Where the Friction Is

Not all the adaptation is smooth. A few consistent pressure points are emerging.

Volume businesses feel it most. A high-volume process server handling 200 cases a month isn’t just doing 200 serves now — they’re doing potentially 600 attempts, each with photo documentation. The workflow tax is real. The servers who’ve invested in good apps are managing. The ones who haven’t are starting to feel squeezed.

Rural serving areas add complexity. In counties like Amador, Trinity, or Modoc, a “different day” attempt might be a 90-minute round trip. The economics of three-attempt diligence change when fuel costs and drive time go up. Some rural servers are building that into their pricing. Others are looking at how to batch rural cases more efficiently.

Substituted service threshold creep. Some attorneys, watching the documentation requirements for diligent search increase, are quietly raising their internal threshold before they’ll authorize a substituted serve. Three attempts used to be enough. Some are now asking for four or five before they’re comfortable. That’s not in the statute — it’s attorney risk management. But it’s a real shift in what gets authorized.


What Successful Adaptation Looks Like

The servers who are ahead of this share a few traits.

They’ve picked an app and committed to it. Not “I’m trying out three apps.” Not “I use my phone’s camera app and email myself the photos.” One system, consistently used, that automatically captures GPS and timestamp data and stores it tied to the case. ServeManager, ABC Legal 24L, ProofServe — any of these work. What doesn’t work is patchwork.

They’ve rebuilt their routing logic. Attempt 1, attempt 2, attempt 3 are scheduled when the case is accepted — not figured out on the fly. Their case management surfaces which cases need what today.

They’re talking to the attorneys they work with. The best server-attorney relationships right now include a conversation about what the attorney needs in the proof of service documentation for each case. Some attorneys want specific time windows. Some have preferences about which app’s export format they want. Getting that conversation out front saves a lot of back-and-forth later.

They’ve updated their pricing. Three documented attempts with GPS photo documentation takes more time and resources than informal diligent search used to. Servers who’ve repriced their substituted service rate to reflect this reality are doing fine. Servers who haven’t are eating the margin difference.


The Bigger Picture

AB 747’s documentation requirements aren’t the end of the story — they’re the infrastructure for what comes next.

Public county registries, going live in 2027, will give opposing parties and courts the ability to look up registered servers and their history. GPS-verified documentation isn’t just about proving you knocked on a door. It’s about building a verifiable record across a career.

The servers who treat the new documentation standard as a bureaucratic burden are going to have a hard two years. The servers who treat it as a professional infrastructure upgrade — building systems now, pricing accordingly, training themselves and their staff — are going to find that 2027 is fine.

The standard was always that you had to make real attempts. The difference is that now you have to prove it.


Quick Checklist: What Adaptation Looks Like Right Now

If you’re a California process server getting ahead of AB 747, here’s where your energy should go:

  • Pick one app for GPS-documented attempts and use it on every job, starting today — not in January
  • Plan three-day attempt windows when you accept a case, not when you’re on attempt two
  • Build time-window variety into your routes — at least one attempt outside typical business hours per case
  • Learn to take a legally useful photo — address visible, at the door, good lighting
  • Review your substituted service pricing — three documented attempts has a real cost
  • Have the documentation conversation with your attorneys now — before a proof of service gets challenged

Bottom Line

The process servers who are thriving under the new standard aren’t superhuman. They built systems. The documentation layer AB 747 adds is real — but it’s manageable with the right tools and the right routing habits.

The ones who wait until January 2027 to figure this out are going to have a painful first quarter.


Pete Campbell is a registered process server in Amador County, California, and the founder of Served Wire. He covers AB 747 compliance, legal tech, and the business of process serving.

Served Wire Newsletter

Get this in your inbox every week.

AI tools, compliance updates, and practical tips for process servers and legal pros. Free, always.

[Newsletter signup form — add Beehiiv embed code here]