What a Process Serving SLA Should Do

An SLA should answer four questions for every material stage of the assignment:

1. What must happen?
2. Who owns the action?
3. When must it happen?
4. What happens if the normal workflow cannot continue?

For example, “routine service includes up to four attempts” is a pricing statement. It does not define an operating standard. A useful provision would also state when the assignment becomes active, when the first attempt should occur, whether timing should vary, what a report must include, when another attempt should be scheduled, and which observations require escalation before additional fees are incurred.

The distinction matters because the number of attempts alone does not show whether an assignment was managed well. Three identical visits to an apparently vacant property may consume the included attempt count without moving the case forward. Two well-planned attempts supported by address verification, varied timing, and a clear workplace lead may create far more value.

The SLA should therefore focus on process quality, decision points, and visibility, not only attempt quantity.

An SLA Is Not a Guarantee of Service

A process serving company controls its intake, dispatch, communication, documentation, escalation, proof preparation, and billing practices. It does not control whether a person is home, whether a workplace grants access, whether an address is current, or whether a recipient changes a routine.

The agreement should avoid promising a universal success rate or guaranteed completion by a date when completion depends on third-party conduct. It can require a provider to begin within a defined period, follow an approved strategy, report promptly, and alert the firm when the remaining timeline becomes unrealistic.

That is a meaningful service level because it measures the management of the assignment, not an outcome the vendor cannot fully control.

What the Firm Should Define Before Writing the SLA

The firm should begin with its own workflow. A vendor cannot consistently meet an expectation the firm has not clearly identified.

Legal operations and litigation teams should map:

• the case types and documents most frequently assigned;
• the counties, states, or jurisdictions involved;
• average and peak monthly assignment volume;
• the percentage of routine, rush, difficult, and multi-address matters;
• the people authorized to submit and change assignments;
• the case-management or billing identifiers required;
• the firm’s internal deadline ownership;
• the preferred update recipients and communication channels;
• the required Proof of Service delivery and filing workflow;
• the information the firm can provide about recipients, schedules, vehicles, and alternate addresses;
• the approvals required for additional attempts, skip tracing, stakeouts, printing, mailing, or filing.

This review often reveals that several “vendor problems” begin upstream. A deadline may arrive only in the body of an email. A paralegal may assume that “rush” means same-day first attempt, while the vendor treats it as dispatch within two business days. A vendor may wait for cost approval while the firm assumes the next attempt is automatic.

The SLA should close those gaps on both sides. It should state what the firm must submit and what the provider must confirm.

Define Scope, Geographic Coverage, and Priority Levels

The agreement should clearly identify the services included. Depending on the relationship, the scope may cover managed process serving, printing, mailing, skip tracing, stakeouts, courthouse filing, document retrieval, witness fees, electronic service, and return of originals.

Geographic coverage should be described operationally. “Statewide coverage” may mean the provider coordinates assignments throughout California, but different counties may still have different availability, mileage, remote-area surcharges, or first-attempt windows. The SLA should explain how the provider handles areas outside its ordinary field network and whether the same reporting and proof standards apply to subcontracted or affiliate servers.

Create Clear Priority Tiers

Terms such as routine, priority, rush, and same day should have defined meanings. A sample structure might look like this:

The final timelines should reflect the provider’s actual network, local geography, cutoff times, weekends, holidays, and safety requirements. The important point is that each term has one shared definition.

A rush service clause should also state whether the provider can decline or condition an assignment when the requested timeline is not realistic. Early candor is more valuable than accepting a job that cannot be performed responsibly.

Set Standards for Intake Review and Assignment Activation

The SLA clock should not begin with an ambiguous email. It should begin at a defined activation event.

Activation may occur when the provider has received and verified:

• readable, complete documents;
• the court and case number;
• the correct legal name of each recipient;
• the service address and any unit or suite number;
• the requested service method or instruction to request clarification;
• the hearing date, service deadline, and any earlier internal target;
• known recipient information relevant to timing or identification;
• billing and matter codes;
• authorization for the selected service level.

The provider should acknowledge receipt within a stated period and distinguish among three statuses:

1. Received: the transmission reached the provider.
2. Needs information: the provider identified a missing or unclear item.
3. Activated: the assignment is accepted and ready for operational work.

