AB 747 GPS Compliance: What Every California Process Server Needs to Know Before 2027

If you’re a California process server and you haven’t started thinking about AB 747, you’re behind. The clock is running — January 1, 2027 is closer than it feels, and when it hits, the old way of documenting service attempts stops being legally sufficient.

I’ve been in this industry long enough to watch people scramble at the last minute for changes like this. Don’t be that person. Here’s everything you need to know to get ahead of it.

What AB 747 Actually Requires

Assembly Bill 747, signed into California law, amends the requirements for registered process servers under Business and Professions Code Section 22350 et seq. The core mandate is straightforward but the implementation details matter:

Starting January 1, 2027, every service attempt must be documented with a geotagged photograph.

That means each time you go to an address — whether the serve is successful or not — you need a photo that proves where you were and when you were there. Not just a written log entry. Not just your own testimony. A photograph with GPS coordinates and a timestamp embedded in the file itself.

The law doesn’t require a specific device or app. What it requires is that the resulting photo contain:

• GPS coordinates embedded in the image metadata (EXIF data), accurate to a reasonable level of precision
• A timestamp reflecting the date and time the photo was taken
• Location data sufficient to identify the address — this generally means coordinates that resolve to within a street-level radius

There’s no requirement that the coordinates appear as visible text overlaid on the photo, though many process servers (myself included) choose apps or cameras that do this anyway, because it makes the documentation easier to read in court.

What “Embedded in the Photo” Actually Means

This is where I see people get confused, so let’s slow down here.

There are two ways a photo can contain GPS information:

1. Embedded in EXIF metadata — This is data baked into the image file at the moment it’s captured. You can’t see it by looking at the photo, but it’s there when you right-click the file and check properties, or run it through any EXIF viewer. This is what AB 747 is pointing at.

2. Burned into the image as visible text — Apps like Timestamp Camera or GPS Map Camera overlay coordinates and timestamps directly onto the visible image. This is a belt-and-suspenders approach: the data is both visible and (if the app does it right) embedded in the EXIF.

My strong recommendation: use a method that does both. Visible text on the photo makes your proof of service bulletproof in practice — a judge or opposing counsel doesn’t need a forensics tool to verify where and when the photo was taken. They can see it.

Important caveat: If you’re using a smartphone, check that location services are fully enabled for your camera app and that you haven’t accidentally stripped metadata when sharing or uploading the photo. Texting images, certain social media uploads, and some cloud sync tools will scrub EXIF data. Always work from the original file.

What Equipment Qualifies

AB 747 does not mandate specific hardware. Any device that produces a geotagged photograph with a verifiable timestamp meets the technical requirement. In practice, your options are:

Smartphones (most common, most practical)
Modern iPhones and Android devices capture GPS coordinates automatically in EXIF data — if location permissions are granted to the camera app. This is already compliant for basic purposes. The weakness is that smartphone EXIF data can be disputed as easy to manipulate, and the coordinates don’t appear visibly on the photo. A third-party app like Timestamp Camera Pro or GPS Camera Stamp addresses this by burning visible data onto the image.

Dedicated cameras with built-in GPS
Rugged point-and-shoot cameras like the Ricoh WG series have GPS chips built in and automatically tag every shot. These are popular with process servers who want a device separate from their personal phone, with no concerns about location permissions or app settings.

Body cameras
Devices like the Axon Body 3 or Reveal RS3 embed GPS, timestamp, and even video alongside still frames. These are overkill for most routine serves, but if you’re working contested matters or high-conflict cases, the continuous record is genuinely valuable.

What doesn’t qualify:
A photo taken on a device with location services disabled. A screenshot. A photo timestamped after the fact. Any image where you’ve modified or stripped the metadata. Don’t try to game this — the point of the law is chain-of-custody integrity.

Building a Compliant Workflow

Here’s the workflow I’d recommend building now, before the law takes effect. The goal is to make GPS photo capture automatic — not something you have to remember to do.

Step 1: Choose your device and verify GPS capture
Whatever you use, confirm it actually embeds GPS coordinates. Take a test photo and check the EXIF data using a tool like Jeffrey’s Exif Viewer (online), Windows Photo Properties (right-click → Properties → Details), or a mobile app like Exif Metadata. If coordinates aren’t showing up, fix your settings before January 2027.

Step 2: Use an app that burns visible data onto the photo
Timestamp Camera Pro (iPhone/Android) is the most widely used option in this space. GPS Map Camera and similar apps also work. Configure it to display: GPS coordinates, date, time, and address (reverse geocoded from coordinates). This makes your documentation readable at a glance.

Step 3: Standardize your photo subjects
At minimum: photograph the address number on the structure and the surrounding area that confirms you’re at the right location. Some servers photograph the door, the street sign at the nearest intersection, and the vehicle in the driveway if applicable. Develop a consistent checklist and stick to it on every attempt.

Step 4: Name and store files with the job in mind
Rename photos with the case number, date, and attempt number before filing them away. A folder structure like 2026/CaseNumber_Defendant_Attempt1/ keeps things auditable. If you’re ever deposed or subpoenaed for your records, you want to pull them up fast and hand them over clean.

Step 5: Backup immediately
GPS photos are only useful if they’re preserved. Cloud backup (Google Photos, iCloud, or a dedicated service) that retains original metadata is essential. Keep a local copy as well. Losing documentation on a contested serve is a bad day.

What Happens If You’re Non-Compliant

This is where it gets serious.

Failing to comply with AB 747’s documentation requirements doesn’t automatically void a service — at least not in every case. But it creates significant exposure:

Professional discipline: Registered process servers operating under the Business and Professions Code are subject to disciplinary action by the county clerk’s office and the state. Non-compliance with documentation requirements is grounds for suspension or revocation of registration.

Challenged proofs of service: Defense attorneys already look for any procedural defect to attack a proof of service. After January 1, 2027, a missing GPS-verified photo becomes an immediate target. If a proof of service is set aside, you may be looking at repeated service costs, court sanctions against your client, and damage to your professional reputation.

Liability exposure: If a case fails or is delayed because your documentation doesn’t meet the new standard, expect a conversation with your E&O carrier — and possibly your client’s attorney.

The simple version: The cost of non-compliance is much higher than the cost of updating your workflow now.

The January 1, 2027 Deadline

You have time, but not much. Six months goes fast when you’re running 30 serves a week. The smart move is to start your compliant workflow now — run it in parallel with your existing documentation until the law takes effect. By the time the deadline hits, it’ll be second nature.

Use this window to:

• Audit your current equipment and settings
• Pick an app or camera that meets the technical standard
• Train any employees or subcontractors you work with
• Update your proof of service templates to reference GPS photo documentation
• Check with your professional association (CAPPS, local county groups) for any guidance or training sessions they’re running

California has been moving toward more rigorous documentation standards for years. AB 747 is a step in that direction, and it won’t be the last one. Building a clean, auditable digital documentation practice now positions you well for whatever comes next.

The Bottom Line

AB 747 isn’t complicated. Take a geotagged photo on every attempt, make sure the metadata is there, keep the files, and you’re compliant. The technology already exists in the phone in your pocket — it’s mostly a matter of turning it on correctly and building the habit.

If you wait until December 2026 to figure this out, you’ll be scrambling. Start now, document everything, and be the process server who can hand over airtight records when it matters.

Have questions about AB 747 compliance or process serving technology? Drop them in the comments or reach out directly.

Want weekly updates on process serving compliance and AI tools? Subscribe to Served Wire — free.
→ servedwire.com/subscribe