The 3-3-3 Rule Is Coming: How to Document Diligent Service Without Killing Your Day

Let me tell you how a lot of process servers currently handle diligent search: they go twice, write “attempted” on a piece of paper, and call it good. Maybe they go a third time if they’re feeling thorough, or if the attorney specifically asked.

That era is ending.

AB 747’s framework — combined with existing California requirements around diligent service for substituted service — is pushing the industry toward what practitioners are calling the 3-3-3 rule: three attempts, three different days, three different times of day. And every attempt needs documented proof: GPS-stamped, timestamped photos.

Here’s how to do it without it eating your schedule alive.

What the Rule Actually Requires

Let me be clear: “3-3-3” is a working standard, not statutory language you’ll find word-for-word in the code. What California law actually requires for substituted service is “reasonable diligence” — meaning you made genuine efforts to personally serve the subject before leaving papers with a competent household member or posting.

Courts have consistently interpreted reasonable diligence to mean:

• Multiple attempts
• At different times of day (not just three trips at 9am)
• On different days (not three trips in one afternoon)

The 3-3-3 framework is the practical standard attorneys and courts are coalescing around: three attempts, spread across at least three different calendar days, at three different time windows (morning, afternoon, evening — or some meaningful variation).

AB 747 adds the documentation layer: each of those attempts now needs GPS-verified photographic proof.

Why Documentation Is the Hard Part

The attempts themselves aren’t new. Most experienced servers were already making multiple trips. The problem is that nobody was documenting them in a way that’s legally defensible under the new standard.

A handwritten note saying “attempted 7/15 at 8am” doesn’t cut it anymore. You need:

• A photo taken at the address at the time of the attempt
• GPS coordinates embedded in the photo metadata
• A timestamp showing the date and time
• Ideally, something that ties the location to the correct address visually

That’s four data points per attempt. Multiply by three attempts and you’re managing twelve pieces of verifiable evidence per serve.

Do this manually and it becomes a records nightmare. The servers who thrive under the new rules will have a system.

Building Your 3-3-3 Workflow

Step 1: Route Smarter, Not Harder

The biggest time drain isn’t the documentation — it’s the driving. Three trips to the same address, scattered across three days, is brutal if you’re not planning around it.

The fix: batch by geography, not by case.

Instead of making three trips to the same address on three different days, cluster all your attempts in a zone and hit multiple addresses per run. You’ll be back in that neighborhood anyway. When you are, knock on that door again.

Most experienced servers already do this intuitively. The discipline is making sure you’re actually hitting three different time windows — not just three trips during your morning route.

Time windows that satisfy courts:

• Morning: 7am–11am
• Midday: 11am–2pm
• Afternoon/Evening: 2pm–8pm

At least one attempt should be outside business hours. People who are being avoided tend to show up in the evenings and on weekends.

Step 2: Use an App That Does the Documentation for You

This is not optional anymore. Doing GPS documentation by hand — taking a photo, emailing it to yourself, logging the coordinates — works but it doesn’t scale and it’s error-prone.

Apps built for process servers handle this automatically:

• ServeManager — integrates attempt logging with photo capture
• ABC Legal 24L — built-in GPS stamping and proof-of-service generation
• ProofServe — designed specifically for AB 747-style documentation
• ServeReferee (in development) — full GPS compliance with affidavit generation

What to look for in any app: automatic GPS embedding (not just a location tag you type in), timestamp that comes from the device clock (not a field you fill in), and export to PDF for the proof of service.

If your current app doesn’t do GPS-embedded photos, start evaluating alternatives now. 2027 is six months away.

Step 3: Take the Right Photo

The photo itself matters. A blurry picture of the sidewalk with nothing identifiable doesn’t prove you were at the right address.

Every attempt photo should show:

• The address number, clearly visible (on the door, mailbox, or curb)
• Enough of the property to identify it (front door, gate, driveway)
• Current conditions (time of day visible in lighting, any notable conditions)

You’re not taking a real estate photo. You’re creating a legal record. Think about what a judge would need to see to believe you were there.

Step 4: Log It Immediately

Don’t wait until you’re back at your desk to log an attempt. Log it at the scene, while the GPS data is fresh and while you remember the details.

Most apps will auto-populate the timestamp and coordinates when you take the photo. Add a brief note: “No answer, lights off, vehicle in driveway” or “Spoke with female occupant, refused to open door.” That context turns a photo into a narrative.

Step 5: Build the Proof of Service as You Go

By the time your third attempt is complete, you should already have 80% of your proof of service written. Attempt 1, attempt 2, attempt 3 — each with date, time, GPS coordinates, and notes.

The final serve (or the substituted service after three failed attempts) just closes it out.

The Efficiency Math

Here’s the honest accounting: the 3-3-3 workflow takes more time per case than the old way. There’s no getting around that.

But it’s worth doing the math. If a contested serve gets thrown out because you can’t document diligence, you eat the drive time and the fee and start over. If a motion to quash succeeds because your attempts were all on the same day, the attorney loses confidence in you.

Done right, the 3-3-3 workflow is insurance. It’s also increasingly what attorneys are requiring in their instructions before the case even comes to you.

Servers who systematize this now will be able to take on more cases, because the documentation runs itself. Servers who don’t will be scrambling to reconstruct attempts from memory when they get their first challenge.

Quick Reference: 3-3-3 Checklist

Before calling a serve diligent, confirm:

• Three separate attempts on three different calendar days
• At least two different time windows covered (morning/afternoon/evening)
• GPS-stamped photo at the address for each attempt
• Brief written note for each attempt (who was seen, conditions, etc.)
• Address visually identifiable in each photo
• All attempt data synced to your case management system

If you can check all six, you have a defensible diligent search.

Bottom Line

The 3-3-3 rule isn’t bureaucratic punishment — it’s the industry standardizing what good servers were already doing. The documentation layer is new, but the discipline isn’t.

Get the right app. Build the routing habit. Take the photo at the door, not from the car. Your proof of service will defend itself.

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.