This distinction prevents a dangerous misunderstanding in which the firm believes an assignment is underway because an email was delivered, while the provider is waiting for a corrected summons, service address, fee approval, or clarification.

Document Review Should Be Defined, Not Assumed

The SLA should state the provider’s operational review. That review may confirm file readability, page count, party name consistency, obvious form omissions, recipient count, known mailing steps, and special instructions. It should also state what the review does not include.

A process serving provider is not a substitute for counsel’s legal analysis. Counsel remains responsible for determining the controlling deadline, legally permitted method, documents to be served, and case-specific requirements unless another allocation is expressly and lawfully agreed. The provider’s role is to identify operational gaps and apparent inconsistencies before dispatch.

Put Deadline Control Inside the Assignment

A deadline should not remain only in one employee’s calendar or in a sentence buried in an email. The SLA should require deadline data to be entered into the assignment record and visible to the people managing the case.

The provider should record separately:

• the hearing or event date;
• the client-provided last date for service;
• the firm’s preferred completion date;
• any filing deadline for the Proof of Service;
• internal escalation dates;
• the source of the deadline information.

The agreement should avoid making the vendor the silent calculator of every legal deadline. A strong workflow allows the vendor to flag apparent inconsistencies, but counsel should provide or confirm the controlling date.

Require a Feasibility Review

When an assignment arrives close to a deadline, the provider should evaluate whether the requested plan is operationally realistic. The review may consider address confidence, travel distance, document type, required method, available attempt windows, recipient schedule, access barriers, and whether a follow-up mailing or filing step is expected.

If the timeline appears unrealistic, the SLA should require prompt notice. The provider should not accept a routine job on Monday, wait until Thursday to dispatch it, and then explain on Friday that the deadline was too short.

The notice should tell the firm what can still be done, what information could improve the plan, what additional service level may be required, and which legal decision remains with counsel.

Define First-Attempt Timing Precisely

“We will start promptly” is not an SLA. The agreement should define the first-attempt target by priority level and state when the clock begins.

The target should also account for time-of-day strategy. Dispatching a residential assignment within 24 hours is not automatically useful if the attempt is made at 1:30 PM despite reliable information that the subject works weekdays until 6:00 PM.

A strong first-attempt standard has two parts:

• speed: the assignment reaches the field within the defined period;
• reasonableness: the attempt window reflects the known facts when practical.

The SLA should state whether weekends and evenings are included, available as an upgrade, or scheduled based on case strategy. It should also identify exceptions such as severe weather, unsafe conditions, building closures, remote travel, or a client-requested hold.

For deadline-sensitive matters, the SLA may require the operations team to confirm the planned first-attempt window rather than merely marking the assignment “dispatched.”

Measure Attempt Quality, Not Only Attempt Count

An attempt should produce a documented field result that helps determine what happens next. The SLA should define the minimum information required after every visit.

A structured report should generally include:

• the date and exact time;
• the complete location attempted;
• the result of the visit;
• how the server attempted contact;
• access conditions such as a gate, callbox, security desk, or locked entrance;
• objective signs relevant to occupancy or business activity;
• contact with residents, neighbors, employees, managers, receptionists, or security;
• what the contacted person stated, without converting the statement into an unsupported conclusion;
• identity information or recipient capacity when service was completed;
• the recommended operational next step or escalation flag.

“No answer” may be the result, but it should not be the entire report. The firm needs to know whether the server reached the correct unit, whether access prevented a door attempt, whether vehicles or lights were present, whether the location appeared vacant, and whether another timing window is likely to be more useful.

Require Objective Language

The SLA should prohibit speculative or inflammatory reporting. One unanswered door does not prove evasion. A receptionist who does not recognize a name does not necessarily establish that the address is wrong. A vehicle in the driveway does not prove the subject was inside.

Reports should distinguish observations, third-party statements, and operational conclusions. This improves client decision-making and creates a more reliable record if the attempt history later supports a diligence declaration or another court request.

Build Status Updates Into the Workflow

A paralegal should not need to send repeated messages asking whether the assignment was received, whether the first attempt happened, or when the proof will be ready.

The SLA should identify which events trigger an update and how quickly the update must be delivered. Common trigger events include:

