As we prepare for California's SPARE Act (AB 747) to go into effect on January 1, 2027, ServeManager is releasing a new update for the Mobile App to help process servers comply with the new diligence standards and maintain accurate gps information when creating their attempts.

Click here to read our blog post that outlines California's SPARE Act (AB 747) 

At a glance, here is what is changing for California SPARE act jobs:

Requirements before you accept

• SPARE Act jobs are tagged in the inbox, and the accept screen lists every check the job will be scored on.

A live compliance score on every job

• Each job shows how many checks have passed and what still needs attention, updated as attempts come in.

Guided attempts

• The attempt form flags missing GPS, photo, service type, and description, and will not submit until the gaps are closed or explained.

Affidavit-ready descriptions

• A checklist of what happened at the address becomes a plain written description, with any declared exceptions on the record.

Why this update?

Servers had to know the rules by heart. California's SPARE Act sets specific due-diligence requirements for each attempt: GPS at the address, a photo of the door, the date and time, and a written account of what happened. Nothing in the app said which jobs fell under the act or what each attempt needed.

Gaps surfaced after the attempt was submitted, often when the affidavit was being prepared. By then the server had left the address and the evidence could not be recovered.

Before accepting the job

• Tag in the inbox. SPARE Act jobs carry a clipboard tag next to the due date and status, so they stand out before the job is opened.

 

• Note on the accept screen. The Accept or Decline card includes a compliance note with a "What's checked?" link.
• Requirements sheet. Lists every check the job will be scored on, such as three attempts on different days, an evening attempt, a weekend attempt, GPS near the address, and a photo on each attempt. 

On the job

• Job Compliance card. Checks passed out of total, a percentage, and a progress bar. Yellow until every check passes, then green.

• Full breakdown. Tapping the card opens the list split into Needs attention and Completed. Each row says why it is open, for example "0 of 1 attempt logged" or "No photo on attempt 1".
• Refreshes on every visit. The score is recalculated by the backend each time the job is opened, so the server sees what each attempt changed.

During the attempt 

• Compliance Guidelines at the top of the form. The job's checks with their current state, so the server knows what this attempt needs to cover.
• Each section flags its gap. GPS, uploads, service type, and description show what is missing. A GPS lock far from the address is a yellow warning; missing evidence is a red block.

• Reasons instead of evidence, when justified. No photo: Unsafe, Door not accessible, or Other. No GPS: No signal. Each needs a short written statement. Door not accessible still expects a photo of the entrance.
• Generated description. Picking an unsuccessful outcome opens a checklist (knocked and announced, no answer, vehicle present, spoke with a neighbor). One tap turns it into a plain description with the date and time, which the server can edit.

• Blocked submit with a fix. On submit every check runs. A failing one shows a message naming the check and what to do, and scrolls the form to it.
• Watermarked photos. In-app photos on these jobs carry a GPS and time watermark, and the same data is written into the file for backend checks.

 

Which jobs have these features?

• New attempts only. Editing or retrying a submitted attempt does not re-run the checks.
• Bulk attempts follow the strictest job. If any selected job qualifies, the whole attempt is guided, with guidelines listed per job.
• Successful service is stricter. The photo must be taken where service was effected, the person served must be recorded, and no photo reason is accepted.

Messages / Description

Common questions