• assignment received;
• missing information identified;
• assignment activated;
• first attempt scheduled or dispatched;
• attempt completed;
• address concern identified;
• additional authorization required;
• service completed;
• required mailing completed;
• proof under review;
• proof delivered;
• filing submitted, accepted, or rejected;
• assignment closed.

The agreement should state whether updates are delivered by portal, email, system integration, or another channel. It should also identify urgent exceptions that require direct human communication, such as a questionable address, a safety issue, an approaching deadline, conflicting client instructions, or a service event requiring immediate factual clarification.

Automation may send routine milestones, but it should not replace an accountable operations contact. The system can trigger the communication. A person must still own the case when judgment is required.

Define Escalation Rules After Unsuccessful Attempts

Many assignments lose time because nobody is required to reassess them. The server makes an attempt, enters a brief result, and places the job back into a queue. The next visit repeats the same timing or address problem.

The SLA should identify conditions that stop automatic repetition and trigger operations review. Examples include:

• two attempts with no meaningful variation in timing;
• a statement that the subject moved;
• an apparently vacant or nonexistent location;
• an incorrect or missing apartment or suite number;
• repeated inability to pass a controlled entrance;
• reliable information about a work schedule or alternate address;
• observations suggesting a different attempt window;
• a remaining deadline too short for the routine plan;
• a developing safety concern;
• a pattern that may justify a difficult-service strategy.

The escalation should produce a decision, not merely a notification. The operations team may recommend a morning or evening visit, workplace attempt, address verification, client request for additional details, additional fee approval, stakeout, or attorney review of another lawful method.

The SLA should define who can authorize each next step and how long the provider will wait for an answer before sending a reminder or marking the assignment on hold. This prevents an urgent case from silently stopping in an approval queue.

Create a Specific Workflow for Address Problems

An address problem can consume days when the provider continues attempting without assessing what the field information means.

The SLA should distinguish among:

• unconfirmed address: no reliable information yet connects or disconnects the subject;
• access problem: the address may be correct, but the server cannot reach the unit or office;
• incomplete address: a unit, suite, building, or other locator is missing;
• apparently stale address: objective observations or reliable statements suggest the subject moved;
• invalid address: the location, unit, or business does not exist as provided;
• alternate lead available: another residence, workplace, or known location may be more productive.

The client update should explain which category applies and what supports it. The provider should not simply change the status to “bad address” without giving the firm enough information to evaluate the conclusion.

The agreement should also state when the provider may recommend skip tracing and address verification, what information the search may use, what approval is required, and how new leads will be documented. Locate data should be treated as a lead requiring evaluation, not an automatic guarantee that the person currently resides at the result address.

Control the Proof of Service Workflow

Service completion is not the end of the assignment. The formal documentation must accurately reflect what occurred.

For specified summons service within California, Code of Civil Procedure section 417.10 requires an affidavit showing the time, place, manner, and facts demonstrating service in accordance with the governing chapter. Depending on the circumstances, the proof may also need the recipient’s name, title, or capacity. These requirements illustrate why field data, mailing records, and proof preparation should remain connected.

The SLA should define:

• which party selects or supplies the Proof of Service form;
• when the provider prepares the proof;
• the standard turnaround after all required service steps are complete;
• how the proof is compared with field notes and case data;
• how names, documents, date, time, location, method, and recipient capacity are checked;
• how required mailing information is captured;
• who signs the declaration;
• how corrections are requested and tracked;
• whether an original, electronic copy, or both will be delivered;
• which matters require attorney approval before filing.

The proof should not be finalized from an expected result before service occurs. Basic caption data may be prefilled, but the service facts must come from the completed event.

Plan for Legal and Form Changes

An SLA that extends across calendar years should include a change-management clause. As of September 2026, the current version of California Code of Civil Procedure section 417.10 remains operative through December 31, 2026. A later version scheduled to become operative on January 1, 2027 adds specified photograph and readable date, time, and location-stamp requirements for certain effected and attempted summons service, with stated exceptions and explanation requirements.

The agreement should require the provider and firm to review applicable workflow, technology, form, retention, and privacy changes before the operative date. It should not describe a future statutory requirement as if it already governed every California assignment in 2026.

Separate Proof Delivery From Filing Responsibility

Preparing a proof, sending it to the law firm, submitting it to the court, and confirming acceptance are separate events.

California Code of Civil Procedure section 417.30 provides that proof of summons service shall be filed after service unless the defendant has previously made a general appearance. The operational agreement should identify who performs that filing and how the result is confirmed. It should not leave the task to assumption.

If the provider files, the SLA should state:

• which courts and case types are included;
• what filing instructions the firm must provide;
• the submission target after proof approval;
• how filing fees and rejection fees are handled;
• how a rejection is reported and escalated;
• whether the provider corrects only clerical issues or returns substantive questions to counsel;
• how the accepted or court-stamped copy is delivered and retained.

If the firm files, the case-closure notice should say that the proof was delivered but not filed by the provider. Clear language prevents “proof complete” from being interpreted as “court filing accepted.”

Make Billing and Change Authorization Predictable

A process serving SLA should connect operational scope to billing. The firm should know what the base fee includes and which events require additional authorization.

The pricing schedule should address:

• included attempt count or service period;
• printing, page, color, and assembly charges;
• mileage, remote-area, parking, toll, or access fees;
• evening, weekend, holiday, priority, and same-day charges;
• mailing and postage;
• witness fees;
• skip tracing or database research;
• stakeout minimums and increments;
• courthouse filing and advance fees;
• cancellation, hold, and rescheduling terms;
• fees for additional addresses or recipients;
• invoice timing, matter coding, and backup documentation.

The agreement should define an approval threshold. Routine work may proceed automatically within the authorized package, while out-of-scope expenses above a stated amount require approval from designated firm contacts.

It should also explain what happens when time does not permit waiting. For example, the firm may preauthorize a limited rush amount for specified case types or require an immediate escalation call. The answer should be chosen before the emergency occurs.

Address Technology, Records, and Information Security

Process serving assignments may contain pleadings, addresses, contact data, photographs, schedules, vehicle information, declarations, and other sensitive case material. The SLA should identify how the provider receives, stores, limits access to, and transmits that information.

Relevant questions include:

• Does each assignment have one structured history?
• Can the firm control who receives status updates?
• Are field notes timestamped and associated with the correct case?
• Can the provider prevent dispatch when required information is missing?
• Are changes to addresses, deadlines, and instructions traceable?
• Can client data be exported at the end of the relationship?
• What retention period applies to field notes, proofs, photographs, and communications?
• How are security incidents communicated?
• Which subcontractors or field professionals can access case data?

A centralized assignment workflow can support consistent timestamps, status triggers, record history, and proof preparation. Technology should reinforce accountability. It should not hide who made a decision or why an assignment stopped.

Choose Metrics the Provider Can Explain

The SLA should include a small set of metrics tied to the firm’s actual risk and workload. More dashboards do not automatically create more control.

Useful measurements may include:

• assignment acknowledgment time;
• percentage of assignments activated without avoidable rework;
• first-attempt timeliness by priority level;
• same-day reporting rate after field activity;
• percentage of failed attempts containing required report fields;
• deadline-risk escalations sent within the required window;
• Proof of Service turnaround after completion of all required steps;
• proof correction rate and reason category;
• invoice accuracy;
• response time for urgent client questions;
• court-filing rejection rate when filing is within scope;
• open assignments with no activity beyond the permitted interval.

Success rate should be interpreted carefully. A provider handling cooperative corporate defendants is not directly comparable to one handling stale addresses and evasive subjects. Metrics should be segmented by service level, matter type, geography, address confidence, and difficulty when possible.

Define Review Cadence and Corrective Action

The agreement should state how often the parties review performance. High-volume firms may use monthly operational reviews and quarterly business reviews. Smaller programs may review quarterly or after a defined number of assignments.

Not every missed target requires a financial penalty. A useful corrective process may include:

1. identify the missed metric and affected assignments;
2. separate isolated exceptions from recurring patterns;
3. determine whether the cause began with the firm, provider, field conditions, or a third party;
4. assign a corrective action and owner;
5. set a review date;
6. apply a credit, remediation plan, or termination right for defined material or repeated failures.

The SLA should also preserve reasonable exceptions. A wildfire closure, unsafe confrontation, sudden court outage, inaccurate client address, or recipient hospitalization should not be treated the same as an assignment that sat unreviewed in a vendor queue.

Sample Process Serving SLA Scorecard

The exact standards should be negotiated for the firm’s caseload and the provider’s verified capabilities. The following framework shows how expectations can be written without promising a result outside the provider’s control.

How to Implement a Process Serving SLA Without Creating Bureaucracy

The best SLA is short enough to use and specific enough to enforce. A 40-page agreement that nobody connects to daily operations will not improve service.

1. Start With the Highest-Risk Gaps

Review recent assignments that created extra work. Look for late starts, unflagged deadlines, vague reports, repeated attempts, address delays, missing mailing records, proof corrections, filing assumptions, and invoice disputes. These failures show which standards need the greatest precision.

2. Build a Responsibility Matrix

For each major step, name the law firm owner, provider owner, required input, target time, and escalation contact. Avoid shared responsibility without a final accountable person.

3. Test the SLA Against Real Scenarios

Run the proposed terms through at least five assignments:

• a routine residential summons with adequate time;
• a next-day restraining order service;
• a corporation with a questionable service address;
• a subject with irregular work hours and two possible locations;
• a successful substituted-service event involving a follow-up mailing and filing request.

If the agreement does not tell the team what happens next in each scenario, it needs revision.

4. Pilot Before Firmwide Rollout

Use a limited set of matters, offices, or practice groups. Measure acknowledgment, activation, attempt timing, reporting, escalation, proof turnaround, correction rate, and administrative follow-up. Adjust targets that are ambiguous or operationally unrealistic.

5. Connect the SLA to Intake and Reporting

Required fields should appear in the submission process. Escalation rules should create actual alerts. Report standards should be reflected in the field form. Proof turnaround should begin from a defined completion event. If the SLA exists separately from the operating system, people will revert to memory and email.

6. Review the Agreement When Law or Volume Changes

Revisit the SLA when the firm enters a new jurisdiction, changes practice mix, significantly increases volume, adopts a new case-management system, or encounters new statutory, form, or court requirements. A current operating agreement is more valuable than a polished document that describes last year’s workflow.

Common SLA Mistakes Law Firms Should Avoid

• Measuring only successful service: this ignores case difficulty and encourages oversimplified comparisons.
• Defining attempt count but not timing or reporting: quantity does not establish quality.
• Starting the clock before intake is complete: this creates disputes about whether the provider had enough information to act.
• Using “rush” without a cutoff or first-attempt definition: both sides may interpret the same word differently.
• Leaving deadline ownership unclear: the provider should record and flag deadlines, while counsel confirms controlling legal dates.
• Ignoring failed-attempt escalation: assignments can repeat unproductive activity until time expires.
• Combining proof delivery and filing: one does not necessarily confirm the other.
• Applying one standard to every county: geography and field availability may require disclosed variations.
• Setting targets the provider cannot actually meet: an ambitious promise is not useful if it produces routine exceptions.
• Failing to define firm responsibilities: missing documents, late approvals, and incomplete addresses must be part of the workflow.

What a Managed Process Serving Relationship Looks Like

In a transaction-only model, the law firm sends documents, a server makes visits, and the firm receives a result. Each problem creates another email and another manual decision.

In a managed relationship, the assignment has an owner and a lifecycle. Intake is checked. The deadline is visible. The first attempt is planned. Field information is structured. Failed attempts create decisions. Address concerns are identified early. Required follow-up steps stay open until completed. The proof is compared with the service record. Filing responsibility is explicit. Performance can be reviewed across all matters.

The SLA is the written expression of that model. It gives the law firm a consistent standard even when different field professionals work in different California counties.

How Proofser Supports Defined Service Standards

Proofser coordinates process serving for law firms through centralized intake, case oversight, structured field reporting, escalation, proof preparation, and statewide operational coordination.

A service-level framework can define how assignments are accepted, prioritized, dispatched, documented, reviewed, and closed. It can also identify the events that require client input, a different attempt window, address research, a difficult-service plan, mailing, proof review, or filing support.

The purpose is not to force every case into an identical pattern. It is to make sure that exceptions become visible and managed. A routine serve can move efficiently. A questionable address can stop before several days are lost. A rush assignment can receive early feasibility review. A completed service can stay open until its required documentation is ready.

For multi-office, recurring, and statewide assignments, one operations contact and one reporting standard can reduce the administrative work created by fragmented county-by-county vendor management.